Settings
Network, deployment and status
Hestr runs in one of three explicit modes. Nothing is fabricated in any of them.
Operating mode
- Mode
- Configured network
- Network
- Robinhood Chain (chain id 4663)
- RPC (browser)
- https://rpc.mainnet.chain.robinhood.com
- RPC status
- checking…
- Contract
- 0xFaa601D5f94991aeDDc46fdA520A6bA287c43D8f
- Payment token
- USDG (Global Dollar) · 6 decimals · 0x5fc5360D0400a0Fd4f2af552ADD042D716F1d168
- Dispute resolver
- 0xAD7d9A785054B592B9F4cA76255018d736850EF9
- Challenge period
- 3 days
- Resolution timeout
- 30 days
- Database
- configured
- Relayer
- none (agents submit directly with their own gas)
- Demo agent
- off
- Index
index: no checkpoint yet
- Session
- not signed in
The three modes
- Local development
- Anvil chain 31337, a MockUSD test token, embedded PostgreSQL, the example provider and a demo agent. Real contracts, fake money.
- Configured network
- A verified chain (Robinhood Chain, chain id 4663, USDG) with a deployment you provide. Live reads and writes. The deployment manifest and verification notes live in docs/deployment.md.
- Unconfigured
- No contract address. Every balance-dependent action is disabled; the console shows setup guidance instead of placeholder numbers.
Agent credentials
Agents use their own key (SDK, MCP, or the demo runner). The key signs EIP-712 payment requests and authenticates API calls; the mandate decides what it may do. Never give an agent the owner wallet, a seed phrase, or a private key with other funds. Production relayer and agent keys stay server-side; nothing funded is ever placed in browser code.
Public versus private
Mandates, balances, escrow, receipts and settlements are public onchain data anyone can read. Agent names, mandate labels, quotes, policy evaluations, approval decisions and notes are application metadata stored in the database and only shown to the signed-in owner.