blockmachine

36 posts

blockmachine banner
blockmachine

blockmachine

@blockmachine_io

Verified RPC infrastructure powered by competing node operators. Bittensor Subnet 19.

London Katılım Ocak 2026
1 Takip Edilen769 Takipçiler
blockmachine
blockmachine@blockmachine_io·
blockmachine just settled its first on-chain buyback. $2,009.73 of customer revenue from Apr 22 → May 15 → 530.84 α of SN19. Sized to match miner payouts and offset emission-driven sell pressure. Cycle one. Buybacks scale with revenue from here. taostats.io/extrinsic/8190…
English
1
4
26
506
blockmachine
blockmachine@blockmachine_io·
Referrals are live. 5-10% recurring on every eligible payment from customers you refer. Paid in USDC. Join our decentralized sales team: blockmachine.io/docs/referrals
blockmachine tweet media
English
4
8
44
11.9K
blockmachine
blockmachine@blockmachine_io·
9/ Long-term, Bittensor product teams should build on top of a commodity RPC layer, not running their own. We are building that layer. The market is forming. The mechanism is working. Stop running nodes. Build products. blockmachine.io
English
1
0
3
292
blockmachine
blockmachine@blockmachine_io·
8/ That changes the calculus for product teams. Running your own RPC stops being the safe default. It becomes the expensive default. The choice where you keep paying an engineering tax that the rest of the market is starting to shed.
English
1
0
3
435
blockmachine
blockmachine@blockmachine_io·
1/ Stop running nodes. Build products. Across the Bittensor ecosystem, teams still spend too much engineering time on RPC reliability, node access, endpoint failover, and infra babysitting. Reliable RPC is necessary. Owning the whole stack usually is not. 🧵
English
6
9
46
4.7K
blockmachine
blockmachine@blockmachine_io·
@DrocksAlex2 That's right. All storage queries are verified against Merkle proofs at the gateway before the response reaches the customer. The remaining methods (runtime calls, subscriptions) are checked by the validators.
English
0
1
18
543
Alex DRocks
Alex DRocks@DrocksAlex2·
@blockmachine_io And all of this is confirmed that they aren't cheating right? I read the paper and it looked solid on the miner verification
English
2
0
12
941
blockmachine
blockmachine@blockmachine_io·
The Bittensor community moves fast. Two days post-mainnet, the blockmachine team has been flipped on SN19 routing share. An independent miner registered 36 hours ago went from 5% to ~38% of traffic share. They're now #1 on the subnet. Eight other independents are serving traffic alongside them. The network has grown from our 24 nodes at launch to 64. The plan was always that our miners would be beaten by the community. We just didn't expect it to happen this fast. This community rocks.
blockmachine tweet media
English
5
15
132
18.5K
blockmachine retweetledi
mogmachine (ττ)
mogmachine (ττ)@mogmachine·
1/ I woke up very stoked today. in 3 years of building on Bittensor, i have never been this excited about a subnet launch. today blockmachine goes live. first ever Bittensor subnet to launch on mainnet with a real product, real customers and real revenue from day one. 🧵 how it works and why it matters 👇
mogmachine (ττ) tweet media
English
24
55
388
32.2K
blockmachine
blockmachine@blockmachine_io·
blockmachine validator code is now public. This is the code that reads gateway logs, verifies miner correctness against reference nodes, computes quality scores, and submits weights on-chain. github.com/taostat/blockm…
English
0
7
28
2.2K
blockmachine
blockmachine@blockmachine_io·
A confirmed correctness failure means a permanent coldkey ban. Not a penalty. Not a timeout. Permanent. Validator code goes public this week.
English
1
1
7
577
blockmachine
blockmachine@blockmachine_io·
If verification fails, the gateway silently retries on a different miner within milliseconds. Failed backends are excluded. The customer never sees it. The failed miner earns zero CU. Subscriptions and runtime calls use sampling-based validation instead of per-request proof.
English
1
0
3
685
blockmachine
blockmachine@blockmachine_io·
How blockmachine verifies miner responses at the gateway: a technical deep dive. Every storage query is cryptographically verified before it reaches you. Not sampled. Not spot-checked. Every one. In our benchmark, verification added under 6 microseconds of end-to-end overhead. 🧵
English
1
7
54
10.9K