Ethereum sets 2029 quantum target as Hegotá takes shape

Ethereum has set a December 2029 target for a quantum-resistant Layer 1 while moving Frame Transactions toward Hegotá and developing execution proofs, privacy tools and a new consensus design.

The Ethereum Foundation’s Protocol Cluster laid out the deadline in its Sept. 7 priorities update, then researchers addressed the roadmap during the Sept. 16 EF Protocol AMA on Reddit. The Foundation said its post-quantum work must cover Ethereum’s execution, consensus and data-availability systems, while several technologies discussed in the AMA remain research proposals or individual researcher views instead of finalized network changes.

EF Protocol has committed to making the Ethereum Layer 1 post-quantum across all three protocol layers by December 2029. Its published plan treats a possible cryptographically relevant quantum computer by 2030 as an aggressive planning assumption, even though the Foundation says most estimates place such a threat later. The cluster called the 2029 deadline “non-negotiable” at least until January 2027, when outside experts are expected to help reassess quantum progress.

Execution accounts form one part of the migration. Ethereum currently relies heavily on elliptic-curve signatures, while the future system needs accounts that can replace their authentication method without waiting for a new hard fork every time cryptographic standards change. Consensus has a separate problem because validator signatures and aggregation are embedded more deeply in protocol rules, requiring dedicated hard-fork work. Data availability must eventually move away from cryptographic dependencies that do not satisfy the post-quantum target.

As crypto.news reported in its coverage of the roadmap, Ethereum’s 2029 plan now places quantum safety among Protocol’s central delivery commitments rather than treating it solely as distant research. Ethereum targets quantum-resistant L1 by 2029

The Foundation has cautioned that core-protocol changes do not automatically protect everything built around Ethereum. Wallets, custody systems, bridges, rollups and applications can retain classical cryptographic dependencies even after Layer 1 changes. The Sept. 16 AMA raised that migration problem directly, including questions about how external systems should identify and replace vulnerable cryptography before the core deadline.

Frame Transactions give Ethereum accounts cryptographic flexibility

EIP-8141, known as Frame Transactions, is now scheduled for inclusion in Hegotá. The draft separates transaction validation, execution and gas payment into programmable frames, allowing an account to define how it verifies authorization instead of relying permanently on Ethereum’s existing transaction-signature model.

The design supports key rotation, sponsored gas payments, alternative fee arrangements and atomic groups of actions. Its post-quantum role comes from cryptographic agility: an account could adopt a different signature scheme through its own validation logic instead of requiring Ethereum to add one fixed post-quantum signature format for every user.

EF Protocol ranked Frames as an S-tier Hegotá item in September and described it as the execution-layer headliner. The current package pairs EIP-8141 with keyed nonces under EIP-8250 and recent roots under EIP-8272. Protocol researchers said the combination supports privacy use cases and provides part of the route away from secp256k1 master keys.

Frames can let users pay transaction costs through sponsors or tokens while validators continue receiving ETH-denominated network fees. The same structure can group related operations so an approval can be rolled back if the later action fails. Ethereum EIP-8141 could remove the need to hold ETH for gas

The specification remains a draft even though it is scheduled for the fork. Ethereum.org currently lists Hegotá as an upgrade in planning, with Q2 2027 shown as an expected period and no confirmed mainnet date. FOCIL and Frames are the two changes formally scheduled in the Hegotá Meta EIP, while much of the remaining scope is still being selected.

zkEVM work is moving from benchmarks toward optional proofs

Ethereum’s L1-zkEVM work is following a staged route. EIP-8025 proposes optional execution proofs that validators and nodes could generate or consume without changing Ethereum’s consensus validity rules. The mechanism would let teams test proof creation, networking, verification and client integration on the live network before proofs become required for block validity.

The proposal remains in draft status and sits in Hegotá’s proposed-for-inclusion section. EF Protocol nevertheless rated EIP-8025 as an A-tier priority in its September assessment, saying it would move stateless-execution work into Ethereum’s canonical specifications and reduce separate zkVM development branches.

Ethereum’s zkEVM roadmap later moves from optional proofs to mandatory proofs, where validators could verify succinct proofs instead of re-executing every block. EF Protocol says the exact fork ordering is still under review because post-quantum consensus work may be moved ahead of mandatory execution proofs.

Performance has improved, but security work is unfinished. The Ethereum Foundation reported in late 2025 that zkVM systems had reached a stage where 99% of Ethereum blocks could be proven within 10 seconds on its target hardware, after proving times had fallen sharply during development. Its current zkEVM tracker still measures ISA compliance, real-time proving and security readiness separately.

Formal verification has not removed the need for testing. A May EF zkEVM report described how verification work on SP1 Hypercube established mathematical guarantees for parts of its RISC-V implementation but later testing uncovered a JALR issue and other gaps in the verification assumptions. The Foundation said formal claims must state precisely what has been proven and what remains outside the proof.

