uink45

[Pier Two @PierTwo_com]

Pier Two is joining MAVAN, a Bitmine company.

https://t.co/Ol71r5Of8d

[Pier Two @PierTwo_com]

The work continues for a Post-Quantum (PQ) Ethereum. To demonstrate robust consensus with secure, scalable signature aggregation – paving the way for a future-proof network.

With each devnet iteration, it has been faster to stabilize than the last. The gap between specification and working software continues to shrink. As the Lean Ethereum community moves toward larger validator sets and more realistic network conditions, Pier Two will continue contributing the implementation work, test vectors, and operational feedback that bring Lean Ethereum closer to a mainnet-ready protocol.

Learn more here: https://t.co/eWY5zhK6oa

[Justin Drake @drakefjustin]

Introducing strawmap, a strawman roadmap by EF Protocol.

Believe in something. Believe in an Ethereum strawmap.

Who is this for?

The document, available at strawmap[.]org, is intended for advanced readers. It is a dense and technical resource primarily for researchers, developers, and participants in Ethereum governance. Visit ethereum[.]org/roadmap for more introductory material. Accessible explainers unpacking the strawmap will follow soon™.

What is the strawmap?

The strawmap is an invitation to view L1 protocol upgrades through a holistic lens. By placing proposals on a single visual it provides a unified perspective on Ethereum L1 ambitions. The time horizon spans years, extending beyond the immediate focus of All Core Devs (ACD) and forkcast[.]org which typically cover only the next couple of forks.

What are some of the highlights?

The strawmap features five simple north stars, presented as black boxes on the right:

→ fast L1: fast UX, via short slots and finality in seconds
→ gigagas L1: 1 gigagas/sec (10K TPS), via zkEVMs and real-time proving
→ teragas L2: 1 gigabyte/sec (10M TPS), via data availability sampling
→ post quantum L1: durable cryptography, via hash-based schemes
→ private L1: first-class privacy, via shielded ETH transfers

What is the origin story?

The strawman roadmap originated as a discussion starter at an EF workshop in Jan 2026, partly motivated by a desire to integrate lean Ethereum with shorter-term initiatives. Upgrade dependencies and fork constraints became particularly effective at surfacing valuable discussion topics. The strawman is now shared publicly in a spirit of proactive transparency and accelerationism.

Why the "strawmap" name?

"Strawmap" is a portmanteau of "strawman" and "roadmap". The strawman qualifier is deliberate for two reasons:

1. It acknowledges the limits of drafting a roadmap in a highly decentralized ecosystem. An "official" roadmap reflecting all Ethereum stakeholders is effectively impossible. Rough consensus is fundamentally an emergent, continuous, and inherent uncertain process.
2. It underscores the document's status as a work-in-progress. Although it originated within the EF Protocol cluster, there are competing views held among its 100 members, not to mention a rich diversity of non-EFer views.

The strawmap is not a prediction. It is an accelerationist coordination tool, sketching one reasonably coherent path among millions of possible outcomes.

What is the strawmap time frame?

The strawmap focuses on forks extending through the end of the decade. It outlines seven forks by 2029 based on a rough cadence of one fork every six months. While grounded in current expectations, these timelines should be treated with healthy skepticism. The current draft assumes human-first development. AI-driven development and formal verification could significantly compress schedules.

What do the letters on top represent?

The strawmap is organized as a timeline, with forks progressing from left to right. Consensus layer forks follow a star-based naming scheme with incrementing first letters: Altair, Bellatrix, Capella, Deneb, Electra, Fulu, etc. Upcoming forks such as Glamsterdam and Hegotá have finalized names. Other forks, like I* and J*, have placeholder names (with I* pronounced "I star").

What do the colors and arrows represent?

Upgrades are grouped into three color-coded horizontal layers: consensus (CL), data (DL), execution (EL). Dark boxes denote headliners (see below), grey boxes indicate offchain upgrades, and black boxes represent north stars. An explanatory legend appears at the bottom.

Within each layer, upgrades are further organized by theme and sub-theme. Arrows signal hard technical dependencies or natural upgrade progressions. Underlined text in boxes links to relevant EIPs and write-ups.

What are headliners?

Headliners are particularly prominent and ambitious upgrades. To maintain a fast fork cadence, the modern ACD process limits itself to one consensus and one execution headliner per fork. For example, in Glamsterdam, these headliners are ePBS and BALs, respectively.

(L* is an exceptional fork, displaying two headliners tied to the bigger lean consensus fork. Lean consensus landing in L* would be a fateful coincidence.)

Will the strawmap evolve?

