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

delegateInfo_getDelegate - Bittensor

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

Returns information for a single delegate by their hotkey. Same response shape as one element of delegateInfo_getDelegates. Cheaper than fetching all delegates when you only need one.

Bittensor-specific custom RPC method. This method is implemented by the Subtensor runtime and is not part of the standard Substrate JSON-RPC surface. Call against a GetBlock endpoint configured for the Substrate interface. The Bittensor Python SDK provides typed wrappers; standard Polkadot.js and substrateinterface require the raw RPC interface (see SDK Integration tabs below).

Parameters

Parameter
Type
Required
Description

delegateHotkey

string

Yes

SS58-encoded delegate hotkey

blockHash

string

No

Block hash to query at

Request Example

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

const data = JSON.stringify({
    "jsonrpc": "2.0",
    "method": "delegateInfo_getDelegate",
    "params": [
        "5GpwjAKpRJ3JpDLvuLn8KGkbSYzZHC9YMVtMs7vCYK4tFKfP"
    ],
    "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

object | null

Delegate info, or null if the hotkey is not registered as a delegate

Use Cases

  • Delegate profile pages

  • Pre-stake verification — confirm a delegate's take and subnet coverage before staking

  • Continuous monitoring of a delegate's performance

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?