Why this chain
Agents will trade here
It is the chain built around tokenized stocks and ETFs, and Robinhood has opened its surfaces to AI agents while stating plainly that it does not supervise them. That gap is the product.
ERC-8004 is already live
The canonical identity and reputation registries were deployed here by their authors, at the same addresses they carry on X Layer and Celo. Nothing had to be forked.
Gasless payments work
USDG implements EIP-3009, so a buyer can sign a transfer and never touch gas. Our facilitator broadcasts it.
Mainnet (
4663) is live for us: agent #0 on the canonical registry is ours, and
paid trust calls settle here in USDG. Testnet (46630) is beta, and carries the
full canonical ERC-8004 trio plus a deployed AgentSpendPolicy vault. Agent #0 on testnet
is ours again: on 2026-11-17 it moved from the former operating wallet, an address
A-Identity retired on 2026-11-11 because someone else holds its key, to
0xCB8824ffAF30687E36374C08eC52298b62871bdf, the founder’s wallet (tx
0x1d7a948cabe05d5b7ad51040c4ef688599f9195caf9cc31809d544924472b989). The vault on testnet
is still owned by that retired address, so it is not ours any more.
Every claim on this page is checkable at /proof/robinhood.Network config
Connect with viem
What is deployed
We did not deploy the mainnet registries. They were already live at their canonical
cross-chain addresses when we arrived; what is ours is agent #0, the first token that
registry ever minted. On testnet the ValidationRegistry implementation was the one piece
missing, and we deployed it by replaying the canonical Safe-Singleton-Factory calldata,
which reproduces the same address rather than forking a new one.
A ValidationRegistry proxy has code at the mainnet family’s address here (read live
2026-10-11; an earlier version of this page said none existed, which was wrong), but we do
not wire it, so a KYA result is not anchored on-chain there. It is still verified
off-chain and recorded; we do not claim an anchor we have not written.
The AgentSpendPolicy vault we deployed here is retired and not ours: 1 USDG a day, 0.25
USDG per payment for the agent key, and anything above is refused with the contract’s typed
AboveAutoApprove error and left to the owner. Since 2026-10-01 the agent key
(0x8C8D...3349) is a separate wallet from the owner key (0xd305...ed36), and its session key,
renewed on 2026-11-08, runs to 2027-01-07. That agent key was also our buyer wallet until
2026-11-17, when a new key took over that role as a precaution; it is still ours and not known to
be compromised, and the vault held 0 USDG when read on 2026-11-17. The owner key is the former operating wallet, which
A-Identity retired on 2026-11-11 because someone else holds its key (since at least
2026-11-01); its key was off our servers by 2026-11-14 (see
SECURITY.md), and the
contract has no owner transfer, so the vault is retired. It was emptied at 22:10 UTC on 2026-11-10 (withdraw tx
0xa67afdaec4cfe6fb8a8b851cc60b3a77ff66c1ba1e196ac489c3a69a3374041d); do not fund it. The
transactions are listed on /proof/robinhood.
Before an agent pays here, /check/robinhood
(or GET /api/robinhood/check?q=..., or the MCP tool evm_pay_check) answers whether a
token is the real USDG and whether the payee holds an ERC-8004 agent id.
The x402 facilitator
An x402 facilitator is the service a seller calls to verify a payment and settle it. We run our own here, and it is open. We are not the only one: as of 2026-09-30 other facilitators serve this chain too, hosted and open-source, some predating our launch. We run ours so that one code path and one receipt standard cover every EVM chain it sells on: since 2026-11-11, that is here and Arc Mainnet. To be precise about what that does and does not claim: gasless EIP-3009 relaying on USDG predates us on this chain by weeks, and an x402 settlement is indistinguishable on-chain from any other relayed authorization. What is ours is the facilitator below, and the rule that nothing counts as settled without a receipt carrying the matching Transfer log.
Base URL:
https://a-identity-backend.onrender.com/api/facilitator. Both x402 wire
spellings are accepted for network: the v1 slug (rhchain) and the v2 CAIP-2 id
(eip155:4663).
The signing domain is proven, not pasted. USDG exposes neither version() nor
eip712Domain(), so the EIP-712 domain cannot be read from the contract. We rebuild each
candidate domain and accept only the one that reproduces the live DOMAIN_SEPARATOR. If
none matches, no payment challenge is served at all, because inviting a buyer to sign
against a guessed domain produces an authorization nobody can settle.