Yes, the strawmap is a living and malleable document. It will evolve alongside community feedback, R&D advancements, and governance. Expect at least quarterly updates, with the latest revision date noted on the document.

Can I share feedback?

Yes, feedback is actively encouraged. The EF Protocol strawmap is maintained by the EF Architecture team: @adietrichs, @barnabemonnot, @fradamt, @drakefjustin. Each has open DMs and can be reached at first.name@ethereum[.]org. General inquiries can be sent to strawmap@ethereum[.]org.

[zeamETH @zeamETH]

devnet-3 here we come! 🎇🎇🎇
primary interop achieved🦾🦾🦾

why is this important?👇👇👇

now we have specialized aggregators for aggregating the PQ signatures that everyone else imports in their forkchoice and block producer packs for new blocks

this brings us closer to how this will work in mainnet for @leanEthereum

next up for devnet-4 is recursive aggregation of these signatures and we already started on its specs

[Obol @Obol_Collective]

Bull or bear, Obol Distributed Validators consistently outperform legacy validators 🎯

@PierTwo_com is currently at a 99% monthly RAVER score, with most of its stake distributed across DVs (Source: @ratedw3b)

[lean Ethereum @leanEthereum]

The drums of quantum computing are getting louder.
An ambitious roadmap backed by concrete designs and 30+ years of cryptographic research is already underway.

Learn more at leanroadmap[.]org."

[Pier Two @PierTwo_com]

Lido V3 is live on Ethereum mainnet.

The RockSolid AutoPlus Looped ETH Vault is now available. The first to hit mainnet.

@rocksolidHQ's ERC-7540 Asynchronous Tokenized Vault standard, built on top of @LidoFinance's stVault, is flexible and agnostic to provide the workflows and controls necessary to deliver outcomes for institutional clients seeking stronger liquidity provisions and broader utility.

Supported by @PierTwo_com's non-custodial validator infrastructure, to meet institutional grade security and uptime requirements.

More about the RockSolid AutoPlus Looped ETH Vault can be found at: https://t.co/5h3s76Agz2

[Pier Two @PierTwo_com]

Next week, @PierTwo_com's @pat_mcnab joins @paladin_eth from @rocksolidHQ and @jesperjohansen from @Northstake_dk on the @LidoFinance V3 Mainnet Launch Community Call.

Join us here: https://t.co/AqqlsE4mMl

[Lido @LidoFinance]

Lido V3, initializing…

Don’t miss the upcoming stVaults Builders Fireside Chat where we'll cover the most novel staking products built with Lido V3 and stVaults.

Featuring @Northstake_dk, @PierTwo_com & @rocksolidHQ.

📆 2pm UTC, February 3rd.

[Katya Riazantseva @Sib_Katya]

@leanEthereum Devnet-2 is demonstrating consistent finality across 4 clients: @zeamETH, @ReamLabs, @qdrvm_io and @PierTwo_com 🥳🚀

[Justin Drake @drakefjustin]

Today marks an inflection in the Ethereum Foundation's long-term quantum strategy.

We've formed a new Post Quantum (PQ) team, led by the brilliant Thomas Coratger (@tcoratger). Joining him is Emile, one of the world-class talents behind leanVM. leanVM is the cryptographic cornerstone of our entire post-quantum strategy.

After years of quiet R&D, EF management has officially declared PQ security a top strategic priority. Our journey began in 2019, with the "Eth3.0 Quantum Security" presentation at StarkWare Sessions. Since 2024, PQ has been central to the @leanEthereum vision. The pace of PQ engineering breakthroughs since then has been nothing short of phenomenal.

It's now 2026, timelines are accelerating. Time to go full PQ:

→ PQ ACD: Antonio Sanso (@asanso) kicks off a bi-weekly All Core Devs PQ transactions breakout call next month. These sessions focus on user-facing security, covering dedicated precompiles, account abstraction, and longer-term transaction signature aggregation with leanVM.
→ PQ foundations: Today we are announcing a $1M Poseidon Prize to harden the Poseidon hash function. We are betting big on hash-based cryptography to enjoy the strongest and leanest cryptographic foundations. Check out our other $1M PQ initiative, the Proximity Prize.
→ PQ devnets: Multi-client PQ consensus devnets are live! Shoutout to pioneers @zeamETH, @ReamLabs, @PierTwo_com, @geanclient, @ethlambda_lean, as well as established consensus teams Lighthouse, Grandine, and soon Prysm. This incredible teamwork is coordinated by @corcoranwill via weekly PQ interop calls.
→ PQ workshops: Building on last year's PQ workshop in Cambridge (see photo), the EF is hosting another 3-day PQ event in October. Top experts from around the world will convene. In addition, a PQ day is set for March 29 in Cannes just ahead of EthCC.
→ PQ FV and AI: Last week Alex Hicks (@alexanderlhicks) ran a specialised maths AI for 8 hours, at a $200 cost. It one-shotted a formal proof one of the hardest lemmas in the foundations of hash-based snarks. Mind-blowing. Applied cryptography will never be the same.
→ PQ roadmap: A comprehensive breakdown of the EF's proposed PQ strategy will be shared soon™ on pq[.]ethereum[.]org. The roadmap targets a full transition in coming years with zero loss of funds and zero downtime. Stay tuned :)
→ PQ education: The ZKPodcast (@zeroknowledgefm) is producing a 6-part video series on Ethereum's PQ strategy. EF Enterprise Acceleration is also preparing material for enterprises and nation-states. Finally, Ethereum is now represented on the PQ advisory board that Coinbase announced yesterday.

