Capability Status
OAW is a reference SDK. Honesty is enforced in code, not just in prose:
VenueCapabilityContract.maturityis"reference"for every shipped adapter.VenueCapabilityContract.integrationNotesstates what must be wired for production.- Every
ExecutionResultcarriesreferenceAdapter: trueand aref_-prefixed receipt, so a reference run is never mistaken for a live trade.
caution
A reference adapter proves the full control flow (authority → pre-bind → funding → gated execution → receipts) but makes no live venue API call. Production requires wiring each venue's real SDK/API. Live money movement is off by default.
Venue adapters
| Venue | Chain | Class | Auth / signing | Maturity |
|---|---|---|---|---|
| Polymarket | Polygon | prediction | deposit wallet · EIP-1271 · CLOB | reference · needs venue API |
| Hyperliquid | Arbitrum | perp / spot / HIP-3·4 | API/agent wallet · approveAgent | reference · needs venue API |
| Pump.fun | Solana | token (non-EVM) | managed Solana wallet | reference · needs venue API |
| Bankr | Base | token | Base account | reference · needs venue API |
| Virtuals | Base | ACP / token | ACP-native · Mode B sidecar | reference · needs ACP wiring |
| DegenClaw | Arbitrum | perp / spot | ACP-native · Mode B sidecar | reference · needs ACP wiring |
| Trade.xyz | Arbitrum | perp / spot | route-proof | reference · needs venue API |
| Binance · Kalshi | — | — | — | registry only (not bindable) |
Authority modes
| Mode | Who creates the wallet | Status |
|---|---|---|
| A — provider-managed (Privy) agent wallet | Your backend, programmatically | Production |
| B — linked existing Virtuals wallet | The user, in the Virtuals portal → you link it (ownership-proof) | Production |
| C — Virtuals headless create (consented) | Virtuals server API | Unverified — proposal target |
| D — register a Privy wallet into EconomyOS | Virtuals server API | Unverified — proposal target |
Modes C and D throw explicit pending-upstream errors in the reference SDK rather than fabricating support. See the Virtuals proposal.
What "live-ready" requires
A venue action is live-ready only when all of these hold:
- Agent authority resolved (Mode A or verified Mode B)
- Venue binding created through the pre-bind gate
- Funding present on the venue's settlement chain
- Venue policy + global spend caps pass
- The venue's live-execution flag is on, and approval is present where required
- A production adapter is wired (not the reference stub)
Until then OAW returns a precise status (ready_but_live_locked, requires_approval,
agent_wallet_required, …) — never a fake "it traded" signal.