Skip to content

What Is Chain Consensus on Bittensor? How Blocks Differ from Yuma

Learn what chain consensus means on Bittensor, how Proof of Authority works today, and why it is different from Yuma Consensus.

Table of Contents

Bittensor uses “consensus” in two different ways, and confusing them can make the network seem more complicated than it is.

At the chain layer, consensus decides who produces blocks and when those blocks are final. At the subnet layer, Yuma Consensus helps decide how miner evaluations become rewards. Those are related parts of the broader Bittensor system, but they do not do the same job.

This guide explains what chain consensus means on Bittensor today, why Subtensor currently uses Proof of Authority, how that differs from Yuma Consensus, and why holding TAO or running a node does not automatically make someone a block-producing authority.

Why Bittensor Has Two Consensuses

Bittensor has two different consensus contexts because it has two different coordination problems.

Chain consensus keeps the blockchain ordered. It determines which blocks are produced, which version of the chain is accepted, and when blocks become final. Yuma Consensus operates inside Bittensor’s subnet economy, where subnet validators evaluate miners and those evaluations are turned into incentives.

TermWhere It AppliesWhat It Decides
Chain ConsensusSubtensor BlockchainWho Produces Blocks And When They Are Final
Yuma ConsensusBittensor SubnetsHow Miner Evaluations Help Determine Rewards

What Subtensor Does

Subtensor is the blockchain that coordinates Bittensor.

The chain records network participation, handles TAO, tracks subnet activity, and coordinates the incentive system. The useful work itself happens off-chain inside subnets, where miners perform tasks and subnet validators evaluate them. Bittensor’s network documentation describes Subtensor as a Substrate-based chain that produces one block about every 12 seconds.

Finney is the name of Bittensor’s mainnet. For a reader trying to understand consensus, the important point is not how to connect to Finney, but what Finney is coordinating: a chain layer that orders transactions and a subnet layer where machine intelligence and other digital work are evaluated.

That is why Bittensor can talk about consensus in two places. The blockchain needs consensus to order blocks, and subnets need a mechanism to turn validator judgments into reward shares.

What Chain Consensus Does

Chain consensus is the process that lets Subtensor agree on the state of the blockchain.

It answers questions such as:

  • Which transactions are included in the next block?
  • Which authority is allowed to author that block?
  • When is a block final enough that the network treats it as irreversible?
  • Which chain should nodes follow if there is a temporary fork?

On Bittensor today, chain consensus is not decided by Yuma Consensus, subnet miners, or TAO holders voting on each block.

Instead, Subtensor currently uses a Proof of Authority model in which an approved set of authorities produces and finalizes blocks. Other nodes can still verify the chain, relay data, and provide RPC services, but that does not make them block authors.

How Blocks Are Produced and Finalized Today

Subtensor’s current chain consensus has two main layers: block production and finality.

LayerCurrent MechanismRole
Block ProductionAuraAssigns Block-Production Slots To Members Of The Authorized Validator Set
Block FinalityGRANDPAFinalizes The Chain After More Than Two-Thirds Of Authority Voting Weight Agrees

Aura handles block production by assigning slots to members of the authorized validator set. GRANDPA handles finality by finalizing a chain after more than two-thirds of authority voting weight agrees. Once GRANDPA finalizes blocks, those blocks are irreversible under the protocol’s finality rules.

This is the chain-level meaning of “consensus” on Bittensor today. It is about block production, ordering, and finality.

It is also why “validator” can be a confusing word in Bittensor. A chain authority that participates in Aura and GRANDPA is not the same thing as a subnet validator that scores miners. Both words appear in the ecosystem, but they refer to different roles depending on the context.

Who Can Author a Block

Only approved authorities can author blocks or vote on finality in Subtensor’s current Proof of Authority design.

Running a node, holding TAO, or exposing an RPC endpoint does not automatically add someone to that authority set.

A non-authority node can still be useful. It can verify chain data, relay blocks and transactions, serve applications, and help users interact with the network. But under the current model, it does not produce blocks unless it is part of the approved authority set.

The authority set can be changed through privileged on-chain administration. That permissioned selection is the reason the current chain-level mechanism is classified as Proof of Authority. For readers interested in the broader governance and stewardship picture, read our guide to who controls Bittensor:

Who Controls Bittensor?
Bittensor has no single owner. Protocol keys, code repos, validators, subnet owners, and TAO holders each control a different layer.

Does Holding TAO Secure Block Production?

Holding or staking TAO does not currently make someone a chain block producer.

TAO stake matters deeply in Bittensor’s subnet economy, especially for validator weight, permits, incentives, and emissions. But that is different from joining the chain authority set that authors and finalizes blocks.

In other words, staking TAO can affect subnet validator influence, but it does not automatically give the staker a role in Aura block production or GRANDPA finality.

Bittensor has subnet validators that evaluate miner work, and it has chain authorities that participate in block production and finality. Those roles are not interchangeable.

For a deeper explanation of subnet-side validator influence, read our stake weight explainer guide:

What Is Stake Weight on Bittensor? Alpha, Root TAO, and Validator Power
Learn what stake weight means on Bittensor, how alpha stake and root TAO combine through tao_weight, and why it matters for validator permits and Yuma Consensus.

Is Bittensor Moving to Proof of Stake?

Bittensor’s current roadmap is to replace Proof of Authority with Nominated Proof of Stake, but that transition has not been activated on-chain.

Under Nominated Proof of Stake, nominators support validator candidates, and the active validator set is selected from that stake-backed support. That would make the chain-authority selection process different from today’s permissioned Proof of Authority model.

