Drand
#26Distributed randomness beacon integration
Part of Consensus & Finality: Block production, finality, and chain security
The Drand beacon configuration used for verifying randomness pulses.
Emitted when the Drand beacon configuration has been updated.
The offchain worker failed to connect to the Drand beacon API.
Tracks whether specific migrations have been executed.
Maximum milliseconds to wait for HTTP requests to the Drand beacon.
The pulse round number is invalid or out of expected sequence.
The most recent Drand round number stored on-chain.
Emitted when a new randomness pulse has been successfully verified and stored.
The block number when the next unsigned pulse transaction will be accepted.
A required value was not found in storage when expected.
The oldest Drand round number retained in storage.
Verified randomness pulses from the Drand beacon, keyed by round number.
An error occurred during the pulse verification process.
Updates the Drand beacon configuration used for pulse verification.
Sets the oldest round number that the chain will retain in storage.
Emitted when the oldest stored round boundary has been updated.
An internal counter would exceed its maximum value (u32::MAX).
Base priority for unsigned Drand pulse transactions in the transaction pool.
The submitted Drand pulse failed cryptographic verification.
Submits and verifies a Drand randomness pulse to be stored on-chain.