Butta.eth

@ethStaker | @beaconcha_in | @efprotocol

[ً @lightclients]

EIP-8037 is scheduled for Glamsterdam and will increase the gas cost of creating new accounts and writing to new storage slots by 5-8x.

What protocols have hard-coded expectations about state gas costs? What is at risk of breaking?

[Butta.eth @Butta_eth]

@d_gusakov @LidoFinance The missing part is how much those 422 operators control. Either way, still an improvement 👍🏻

[Butta.eth @Butta_eth]

@beaconcha_in here in action: https://t.co/wfcyxc1Ycx :)

[beaconchain.eth 📡 @beaconcha_in]

A clearer validator lifecycle:

- New Withdrawn step in the timeline
- "Consolidation in progress" now surfaces in the overview card
- Consolidation, withdrawal & exit tables get a Status column with consensus-layer rejection reasons

[Butta.eth @Butta_eth]

Only a question of when 😎

[nicolas, 30 ans @nic_carter]

Remember when I told you ETHBTC was a decent proxy for how much investors care about quantum risk?

[Butta.eth @Butta_eth]

@drakefjustin Thank you for your efforts in Bitcoin security research.

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

[trent.eth @trent_vanepps]

https://t.co/GajUKQC8li

[beaconchain.eth 📡 @beaconcha_in]

Our latest release, 26.20 is live.

🔐 TOTP 2FA
🔄 Pectra consolidations in the explorer
✅ Entity selector API available for v2 APIs

Details 👇

[Butta.eth @Butta_eth]

@d_gusakov @fundstrat @ratedw3b @miga_labs @beaconcha_in Do you have their onchain data (like withdrawal addresses)?

[Roman Storm 🇺🇸 🌪️ @rstormsf]

Ethereum has been winning, is winning, and has never lost.

The most-used subprotocol or subchain by actual users is EVM-based. Every major wallet either supports ETH natively or is built entirely on EVM architecture.

Every chain that tried to compete failed to attract meaningful developer adoption. Algorand, Tezos, Polkadot - none crossed the threshold. Most “ETH killers” eventually found a single niche and settled: NEAR became a solid intent-based bridge layer, TRON became a USDT wallet. That’s not winning, that’s narrowing.

Cheap L2s never retained long-term users either. The pattern is always the same: airdrop announcement, usage spike, MEV bots flood in because gas is cheap, then silence. Base is a clean example of that cycle.

Ethereum sets the vision. Every fork and new proposal chases the EIP backlog because the entire infrastructure stack - Etherscan, Infura, Alchemy, Blockscout - standardized on EVM. Deviate from that standard and you’re on your own. That’s why deploying a forked contract to TRON is a nightmare, why Optimism shipped multiple broken hard forks chasing weird gas estimation edge cases, and why dapp developers refuse to write chains of if/else blocks just to handle behavioral differences across 10+ forked EVMs.

No one wants that complexity in their JavaScript. No wallet team wants to maintain it either.

Conform to EVM or get left behind. Ethereum didn’t enforce that rule - the ecosystem did.

[eric @econoar]

This was always the end game

As time goes on and marketcap goes up, Twitter influence dies out

For smaller caps it's still important but not as things mature

[Butta.eth @Butta_eth]

@jdetychey @Cometh @KaikoData congrats!!

[terence @terencechain]

A quick post on how ePBS changes Ethereum scaling:
https://t.co/texbKsqMAb

[beaconchain.eth 📡 @beaconcha_in]

Shipped on https://t.co/prW3YorSh6 this week 🧵

... faster navigation, clearer reward breakdowns, a smarter simulator, and better API docs. 👇

[marc | wolovim.eth @wolovim]

ICYMI ✨

eight(!) glamsterdam EIPs moved from CFI (Considered) to SFI (Scheduled) last ACDE call

🧵

[Butta.eth @Butta_eth]

@d_gusakov @LidoFinance @ethereum lfg 🫡

[gusakov.eth | Lido @d_gusakov]

@LidoFinance is on the way to consolidate all curated validators to 0x02! The very first Hoodi consolidation has been completed today, kicking off a massive wave of testing. Next stop is @ethereum Mainnet. See you all in August 2026!

https://t.co/fzO6ubko5m

[Ben Edgington @benjaminion_xyz]

Upgrading Finality - Edition 1

Check out the plan for bringing fast finality to Ethereum.

Hosted on the the brand new and shiny EF Protocol Consensus website 😁 Lots of good stuff there!

https://t.co/49edpFXtKb

[Zach Pandl @LowBeta]

OK let's do this: we're weighing in on the contentious issue of $ETH's supply model

TLDR: We think a change is warranted and would be bullish for $ETH longer-term

The topic is a good litmus test for how people think about valuing crypto assets!

Our take ⬇️⬇️