The caveat is timing. The current documentation describes the target as roughly within the next year, but also frames that as a planning estimate rather than a fixed activation date. Implementation details and timing may change before the transition goes live.

Until the transition is activated on-chain, Subtensor remains a Proof of Authority network at the chain layer.

That means readers should avoid saying “Bittensor is proof of stake today” when referring to chain consensus. A more accurate phrasing is that Bittensor currently uses Proof of Authority for chain consensus and has a planned transition toward Nominated Proof of Stake.

How This Differs From Yuma Consensus

Yuma Consensus does not produce blocks or finalize the Bittensor blockchain.

Yuma Consensus is the subnet-level mechanism that aggregates subnet validators’ evaluations of miners and helps determine incentives. It is part of how Bittensor turns subjective evaluations of useful work into reward signals. That is why Yuma is central to miner rewards, subnet competition, and validator behavior, but not to chain finality.

A simplified version looks like this:

  1. Miners perform work inside a subnet.
  2. Subnet validators evaluate that work by setting weights.
  3. Yuma Consensus aggregates those evaluations in a stake-weighted way.
  4. The result helps determine how rewards are allocated inside the subnet economy.

That mechanism is separate from Aura and GRANDPA. Aura and GRANDPA decide chain block production and finality. Yuma Consensus helps decide subnet incentives.

What Chain Consensus Is Not

Chain consensus is not the Senate. It is not the Triumvirate. It is not subnet-owner hyperparameter control. It is not Dynamic TAO emission routing. It is not Yuma’s clipping logic, kappa threshold, validator permits, or reward math.

Those topics matter, but they answer different questions.

The Senate and related governance structures concern protocol stewardship and decision-making. Subnet owners manage subnet-specific parameters and incentive design. Dynamic TAO affects how emissions are routed across the subnet economy. Yuma Consensus affects how subnet validator evaluations become rewards.

Chain consensus answers a narrower question: how the Subtensor blockchain produces and finalizes blocks.

Why The Distinction Matters

The difference between chain consensus and Yuma Consensus shapes how readers understand Bittensor’s architecture.

If someone thinks Yuma finalizes blocks, they may misunderstand what subnet validators actually do. If someone thinks staking TAO automatically makes them a chain validator, they may misunderstand the current Proof of Authority model. If someone assumes Bittensor is already Nominated Proof of Stake, they may describe the live network inaccurately.

A cleaner model is this:

  • Subtensor is the blockchain coordination layer.
  • Proof of Authority currently orders and finalizes the chain.
  • Aura handles block-production slots.
  • GRANDPA handles finality.
  • Yuma Consensus aggregates subnet validator evaluations into incentive signals.
  • TAO stake affects subnet-side weight and rewards, not automatic membership in the chain authority set.

This keeps the two meanings of consensus separate without requiring a full Substrate course.

Conclusion

Bittensor uses “consensus” in two places because the network has both a blockchain coordination layer and a subnet incentive layer.

At the chain layer, Subtensor currently uses Proof of Authority. Aura assigns block-production slots to approved authorities, and GRANDPA finalizes blocks after more than two-thirds of authority voting weight agrees. Holding TAO, running a node, or serving RPC does not automatically make someone part of that block-authoring set.

At the subnet layer, Yuma Consensus helps turn subnet validators’ miner evaluations into rewards. It is essential to Bittensor’s incentive system, but it does not produce or finalize blocks.

Keeping those two meanings separate makes Bittensor easier to understand: chain consensus keeps the blockchain ordered, while Yuma Consensus helps the subnet economy decide who contributed useful work.

FAQs

Does Yuma Consensus Produce Blocks?

No. Yuma Consensus does not produce or finalize blockchain blocks. It aggregates subnet validators’ evaluations of miners and helps determine reward shares inside Bittensor’s subnet economy.

What Consensus Does Bittensor Use Today?

At the chain layer, Subtensor currently uses Proof of Authority. Aura handles block-production slots, and GRANDPA handles finality after more than two-thirds of authority voting weight agrees.

Is Bittensor Proof Of Stake Today?

Not at the chain layer. Bittensor’s current chain consensus is Proof of Authority, with a planned transition to Nominated Proof of Stake. Until that transition is activated on-chain, Subtensor remains a Proof of Authority network.

If I Stake TAO, Am I Securing Block Production?

No, not by joining the chain authority set. TAO stake affects subnet-side validator weight and emissions, but it does not automatically make the staker a block-producing chain authority under the current Proof of Authority model.

If I Run A Subtensor Node, Can I Author Blocks?

Only if the node is part of the approved authority set. Other nodes can verify the chain, relay blocks and transactions, and expose RPC services, but they do not author blocks merely by running.

What Is Subtensor?

Subtensor is the blockchain that coordinates Bittensor. It records participation, handles TAO, coordinates subnet activity, and produces blocks on the Finney mainnet.

What Finalizes A Bittensor Block?

GRANDPA finalizes blocks after more than two-thirds of authority voting weight agrees. Yuma Consensus does not finalize blocks, and subnet epochs are not the same thing as chain finality.

Why Are There Two Types Of Validators In Bittensor?

The word “validator” can refer to different roles. Chain authorities participate in block production and finality. Subnet validators evaluate miners inside subnets and influence rewards. The context determines which role is being discussed.

Financial Disclaimer

This article is for educational purposes only and should not be taken as financial, investment, legal, or tax advice. Digital assets, staking, and blockchain networks involve risk. Readers should do their own research before making decisions involving TAO or any crypto asset.

Comments

Latest