SN 19. Rank 32 of 32 by emission
blockmachine
Blockmachine (SN19) provides decentralized RPC and archive node infrastructure for Bittensor and Ethereum.
In their own words · raw.githubusercontent.comSN19 blockmachine answers questions that apps ask blockchains, like a call centre staffed by freelance operators who set their own price per call and are paid only for answers checked as correct.
The commodity, explained from zero
Every wallet, explorer and trading bot asks a blockchain questions: what is the latest block, what is this balance, did this transaction go through. Those questions go to an RPC endpoint, a server running a full copy of the chain, and running one is expensive. Blockmachine sells access to such servers for eleven chains, Bittensor and Ethereum among them, at a single address per chain. Usage is metered in Request Units, where a simple query costs 1 and a heavy one more.
The price list is public: a keyless free tier at 300 requests a minute, a $9 Standard plan for 5 million units a month, up to $999 for a billion. "Failed requests don't cost you anything." A calculator on the pricing page puts 100 million requests at $165 against $979 at Alchemy, a named competitor. The front page carries testimonials from three customers, including Taostats: "At 15 billion requests a month, we can't afford for our RPC layer to be the weak point."
Why it is on Bittensor at all
The technology page states the case as cost and trust: "Most supply is still centralized, opaque, and economically misaligned." Competing suppliers bid the price down, and every response can be checked. Here the call-centre comparison breaks: a call centre pays operators by the hour, while blockmachine pays only for answers a validator has re-run and matched, and an operator's unclaimed share is destroyed rather than shared.
How the work gets done
Miners, the operators, run their own chain node behind a gateway the network supplies, register it, and set a price in US dollars per unit of work. Customer requests are routed by a score that combines that price with quality, meaning latency, uptime and correctness, and a burst test measures each node under heavy load so strong hardware earns a bigger share. Validators, the auditors, read the gateway logs, re-run samples against reference infrastructure and compare results; a mismatch has no appeal, and the whitepaper provides for permanent bans. Each epoch of about 72 minutes, emission, the subnet's share of newly minted TAO, is paid in proportion to the units each miner served at its bid price.
How you would know it works
The buybacks page: "For every alpha token paid to miners, blockmachine purchases an equal amount of SN19 alpha" for a reserve, and it lists four settled cycles from May to August 2026, 4,812 alpha for $12,328 in total, each row linked to a Taostats transaction, last synced at block 9,033,809 on 2026-09-10. Anyone can call the free endpoint at rpc.blockmachine.io.
What is missing
The live performance and miner dashboards render empty without a browser. There is no status page and no service-level agreement; support is an email and a channel on the shared Bittensor Discord, and the chain's discord field is empty. The miner README registers on a testnet and gives no mainnet cost (about 1 TAO on chain on 2026-09-09). The chain's repository field is a one-file page linking to the real miner and validator repositories, and the chain description's wording appears nowhere on the site.
Go deeper
- Front page, chains and testimonials
- Dated buyback ledger with proofs
- Miner README: eligibility and scoring
Sources for this explainer
Metaphor: a call centre staffed by freelance operators. Every claim is drawn from the evidence set or the subnet's own materials; "(inferred)" marks a conclusion rather than a quote. Corrections.
How we scored it
Four audiences, four questions each, scored on what a first-time reader can find in five minutes. Method in the rubric.
- subnet_name
- blockmachine
- github_repo
- github.com
- subnet_contact
- team@blockmachine.io
- subnet_url
- blockmachine.io
- discord
- not set
- description
- Harnessing Bittensor's incentive layer to forge self-optimizing infrastructure.
- additional
- not set
Stakers and validators●●●●● 4.3
Should I allocate here? · rank 1 of 32 for this audience
Q1What it is●●●●● 4
Blockmachine provides RPC access across supported chains. Requests are served by competing suppliers, failed requests are not billed
front page, per Request Unit pricing one click away
Q2Who it is for●●●●● 5
SN19 buybacks are read from the PSR coldkey and linked to Taostats proof.
four settled cycles May to Aug 2026 totalling $12,328, synced at block 9,032,798 on Sep 9, 2026, Taostats testimonial
Q3How it resists gaming or fails●●●●● 4
whitepaper v1.0.0 with Correctness Enforcement, Mechanism Resilience and Parameter Reference sections, Merkle verification and permanent bans, resilience section not read so failure modes unconfirmed
Q4Identity and documentation●●●●● 4
identity 5 of 7 (discord and additional not set), url has no scheme but resolves, github is a one file README linking the miner and validator repos, Bittensor and buybacks pages, contact matches
Miners●●●●● 4.0
Can I compete, and what wins? · rank 3 of 32 for this audience
Q1What it is●●●●● 4
You run your own node for your chosen chain, fronted by our nginx gateway that authenticates requests from the Blockmachine network
JSON-RPC in, verified responses out, eligibility table, no demo
Q2Who it is for●●●●● 4
You set a price in USD per Compute Unit (CU).
eligibility rules per chain, capacity testing, cheaper good miners get more traffic, README registers on testnet 417, no mainnet cost (burn 1.0 TAO)
Q3How it resists gaming or fails●●●●● 4
routing score combines price and quality (latency, uptime, reliability, correctness), permanent bans for confirmed mismatches in the whitepaper, emissions per CU served, no examples, no immunity
Q4Identity and documentation●●●●● 4
step by step install, register and price CLI guide with troubleshooting and a CLI reference, the chain github_repo is a link page pushed 2026-07-27, miner repo push date not checked, no releases
Buyers and enterprises●●●●● 4.5
Can I use this today? · rank 2 of 32 for this audience
Q1What it is●●●●● 5
Bittensor RPC (HTTP): https://rpc.blockmachine.io
endpoints for 11 chains with a quickstart and curl examples, docs at blockmachine.io/docs, keyless free endpoints listed on the site
Q2Who it is for●●●●● 5
RPC pricing as low as $1 per million requests
plan table from Free to Enterprise $999 per month in llms.txt, cost calculator against Alchemy, QuickNode and dRPC, Taostats named as a customer
Q3How it resists gaming or fails●●●●● 3
public performance dashboards for uptime and latency (empty to a fetcher), failed requests not billed, a Discord channel on the shared Bittensor server and team@blockmachine.io, no status page or SLA
Q4Identity and documentation●●●●● 5
docs index with an RPC overview and per chain pages, llms.txt is a full API reference including the User Management API, contact team@blockmachine.io matches the chain subnet_contact
Newcomers●●●●● 4.3
What is this and why does it matter? · rank 3 of 32 for this audience
Q1What it is●●●●● 4
Fast, correct, verifiable blockchain infrastructure.
plain front page paragraph, the chain description about harnessing Bittensor's incentive layer is not on the page, RPC left unexplained
Q2Who it is for●●●●● 5
Most supply is still centralized, opaque, and economically misaligned.
with the pricing page comparing costs against Alchemy, QuickNode and dRPC and the Bittensor page on paying for served requests
Q3How it resists gaming or fails●●●●● 4
dated buyback ledger synced at block 9,032,798 on Sep 9, 2026, roadmap with 19 of 21 milestones live, performance and miners dashboards render empty to a fetcher, no benchmark
Q4Identity and documentation●●●●● 4
subnet_name blockmachine matches the site, description is a sentence, url resolves without a scheme, technology and Bittensor pages serve as about and learn pages, chain wording not used on the site
How this score came to be. Verified means the scorer fetched the page and the words are on it; inferred means concluded from code, absence, or a third party. The link badge is a separate automated check made before publication.
Something wrong? Corrections of fact are applied as they arrive during the window; score disputes are batched at its close. How to file one · GitHub issue · email.