devlongs

eng lead @geanclient, building the final design of ethereum

[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.

[devlongs @devlongs_]

Geanie 🔥

[Web3 Philosopher @seunlanlege]

So cool to see there's a Nigerian Blockchain Lab building an ethereum consensus client @geanclient

It's our time 💪🏾

[devlongs @devlongs_]

@seunlanlege @geanclient It is our time. Thanks, ser.

[devlongs @devlongs_]

@fede_intern weldone Fede. Can't wait to give Concrete a shot.

[vitalik.eth @VitalikButerin]

@fede_intern @ethereumfndn @aerugoettinea more people should know @kevaundray

and for that matter the others doing the zkevm work (including those outside EF)

(Justin is of course great, but I've mentioned justin being great many times already😄)

[devlongs @devlongs_]

A major milestone for Gean and another step toward production-grade Lean Ethereum consensus infrastructure in Go.

Live dashboard: https://t.co/qlrBpFFLNV

[devlongs @devlongs_]

Gean is now passing all Lean Ethereum Hive test suites (200/200), the official conformance tests that run Lean Consensus clients against the spec.

This includes interop, rpc-compat, reqresp, gossip, validation, fork-choice, state-transition and signature verification suites.

[Thomas Coratger @tcoratger]

The timeline for Q-Day is accelerating.

The probability of a Cryptographically Relevant Quantum Computer (CRQC) breaking blockchain cryptography by 2032 has shot up.

Here is a technical breakdown of @drakefjustin's recent presentation on the quantum threat at @zkproof. 🧵👇

[YoungHoon Kim @yhbryankimiq]

THE MORE I STUDY SCIENCE, THE MORE I BELIEVE IN JESUS. 100%

[devlongs @devlongs_]

@fede_intern 😅

[devlongs @devlongs_]

👏 👏 👏

[gean @geanclient]

We have completed devnet-4 development and currently participating in the devnet-4 multi-client interop run.

Here are some of the notable implementations done for devnet-4

[B L E S S I N G | web3creed 🛡️ @dicethedev]

I mapped out projects from Cohort 5 & 6 what’s been explored and where there’s still room to contribute.

Read here: https://t.co/jh2rRnCJ5m

[devlongs @devlongs_]

ethlambda 🤝 gean

[ethlambda @ethlambda_lean]

Here's a peek at our internal devnet, currently finalizing with 2 ethlambda, 1 zeam and 1 gean clients 🚀

[ethlambda @ethlambda_lean]

Here's a peek at our internal devnet, currently finalizing with 2 ethlambda, 1 zeam and 1 gean clients 🚀

[Hubert Thieblot @hthieblot]

Only suffering makes you a better founder.

The rejections. The flat metrics. The 3 AM ceiling stares wondering if you’re delusional.

Embrace it. High pain tolerance is the only moat that can't be disrupted.

Don't seek ease. Seek strength. Aim for the impossible.

[The_5thSon @The_5thSon]

The @ethereumfndn formal verification timeline ends at the consensus client layer in 2027. I'm not waiting. I've spent the last while building a mental model for formal verification and Lean4 before writing a single line of code.

Here's what I learned and where I'm headed. 🧵

[Protocol Guild @ProtocolGuild]

Ethereum core devs have a new mandate in 2026:

'Harden the L1'

Here's what that actually means:

[The Chopping Block @_choppingblock]

.@drakefjustin:

“Client diversity has saved Ethereum multiple times.”

But what really stuck was:

“There is a potential outcome here where it’s not quite quantum computers that break ECDSA, it’s actually AI.”

“And so part of the rush… is not just to make Ethereum post-quantum secure, but it’s also to make it post-AI secure.”

[devlongs @devlongs_]

gean update!

we have just wrapped up devnet-3. solid progress across consensus, stability, and sync. Now moving into devnet-4 as specs stabilize and interop begins.

Steadily progressing towards testnet.

[Ream Labs @ReamLabs]

1/ 🧵 We attended FORT MODE — the post-quantum consensus day at EthCC[9] — and have published our full view on the PQ devnet roadmap.

An early view of what we concluded and TLDR of the event 👇