evm-rpc

EVM RPC: Receipt and Trace Playbook

Use this skill for EVM transaction debugging with JSON-RPC.

Quick Start

Set a hash and endpoint, then run receipt first and trace second.

evm_tx="0xYOUR_evm_tx"
EVM_RPC="https://evm-rpc.archive.testnet-2.nibiru.fi"

curl -s -X POST \
  -H "Content-Type: application/json" \
  --data "{\"jsonrpc\":\"2.0\",\"method\":\"eth_getTransactionReceipt\",\"params\":[\"$evm_tx\"],\"id\":1}" \
  "$EVM_RPC" | jq

curl -s -X POST \
  -H "Content-Type: application/json" \
  --data "{\"jsonrpc\":\"2.0\",\"method\":\"debug_traceTransaction\",\"params\":[\"$evm_tx\",{\"tracer\":\"callTracer\"}],\"id\":1}" \
  "$EVM_RPC" | jq

Endpoint Map - Nibiru Examples

Chain-agnostic rule: methods determine endpoint family.

Purpose	Example endpoint	Methods
EVM JSON-RPC (mainnet)	https://evm-rpc.nibiru.fi	eth_*, debug_*, net_*, web3_*
EVM JSON-RPC archive (mainnet)	https://evm-rpc.archive.nibiru.fi	historical reads, tracing
EVM JSON-RPC archive (testnet)	https://evm-rpc.archive.testnet-2.nibiru.fi	testnet tracing and historical reads
Comet RPC archive (mainnet)	https://rpc.archive.nibiru.fi	/block_results, /consensus_params
Comet RPC archive (testnet)	https://rpc.archive.testnet-2.nibiru.fi	/block_results, /consensus_params

Rules:

• Run eth_* and debug_* only on EVM RPC endpoints.
• Run /block_results and /consensus_params only on Comet RPC endpoints.
• Prefer archive endpoints for old heights/hashes and tracing workflows.

Basic Queries (Health / Identity)

web3_clientVersion

Queries the traceability info like the client name, version, Git commit, Go version, runtime architecture, and build tags.

curl -X POST https://evm-rpc.nibiru.fi \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "method": "web3_clientVersion",
    "params": [],
    "id": 1
  }'

The response looks like this: "Nibiru 2.6.0: Compiled at Git commit 3cf97e3468f8ce922c8760f839f8f336ca0c37f4 using Go go1.24.5, arch amd64, and build tags (netgo osusergo ledger static rocksdb pebbledb muslc)"