Ethereum proposal could change staking deposits for future validator keys

Ethereum developers opened an early draft to make staking deposits compatible with future validator-key formats. The draft could allow a later network upgrade to permanently reject new deposits using the current BLS format. Pull request #12235 opened on Aug. 24 and remained an unmerged Draft as of Aug. 26. The working file still uses placeholder number 9999. An Ethereum EIPs editor suggested number 8394, but the proposal has not been published or accepted as EIP-8394. The current deposit path expects public keys and signatures in fixed BLS12-381 formats. The draft adds a scheme identifier and variable-length fields for public keys and credential metadata. Each field would have an 8,192-byte limit. The execution layer would record deposits. The consensus layer would decide whether each credential is valid and could create or update a validator. The contract would carry non-BLS credentials as opaque data without checking their cryptography. The draft defines disabled, BLS enabled, and BLS retired modes. The modes can move only forward. A protocol-controlled system call would activate BLS retired mode. The contract would then reject new BLS deposits and could not restore BLS onboarding. Deposits that entered the pending queue before the retirement boundary would remain eligible for normal processing under the current consensus framework. A separate credential-scheme proposal would still need to define signature validation, validator-state representation, top-ups, duplicate handling, uniqueness, and key replacement. Activating the deposit path would require a coordinated execution-layer and consensus-layer fork. Ethereum's post-quantum roadmap pairs the hash-based leanXMSS validator signature scheme with leanVM. leanVM is intended to aggregate larger post-quantum signatures efficiently. The roadmap separates key registration, signature verification, attestations, and full aggregation into staged milestones. Ethereum says no quantum computer can threaten its cryptography today. Its approximately 2029 target is a planning goal.