Subnet 19: blockmachine
Blockmachine is Bittensor Subnet 19 (SN19), operated by the taostat team, with source code published in the Blockmachine repository and project information at blockmachine.io. The subnet creates a decentralized marketplace for blockchain RPC infrastructure, connecting customers who need reliable RPC access with miners who operate full nodes. A protocol gateway routes customer requests to a competitive field of independently operated nodes, using Bittensor’s incentive layer to reward quality service and competitive pricing.
How the Mechanism Works
The economic engine of Blockmachine is a continuous price-and-quality auction. Miners bid a USD-denominated price per request unit — a normalized measure of RPC work — and the protocol gateway directs customer traffic toward miners offering favorable price-to-quality ratios.
Quality is measured by validators operating independently outside the gateway. Each scoring epoch (roughly 72 minutes), validators retrieve logs of recent gateway activity from public cloud storage and compare what each miner returned against reference responses from independent blockchain nodes. The correctness check is external: validators do not rely on the gateway’s own records to judge accuracy, but instead re-query the same data themselves. Scores are then converted to weights and committed on-chain, where Yuma Consensus translates them into emissions. Miners who serve more request units at a competitive price with high response correctness earn proportionally higher rewards.
The subnet supports RPC traffic for multiple blockchain networks, including Bittensor’s own chain, Ethereum, and BSC. A central registry maintained by the Blockmachine team distributes scoring parameters and reference endpoint configuration to all validators, allowing protocol rules to evolve without requiring simultaneous software upgrades across the validator set.
Participating as a Miner
Miners on Blockmachine operate blockchain full nodes — either standard syncing nodes for everyday RPC queries or archive nodes capable of serving deep historical state — and expose them to the network through the Blockmachine gateway. After registering a hotkey on subnet 19 and announcing a price per request unit, a miner begins receiving requests routed by the gateway in proportion to quality score and bid competitiveness.
Revenue comes from Bittensor emissions allocated by the validator weight system. Because the gateway logs are public and validators score every epoch, miners have a strong incentive to maintain uptime and respond correctly rather than gaming the system. Miners can adjust their pricing and operate multiple nodes simultaneously to scale throughput.
Participating as a Validator
Validators on Blockmachine perform independent quality audits rather than generating or routing traffic themselves. Each epoch a validator pulls the public gateway logs, samples recorded request–response pairs, and verifies the responses by re-querying reference nodes it controls or trusts. The gap between what the miner answered and what the reference returned determines the quality score for that miner that epoch.
Validators must hold a registered hotkey on subnet 19 with sufficient stake to be included in the active validator set. Authentication against the Blockmachine registry uses the hotkey directly via a challenge–response flow, so no separate credentials are required. Because scoring parameters are distributed by the registry, validators stay current with protocol changes automatically rather than requiring manual configuration updates.
On-Chain Identity
Subnet 19 is registered under coldkey 5FWh37LfVV5LE9dZA91STzbtebh6vxYa3MH71c621sYafo1L. Live
neuron counts, emissions, and staking data are tracked on
taostats.io/subnets/19. Source code is maintained at
github.com/taostat/blockmachine, with dedicated
repositories for the miner and
validator components.
Relationship to Yuma Consensus
Subnet 19 uses Yuma Consensus to convert the correctness-and-pricing weight vectors that validators submit into the emission shares distributed to miners and validators within the subnet each tempo. The linked documentation describes how validator weight submissions are aggregated into consensus weights for each miner registered on the subnet.
In Blockmachine’s context, validators pull public gateway logs each epoch, verify miner RPC responses against independent reference nodes, and translate those correctness scores into weight vectors for the subnet. The Emission documentation describes how those consensus weights determine each participant’s share of the subnet’s accumulated emission each tempo.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For blockmachine (SN19), that sequence changes how readers should interpret RPC infrastructure service examples and request-correctness scoring outcomes.
In localnet, blockmachine-compatible miners and validators can be developed and tested in an isolated environment. Localnet RPC service results and emission outcomes do not represent production subnet performance.
On testnet, blockmachine-compatible RPC request and validation workflows can be exercised in a shared, non-production network. Testnet correctness scores and validator weights are separate from mainnet subnet state.
On mainnet, blockmachine (SN19) is the live production subnet where miners serve authenticated blockchain RPC requests and validators rate correctness to determine real Bittensor emissions. The blockmachine repository is the registered project repository for SN19 on the production network.
The Bittensor Networks reference separates mainnet, testnet, and localnet. An RPC service result or emission outcome from one environment should not be read as representing production subnet performance in another environment.
Miner and Validator Roles
Subnet 19 operates under the standard Bittensor two-role structure. Miners supply the subnet’s capability and validators evaluate those contributions and set weights. Reward distribution follows Yuma Consensus.
Reader Boundary
Subnet 19 blockmachine should not be read as generic Bittensor subnet documentation, a single operator’s RPC endpoint, or proof that gateway logs alone define correctness. It names one subnet’s decentralized blockchain RPC marketplace on netuid 19 (Understanding Subnets, Glossary: Netuid).
Reference Nodes Supply External Correctness Checks
The blockmachine repository describes validators comparing miner responses against independent reference nodes rather than trusting gateway records alone (blockmachine repository).
Correctness scoring therefore depends on re-querying the same data outside the routing layer.
Public Gateway Logs Feed Validator Audits
Each scoring epoch, validators retrieve recent gateway activity from public logs and sample recorded request-response pairs for verification (blockmachine repository).
That workflow keeps quality measurement separate from the traffic-routing gateway.
Validator Weights Still Flow Through Yuma Consensus
Subnet 19 uses Yuma Consensus to convert validator weight submissions into emission shares each tempo (Yuma Consensus, Emission).