Ethereum Deposit Contract Draft Allows for Quantum-Resistant Keys

Ethereum (ETH) developers have submitted a draft to change the validator deposit contract structure to accommodate quantum-resistant key formats. While the staking method will not change immediately, this proposal aims to lay the groundwork for a long-term replacement of the BLS-based validator key system.

The PR #12235 in the Ethereum EIPs repository was posted on August 24 under the title "Post-quantum-ready deposit contract." The status is draft, and there is a suggestion in the GitHub editor comments to rename the file to eip-8394, but the formal adoption of the EIP number and its effective date have not been determined.

The key point is to change the fixed-length public key and signature data submitted by validators when participating in staking to a variable length. Currently, the Ethereum consensus specification requires a 48-byte public key and a 96-byte signature in the deposit function. This structure is aligned with the BLS12-381 format.

The new draft focuses on broadening the deposit path to accommodate future key formats and metadata. Post-quantum signatures may typically result in larger data sizes compared to existing signatures, indicating a need for a more flexible format at the validator entry stage.

Decrypt reported that this draft is designed to allow keys and credential metadata to be received up to a maximum of 8192 bytes each. It also explained that the contract mode includes a mechanism to permanently suspend BLS deposits. However, the contract address, deployment code, and activation time have not been determined.

The official Ethereum documentation states that after the transition to proof of stake, validator keys will be used separately, and the validator's public key will be included in the deposit data. Validator keys are used for block proposals and proofs. Changes to the deposit contract are not merely a screen redesign but a redesign of the entry point for new validators into the network.

EIPs are documents proposing standards and changes for the Ethereum network. For a core EIP to be applied to the actual network, it must go through a process that includes public discussion, specification confirmation, client implementation, and network upgrades. The fact that this PR is in the draft stage indicates that it is at the beginning of this pathway.

This draft does not immediately complete quantum-resistant staking. It merely creates a pathway for new keys without specifying which post-quantum signature algorithm will be used. Signature verification, validator state representation, duplicate handling, and key replacement methods will require separate protocol upgrades.

The PR author also indicated that they are awaiting processing directions related to EIPs 7251, 8282, and 7002. This suggests that issues such as validator balances, withdrawals, forced exits, and key management need to be organized in conjunction with adjacent EIPs.

The official Ethereum post-quantum roadmap suggests changing the consensus layer BLS signatures to leanXMSS and compressing larger signatures to leanVM. The official document defines this schedule as a planning goal rather than a firm commitment, stating that the target for completing the core post-quantum infrastructure is around 2029.

The Post-Quantum Ethereum page also describes this transition as a multi-stage process. The pathway leads from PQ key registry, PQ signature verification precompiles, PQ proofs, to full PQ consensus. This deposit contract draft is more like a piece that opens the entry point for the consensus layer in the overall transition.

Concerns about standardization risks have also been raised within the technical community. In discussions among Ethereum Magicians, there were worries that wallets, apps, and account implementations, as well as future EIPs, could diverge into different cryptographic interfaces. It has been pointed out that aligning implementation standards is as important as algorithm selection.

Other pathways addressing the same issues are also being discussed. The EIP-8222 "Lean Staking" discussion proposed a two-tier staking structure that separates deposits from validator key exposure. This indicates that the approach to changing the validator entry structure has not been narrowed down to a single method.

Public reactions are still primarily centered around the technical community. Discussions are focused more on how to align post-quantum transition plans and cryptographic interfaces rather than immediate market reactions that might affect prices or trading volumes. This trend is being interpreted as an issue of long-term protocol design rather than short-term investment material.

For Korean readers, this issue is closer to infrastructure risk management than short-term price material. The fact that Ethereum is moving discussions on post-quantum security and cryptographic design into the roadmap aligns with previous design discussions. This deposit contract draft is a proposal to make the validator entry point more flexible within that flow.

The currently confirmed stage is the submission of the draft. The existing validator signature system will not be replaced immediately, and actual implementation will require a fork that adjusts both the execution layer and the consensus layer along with a separate EIP.