Izzy

Chief of Staking at @LidoFinance

[Izzy @IsdrsP]

2025 has been a triumphant year for @LidoFinance, which has broken new ground in both DeFi and TradFi. Lido v3, launching soon, will transform Lido from a “one size fits most” solution into one that offers customizable staking solutions for any need.

[Felix Lutsch @FelixLts]

Yesterday, we've announced Liquid Lane - a vault-based RFQ solution going to market with RWAs.

LL provides an alternative solution for issuers to idle buffers and DEX/AMM liquidity. This research piece goes deep into the structural benefits incl. analytics on capital efficiency

[Zodiac @zodiaceco]

Community Notice: Zodiac Roles Modifier v2 and Delay Modifier v1.1.0 — Security Update

We identified a vulnerability in two Zodiac modules: Roles Modifier v2 and Delay Modifier v1.1.0. It affects only accounts where one of these modules is enabled AND a Safe account with a vulnerable fallback handler is itself assigned as a module or role member to the affected module.

Safe smart contracts, Safe{Wallet} infrastructure & UI are not affected.
Other Zodiac modules and setups are also not affected.

We've been working directly with affected users since identifying the issue. Over 95% of identifiable accounts have already resolved it.

If you have either module enabled and have not yet acted, check your account and follow the steps: https://t.co/1wWBSPehT7

We apologize for the disruption and concern this incident has caused. Our team is working as quickly as we can to support affected users and help wherever possible.

A full post-mortem will follow.

If you have any questions, reach us at [email protected]

[Linea.eth @LineaBuild]

Curious about Lineth?

Join us for an overview and use case session with the team on @lfdecentralized’s Discord.

June 10, 2026: 6am PT / 9am ET / 3pm CET
Register: https://t.co/POp2Sa3ySa

[Gnosis Pay 🦉💳 @gnosispay]

An update on the Gnosis Pay incident. As of now, the issue is fully contained.

We expect to begin enabling operations in batches on Wednesday evening (GMT+2), with the goal of restoring normal card usage progressively after that. 🧵

[Justin Drake @drakefjustin]

Today a crazy quantum story just got wilder.

On March 31, the Google Quantum AI team published a landmark result on Shor's algorithm for elliptic curve cryptography. Technically, the paper was a bombshell: a dramatic 10x improvement over the state-of-the-art. As a stunt and wakeup call to the blockchain space, those optimisations were illustrated on secp256k1, the elliptic curve underlying Bitcoin and Ethereum signatures.

But perhaps the most striking part of the paper was sociological, not technical. Instead of following standard academic process, the optimisations were kept secret, hidden behind a zero-knowledge (ZK) proof. Google's accompanying blog post mentions they "engaged with the U.S. government". The ZK proof demonstrates the existence of algorithmic improvements without leaking details. Academic censorship with ZK, a historic first!

As a co-author of the Google paper I witnessed some of the context surrounding this censorship. To be honest, multiple aspects of that context don't sit well with me. As much as I believe the general public ought to know more, I am limited in my ability to whistleblow. Though let me be clear about one thing: the Google team's professionalism has been absolutely exemplary, and they deserve nothing but praise.

Censorship has a way of backfiring. The Streisand effect, where an attempt to bury something only draws more attention to it, is exactly what's unfolding today. First, Google's key optimisation has been rediscovered by the French. And in a thrilling turn of events, a collaborative Shor-at-home challenge just launched. The initiative, available at ecdsa[.]fail, breached a new Shor world record in a matter of hours.

Let's start with the rediscovery. Just two months after Google's paper, French quantum expert André Schrottenloher cracks the main secret optimisation. His paper, titled "Optimized Point Addition Circuits for Elliptic Curve Discrete Logarithms", landed on the arXiv today. Big congrats to André, who beat several other nerdsnipped experts to it. In a blog post also published today, Craig Gidney, the world expert on Shor optimisations, revealed that he'd been sitting on this very optimisation for a whole year under censorship pressure.

Interestingly, André missed a handful of minor optimisations, both from Google's original publication and from improvements found since. It's plausible there's still plenty of juice left to squeeze out of Shor, and this is exactly what the ecdsa[.]fail challenge is about. The verifier program developed for the ZK proof does double duty, automatically filtering for valid submissions. Dozens of compounding small and micro improvements are rolling in. As of the time of writing there's an 8.4% improvement to Google's circuit, as measured by the product of logical qubit count and Toffoli gate count. Nice!

The nerdsnipping ran deeper than anyone expected. Over the last few weeks it became clear it extended well beyond André and other quantum experts. Behind the scenes, a small army of amateurs quietly got to work. Inspired by Karpathy-style autoresearch, they turned AI on Shor. Ironically, the verifier program for the ZK proof makes an ideal reward function for AIs. The barrier to entry for this modern style of research is refreshingly low, with several non-experts, even a teenager, finding nice optimisations. Get in touch if you'd like to join a Telegram group with fellow autoresearchers :)

Part 2: neutral atoms and qday

The story doesn't end with Google. On the same day Google went public, a stealthy startup called Oratomic published its own Shor paper in a coordinated release. It made a splash, ultimately becoming the most upvoted paper on scirate[.]com, a website ranking arXiv papers.

Oratomic's claim was wild. By building on Google's logical optimisations and applying custom physical optimisations for neutral atoms, they claimed just 10K physical qubits were sufficient to run Shor's algorithm on secp256k1. That number is mind-bogglingly low.

