Dendrite
A dendrite is the client-side component that sends requests to axon endpoints in Bittensor subnet communication (Glossary: Dendrite, Dendrite reference).
The term identifies the request side of the axon-dendrite path. It is separate from the subnet role, subnet task, scoring rule, and chain record that may surround a particular exchange.
Client-Side Role
Bittensor documentation describes Dendrite as a network client for sending requests to axon endpoints and processing responses (Dendrite reference, Glossary: Dendrite).
That makes dendrite a direction and component term. It names the side that contacts an axon, rather than the full validator program, the task being evaluated, or the economic rule that may later use the returned information.
Axon Pairing
Dendrite and axon describe opposite sides of a subnet communication path. Axon is the server-side endpoint that receives incoming synapse objects, while dendrite is the client-side component that sends requests to those endpoints (Glossary: Axon, Axon reference).
The distinction is useful because both terms can appear near validator and miner behavior. Dendrite marks the request side; axon marks the receiving endpoint. Neither term, by itself, explains the subnet’s task design or reward calculation.
Synapse Messages
Subnet communication uses synapse objects for structured information exchange between validators and miners (Glossary: Synapse, Synapse reference).
Dendrite belongs to the path that sends a synapse toward an axon endpoint and handles the response. The synapse carries task-specific content, while dendrite describes the client-side route used for that exchange.
Validator and Miner Context
Dendrite language often appears near subnet validators because validators can use client-side communication to query miner axons. The validator and miner roles remain separate role concepts (Glossary: Subnet Validator, Glossary: Subnet Miner).
A dendrite can participate in validator-side communication, but it does not define validator judgment, miner work, or the incentive mechanism. Those meanings come from the subnet’s protocol, task, and evaluation design.
Protocol Boundary
Different subnets can define different tasks and evaluation standards. Bittensor documentation connects subnet tasks to miner work, and incentive-mechanism documentation places miner work, validator evaluation, and emission outcomes inside subnet-specific mechanisms (Glossary: Subnet Task, Understanding Incentive Mechanisms).
Within that setting, dendrite is a communication component rather than a scoring model. It can help carry request and response material, but the subnet protocol explains what that material means for evaluation.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For dendrite, that sequence changes how readers should interpret request-and-response examples.
A dendrite exchange observed in localnet can test client wiring in isolation. Testnet examples add shared non-production subnet conditions. Mainnet dendrite behavior concerns production validator-to- miner communication on the active network (Bittensor Networks).
An example from one environment should not be treated as proof about endpoint behavior in another.
Relationship to Yuma Consensus
Dendrite 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, dendrite 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
Dendrite does not name a wallet action, a persistent chain record, a validator score, or a guarantee that an endpoint will respond in a particular way (Glossary: Dendrite, Subtensor Storage, Subtensor Events).
Dendrite identifies the client-side request component, while axon, synapse, subnet task, and incentive mechanism references describe neighboring parts of the system.
Dendrite Processes Axon Responses
The Dendrite reference describes Dendrite as a network client that sends requests to axon endpoints and processes the responses it receives. Dendrite vocabulary therefore covers both the outbound request and the returned response handling on the client side.
That keeps dendrite in the communication path only. Response content still belongs to the synapse and subnet task being exchanged, not to dendrite as a scoring label.
Synapse Objects Carry the Request Payload
Subnet communication passes structured synapse objects between validators and miners. Dendrite is the client-side component that routes those objects toward axon endpoints and handles the reply path (Synapse reference).
Readers should attach the synapse type and subnet context when describing what a dendrite exchange contained. Dendrite names the transport component; synapse names the message object.
Relationship to Synapse
Dendrite and synapse are related but different parts of Bittensor subnet communication vocabulary. Synapse names the structured message object passed between validators and miners, while dendrite names the client component that sends and receives those messages during a subnet task (Glossary: Synapse, Glossary: Dendrite).
For readers, synapse is the message-object term and dendrite is the communication-component term. They often appear in the same example, but one names what is exchanged and the other names which part of the client stack carries the exchange. The terms should not be read as naming the same layer of subnet communication.
A synapse type alone does not describe every dendrite exchange, and a dendrite mention does not replace the synapse definition that says what the message contains (Glossary: Axon).
Readers should keep message-object vocabulary separate from communication-component vocabulary so each term stays attached to its own role in validator-to-miner traffic.