archive_v1_body - Bittensor RPC Method
Retrieve the block body (list of extrinsics) for a given block hash from the archive RPC on Bittensor.
Returns the body of a block identified by its hash via the new JSON-RPC v2 archive API. The block body contains the ordered list of extrinsics (transactions, inherents, and unsigned calls) included in that block. This method is part of the archive namespace introduced in the new JSON-RPC specification and is designed for clients that need efficient historical data access on Bittensor without maintaining a full follow subscription.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
hash | string | Yes | The hex-encoded block hash (e.g. "0x1e8a...") whose body to retrieve. |
Response
| Field | Type | Description |
|---|---|---|
result | array | null | Array of hex-encoded SCALE extrinsics included in the block, in execution order. null if the block hash cannot be resolved. |
Each item in the array is a hex-encoded SCALE-encoded extrinsic. Returns an empty array when the block body is available but contains no extrinsics.
Code Examples
Use Cases
- Indexers and explorers -- Retrieve all extrinsics in a historical block for indexing transfers, staking operations, and subnet registrations on Bittensor.
- Analytics pipelines -- Extract historical transaction data across block ranges without replaying the chain. Combine with
archive_v1_hashByHeightto iterate blocks sequentially. - Audit tooling -- Verify the contents of specific blocks during forensic analysis of on-chain activity.
- Subnet monitoring -- Examine historical blocks for subnet registration, weight-setting, and staking extrinsics to analyze Bittensor network behavior over time.
Bittensor Context
On Bittensor, block bodies contain Substrate extrinsics that encode TAO transfers, subnet operations (register, set_weights, add_stake, remove_stake), and governance actions. Each extrinsic is SCALE-encoded and must be decoded using the runtime metadata from the same block era.
Notes
- This method is part of the new JSON-RPC v2 specification and may not be available on all node configurations.
- On public shared RPC endpoints the archive namespace may be disabled or rate-limited.
- For real-time block body access, consider using
chainHead_v1_bodywithin a follow subscription instead.
Related Methods
archive_v1_header-- Get the header for a historical blockarchive_v1_call-- Execute a runtime call against historical statearchive_v1_hashByHeight-- Resolve a block height to a hash before querying its bodychainHead_v1_body-- Get block body within a follow subscriptionchain_getBlock-- Legacy method to retrieve a full block (header + body)