Knowing essentially nothing about neutral atoms when Oratomic's paper landed, I was intrigued and decided to learn more about the tech. I fell straight down the rabbit hole and spent a couple hundred hours on the topic. I got a little obsessed and watched every YouTube video I could find and spoke to a bunch of experts.

My conclusion? The tech is real, very real. Even Google recently decided to start a neutral atom lab, a notable pivot from their sole focus on superconducting qubits. If you care about qday, i.e. the day a quantum computer will break the first piece of cryptography in production, neutral atoms demand your attention. I shared some of my learnings on Shor and neutral atoms in a 30min talk at the ZKProof cryptography conference. You can find it on YouTube by searching "zkproof neutral atom".

Here's an interesting observation about this duo of breakthrough papers: neither Google nor Oratomic say a word about what their results mean for qday. No timelines. Zero. Nada. That is especially baffling given that the whole point of whitehat quantum cryptanalysis is to inform qday estimations and help the general public make good decisions.

So let me attempt to partially fill the silence, similarly to what Scott Aaronson did in his April 29 post. Given everything I know, including scary non-public information, I now put the odds of qday by 2032 at 50%. 10% by 2030.

Anecdotally, the US government has its own date: 2035. Originating at the NSA and later adopted by NIST, it's when branches of the US government will be disallowed from using quantum-vulnerable cryptography. In plain language: with hindsight, that date is a joke and should be discounted entirely. I don't see how NIST avoids being forced to pull it forward by years.

Part 3: post-quantum cryptography

There are good reasons to sound the alarm today, but please do not panic. Rushing carelessly towards immature post-quantum cryptography is a recipe for disaster. IMO a good target date for migration is 2029, roughly 3.5 years out. 2029 happens to be the date selected by Google, Cloudflare, and the Ethereum Foundation.

These days most of my time goes to safely migrating Ethereum towards post-quantum cryptography as part of the broader lean Ethereum effort. There's a lot to do. We need to rip out and replace BLS signatures at the consensus layer, KZG commitments at the data layer, and ECDSA signatures at the execution layer.

The plan to get there is compelling, and is based on hash-based cryptography. Within the Ethereum Foundation we've developed a Swiss army knife called leanVM (github[.]com/leanEthereum/leanVM) powered by the magic of hash-based SNARKs. Thanks to truly exceptional work by Emile, Thomas, and others, its performance is derisked. Regarding security, leanVM is a jewel, a minimal zkVM crafted for end-to-end formal verification and maximum security.

Want to help? There are two $1M initiatives. First, the Proximity Prize (proximityprize[.]org). Solve a long-standing mathematical conjecture in coding theory, improve hash-based SNARKs, and go home a millionaire. Second, the Poseidon Initiative (poseidon-initiative[.]info), offers $1M for breaking Poseidon, the SNARK-friendly hash function.

[Lido @LidoFinance]

https://t.co/ijyb0llvkz

[Gnosis Pay 🦉💳 @gnosispay]

A bug related to the @gnosispay delay module has been discovered. We are investigating & will share updates as soon as possible.

If you are able to withdraw funds from the Gnosis Pay card to your wallet, we strongly recommend that you do that.

Affected users will be reimbursed.

[Guillermo del Toro @RealGDT]

If I may- in my estimation- #WidowsBay may very well be the best streaming series in a long time… and hands down one of the most mesmerizing acts of narrative prestidigitation in Horror.

[Aave @aave]

https://t.co/ixfuSrVKA8

[Lido @LidoFinance]

stETH & LDO holders are eligible for the 'cSSV Syndicate Boost', with up to +20% added boost on their SSV staking rewards.

↓

[Lido @LidoFinance]

Powered by stVaults.

stVaults are now supported by @CactusCustody, the digital asset custody arm of @BITofficial_EN.

Clients can create & manage stVaults via Cactus Link: Choose validators, fees & MEV routing with on-demand liquidity via stETH minting.

https://t.co/UVOUY9km68

[Teddy @WarnerTeddy]

i mounted a tiny microphone on my apartment balcony to listen for any birds passing by and built a site to collage them as they're heard

[Lido @LidoFinance]

Across derivatives markets, collateral efficiency matters.

In a clip from our recent Lido Poolside call, Griffin Sears from @FalconXGlobal explains how liquid staked assets like Lido's stETH can support derivatives and leveraged strategies while reducing balance sheet drag.

Watch the full discussion here: https://t.co/w61Rd9lkVU

[cyber•Fund @cyberfund]

https://t.co/lSWbeaS69c

[Lido @LidoFinance]

Security Stance

This year's wave of DeFi exploits has repriced security, where Lido has been putting in the work for years.

• Zero staking user funds lost in protocol history.
• 100+ audits: one of the most audited protocols in DeFi.
• Seven layers of defence for safety of users.

[Lido @LidoFinance]

RECAP: Lido Tokenholder Update, May 2026

• Current Market Conditions
• Q1 Financials & Profitability
• KelpDAO Exploit Impact
• Tokenholder Alignment Progress & Buybacks
• Security Stance
• Next Steps

↓

[Lido @LidoFinance]

1 hour till the Lido Tokenholder Update!

Tune in for insights into the latest Lido protocol updates, Ethereum staking developments, and a look at what's next.

Follow along here:
https://t.co/YAeS2cuMw1

[Lido @LidoFinance]

Kelp Incident Review: EarnETH Exposure, Response, and Risk Framework Changes

https://t.co/8PoPO9uRk3

[Will Manidis @WillManidis]

https://t.co/aHOHtb1rcW

[Protocol Guild @ProtocolGuild]

4 years ago @LidoFinance kicked off the Protocol Guild pilot with a contribution of 2mm LDO 🫡