RPC Routes

In addition to the standard Ethereum JSON-RPC methods, your Stagenet exposes a dev_* namespace for performing development actions.

Categories

• Workspaces — attach a per-address dashboard to a wallet, mainnet contract, or any address with an ABI.
• Import Contracts — push compiled contracts to your Stagenet so deployments get auto-attached Workspaces.
• Balances — add or overwrite native and ERC20 balances.
• State — override code, nonce, balance, and storage on any account.
• State Tracking — record balances, ERC20 holdings, storage slots, and view function results over time.
• Function Overrides — intercept contract reads and return a fixed value.
• Impersonation — send transactions from any address without its private key.

Calling conventions

All dev_* methods follow standard JSON-RPC 2.0. POST to your Stagenet RPC URL:

curl -X POST <YOUR_STAGENET_RPC_URL> \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "dev_addBalance",
    "params": ["0x1111111111111111111111111111111111111111", "1000000000000000000"]
  }'

Amounts are passed as strings — either a decimal integer or a 0x-prefixed hex value. This avoids JSON number precision loss for values larger than 2^53.

Addresses are 0x-prefixed Ethereum addresses, case-insensitive.

Errors are returned in the standard JSON-RPC error field. A 200 OK HTTP response with error populated still indicates failure — always check the body.