Plug into Bittensor's decentralized AI economy

Bittensor is a strong blockchain for applications that rely on decentralized production of AI and other computational services. Its main advantage is access to subnet-based markets for inference, training, compute, storage, forecasting, research, and verifiable computation.

GetBlock provides managed Bittensor RPC infrastructure that gives developers access to the Bittensor (TAO) network without running their own Subtensor node. Instead of operating and maintaining a node yourself, GetBlock provides hosted endpoints that your application can use to read blockchain data, submit transactions, monitor network activity, and interact with Bittensor's EVM and subnet ecosystem.

Bittensor wallets come in two forms. Standard Bittensor wallets use Polkadot-style ss58 addresses and sign Substrate-side transactions (staking, subnet operations). EVM-side smart contract interactions require EVM-compatible wallets using h160 addresses, like MetaMask, which can connect to the Substrate chain by pointing it at an RPC endpoint and setting the Chain ID to 964.

Bittensor RPC nodes expose the full public blockchain state and transaction interface. Developers can query blocks, headers, runtime metadata, storage, accounts, subnets, neurons, delegates, and EVM state, subscribe to chain events, and submit signed Subtensor or EVM transactions.

Connect by sending requests to the endpoint URL available through RPC providers such as GetBlock, which expose Substrate and EVM JSON-RPC. For EVM interactions, configure your wallet or SDK with Chain ID 964 for mainnet. For Substrate interactions, use the official Bittensor Python SDK or any Substrate-compatible client and point it at the endpoint.

Bittensor RPC methods fall into three groups. Substrate methods include state_getStorage and state_call for querying chain state, author_submitExtrinsic for transactions, and subtensor_* namespace methods for subnet-specific queries (e.g., metagraph, neuron data, subnet emissions). EVM JSON-RPC methods follow the standard Ethereum API, e.g. eth_getBalance, eth_call, eth_sendRawTransaction, and eth_getLogs. rpc_methods is the best first call because it tells you exactly what a given endpoint supports.

Yes. Bittensor RPC supports real-time data streaming over WebSocket (WSS) through JSON-RPC subscription methods. These methods are useful for building live dashboards, block explorers, staking and subnet monitors, transaction trackers, and other applications that need blockchain updates as they happen.

For EVM interactions, mainnet Chain ID is 964 and testnet Chain ID is 945. The Substrate side of Subtensor does not use a numeric Chain ID; instead, mainnet is identified by the codename “finney” and testnet by “test”. Configure both fields correctly in EVM wallets and Substrate clients respectively.