Reazy
Paper
Network: checking…Details
Reazy Vault

Make permissions explicit

The vault is how an agent would trade real assets without being able to take them: funds stay in a contract only you can withdraw from, and the agent gets a narrow, revocable permission.
Vault contract
Not configured
No address is recorded for this network.
Live execution
Not configured
Agents run in paper mode only.
Network
Built for Robinhood Chain
Chain ID 4663 · gas in ETH

What the vault contract must guarantee

Required · not deployed
  1. 01Owner-controlled withdrawalsOnly the owner address can move assets out of the vault. No agent, operator or Reazy key can.
  2. 02Explicit operator authorizationAn agent can act only after the owner names its operator address in a transaction.
  3. 03Revocable operator accessThe owner can remove the operator at any time, in one transaction, without Reazy.
  4. 04Pause mechanismThe owner can pause all trading by the vault. Withdrawals stay available while paused.
  5. 05Allowlisted assetsThe vault trades only token contracts the owner listed.
  6. 06Allowlisted venuesThe vault calls only venue contracts the owner listed.
  7. 07Bounded approvalsToken approvals are for the exact trade amount and are cleared after it.
  8. 08Enforced trade constraintsPer-trade size and minimum output are checked by the contract, not by a server.
  9. 09Clear eventsEvery authorization, trade, pause and withdrawal emits an event.
  10. 10No arbitrary calls by the agentThe operator cannot make the vault call an arbitrary address or function.
  11. 11Tests covering authorization and outflowsA test suite proves who can move what, including the failure cases.
  12. 12Independent reviewThe deployed bytecode is verified on the explorer; any audit claim names the auditor and the report.

A contract that simply forwards calls to a router does not meet this list and will not be labelled a vault here. Live features stay disabled until every item is true of a deployed, verified contract.

Before any live transaction, you would see

  • NetworkRobinhood Chain (chain ID 4663)
  • AssetThe token and its contract address, e.g. USDG
  • AmountThe exact amount, in token units
  • Destination or spenderThe address that receives funds or the allowance
  • Permission being grantedIn plain words, and how to revoke it
  • FeesNetwork fee estimate, where the wallet provides one

After submission, you would see

  • Transaction hashWith a link to the explorer from the verified network configuration
  • PendingBroadcast, not yet included in a block
  • ConfirmedIncluded, with the block number
  • Failed or replacedReverted, dropped or replaced by another transaction

Submitted is not the same as confirmed. Reazy would never show a submitted transaction as done.

Integration interface

The application talks to a vault through two adapters, VaultAdapter and ExecutionAdapter (src/server/data/types.ts). Their only implementations today report “not configured” and refuse every call that would move funds (src/server/adapters/gated.ts). Enabling live execution means deploying and verifying a contract that meets the list above, recording its address in the network configuration, and implementing those two adapters against it.