Establish your perimeter.
- Connect your wallet. Use MetaMask or another injected EVM wallet. Switch to Robinhood Chain and sign the sign-in message.
- Register an agent. Give it a name, describe its role, and decide whether it can request policy evaluations.
- Define a policy. Set an amount limit and expected slippage limit. Add approved tokens and destination addresses. Enable policy authorization when ready.
- Evaluate an intent. Select the agent and token, enter a destination and amount, then review the rule-by-rule decision.
- Review the record. Open Activity to search evaluations, inspect policy snapshots, or export records.
Identity is not authority.
Agents belong to the wallet that registers them. Each agent has a name, description, active status, and an explicit permission to request evaluations. An inactive agent or one without evaluation permission receives REJECT.
Registration creates an application identity. It grants no independent access to your wallet, tokens, or smart contracts. You can edit permissions or deactivate an agent in the Agent Registry.
Explicit beats implied.
The policy defines an amount ceiling, expected slippage ceiling, approved tokens, approved destination contracts, and an authorization switch. An empty destination list rejects every intent. New wallets begin with authorization paused.
- Amount
- A positive decimal string in the selected token’s units. The same numeric ceiling applies independently to each approved token. It is not a USD value, a daily cap, or an aggregate spending budget.
- Slippage
- The expected slippage supplied in an intent. Internally represented as integer basis points; 50 basis points equals 0.5%. This check does not measure actual market slippage.
- Tokens
- Use
nativefor ETH. For ERC-20 addresses, the server verifies decimals and symbol through Robinhood Chain RPC. Tokens above 18 decimals are unsupported. - Destinations
- Only exact approved addresses pass. Listing an address does not establish that its contract is safe or verify its behavior.
- Versions
- Every policy save increments its version. Concurrent stale writes are rejected. Each evaluation records the version and full policy snapshot it used.
Eight checks. One decision.
The Execution Terminal evaluates network, agent status, agent permission, authorization, token allowlist, destination allowlist, amount, and expected slippage. Every rule must pass to receive ALLOW.
Amount comparisons use integer token units and validate token precision. Limits are inclusive. The same intent and policy produce the same decision; evaluation IDs and timestamps identify each request.
SENTRI evaluates submitted intent fields. It does not execute a contract call, predict a swap outcome, inspect arbitrary calldata, or confirm an onchain transaction.
A reason behind every result.
Each record contains a unique ID, timestamp, agent ID and name, wallet, network, normalized intent, policy version and snapshot, decision, and rule explanations. These are persistent application records, not an immutable blockchain log.
The Audit Trail supports search, decision filters, expandable details, and JSON export. Records are not fabricated and contain no transaction hash when no transaction was submitted.
Your keys stay with you.
Connect an injected EVM wallet and sign a human-readable message to prove ownership. No private keys, token approvals, or transaction signatures are requested by sign-in. EOA signatures are supported; smart-contract account signatures are currently unsupported.
Sign-in challenges expire after five minutes and can be used once. Sessions use an HttpOnly, SameSite=Strict cookie and expire after 12 hours. Account or network changes clear the visible workspace until the connection is verified again. Production session cookies are Secure.
All policy and agent mutations are authenticated and wallet-scoped on the server. A wallet cannot select another owner by sending an address in a request.
Robinhood Chain.
- Network
- Robinhood Chain Mainnet
- Chain ID
- 4663
0x1237 - Native currency
- ETH
- Public RPC
https://rpc.mainnet.chain.robinhood.com- Explorer
- Robinhood Chain Blockscout ↗
See Robinhood’s official network documentation ↗. Wallet network verification and native balance retrieval use the connected wallet provider. Balances from other chains are not displayed as Robinhood Chain balances.
Know what is connected.
Available: wallet connection, chain verification, native balance retrieval, agent management, versioned policies, deterministic policy evaluation, and audit history.
Not connected: EVM call simulation, swap routing, automatic execution, transaction submission, or a deployed enforcement smart contract. There is no transaction broadcast button in this release.
An ALLOW decision expresses that the submitted fields comply with the saved policy. It does not grant wallet authorization or prevent transactions sent through other applications. Policies are enforced within SENTRI’s evaluator, not globally across the wallet.
Shared state belongs on the server.
Production storage uses a configured Redis REST database. If that database is absent or unavailable, authenticated storage operations fail. Browser-local storage is never substituted for production persistence.
Capacity per wallet: 50 agents, 20 approved tokens, 50 destination addresses, and 2,000 evaluations. The audit limit stops new evaluations without discarding old records. JSON export is available; clearing or archival of server history is not available in this release.
During local development only, a file-backed adapter serializes writes within a single process. This adapter is not suitable for production or multiple application instances.