Deployment status
Last reviewed: July 13, 2026.| Component | Status | Evidence |
|---|---|---|
| Unified Anchor source | Implemented | program/programs/slip contains one market family and five instructions. |
| Unified SBF | Built locally | Anchor and cargo build-sbf pass. |
| Unified IDL and Codama client | Generated | Checked into program/idls and packages/sdk/src/generated. |
| Surfpool lifecycle | Passing | Real SBF, token transfers, proof resolution, claims, and refunds. |
| SDK | Implemented | AI compiler, TxLINE client, executed transactions, builders, readers, subscriptions, proof mapping, and integer money helpers. |
| Keeper | Implemented | Unified discovery and terminal-priority resolve/void policy. |
| Web | Implemented | AI Rulebook route, market list, creation, detail, stake/claim, tickets, and public reads. |
| Public devnet unified program | Not deployed | Published program may still be the legacy binary. |
| Public write controls | Disabled | NEXT_PUBLIC_SLIP_MARKET_ENABLED defaults to false. |
| Mainnet | Not deployed | No mainnet claim is made. |
Consequence for judges
The repository contains a working local implementation, but judges cannot complete the unified create-to-claim lifecycle on public devnet until the upgrade authority deploys the checked-in binary. The UI hides unsupported writes rather than presenting controls that would fail against the legacy program.External completion conditions
Deployment becomes complete only after all of the following exist:- an authorized upgrade transaction for the exact checked-in SBF;
- confirmation that the deployed program exposes the unified instruction discriminators;
- one real devnet create, multi-wallet buy, resolve, claim, and refund lifecycle;
- server and browser RPCs pointed at that deployment;
NEXT_PUBLIC_SLIP_MARKET_ENABLED=truein the hosted web environment;- a working public URL or functional API/devnet endpoint supplied to judges.