spencer 🏴 retweeted
Today the EF and OA announce zkAPI—a new means for private AI
Picture this: deposit ether into a vault, sign a zk proof, get a fixed amount of private inference. Advances like these help us move past middlemen's requirements that we link our data and identities.
Read more below
Quick updates on the Open Anonymity project (@OpenAnonProject)!
1. OA-chat is live! You can now signup: chat.openanonymity.ai
2. We collaborated with @ethereumfndn (@VitalikButerin, @DavideCrapis, @VittoStack, @curryrasul) to develop zkAPI, a new zero-knowledge protocol for accessing gated / paid APIs with unlinkability. It’s like a generalization of OA unlinkable inference that also abstracts payments away. Now also available on OA-chat!
I'm excited because more infrastructure should exist where privacy and sovereignty is foundational and people are in control.
spencer 🏴 retweeted
Security researchers, get ready! The Glamsterdam upgrade is approaching. The Ethereum Foundation’s bug bounty program will begin accepting reports for Glamsterdam bugs once the Sepolia upgrade blog post is published. And take note of the reward multipliers!
ethereum.org/bug-bounty/#gla…
I just read my first AI book.
Two months ago, I asked ChatGPT to imagine what the world might look like in 2050.
The answer was very interesting, so I asked it to write an entire fiction book set in that future.
It generated a ~100-page story about a world where AI gets so good at predicting human behavior that it can prevent tragedies before they happen.
The story explores a simple question: if AI could make the world safer by slowly taking away our ability to make mistakes, would we let it?
Among all the futuristic visions in movies and books, this one feels the most plausible to me.
The v1 of the book was a bit slow, so I asked ChatGPT to make a v2 more dynamic.
Here’s the book: drive.google.com/drive/u/0/f…
The chat expired, so ChatGPT made a new version. We might not be reading the same version.
spencer 🏴 retweeted
my bend evm seems to pass all the Amsterdam Ethereum HF state tests - its extemely slow but its worth taking a look as i diff tested w revm/evm2 and looks good
github.com/gakonst/evm-bend
spencer 🏴 retweeted

