George Agapov

If this works, the blockchain disappears into the background. What users see is seamless capital across systems. What's still to be determined — who controls the rails that make that possible.

The most interesting institutional theme at @TheAgora_Event wasn't DeFi yields or RWA hype — it was collateral mobility. Quietly becoming one of the most important shifts in crypto infra🧵

Lending protocols like Aave and Morpho are part of this picture too. Increasingly seen as system-facing infrastructure, not just yield products.

Blockchain rails make reuse possible across systems that previously couldn't talk to each other. DTCC is already exploring Canton-based collateral to assist settlement. And with RWAs maturing, using tokenized assets as collateral for trades seems increasingly within reach.

The idea is simple: collateral locked in one system can't work in another. Fragmentation has a real cost — in capital efficiency, in missed trades, in idle liquidity.

@ConsensysAudits dinner was truly outstanding. Deep conversations all evening — loved talking to @KotyaSec (audits are poetry in his parlance, and the enthusiasm is contagious), @mmagician, @xenowits, @Didier_Le_Floch, @ndigitalasset, @nicht_tintin and others. Real pleasure.

Spent last week at EthCC in Cannes. One of those events where you leave with a full notebook and an even fuller contact list. 🧵

@GSR_io Soiree was a fantastic side event. DeFi practitioners, traders, investors all in one room. Great conversations, many follow-ups to happen.

Conversations on the floor matched the quality of the panels. Hard to find someone you wouldn't learn something from in a 5-minute chat.

My favorite part was @TheAgora_Event conference by @KaikoData. Panels assembled with real taste — many of them so good I kept losing track of time.

A quote from EthCC 2026 that stayed with me

At that same dinner 🍽️, I had the pleasure to meet @just_georgeee working on @minaprotocol. Cool to see them exploring applications of recursive ZK and constant-sized proofs beyond blockchain - we all know the tech has legs outside of crypto and they are actively exploring it

@frankencoinzchf @chain_security Ossau-Iraty

Tonight, we'll have cheese with our friends from @chain_security. Want some as well? Comment about your favourite cheese as and win a spot for tonight!

Just wrapped up day one at ETHCC! Great to talk to business leaders about the institutional adoption of blockchain technology. Still around tomorrow, DM if you want to talk about ZK and Mina!

@AlexRdgzG @merzsp Congratulations! Quick question, perhaps a naive one: is the original Poseidon affected as well, or is the risk specific to Poseidon2(b)?

📃New article with @merzsp ! We present new algebraic techniques to attack the Poseidon2 and Poseidon2b 🧜🔱 hash functions. This is a class on 'Skipping Class', and how to make 15000$ in one day. 💸 (1/12)

@garethtdavies @MinaProtocol This limit exists because consistent blocks full of large zkApps would push RAM consumption beyond what we currently recommend for node operators. After the hardfork, we'll deliver further RAM optimizations, and the limit will be safely removed.

@just_georgeee @MinaProtocol So the limit isn’t part of consensus? After the release older nodes would see a block with say 14 zkApp tx as valid?

The road to Mesa continues. Read more about the progress in our latest blog post here: minaprotocol.com/blog/road-to-m…

@garethtdavies @MinaProtocol Correct. It's called a "zkApp soft limit" because it's self-imposed by block producers. Anyone can create a block with >12 zkApps and it will be valid. One oversized block isn't a problem. The issue arises only when the majority of block producers consistently exceed the limit.

@garethtdavies @MinaProtocol The biggest blocker was RAM usage. Tying limit removal to the hard fork would've delayed everything. Better to ship the foundation now, then remove the limit quickly in a regular release after.

@garethtdavies @MinaProtocol Surely not. No hard fork needed to remove the limit—just a regular release. We considered doing it before this hard fork, but it wasn't cleanly doable without foundational work from github.com/MinaProtocol/m…, which enables removing the limit safely post-fork.

@garethtdavies @MinaProtocol The 12 zkApp limit isn't permanent. We scoped the hard fork to ship safely after seeing some issues in stress tests. RAM and networking improvements are already being drafted and will come in regular releases after the hardfork. Better to ship now and iterate quickly after.

@MinaProtocol This is an incredibly disappointing update. MIP6 was stated to remove the 24 zkApp soft limit, and now, after all this time, we are actually going to halve the existing limit! (I appreciate that we can do more with them).