Venues
A venue is anything an agent trades on. OAW models each as a declarative capability contract + one adapter. Seven reference adapters ship today across EVM and non-EVM.
| Venue | Chain | Class | Auth / signing | ACP-native | Maturity |
|---|---|---|---|---|---|
| Polymarket | Polygon | prediction | deposit wallet · EIP-1271 · CLOB | — | reference |
| Hyperliquid | Arbitrum | perp / spot / HIP-3·4 | API/agent wallet · approveAgent | — | reference |
| Pump.fun | Solana | token (non-EVM) | managed Solana wallet | — | reference |
| Bankr | Base | token | Base account | — | reference |
| Virtuals | Base | ACP / token | ACP sidecar (Mode B) | ✅ | reference |
| DegenClaw | Arbitrum | perp / spot | ACP sidecar (Mode B) | ✅ | reference |
| Trade.xyz | Arbitrum | perp / spot | route-proof | — | reference |
| Binance · Kalshi | — | — | — | — | registry only |
Venue classes
- Prediction (Polymarket) — EIP-1271 deposit wallet + CLOB credentials, settles on Polygon via an any-chain deposit bridge.
- Perps / spot (Hyperliquid, Trade.xyz) — an approved API/agent wallet on Arbitrum; Hyperliquid covers HIP-3/4 assets too.
- Tokens (Pump.fun on Solana, Bankr on Base) — managed wallet / native account.
- ACP-native (Virtuals, DegenClaw) — require a linked Virtuals identity + signer and execute through the ACP sidecar under a verified Mode B authority.
Adding a venue
It is data + one adapter — no core changes:
- Add a
VenueCapabilityContractto the registry (keepbindingSupported: falseuntil the adapter can service it). - Implement a
VenueAdapter(setup/readiness/fundingTarget/executeOrPlan) using the sharedgatedExecutehelper. - If it settles on a new chain, add it to the funding chain map.
Reference, not live
Every venue above is a reference adapter — it proves the bind/fund/execute flow but
makes no live venue API call. Each contract's integrationNotes lists exactly what to wire
for production. See Capability status.