Derive.xyz@DeriveXYZSep 17
Australia
AustraliaConnected via WebAccount-level information, not a live location or per-post device.
We support EIP-8198 (Quick Slots) and @ethlabs_org’s push for faster Ethereum blocks!
Great read on the trading costs of slow blocks. Our own @josh_pwrk explains how arbitrageurs could take less price risk while waiting for their L1 spot trades to land, letting them step in on smaller price gaps and help keep spreads tight.
We're bringing Derive V3 to Ethereum L1, so we’d love to see this ship.
spencer 🏴 retweeted
🎄🌲When Binary Tries?🌲🎄
You're witnessing @Nethermind @ErigonEth @go_ethereum and @Consensys 's Besu all handling a reorg while moving into Partitioned Binary Trie (eips.ethereum.org/EIPS/eip-8…)
You can't get it more solid than this!
Next step 👉 Mainnet migration tests
👇👇
spencer 🏴 retweeted
today EF Protocol published two posts. we hope you check them out!
for me, they mark the end of a transition that started back in april. when @kevaundray, @0xfredrik, and i stepped into the cluster coordinator roles, the job within the job was cluster-wide alignment: shaping a strategy born from our imperative (concentrate Protocol on what only Protocol can and will do), grounded in CROPS, and aimed at what Ethereum needs right now to endure for 1,000 years.
1️⃣ the first post makes that strategy public: a quantum-resistant ethereum L1 by december 2029, the multi-fork plan to get there, and what each of our five research arcs needs from the upcoming forks.
2️⃣ the second post is our first unified hardfork opinion: grades from every team in the cluster, argued down to one tier list covering every EIP proposed for hegotá, with the reasoning behind every grade.
read the priorities first. the tier list is those priorities applied.
lastly, Protocol is hosting a Reddit AMA on r/ethereum, sept 16 at 2pm UTC. hope to see you there. question form in the next post. 👇
The Protocol Cluster has published two new posts:
Hegotá EIP Opinion Post and Tier List evaluates and grades all 62 EIPs proposed for Hegotá, providing the cluster’s first unified tier list for a network upgrade
Current and Emerging Priorities covers commitments and research arcs, anchored on a quantum-resistant Ethereum L1 by Dec. 2029
Offered as one input to Hegotá scoping, roughly 60 researchers, engineers, and individual domain experts across all 9 teams in the Protocol Cluster contributed to the Hegotá tier list, providing 397 tier grades before discussing contested items live.
The plan, commitments, and shared set of cluster-wide priorities covered in the companion post provide the context behind the final tier grades.
The Protocol cluster will host a Reddit AMA on r/ethereum on September 16 at 2pm UTC to talk through these priorities, the Hegotá tier list, and anything else on your mind.
→ Submit questions ahead of time here: pad.ethereum.org/form/#/2/fo…
Read the articles here:
→ EF Protocol - Current and Emerging Priorities: blog.ethereum.org/2026/09/07…
→ EF Protocol - The Hegotá EIP Opinion Post and Tier List: blog.ethereum.org/2026/09/07…
spencer 🏴 retweeted
We've published the EF Protocol cluster's priorities and our first shared Hegotá EIP tier list, with input from ~60 researchers and engineers across all 9 Protocol teams.
We're aggressively targeting a quantum-resistant Ethereum L1 no later than December 2029. That has implications for what we propose including in Hegotá, and how much capacity we leave for the forks after it.
Keeping mainnet safe remains our first priority.
We'll be on r/ethereum for an AMA on September 16 at 2pm UTC. Please come ask us about the priorities, the tier list, or anything else you're curious about.
Tier and priorities posts and question form can be found below in this thread:
spencer 🏴 retweeted
Revolut, a leading fintech with 80 million customers globally, is launching a Euro stablecoin on Ethereum.
Welcome to @Ethereum, EURR.
spencer 🏴 retweeted
EIP-7610 is officially out of Glamsterdam. Thanks @JochemBrouwer96 for the PR! 🙌
eips.ethereum.org/EIPS/eip-7…
Next up: expect the Glamsterdam Meta EIP-7773 to move to Review 🔜
github.com/ethereum/EIPs/pul…
#Ethereum #Glamsterdam #EIP7773
The latest AllCoreDevs Consensus #185 updates are now live on @EIPsInsight.
Sepolia Glamsterdam is proposed for September 28, with Hoodi targeting October 26, pending further testing and confirmation.
EIP-7610 is officially cancelled from Glamsterdam, superseded by EIP-8253 targeting Hegota.
EIP-833 and EIP-8379 have moved forward for Hegota, while the reduced CL block retention proposal remains under discussion.
A non-finality DevNet is targeted for the week after next, with all clients expected to be on trunk/unstable branches first.
Hegota EIP tier rankings are also due from client teams by mid-September, with rough consensus targeted before DevCon.
🔗 eipsinsight.com/calls/acdc/1…
#Ethereum #ACDC #Hegota #Glamsterdam
spencer 🏴 retweeted
Introducing the Platåberget testnet! Its our Glamsterdam focused testnet to help the community test all the upcoming changes. Please get involved with the testing efforts!
blog.ethereum.org/2026/08/17…
spencer 🏴 retweeted
EF has shipped something most people haven't noticed yet.
This is going to make every wallet private by default.
Let me tell you about Kohaku 🧵
spencer 🏴 retweeted

