TriportRPC

Robinhood address history

Triport does not currently publish an indexed address-history endpoint for Robinhood mainnet, chain ID 4663. There is no published history depth, indexed-through block, pagination contract, or indexer rate limit for this product.

The existing endpoint is POST https://triport.io/rpc/robinhood. It provides block, transaction, receipt, log, and best-effort debug reads. These methods provide inputs for an indexer; they do not return a complete list of an address's activity.

ActivityAvailable inputAdditional work needed for complete history
Incoming and outgoing ETHFull transactions and receiptsIndex sender/recipient across a verified block range; distinguish failed transactions from completed transfers
Internal ETH transfersdebug_traceTransaction / block traces with callTracerIndex successful value transfers, including ancestor-revert handling; track trace coverage separately
ERC-20 transfersReceipt logs or eth_getLogs with Transfer topicsIndex both address directions, distinguish ERC-20 from ERC-721 events, and preserve raw integer amounts
Contract creationsreceipt.contractAddress and CREATE/CREATE2 tracesIndex top-level and factory-created contracts, including zero-value creations

For an individual known transaction, a trace request is:

curl https://triport.io/rpc/robinhood \
  -H "x-token: $TRIPORT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"debug_traceTransaction","params":["0xbf550a9a5ceab4b61f7e1ef4e792cc7c96eb89d9b1e93fa8945ad71f8b660a01",{"tracer":"callTracer","timeout":"5s"}]}'

This is a single-transaction trace example, not an address-history query. Debug methods remain best-effort; consult RPC behavior and limits. trace_filter and alchemy_getAssetTransfers are not in the published Robinhood method catalog.

External ecosystem explorers have separate availability and coverage. A successful HTTP response with an empty list does not establish that an address has no history: inspect indexing status. An explorer's latest block must be compared with an independent RPC head; its own lagBlocks: 0 is insufficient. Public explorer limits do not inherit Triport RPC plan limits.