Believe in something. Believe in PQ security.

[lean Ethereum @leanEthereum]

congrats to all the teams that just reached pq-devnet-2!

the breakthrough?: leanCL teams are now aggregating post-quantum signatures via leanVM!

more details in the next post 🚀

[zeamETH @zeamETH]

alright we now have leanVM aggregation!🎉🔥🚀

devnet-2 interop achieved within leading lean clients
now turn for devnet-2 long runs and debuggings 🦾

spec work already on for devnet-3 🤌

[zeamETH @zeamETH]

@PierTwo_com 's Lantern achieves devnet1 🎆
welcome to the PQ ethereum ring Lantern
👏👏👏

[lean Ethereum @leanEthereum]

hello world

[Justin Drake @drakefjustin]

Craaazy 365 days of @leanEthereum progress. Cheers to the builders. Cheers to the dreamers. Cheers to anti-fragility, too :)

Devcon, Bangkok — Nov 12, 2024. The suspense is real. The room overflows; hundreds can't get in. An "announcement of an announcement" had sparked wild speculation about my "most ambitious initiative".

Who knew the beam chain vision would evolve into lean Ethereum? Next-level ambition, seeping into all layers of L1. Snarks for consensus and execution. Fort mode and beast mode.

What's new? zkEVMs. Real-time proving. Full validation in a tab, on a phone. Let's pump L1 gas with the exponential snark curve. Starting in months, not years. To me it all points to 10K TPS, the gigagas frontier.

Dream bigger dreams for L1. Believe in something.

———

part 1—lean consensus

devnets

→ clients: 4 new lean CL clients (Zeam, Ream, Qlean, Lantern)
→ languages: 3 new CL languages (Zig, C++, C)
→ specs: by @tcoratger + 14 others; 3SF-mini subspec by @vitalikbuterin
→ testing: revamped test framework by @fselmo2; @Sib_Katya metrics
→ devnets: multi-client 3SF with 4s slots and 12s finality; PQ soon™

coordination

→ hires: EF Protocol coordinators @corcoranwill and @ladislaus0x
→ CL teams: led by @Gajpower, @unnawut, @kamil_abiy, @mstore80
→ 7 consensus calls: teams, PQ, p2p, exit queue, APS, 3SF, PQ specs
→ Cannes workshop: 1 day at EthCC in June; interop kicked off
→ 13 interop calls: by @corcoranwill on Wednesdays at 2pm UTC
→ Cambridge Oct workshops: 1 day leanVM, 3 days PQ, 3 days CL

cryptography

→ leanSig: 3 papers on hash sigs by Benedikt, @khovr, @kudinov_mikhail
→ leanVM: fast minimal aggregation zkVM by Emile
→ WHIR: fast Plonky3 implementation by @tcoratger
→ optimisoors: @AngusGruen, @GiacomoFenzi, @lambdaclass, @kiliconu
→ Poseidon2: 4 cryptanalysis workshops by @khovr, @asanso
→ maths: $1M Millennium-like proximity prize; papers flowing
→ formal verification: ArkLib by @QuangVDao

research

→ consensus team: hires @yannvon and lead @robsaltini join @luca_zanolini
→ faster finality: 1- or 2-round designs with Ethereum-grade liveness
→ 3sf-gold: new fast inclusion by @fradamt, @vitalikbuterin from Cambridge
→ p2p: @qdrvm_io simulator; @raulvk ethp2p; @soispoke leanp2p
→ rainbow staking: new Cambridge ideas; specs by Dan Goron & Alex Vlad

———

part 2��lean execution

zkEVM tech