Protocol Guild@ProtocolGuildMay 12
United States
United StatesConnected via United States App StoreAccount-level information, not a live location or per-post device.
1/ We're thrilled to welcome @AztecFND as the latest project to take the 1% Pledge 🎉
1% of the AZTEC token supply has been deposited into Protocol Guild's 4-year vesting contract to support 187 Ethereum core contributors across client teams, research, and coordination
spencer 🏴 retweeted
Interop for Glamsterdam was a big success, and from what I can tell, it will bring major scaling improvements to Ethereum.
With BALs (EIP-7928), nodes can parallelize transaction execution, state root computation, and batch prefetch the state needed for a block.
With ePBS (EIP-7732), we get ~2-3x more time for execution.
Devs have been shipping non-stop this week, and I’m as tired as I am convinced this fork will be a huge unlock.
100 Ethereum contributors went to the edge of the earth and came back with a path to make it faster, stronger,
and might i say,
a bit more badass.
A new dawn: blog.ethereum.org/2026/05/02…
Frames by Lou3ee
spencer 🏴 retweeted
Today is a monumentous day for quantum computing and cryptography. Two breakthrough papers just landed (links in next tweet). Both papers improve Shor's algorithm, infamous for cracking RSA and elliptic curve cryptography. The two results compound, optimising separate layers of the quantum stack. The results are shocking. I expect a narrative shift and a further R&D boost toward post-quantum cryptography.
The first paper is by Google Quantum AI. They tackle the (logical) Shor algorithm, tailoring it to crack Bitcoin and Ethereum signatures. The algorithm runs on ~1K logical qubits for the 256-bit elliptic curve secp256k1. Due to the low circuit depth, a fast superconducting computer would recover private keys in minutes. I'm grateful to have joined as a late paper co-author, in large part for the chance to interact with experts and the alpha gleaned from internal discussions.
The second paper is by a stealthy startup called Oratomic, with ex-Google and prominent Caltech faculty. Their starting point is Google's improvements to the logical quantum circuit. They then apply improvements at the physical layer, with tricks specific to neutral atom quantum computers. The result estimates that 26,000 atomic qubits are sufficient to break 256-bit elliptic curve signatures. This would be roughly a 40x improvement in physical qubit count over previous state-of-the-art. On the flip side, a single Shor run would take ~10 days due to the relatively slow speed of neutral atoms.
Below are my key takeaways. As a disclaimer, I am not a quantum expert. Time is needed for the results to be properly vetted. Based on my interactions with the team, I have faith the Google Quantum AI results are conservative. The Oratomic paper is much harder for me to assess, especially because of the use of more exotic qLDPC codes. I will take it with a grain of salt until the dust settles.
→ q-day: My confidence in q-day by 2032 has shot up significantly. IMO there's at least a 10% chance that by 2032 a quantum computer recovers a secp256k1 ECDSA private key from an exposed public key. While a cryptographically-relevant quantum computer (CRQC) before 2030 still feels unlikely, now is undoubtedly the time to start preparing.
→ censorship: The Google paper uses a zero-knowledge (ZK) proof to demonstrate the algorithm's existence without leaking actual optimisations. From now on, assume state-of-the-art algorithms will be censored. There may be self-censorship for moral or commercial reasons, or because of government pressure. A blackout in academic publications would be a tell-tale sign.
→ cracking time: A superconducting quantum computer, the type Google is building, could crack keys in minutes. This is because the optimised quantum circuit is just 100M Toffoli gates, which is surprisingly shallow. (Toffoli gates are hard because they require production of so-called "magic states".) Toffoli gates would consume ~10 microseconds on a superconducting platform, totalling ~1,000 sec of Shor runtime.
→ latency optimisations: Two latency optimisations bring key cracking time to single-digit minutes. The first parallelises computation across quantum devices. The second involves feeding the pubkey to the quantum computer mid-flight, after a generic setup phase.
→ fast- and slow-clock: At first approximation there are two families of quantum computers. The fast-clock flavour, which includes superconducting and photonic architectures, runs at roughly 100 kHz. The slow-clock flavour, which includes trapped ion and neutral atom architectures, runs roughly 1,000x slower (~100 Hz, or ~1 week to crack a single key).
→ qubit count: The size-optimised variant of the algorithm runs on 1,200 logical qubits. On a superconducting computer with surface code error correction that's roughly 500K physical qubits, a 400:1 physical-to-logical ratio. The surface code is conservative, assuming only four-way nearest-neighbour grid connectivity. It was demonstrated last year by Google on a real quantum computer.
→ future gains: Low-hanging fruit is still being picked, with at least one of the Google optimisations resulting from a surprisingly simple observation. Interestingly, AI was not (yet!) tasked to find optimisations. This was also the first time authors such as Craig Gidney attacked elliptic curves (as opposed to RSA). Shor logical qubit count could plausibly go under 1K soonish.
→ error correction: The physical-to-logical ratio for superconducting computers could go under 100:1. For superconducting computers that would be mean ~100K physical qubits for a CRQC, two orders of magnitude away from state of the art. Neutral atoms quantum computers are amenable to error correcting codes other than the surface code. While much slower to run, they can bring down the physical to logical qubit ratio closer to 10:1.
→ Bitcoin PoW: Commercially-viable Bitcoin PoW via Grover's algorithm is not happening any time soon. We're talking decades, possibly centuries away. This observation should help focus the discussion on ECDSA and Schnorr. (Side note: as unofficial Bitcoin security researcher, I still believe Bitcoin PoW is cooked due to the dwindling security budget.)
→ team quality: The folks at Google Quantum AI are the real deal. Craig Gidney (@CraigGidney) is arguably the world's top quantum circuit optimisooor. Just last year he squeezed 10x out of Shor for RSA, bringing the physical qubit count down from 10M to 1M. Special thanks to the Google team for patiently answering all my newb questions with detailed, fact-based answers. I was expecting some hype, but found none.
🚀 Twigg's biggest update is live
An AI research assistant that actually does the work:
✍️ Edits your documents (line-by-line, with full edit history)
📄 Reads and parses PDFs automatically
📥 Fetches papers from URLs
🗂️ Manages your files (create, edit, organize)
🌳 Keeps context clean with tree-based conversations
Built for researchers, writers, and anyone tired of restarting chats.
Try it free: twigg.ai
What would you want it to do next? 👇
#AI #AgenticAI #ResearchTools #AcademicTwitter #PhDLife
spencer 🏴 retweeted
🧵Thread Series (1/3): STEEL at Ethereum Foundation
1/ This last summer I worked at Ethereum Foundation (@ethereumfndn) as one of their first official interns. My work was with the STEEL team, specifically on the EELS side of things.
What does that mean? Lets unpack...
👇








































