For the complete documentation index, see llms.txt. This page is also available as Markdown.

state_call - Bittensor

Example code for the state_call JSON-RPC method. Complete guide on how to use state_call JSON-RPC in GetBlock Web3 documentation.

Executes a runtime API call — the bridge for accessing typed runtime APIs that aren't exposed as direct RPCs. This is how Polkadot.js routes calls like api.call.subnetInfoRuntimeApi.getSubnetInfo(netuid) under the hood. For Bittensor, the direct subnetInfo_* / neuronInfo_* / delegateInfo_* RPCs are often easier to use.

Substrate native JSON-RPC method. Call against a GetBlock endpoint configured for the Substrate interface. For typed SDK access, use Polkadot.js (TypeScript) or substrateinterface (Python).

Parameters

Parameter
Type
Required
Description

method

string

Yes

Runtime API method — <RuntimeApiName>_<methodName> (e.g. SubnetInfoRuntimeApi_get_subnets_info)

data

string

Yes

SCALE-encoded call data (hex)

blockHash

string

No

Block hash to execute at

Request Example

curl --location --request POST 'https://go.getblock.io/<ACCESS-TOKEN>/' \
--header 'Content-Type: application/json' \
--data-raw '{
    "jsonrpc": "2.0",
    "method": "state_call",
    "params": [
        "SubnetInfoRuntimeApi_get_subnets_info",
        "0x"
    ],
    "id": "getblock.io"
}'
import axios from 'axios';

const data = JSON.stringify({
    "jsonrpc": "2.0",
    "method": "state_call",
    "params": [
        "SubnetInfoRuntimeApi_get_subnets_info",
        "0x"
    ],
    "id": "getblock.io"
});

const config = {
    method: 'post',
    url: 'https://go.getblock.io/<ACCESS-TOKEN>/',
    headers: {
        'Content-Type': 'application/json'
    },
    data: data
};

axios(config)
    .then(response => console.log(JSON.stringify(response.data, null, 2)))
    .catch(error => console.log(error));

Response Example

Response Parameters

Field
Type
Description

result

string

Hex-encoded SCALE-encoded result of the runtime API call

Use Cases

  • Calling runtime APIs that don't have direct RPC bindings

  • Querying typed Bittensor runtime APIs (subnet info, neuron info) at the SCALE level

  • Backwards compatibility — many things eventually move from custom RPC to runtime APIs

Error Handling

Status Code
Error Message
Cause

403

Forbidden

Missing or invalid <ACCESS-TOKEN>

-32602

Invalid params

Request parameters are missing or malformed

-32601

Method not found

Method does not exist on this interface — check whether you're calling a Substrate method on an EVM endpoint or vice versa

-32603

Internal error

Server-side error while processing the request

429

Too Many Requests

Rate limit exceeded for your plan

SDK Integration

Last updated

Was this helpful?