The Formal Verification team has continued building machine-checked tools. Its August better.codes program uses Lean and ArkLib to test cryptographic soundness claims for hash-based proof systems, while Q2 grants supported verification work on RISC-V zkVM constraints and Ethereum execution tooling.

Privacy and faster finality are being developed across several forks

Privacy sits beside post-quantum work as one of EF Protocol’s multi-fork research programs. The Foundation’s current plan starts with transaction-level tools around Hegotá, including Frames and FOCIL, before pursuing post-quantum privacy and encrypted mempool designs later.

FOCIL is intended to make transaction inclusion less dependent on a single block builder. Combined with programmable accounts and keyed nonces, the design could let privacy applications use Ethereum’s normal transaction pipeline without requiring a dedicated relay for every private operation. Ethereum’s privacy roadmap describes Frames as a way to support privacy-preserving validation and gas abstraction while FOCIL provides an inclusion mechanism.

A separate draft, EIP-8182, had proposed an enshrined private ETH and ERC-20 transfer mechanism. EF Protocol declined it for Hegotá in September, saying the Frames-based route could support privacy without placing one specific privacy system directly into the protocol. The decision does not mean native privacy has been abandoned; it changes the engineering route currently favored by Protocol.

As crypto.news reported in May, Vitalik Buterin had already described account abstraction, FOCIL and keyed nonces as pieces of Ethereum’s privacy work. Vitalik Buterin maps three-step Ethereum privacy upgrade

Finality research is moving on a separate timeline. EF Protocol’s Sept. 7 roadmap names decoupled consensus as the leading candidate for the I* fork after Hegotá. The design separates block availability from the finality mechanism and is intended to reduce finality from minutes toward seconds over successive protocol changes. Specifications and prototypes remain in development.

Quick Slots, which could shorten Ethereum’s current 12-second slot time, has not received the same Hegotá commitment. EF Protocol rated EIP-8198 as B-tier and said it needs a complete specification, implementation, ecosystem assessment and confirmation that it will not interfere with decoupled consensus.

In related coverage, crypto.news reported on Sept. 18 that Ethereum Institutional backed work exploring a reduction from 12-second to 10-second blocks, while noting that EIP-8198 had not been scheduled for inclusion. Ethereum Institutional backs plan to cut block times to 10 seconds

ETH issuance remains a community policy question

The Sept. 16 AMA returned repeatedly to ETH issuance and the size of the staking base. Several questions challenged Ethereum’s existing reward curve and asked whether continued staking growth could create pressure on unstaked ETH holders or concentrate the validator system.

A concrete proposal exists, but it has not been adopted. EIP-8363 proposes a tapered issuance burn that would reduce net validator issuance as the staking ratio increases and cancel consensus issuance at a defined saturation balance close to 50% of ETH supply. The draft proposes an 18-month transition if it were ever activated.

EF Protocol unanimously declined EIP-8363 for the Hegotá scoping process, while explicitly stating that the decision was “not a judgment on the merits.” The cluster said issuance affects every holder, staker and Ethereum’s security budget, so it expects the subject to continue through an ecosystem process instead of being settled by one fork-selection group.

As crypto.news previously reported, the draft would progressively reduce staking issuance as more ETH is staked, but it remains a proposal under discussion and has no approved activation fork. Ethereum proposal could end staking rewards at 50%

The debate therefore differs from Frames, which has a scheduled fork slot. Researcher support for changing issuance represents personal or proposal-level positions until Ethereum’s governance process reaches agreement on an actual specification and upgrade path.

EF’s reorganized teams divide protocol, access and institutional work

The Ethereum Foundation’s June reorganization created five main work clusters: Protocol, Access, User, Community and Institutional, alongside operations and management functions. The Foundation said the restructuring reduced its staff by 54 people, close to 20%, while changing how research, user needs and institutional communication are divided.

Protocol now owns hard-fork delivery and research areas such as post-quantum security, zkEVM and Layer 1 privacy. The Access Layer focuses on areas including transactions, proving, delegation and user control, while the Institutional Layer works with financial institutions, companies, governments, universities and nonprofit organizations.

EF Protocol’s Sept. 7 priorities document says its December 2029 target will require overlapping work across Hegotá, I*, J* and later forks instead of finishing one upgrade before research begins on the next. Client teams, cryptographers, security reviewers and outside researchers are expected to work on multiple stages at once.

The next confirmed protocol checkpoint is Hegotá’s continuing scope process. Frames and FOCIL are scheduled, EIP-8025 remains proposed, and additional candidates must pass specification, prototype and testing requirements before Ethereum developers decide whether they belong in the fork.

FAQs