Skip to main content

​
Test RPCs

Rhaios runs managed test RPCs — full Ethereum and Base chain forks that mirror mainnet state at a recent block. Agents can fund wallets, execute yield operations, and verify results without spending real tokens.

​
What is a test RPC?

A test RPC is an isolated fork of a live chain. It has the same contract state, token balances, and protocol deployments as mainnet, but transactions on the fork do not affect the real chain. Rhaios manages these forks automatically. When an agent calls a testing tool or the server runs a preflight simulation, the server routes the operation through the appropriate fork.

​
Why test RPCs exist

Use caseHow it works
Pre-prod testingAgents fund wallets and execute yield flows on a persistent fork. No real funds required.
Preflight simulationBefore submitting a signed transaction to the real chain, yield_execute simulates it on an ephemeral fork to catch reverts before they cost gas.
These are separate fork types:
  • Persistent forks — one per chain, created on first use, auto-recreated if evicted. Used by testing_fund_wallet and yield_setup_relay.
  • Ephemeral forks — created per-simulation, destroyed immediately after. Used by preflight simulation in yield_execute.

​
Token-gated access

Testing tools require a testing token issued by Rhaios. Pass it as testingToken in every testing_fork_status and testing_fund_wallet call. Testing tokens authorize:
  • Checking fork health and policy limits
  • Funding wallets with test ETH and USDC on managed forks
To request a testing token, contact the Rhaios team.

​
Funding caps

Each testing_fund_wallet call is capped:
TokenMax per call
ETH0.02 ETH
USDC50 USDC
Multiple calls are allowed. Caps are per-call, not per-wallet.

​
Supported chains and tokens

ChainChain IDUSDC address
Ethereum10xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48
Base84530x833589fcd6edb6e08f4c7c32d4f71b54bda02913

​
Testing workflow

​
Preflight simulation

When preflight is enabled, yield_execute creates an ephemeral test RPC at the latest block, simulates the signed transaction, and only submits to the bundler if simulation succeeds. The ephemeral fork is destroyed after each simulation regardless of outcome. Simulation failures block execution and return an error. There is no mode that allows a failed simulation to proceed. See Architecture for more on the execution flow.

​
Relationship to production

Test RPC operations never touch real chains. When you are ready for production:
  1. Fund your agent wallet with real USDC on Base or Ethereum
  2. Point RHAIOS_MCP_URL at the production endpoint
  3. Remove testingToken — core yield tools do not require it