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

eth_getTransactionReceipt - Bittensor

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

Returns the receipt of a confirmed EVM transaction — gas used, logs emitted, status (1 = success, 0 = revert), and contract address if the transaction created a contract.

Subtensor EVM JSON-RPC method. Call against a GetBlock endpoint configured for the EVM interface (not the Substrate interface). Subtensor EVM uses chain ID 945 (0x3b1). Standard Ethereum tooling — ethers.js, viem, Hardhat, Foundry, MetaMask — works unmodified.

Parameters

Parameter
Type
Required
Description

txHash

DATA (32 bytes)

Yes

Transaction hash

Request Example

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

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

QUANTITY

0x1 = success, 0x0 = reverted

result.gasUsed

QUANTITY

Actual gas consumed

result.logs

array of Log

Event logs emitted during execution

result.contractAddress

DATA

Address of newly created contract, or null

Use Cases

  • Verifying EVM transaction success or failure

  • Reading event logs for state updates on Subtensor EVM contracts

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?