# AgentCity: Robinhood Chain ecosystem snapshot

**To:** Nova, Research lead — literature and evidence  
**For:** AgentCity client  
**Research cut-off:** 8 October 2026  
**Scope:** public-mainnet ecosystem; not investment, legal, or compliance advice.  

## Executive finding

**Confirmed.** Robinhood Chain is a live, permissionless, Ethereum-compatible Layer 2 (chain ID 4663), publicly launched on 1 July 2026. It is built with Arbitrum technology, uses ETH for gas, targets financial applications and tokenized real-world assets, and is separate from a Robinhood brokerage account. [Robinhood’s mainnet announcement](https://robinhood.com/newsroom/robinhood-accelerates-global-expansion-robinhood-chain-mainnet-stock-tokens-agentic-trading/) and [network support reference](https://robinhood.com/us/en/support/articles/robinhood-chain-testnet/) support these claims. “AI-native” is product positioning, not proof that an autonomous agent is safe or authorized to trade.

For AgentCity, the immediate value is an EVM settlement layer with active swap/lending infrastructure and programmable stock-token data. The important caveat is that the public mainnet is young, control is not fully decentralized, and the evidence for a Robinhood Chain NFT marketplace or full wallet NFT support is presently incomplete.

## What the chain is

**Confirmed.** Any EVM wallet can add the chain and Robinhood Wallet supports it natively. Fees are ETH. The canonical bridge moves ETH/ERC-20s between Ethereum and the L2 (estimated deposits ~10 minutes; withdrawals ~seven days); LayerZero/Stargate and Chainlink CCIP/Transporter are partner routes. [Network configuration](https://docs.robinhood.com/chain/add-network-to-wallet/) and [bridge documentation](https://docs.robinhood.com/chain/bridging/).

**Confirmed.** Its security/governance model has material centralized components: an eight-seat Security Council (Robinhood holds two seats); ordinary changes require 6/8 approvals and a seven-day timelock, while emergencies require 7/8 and bypass the timelock. BoLD dispute resolution currently has two permissioned validators, run by Offchain Labs and Alchemy. [Robinhood Chain governance documentation](https://docs.robinhood.com/chain/governance/) is explicit on both points.

**Inference.** “Permissionless to deploy and use” should not be read as “trust-minimized like Ethereum L1.” An AgentCity treasury must treat sequencer, bridge, validator, upgrade, and smart-contract risk as separate dependencies, with spending limits and an exit plan.

## Apps, infrastructure, and tokens

| Area | Confirmed snapshot | Why it matters to AgentCity |
|---|---|---|
| Wallet/access | Robinhood Wallet and standard EVM wallets can connect; the chain is separate from brokerage/crypto accounts. | Distinct agent addresses and auditable permissions. |
| Public exchange | Uniswap v2/v3/v4 and UniswapX are live; Robinhood also names Rialto, Lighter, Arcus, and 1inch as DEX paths. [Uniswap](https://blog.uniswap.org/robinhood-chain-is-live), [Robinhood](https://robinhood.com/newsroom/robinhood-accelerates-global-expansion-robinhood-chain-mainnet-stock-tokens-agentic-trading/). | Measure routing, liquidity, price impact, and contract addresses at transaction time. |
| Lending/perpetuals | Robinhood’s wallet lending path uses Morpho; wallet perpetuals use Lighter. | Evaluate; leveraged products can lose principal. |
| Data/infrastructure | Robinhood names Alchemy, BitGo, and Chainlink; every Stock Token has a Chainlink feed. | Feeds and contracts remain dependencies. |
| Gas and bridge assets | ETH is the gas asset. Documentation specifically names ETH/ERC-20s on the canonical bridge and WBTC and USDG on a LayerZero/Stargate route. | There is no evidence here of a native “ROBINHOOD”/“HOOD Chain” gas token; do not invent one. Verify every token address against the relevant canonical registry. |
| Flagship assets | Robinhood Stock Tokens are 18-decimal ERC-20 tokenised debt securities representing economic exposure to named US shares/ETFs; they are not ownership of the underlying share. Only an authorised participant (currently BBVI at issuance) mints/redeems directly after KYB. [Stock Token documentation](https://docs.robinhood.com/chain/stock-tokens/) and the [live canonical-contract registry](https://docs.robinhood.com/chain/contracts/) are the authoritative sources. | Contracts can compose these assets (e.g., price display, collateral logic), but AgentCity must block restricted users/jurisdictions and must not equate them with equities or voting rights. |

**Confirmed limitations.** Stock Tokens are not available to US persons and have other jurisdictional restrictions. Minting/burning is not continuously open, even though end users may trade onchain outside the tokenization window. Asset-specific trading capability must be checked. Dividends and splits are reflected through an onchain multiplier, while the Chainlink price incorporates it. These mechanics make naïve “one token = one share” accounting wrong. [Stock Token documentation](https://docs.robinhood.com/chain/stock-tokens/).

**Unanswered.** Reviewed sources do not provide an auditable ranking by volume, TVL, users, or liquidity. “Main” means named by Robinhood or a primary protocol, not market share.

## NFTs and marketplaces

**Confirmed.** Because Robinhood Chain is EVM-compatible, a developer can deploy ordinary Ethereum-compatible contracts. ERC-721 defines a standard NFT interface for unique assets and transfers; ERC-1155 is the multi-token standard. [ERC-721](https://eips.ethereum.org/EIPS/eip-721) and [ERC-1155](https://eips.ethereum.org/EIPS/eip-1155) are the primary standards. Thus an NFT collection *can* be built as an EVM smart contract, with ownership onchain and metadata commonly referenced by a token URI.

**Inference (conditional implementation path).** A town parcel, resident credential, or limited-edition object could use ERC-721 for unique items or ERC-1155 for editions. A marketplace would need a separately deployed trading contract or a confirmed compatible third-party marketplace: seller grants a narrowly scoped approval, creates a listing/order, buyer settles in an accepted ERC-20/ETH, and the contract transfers the NFT. Metadata hosting, royalties, indexing, discovery, and the marketplace’s enforcement policy are application choices—not supplied by the token standard.

**Uncertainty that should change the plan.** I found no first-party claim of a Robinhood Chain-native NFT marketplace, no official marketplace contract/address, and no promise that Robinhood Wallet presently receives or sends NFTs on Robinhood Chain. Its current NFT support page lists receiving/storing NFTs only on Ethereum, Polygon, Arbitrum, Optimism, and Base; it also says sending is future work. That is evidence of a support gap, not proof that no third-party marketplace exists. [Robinhood Wallet NFT support](https://robinhood.com/us/en/support/articles/nfts/). Robinhood’s brand rules also prohibit putting its marks in NFT artwork, metadata, or smart-contract attributes. [Brand guidelines](https://docs.robinhood.com/chain/brand-guidelines/).

**Practical conclusion.** Pilot NFTs only with a browser EVM wallet and a minimal self-hosted marketplace or independently verified marketplace deployment. Do not promise Robinhood Wallet display, transfer, or discovery until documented and tested. Treat unsolicited NFTs and blanket `setApprovalForAll` as high-risk; Robinhood warns of malicious contracts and fake marketplaces.

## Three concrete opportunities for an AI-agent town

1. **Policy-bounded civic treasury and micro-procurement.** Give each service agent a capped wallet and policy contract: approved counterparties, per-job/daily caps, expiry, dual approval for large spends, and logs. Pay for compute, data, or resident services in ETH/verified ERC-20s; use a small verified DEX allowlist. **Inference:** fast EVM transactions and agent-oriented positioning make this a credible pilot. **Guardrails:** no unrestricted keys or blanket approvals, simulate before broadcast, and retain pause/multisig control. Exclude Stock Tokens until counsel and residency controls approve a use.

2. **Agent reputation, work permits, and town objects.** Mint non-transferable/restricted credentials for completed jobs, authority, or verified sponsors; reserve transferable ERC-721/1155 for town parcels, tickets, or artifacts. **Inference:** standards supply portable primitives and logs make issuance/revocation auditable. **Constraint:** initial UX must sit outside Robinhood Wallet and omit Robinhood marks. Resolve privacy, revocation, Sybil resistance, metadata persistence, and marketplace choice before public minting.

3. **Open financial intelligence, not autonomous speculation.** Build a dashboard/agent service that reads canonical Stock Token contracts, Chainlink feeds, and the asset API; flag multiplier/corporate-action changes, session status, pool liquidity, and bridge delay. Start read-only; let only a human or constrained policy sign pre-approved rebalances. **Confirmed substrate:** ERC-20 Stock Tokens have feeds/API and Robinhood says agents can transact. **Inference:** monitoring is a better first use than free-form trading. **Constraint:** show eligibility limits and debt-security status; never execute for barred users or rely on unaudited LLM output.

## Decision gates and unanswered questions

Before deploying funds or public collectibles, obtain answers through live tests and legal review:

1. Which jurisdictions and legal entities will own AgentCity wallets, and are they eligible for every planned token/service?
2. Which exact canonical contract addresses, RPC provider, bridge, DEX pools, marketplace contract, and wallet UX pass a small-value end-to-end test?
3. What are current liquidity, fees, oracle update behaviour, withdrawal experience, incident response, and upgrade/validator risk tolerances?
4. Does a chosen NFT marketplace index Robinhood Chain and support the desired ERC-721/1155, royalties, metadata, and agent-wallet flows?
5. What human authority can pause/revoke an agent, rotate keys, dispute a payment, and meet tax/accounting obligations?

## Sources and evidence note

All web sources below were accessed 8 October 2026. First-party Robinhood documentation and named protocol materials were preferred. “Confirmed” means directly supported by a cited source; “Inference” is a reasoned proposal; “Unanswered/uncertainty” marks claims the reviewed sources did not establish.

1. [Robinhood: public-mainnet and ecosystem announcement, 1 July 2026](https://robinhood.com/newsroom/robinhood-accelerates-global-expansion-robinhood-chain-mainnet-stock-tokens-agentic-trading/)
2. [Robinhood Chain documentation: network configuration](https://docs.robinhood.com/chain/add-network-to-wallet/)
3. [Robinhood Chain documentation: bridging](https://docs.robinhood.com/chain/bridging/)
4. [Robinhood Chain documentation: governance](https://docs.robinhood.com/chain/governance/)
5. [Robinhood Chain documentation: Stock Tokens](https://docs.robinhood.com/chain/stock-tokens/)
6. [Robinhood Chain documentation: canonical token contracts](https://docs.robinhood.com/chain/contracts/)
7. [Uniswap: Robinhood Chain deployment announcement, 2 July 2026](https://blog.uniswap.org/robinhood-chain-is-live)
8. [Robinhood Wallet: NFT support and risks](https://robinhood.com/us/en/support/articles/nfts/)
9. [Ethereum ERC-721 standard](https://eips.ethereum.org/EIPS/eip-721) and [ERC-1155 standard](https://eips.ethereum.org/EIPS/eip-1155)