Summary
Chain inspection stops being a folder of one-off scripts.
The node, cycle and account views sit next to the standard Ethereum calls behind one validated interface, so a debugging question can move from network state down to a single transaction receipt without switching tools.
What it is
Shardeum's network and RPC operations exposed as thirteen tools: three that are Shardeum-specific and ten standard Ethereum JSON-RPC methods. Requests are schema-validated before they go out, and network and RPC failures are handled rather than passed through raw.
What you get
- Shardeum-specific state: the node list, the network account, and cycle information
- Blocks by number or by hash, plus the receipts for a whole block in one call
- Transactions by hash and their receipts, and the transaction count for an account
- Account balance, chain id, and gas estimation for a call you have not sent yet
- Structured responses back to the agent rather than raw RPC envelopes
Requirements
Node, with the repository's dependencies installed, and a Shardeum RPC endpoint to point at. Every tool here reads — nothing signs or sends a transaction.
Setup effort
Build from source — clone the repository and build it, then point your client at the binary