How Pons moves and safeguards funds
The product combines an exportable account wallet, server-enforced mandate checks, verified onchain routing, receipt-derived accounting, and durable rebalance schedules on Robinhood Chain.
One EOA holds the funds directly
Pons does not deploy or claim a separate vault for each agent. Agent holdings are audited attribution records over balances held by the shared account EOA.
Exportable ownership with a managed signer
You can import the same private key into MetaMask, while Pons can also decrypt and use it server-side for the agent transactions you authorize. Anyone with that key controls the wallet.
The technical geo gate applies to buys only
A residence attestation and Vercel request-country signal are evaluated server-side. Missing, invalid, expired, or restricted results place the account in wallet-only mode.
Quotes are previews; receipts are authoritative
Pons uses live routes and Chainlink values to decide whether a transaction is safe to attempt, then uses confirmed logs and balance deltas to update accounting.
The schedule survives process restarts
A workflow receives only the agent ID and schedule version. Database, cryptography, RPC, and signing work stays inside retryable server steps.
A failed invariant prevents signing
These checks are authorization and accounting boundaries, not decorative dashboard states. Browser controls never replace server enforcement.
Robinhood Chain mainnet configuration
Public identifiers are fixed in the application catalog and independently checked against live contract metadata before writes are enabled.
