eth_getCode - Tempo

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

Returns the contract bytecode deployed at a given address. An empty result (0x) indicates the address is an EOA, not a contract. Tempo's EVM is fully equivalent — this works identically to mainnet Ethereum.

Parameters

Parameter
Type
Required
Description

address

string

Yes

20-byte address of the contract

blockParameter

string

Yes

Block number in hex, or block tag

Request Example

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

Response Example

Response Parameters

Field
Type
Description

result

string

Contract bytecode in hex, or 0x if the address is an EOA

Use Cases

  • Distinguishing contracts from EOAs

  • Verifying TIP-20 token contract deployment

  • Detecting proxy contracts and their implementations

Error Handling

Status Code
Error Message
Cause

403

Forbidden

Missing or invalid <ACCESS-TOKEN>

-32602

Invalid params

Request parameters are missing or malformed

429

Too Many Requests

Rate limit exceeded for your plan

SDK Integration

Last updated

Was this helpful?