Consensus
58 articles in this topic.
-
Activity Cutoff
How activity cutoff names validator inactivity tolerance before stake is masked out of Yuma Consensus, including the legacy fixed-block hyperparameter and the live activity cutoff factor setting under dynamic tempos.
-
Activity Cutoff Factor
How the activity cutoff factor subnet hyperparameter expresses validator inactivity tolerance in per-mille epochs so the effective window scales with tempo.
-
Alpha High
How alpha high sets the upper bound of the liquid alpha range that varies how quickly validator-miner bonds smooth based on consensus alignment.
-
Alpha Low
How alpha low sets the lower bound of the liquid alpha range that varies how quickly validator-miner bonds smooth based on consensus alignment.
-
Alpha Sigmoid Steepness
How the alpha sigmoid steepness subnet hyperparameter shapes how sharply liquid alpha responds to validator consensus alignment when smoothing validator-miner bonds in Yuma Consensus.
-
Bonds Moving Average
How the bonds moving average subnet hyperparameter configures the moving-average smoothing applied to validator-miner bonds in Yuma Consensus.
-
Bonds Penalty
How the bonds penalty subnet hyperparameter sets the magnitude of the consensus penalty applied when validator weights exceed the subnet consensus benchmark in Yuma Consensus.
-
Collusion
How colluding validators could try to skew Bittensor consensus toward favored miners, and why consensus clipping and stake weighting resist it.
-
Commit Reveal
How Commit Reveal delays visibility of validator weight signals so recently produced weights are less useful for copying.
-
Commit Reveal Period
How the commit reveal period subnet hyperparameter sets how many tempos must elapse before committed validator weights are revealed under the commit-reveal weight scheme.
-
Commit Reveal Weights Enabled
How the commit reveal weights enabled subnet hyperparameter turns on the commit-reveal weight scheme that conceals validator weights before reveal.
-
Committing Weights Too Fast
How the CommittingWeightsTooFast error signals that a validator retried a weight commit before the required commit-reveal pacing interval had elapsed.
-
Consensus Score
How Yuma Consensus uses a consensus score to filter outlier validator weights before final rank results.
-
Consensus-Based Weights
How liquid alpha adjusts Bittensor validator-miner bond smoothing according to consensus alignment.
-
Delegation
How delegation names staking TAO to a validator to support validator stake and subnet consensus context.
-
Dividends
How dividends describe the validator-side emission result produced from bonds and miner incentives in Bittensor.
-
Drand Time-Lock Encryption
How Drand time-lock encryption supports delayed validator-weight visibility in Bittensor Commit Reveal.
-
EMA
How an exponential moving average smooths values over time by weighting recent observations more heavily, the technique Bittensor uses to update validator-miner bonds across epochs.
-
Epoch
How an epoch marks a Bittensor subnet's consensus period.
-
Exponential Moving Averages
How exponential moving averages smooth Bittensor flow, bond, and reward signals across repeated updates.
-
Incentive Compatibility
How Bittensor aims to make honest, high-quality contribution the most profitable strategy for miners and validators, so self-interest serves the subnet.
-
Incorrect Weight Version Key
How the IncorrectWeightVersionKey error signals that a validator submitted weights with a version lower than the subnet's required weights version key.
-
Kappa
How the kappa subnet hyperparameter sets the stake-weighted majority ratio Yuma Consensus uses to derive the consensus clipping threshold for miner weights.
-
Last Update
How the last update value records the block of a neuron's most recent update, and how it combines with activity cutoff to decide whether the neuron is active.
-
Liquid Alpha
How liquid alpha varies validator-miner bond EMA smoothing by pair within consensus-based weights.
-
Liquid Alpha Enabled
How the liquid alpha enabled toggle decides whether a subnet uses a single fixed bond-smoothing alpha or a consensus-driven alpha that varies between the alpha low and alpha high bounds.
-
Mechanism Count
How the mechanism count subnet hyperparameter sets how many incentive mechanisms a Bittensor subnet runs.
-
Min Allowed Weights
How the min allowed weights subnet hyperparameter sets the fewest weights a validator must assign when it submits weights on a subnet.
-
Miner Incentive
How miner incentive names the emission share Bittensor miners receive for their work in a subnet.
-
Owner Hyperparam Rate Limit
How the owner hyperparam rate limit sets the cooldown a subnet owner must wait between hyperparameter changes, measured as a multiple of the subnet's tempo.
-
Rank
How rank summarizes consensus-adjusted miner evaluation in Bittensor subnets.
-
Relative Stake Weight
How relative stake weight describes a validator's proportional stake-based influence inside a Bittensor subnet.
-
Self-Weighting
How a lone validator inflating weights for its own miners is blunted by Bittensor's stake-weighted consensus, which clips weights that depart from the broader agreement.
-
Setting Weights Too Fast
How the SettingWeightsTooFast error signals that a validator retried weight submission before the subnet's required weights-rate-limit interval had elapsed.
-
Stake
How stake names the token amount associated with a validator position inside a Bittensor subnet.
-
Stake Weight
How stake weight describes validator influence inside Bittensor subnet consensus.
-
Staking
How staking names the process of attaching TAO support to a validator in Bittensor's subnet consensus context.
-
Subjective Evaluation
How Bittensor scores work that has no single objective answer by treating stake-weighted validator consensus as the accepted standard of quality.
-
Subnet Hyperparameters
How Bittensor subnet hyperparameters shape subnet timing, weight flow, consensus behavior, and emission handling without defining the subnet task itself.
-
TAO Weight
How TAO weight sets the relative role of TAO stake when Bittensor derives validator stake weight inside a subnet.
-
Tempo
How Bittensor subnets use tempos as block-based intervals for reward distribution, weight processing, and subnet timing.
-
Time-Lock Encryption
How time-lock encryption lets Bittensor validators commit weights that cannot be decrypted until a future point, underpinning the commit-reveal weight scheme.
-
Trust
How Bittensor uses trust to describe miner-side support after consensus clipping.
-
UID
How UID names the unique identifier assigned to each participant in a Bittensor subnet.
-
Validator Dividend
How validator dividend names the emission share Bittensor validators receive for their consensus role.
-
Validator Trust
How Bittensor uses validator trust to describe validator influence after consensus clipping.
-
Validator Weights
How validator weights express subnet miner evaluations before Yuma Consensus filters and aggregates them.
-
Validator-Miner Bonds
How validator-miner bonds connect validator evaluation to smoothed subnet consensus outcomes.
-
Weight Copying
How copied validator weight information weakens independent miner evaluation in Bittensor consensus.
-
Weight Matrix
How Bittensor groups validator weight vectors as structured input for Yuma Consensus.
-
Weight Setting
How weight setting names the validator process of scoring miners in Bittensor subnets.
-
Weight Vector
How a weight vector represents one validator's miner evaluations before subnet consensus.
-
Weights Rate Limit
How the weights rate limit subnet hyperparameter sets the minimum block wait between validator weight commits on a Bittensor subnet.
-
Weights Version Key
How the weights version key subnet hyperparameter requires a validator's set_weights call to meet a minimum version before it is accepted.
-
Yuma Consensus
An explanation of Yuma Consensus, the Bittensor mechanism that aggregates validator weights into miner incentives and validator dividends.
-
Yuma Consensus 3
How Yuma Consensus 3 refines Bittensor validator-miner bonding so earlier, independent evaluations can be reflected more fairly.
-
Yuma Version
How the yuma version subnet hyperparameter selects whether a subnet runs Yuma Consensus v2 or v3 when processing validator weights.
-
Yuma3 Enabled
How the yuma3 enabled toggle, documented as YumaVersion, lets a subnet switch its consensus mechanism between Yuma Consensus v2 and v3.