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

state_getStorage - Bittensor

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

Returns the raw storage value at a given storage key. Storage keys are constructed by hashing the pallet name + item name + (optionally) the parameter — typically computed by SDKs like Polkadot.js rather than constructed by hand.

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

key

string

Yes

Hex-encoded storage key (typically computed via xxhash128(pallet) + xxhash128(item) + ...)

blockHash

string

No

Block hash to query at. Omit for the latest block.

Request Example

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

const data = JSON.stringify({
    "jsonrpc": "2.0",
    "method": "state_getStorage",
    "params": [
        "0x26aa394eea5630e07c48ae0c9558cef7b99d880ec681799c0cf30e8886371da9"
    ],
    "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 | null

Hex-encoded SCALE-encoded value, or null if the storage item is not set

Use Cases

  • Reading raw chain state when you know the exact storage layout

  • Building custom indexers that decode SCALE manually

  • Querying storage at a specific historical block

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

-32602

Invalid storage key

Storage key must be valid hex starting with 0x

SDK Integration

Last updated

Was this helpful?