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

payment_queryInfo - Bittensor

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

Returns fee, weight, and class information for a given extrinsic — without submitting it. Used to estimate transaction costs before signing.

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

extrinsic

string

Yes

Hex-encoded SCALE-serialized extrinsic (may or may not be signed)

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": "payment_queryInfo",
    "params": [
        "0x4502840022df56fa4a52f1eb96d4f1a9cdfb4cfbe5e7eb4..."
    ],
    "id": "getblock.io"
}'
import axios from 'axios';

const data = JSON.stringify({
    "jsonrpc": "2.0",
    "method": "payment_queryInfo",
    "params": [
        "0x4502840022df56fa4a52f1eb96d4f1a9cdfb4cfbe5e7eb4..."
    ],
    "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.weight.refTime

integer

Computation cost (reference time, picoseconds)

result.weight.proofSize

integer

PoV (proof of validity) size in bytes

result.class

string

Dispatch class — Normal, Operational, or Mandatory

result.partialFee

string

Estimated fee in rao (1 TAO = 10^9 rao) — does not include tip

Use Cases

  • Pre-flight fee estimation for wallet UIs

  • Detecting excessively expensive extrinsics before submission

  • Building fee oracles for TAO/USD denominated estimates

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?