Drand Time-Lock Encryption
Drand time-lock encryption helps Bittensor Commit Reveal keep newly submitted validator weights concealed until a later reveal round. In the commit-then-reveal flow, validators commit weight information before it becomes readable, reducing the usefulness of copied public weights (Commit Reveal, Glossary: Drand/time-lock encryption).
The term belongs to timing and visibility. It explains when committed validator-weight information can be read, while validator weights and Yuma Consensus explain how revealed evaluations are used after the delay (Glossary: Validator Weights, Yuma Consensus).
Delayed Visibility
Delayed visibility matters because validator weights are valuable consensus inputs. A validator that can simply reuse public weight signals adds less independent evaluation to a subnet (The Weight Copying Problem).
Commit Reveal reduces that copying window by separating submission from later readability. The validator commits information first, and the readable weight information appears later in the reveal part of the process (Commit Reveal).
That delay is useful because the valuable signal is the fresh validator evaluation, not a public copy of another validator’s recent weights. Drand time-lock encryption is the timing tool that helps preserve that delay.
Drand Round Timing
Time-lock encryption binds access to a later round instead of immediate decryption. Encrypted data becomes decryptable only after a future Drand round (Glossary: Drand/time-lock encryption).
The Drand round supplies the timing reference. Before that round, the committed weight information stays concealed; after the relevant round, the reveal process can make the information readable.
This makes the phrase more specific than generic encryption. The important feature is delayed readability tied to a future Drand round, not merely that the data was encrypted.
Commit Reveal
Commit Reveal uses concealed weight submission before later reveal. Drand time-lock encryption fits that process as the timing layer: committed weight data remains unreadable until the target round, then the revealed information can enter the consensus flow (Commit Reveal, Glossary: Drand/time-lock encryption).
That placement keeps the concept narrow. Commit Reveal is the broader commit-then-reveal process; Drand time-lock encryption is the delayed-readability tool used inside that process.
Consensus Role
Drand time-lock encryption controls when concealed weight information becomes readable; it does not score miners or allocate emissions. After reveal, validator evaluations enter the Yuma Consensus aggregation process for miner incentives and validator dividends (Yuma Consensus, Commit Reveal).
The delayed-visibility layer protects inputs before that aggregation step. Once the weights are revealed, nearby terms such as validator weights, rank, incentives, and dividends describe the consensus and emission path.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For Drand time-lock encryption, that sequence changes how readers should interpret concealed commit payloads and reveal-round timing examples.
In localnet, time-lock concealment can be tested in an isolated environment. Localnet Drand round references do not represent production commit-reveal behavior.
On testnet, concealed weight submission can be exercised in a shared non-production network. Testnet reveal timing is separate from mainnet subnet state.
On mainnet, Drand time-lock encryption applies as a live timing layer on production subnets using commit reveal. Observed concealment intervals depend on the selected subnet’s reveal settings and the Drand round schedule (Commit Reveal).
The Bittensor Networks reference separates mainnet, testnet, and localnet. A time-lock example from one environment should not be read as representing production weight concealment in another environment.
Relationship to Yuma Consensus
Drand Time-Lock Encryption and Yuma Consensus describe related parts of Bittensor’s incentive system. Yuma Consensus is the on-chain process that aggregates validator weight signals within a subnet into miner incentives and validator dividends, applying consensus clipping, bonding, and emission calculation (Yuma Consensus).
For readers, drand time-lock encryption names a specific part of that incentive picture, while Yuma Consensus names the consensus process that turns validator weights into the resulting incentives and dividends.
Reader Boundary
Drand time-lock encryption should not be read as a separate consensus algorithm, a miner scoring method, or an emission allocator. It names a timing and visibility tool that delays readability of committed validator-weight information until a future Drand round (Glossary: Drand/time-lock encryption, Commit Reveal).
The term belongs beside Commit Reveal and weight-copying protection. Validator weights and Yuma Consensus explain how revealed evaluations are used after the concealment interval ends (Glossary: Validator Weights, Yuma Consensus).
Concealed Weights Stay Out of Yuma Until Reveal
Committed weights remain encrypted on chain during the concealment interval and therefore do not enter Yuma Consensus until reveal completes (Commit Reveal, Yuma Consensus).
That timing boundary is different from merely hiding scores from observers. Concealed commitments are excluded from aggregation until they become readable validator-weight inputs.
Drand Rounds Supply the Delay Reference
Time-lock encryption binds decryption to a future Drand round rather than immediate access. Before that round, committed weight information stays concealed; after reveal, the weights can enter the consensus flow for the relevant epoch (Glossary: Drand/time-lock encryption, Glossary: Tempo).