Validation
43 articles in this topic.
-
Axon
How axon names the server-side endpoint in Bittensor subnet request and response communication.
-
Blockchain Validator vs Subnet Validator
How Bittensor distinguishes network-level blockchain validators from subnet-level validators.
-
Bonds Reset Enabled
How the bonds reset enabled subnet hyperparameter decides whether validator-miner bonds for a hotkey can be cleared, with resets triggered through metadata commitment.
-
Child Hotkey
How a child hotkey lets a parent hotkey re-delegate stake so the child validates on the parent's behalf on a subnet, without transferring ownership.
-
Child Hotkeys
How a Bittensor delegate validator authorizes child hotkeys to validate on its behalf in a selected subnet, and how child take works.
-
Childkey Take
How childkey take describes the subnet-specific share of dividends a child hotkey keeps when it validates on behalf of a parent hotkey.
-
Commit Reveal
How Commit Reveal delays visibility of validator weight signals so recently produced weights are less useful for copying.
-
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.
-
Dendrite
How dendrite names the client-side request component used with axons in Bittensor subnet communication.
-
Digital Commodities
How Bittensor subnets define useful digital work for miners to produce and validators to evaluate.
-
Duplicate Uids
How the DuplicateUids error signals that a set_weights call repeated the same UID more than once in its uid list.
-
Invalid IP Type
How the InvalidIpType error signals that a serve_axon or serve_prometheus call used an IP version other than IPv4 or IPv6.
-
Invalid Port
How the InvalidPort error signals that a serve_axon or serve_prometheus call submitted a port value the runtime rejects as not a usable network port.
-
Invalid Reveal Commit Hash Not Match
How the InvalidRevealCommitHashNotMatch error signals that a reveal_weights call submitted a hash the runtime could not pair with any non-expired committed hash for the caller.
-
Liquid Alpha
How liquid alpha varies validator-miner bond EMA smoothing by pair within consensus-based weights.
-
Max Validators
How the max validators subnet hyperparameter caps how many validators a subnet allows, which bounds how many validator permits it issues.
-
Mining and Validating in Bittensor
A factual overview of how miners produce subnet work, validators evaluate that work, and consensus turns validator signals into subnet emissions.
-
Off-Chain Validation Systems
How off-chain validation systems describe subnet-specific miner evaluation before Bittensor consensus uses validator weight signals.
-
Root Validator
How a root validator names the validator role on the Root Subnet, where TAO stake is not tied to one mining subnet.
-
Stake Threshold
How the global stake threshold root parameter sets the minimum stake weight a neuron needs before it can be considered for a validator permit during the epoch.
-
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
How a Bittensor subnet organizes a specialized market for digital work, miner production, and validator evaluation.
-
Subnet Creator
How a subnet creator defines the work and evaluation context for a Bittensor subnet.
-
Subnet Miner
How a subnet miner performs the work a Bittensor subnet asks validators to evaluate.
-
Subnet Protocol
How a subnet protocol defines the interaction rules between miners and validators.
-
Subnet Scoring Model
How a subnet scoring model defines validator evaluation of miner responses inside a Bittensor subnet.
-
Subnet Task
How a subnet task defines the work miners produce and validators evaluate in Bittensor.
-
Subnet Validator
How a subnet validator evaluates miner work inside a Bittensor subnet.
-
Synapse
How synapse names the structured message object exchanged through Bittensor subnet communication.
-
Trust
How Bittensor uses trust to describe miner-side support after consensus clipping.
-
UID Vec Contain Invalid One
How the UidVecContainInvalidOne error signals that a set_weights submission named at least one UID that does not exist on the target subnet.
-
Validator Deregistration
How validator deregistration removes a low-performing Bittensor subnet validator from a UID slot when subnet capacity and registration rules require replacement.
-
Validator Permit
How a validator permit marks validation rights inside a Bittensor subnet.
-
Validator Registration
How validator registration names the process that gives a Bittensor subnet validator a UID slot after registering a hotkey with that subnet.
-
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.
-
VPermit
How VPermit represents the subnets where a delegate is authorized to validate.
-
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 Vec Not Equal Size
How the WeightVecNotEqualSize error signals that a set_weights call's uid list and value list did not have matching lengths.
-
Weight Vector
How a weight vector represents one validator's miner evaluations before subnet consensus.
-
Yuma Consensus 3
How Yuma Consensus 3 refines Bittensor validator-miner bonding so earlier, independent evaluations can be reflected more fairly.