web3wagmi
← All standards

EIP-8321 Hash-Chain RANDAO

DraftCorecreated 2026-07-05requires EIP-7916

Replace the BLS-signature RANDAO reveal with a post-quantum hash-chain commit-reveal scheme

Authors: Kevaundray Wedderburn (@kevaundray), Benedikt Wagner (@benedikt-wagner), Tom Wambsgans (@TomWambsgans), Justin Drake (@JustinDrake), Thomas Coratger (@tcoratger)

Depends on (1)

Proposals this one names in its requires field.

EIP-7916SSZ ProgressiveList

What the specification covers

AbstractMotivationSpecificationCryptographic FunctionsConstantsPresetHash Chain Construction (Off-Chain)Chain ExhaustionContainersNew ContainersModified ContainersBlock ProcessingModified process_randaoModified process_operationsNew process_randao_commitment_registrationNew queue_randao_commitmentEpoch ProcessingNew process_pending_randao_commitmentsGossipFork TransitionSunset of the Legacy PathRationaleWhy a Hash Accumulator on the Hash-Chain PathWhy BLAKE3 Instead of the Consensus hashWhy One Link per Block ProposedWhy the Protocol Does Not Track Chain LengthWhy an Activation Delay on Registration, and Why MIN_SEED_LOOKAHEAD + 2Why at Most One Pending Registration per ValidatorWhy Registration Is One-Time, and Replay-SafeWhy Keep a Legacy Fallback Instead of a Registration DeadlineBackwards CompatibilityTest CasesSecurity ConsiderationsBiasability Is UnchangedRegistration Cannot Be Used ReactivelyDegenerate ChainsChain Loss and TheftReveal Exposure in Orphaned BlocksErroneous CommitmentsQuantum AdversariesDenial of Service via RegistrationsCopyright

This proposal declares no Solidity interface, so there is nothing to compute. It may be a core protocol change, a meta proposal, or written in prose only.

Compare with

Parsed from the canonical specification · discussion