→ real-time proving: ~100 engineers pushing across ~10 zkVM teams
→ GPU proving: 16 5090s (10kW) proving mainnet; $0.01/block
→ guests: revm (Reth), levm (Ethrex), evmone (Zilkworm), ZKSync OS
→ more guest programs: Geth, Besu, Nethermind and others soon™
→ RISC-V: de facto ISA of choice for zkEVM proving
→ Picus: prolific Veridise tool to identify under-constraints
→ formal verification: $4M across 40 grants by @alexanderlhicks

Ethproofs community

→ zkVM integrations: Airbender, OpenVM, Pico, R0VM, SP1, Ziren, ZisK
→ other integrations: Cysic, Fermah, Marlin, Snarkify, Zilkworm, ZkCloud
→ website: driven by @fbwoolf under new EF Ethproofs team
→ 7 calls: zkVMs, RTP, gigagas, RISC-V, native rollups, proximity gaps
→ Ethproofs day: Nov 22 at Devconnect; register at ethproofs[.]day
→ zkAttester demo: my home validator on zkEVM proofs at Ethproofs day

EF zkEVM team

→ new team: led by @kevaundray with Cody, Han, Ignacio, Radek, Sophia
→ EF blog post: real-time proving requirements by @_sophiagold_
→ zkLighthouse: modified Lighthouse client by @kevaundray
→ zkEVM/acc: @ignaciohagopian benchmarks; @codytouchgrass tests
→ more zkEVM/acc: @kevaundray standardisation; Ere by @han__0110

future of EL

→ Fusaka: per-tx gas limit (EIP 7825); MODEXP killer (EIPs 7823, 7883)
→ EVM 2.0: @vitalikbuterin proposal to enshrine RISC-V under the EVM
→ native rollups: championed by @lucadonnoh; wrote book and draft EIP
→ gas auto-pumps: 3x/year gas pumps (EIP-7938 by @dankrad)
→ gigagas L1: champion wanted—reach out :) [email protected]

[Pier Two @PierTwo_com]

Pier Two is excited to be supporting BAM for the Pier Two Infrastructure validator.

BAM aligns incentives of validators with App developers, resulting in better execution for users and unlocks new rewards for those delegating SOL.

Huge props to the @jito_sol team on shipping. Again.

[Pier Two @PierTwo_com]

BREAKING NEWS: Pier Two Strengthens Solana Performance with Acquisition of Blockport.

Read more about the acquisition here: https://t.co/ykEgYSfo3Y

Pier Two has bold plans for the Solana ecosystem, and with Adrian and Nik joining Pier Two, those plans become accelerated to deliver exceptional outcomes for Pier Two clients.

[Pier Two @PierTwo_com]

After another successful hard fork, Ethereum enters it’s next era. And that is good news for stakers.

@PierTwo_com, a leading professional staking service provider, is excited to announce Pectra Staking Manager, now live at https://t.co/wd3MYzSmOH. Codeveloped with @Labrys_io and with grant support from @EF_ESP, to deliver a world-class public good to the @ethereum community acting to secure the network through participation in staking.

You retain full control over your validators and staked ETH at all times. The Pectra Staking Manager does not control, custody, manage, or interact with your ETH or validator keys – you do.

The goal is to enable the maximum number of participants to take advantage of the Pectra hard fork features for staking.

Including:
- 𝗘𝗮𝗿𝗻 𝗠𝗼𝗿𝗲 𝗥𝗲𝘄𝗮𝗿𝗱𝘀: Put idle ETH to work on your validator by not having to wait for another 32 ETH as well as harness the auto-compounding benefits of Pectra.
- 𝗚𝗮𝗶𝗻 𝗖𝗼𝗻𝘁𝗿𝗼𝗹: Submit partial withdrawals and full exits by triggering them via a Web3 wallet or your preferred custodian with your validator withdrawal address.
- 𝗦𝗰𝗮𝗹𝗲 𝗘𝘁𝗵𝗲𝗿𝗲𝘂𝗺: Instead of managing multiple 32 ETH validators, consolidate your validators into a single validator, up to 2048 ETH, to reduce Ethereum network strain.

To learn more check out our blog: https://t.co/Ftli5SlOyI

[Pier Two @PierTwo_com]

Pier Two is working hard for its customers to prepare for @ethereum's Pectra (Electra + Prague) Hard Fork on 7 May 2025.

A common question we’ve been answering: what does Pectra mean for withdrawals, and therefore ETH liquidity?

So, we thought it would be helpful to set out exactly how ETH withdrawals will work after Pectra.

Covering Partial Withdrawals, estimating how long it takes to receive the ETH back into your non-custodial account, the Sweep Delay and some worked examples of scenario planning.

If you are staking ETH, or planning to, definitely check out our latest article: https://t.co/lXwLDaxphZ