If we ship FOCIL (EIP-7805), Frame Transactions (EIP-8141), Keyed Nonces (EIP-8250) and Recent Roots (EIP-8272) in Hegota, we get native, trustless, censorship resistant private transactions on Ethereum next year.

One step closer to 4-8x faster Ethereum finality! It took some time and lots of tokens, but we now have a formally verified proposal for a decoupled consensus protocol in I* (a future Ethereum upgrade)! Not yet a full spec (up next), but it includes all the key consensus-relevant details to become one. Since Ethereum aspires to be live without most of the stake online, the protocol involves many more components than a normal BFT protocol, and its correctness involves much more than standard safety and liveness. Those nuanced properties are now verified! What's more, I came away convinced that all protocol design will involve AI-assisted Formal Verification in the future, both for correctness and iteration speed. The work wasn't limited to just: Design the protocol -> Formally verify it Instead, the loop became more like: Design -> Formal Model -> Find exactly what breaks and why -> Redesign it. For a fairly complicated protocol like this one, I think having the Lean model be part of the design loop played a big role in accelerating the process. A future with agents paired with formal models is a superpower for Ethereum development, because they can then use those models to find exactly where an argument breaks down, formalize counterexamples, test proposed fixes, iterate on the protocol. Many details that would slip under the radar when asking agents (and indeed, humans) can now be specified exactly and checked by the Lean kernel. This then forces agents to be more precise and lets them make verifiable progress on their own. It's been incredible to see this play out, seeing agents find gaps and propose protocol changes to fix them. In other words, autoresearch can speed up protocol design, formal verification is here to stay, and Ethereum Finality will get faster.

EIP-8141 Frame Transactions and friends (8250 keyed nonces, 8272 recent roots, 7906 transaction assertions) merged to @Nethermind master github.com/NethermindEth/net… ! Only 40k lines of code - lot of tests and comments though. Frame Transactions 40k 😉

Features moved to "considered" status for Hegotá today (the fork following Glamsterdam): - three Frame txs EIPs (tx assertions via state diff opcode, keyed nonces, recent roots) - remove bloom filters - bump nonce of zero-nonce storage accounts - remove storage-clear refund & refund cap - unified tx content floor & block access list byte floor - call & return opcodes for the EVM - reserve EXTENSION (0xae) opcode Some that the call in 2 weeks will cover that ecosystem devs might be interested in chiming in about: - TCREATE opcode - account code restricted ecRecover - SETCODEFROM code reuse instruction - precompiles for ML-DSA verification - deactivate SELFDESTRUCT - EVM-ify the identity precompiles - read BLOCKHASH from storage and update cost "Considered" status doesn't definitely mean it'll be included, so if you're a dev and see one that you're excited about, find its champion on Forkcast and ask them if they need any help around it!

If you want to get a feel for what the future of privacy on Ethereum looks like 👇

🥷 Keyed Nonces (EIP-8250) and Recent Roots (EIP-8272) were just CFI'd in Hegota 🥷 One more step towards native privacy coming to Ethereum Buckle up ❤️‍🔥

HABEMUS TESTNET — DAISUGI v0.1 A post-quantum Ethereum testnet using hash-based SPHINCS signatures with non-native account abstraction. Big thanks to @riva_labs and @GiulioRebuffo. Coming next: • Frame Transactions • Signature aggregation via LeanSPHINCS Believe in somETHing. Link ⬇️

im now fully hegota-pilled

∂TVL/∂Privacy > 0, ∂TVL/∂Trust < 0 *modulo marketing budgets

😂 *when Ethereum adds native privacy, in 2027

built @soispoke's matcha sender-width for keyed-nonce frame-txs. github.com/NethermindEth/net…

lol nah, privacy is _not_ dead, we've just built the wrong defaults so far. any kind of privacy must be part of the _runtime_ (can be an execution layer, can be a browser, etc.), not something users have to configure. that's why i've been saying for years: we must ship _L1 enshrined unconditional_ privacy. if the default tx is private by default, you scale privacy and you win. i won't stop until i can replace my xmr txs with eth txs. build the right system defaults, and you win. ethereum enshrined privacy will win.

Thanks to everyone who joined the EF Protocol AMA with questions! Lots to dig into on zkEVM, post-quantum (PQ) Ethereum, and formal verification (FV). Here's a guide to 24 relevant questions with answers, with direct links to each discussion. 1/12

It's only dead if you give up I'm not giving up on privacy. I'm doubling down. firefly.social/post/x/210138…

I think it's still a bit hard for people to grasp how privacy on Ethereum will look 1/2 years from now just because how different it will be from today. But the best mental model is: at least feature parity with regular private transfers à la Zcash + a variety of private DeFi apps, all fully trustless/unstoppable AND 10x better UX and protections with Kohaku (including anon broadcast, private reads, et.c...)

Starting now: Join the 15th EF Protocol Cluster AMA on r/Ethereum! Submit your questions about Ethereum and join the conversation here: teddit.net/r/ethereum/commen…

It was great to with @DeFi_Dad and @Nomaticcap about our roadmap for Ethereum protocol privacy on @edge_pod! We discuss Hegota EIPs (7805, 8181, 8250, 8272), PQ privacy, differences with Zcash, etc...

New @Edge_Pod's out! Today, every transaction you make onchain is trackable. But private DeFi on Ethereum is closer than you think. EF researcher @soispoke says it's possible we get native, trustless, censorship-resistant private transactions on Ethereum by next year.

my Hegotá EIP ranking from @etheconomiczone perspective ↳ EIP-7906 (state diff assertions) -> a batch-posting bundle can verify its preconditions on chain and fail fast instead of half landing. best atomicity backstop here ↳ EIP-8025 (optional execution proofs) -> L1 execution proofs feed straight into multi-prover rollup verification ↳ EIP-8250 (keyed nonces) -> parallel nonce lanes end poster-tx livelock. Frames already SFI, so this is gud ↳ EIP-8198 Quick Slots -> sync composability latency is bounded by slot time ↳ EIP-8371 RowDAS -> cheaper blob posting ↳ EIP-8146 BAL sidecars -> cheaper proving ↳ EIP-8304 trustless log/tx index -> trustless derivation ↳ EIP-8272 recent roots for frames everything else: B or below

S-tier privacy from @l2beat and @donnoh_eth 🔥