The three augmentations
What the V3 pivot bought us
The v0.3 thesis is that DeepBook V3 is the trading engine for everything:
The v0.2 internal AMM and Seal-encrypted intent ledger were deleted. They served their purpose but don’t fit V3-native architecture.
Full system

Signed PTBs go from the React frontend to four on-chain targets. The Docker-composed backend runs api, indexer, quote-worker, resolver, and agent-service, fronted by Postgres and Redis. Pyth Hermes feeds prices to the resolver.
On-chain layering

DarkPool sits on top of Predict and V3. We add three module groups: vault privacy, agent delegation, non-price resolution. Predict and V3 are unchanged. Sui is the foundation.
Sui-unique advantages
- Atomic PTB settlement. Pyth price update + OracleSVI settle + position redemption + fee distribution in one transaction.
- TradeCap delegation. Agents trade without withdrawal rights via DeepBook V3’s existing capability pattern.
- Move-native Optimistic Oracle. Bond-backed propose/dispute on-chain, settles in minutes.
- PLP share-based liquidity. AI agents act as 24/7 vault suppliers.
Invariants
- Attribution.
predict_facade::attribute_*is wired into the resolver’s settlement PTB andscripts/supply-plp.ts. Frontend and agent-service mints are unattributed. - Predict pin.
predict-testnet-4-16. Never referencemain. - Env.
.envis gitignored,.env.exampleis the schema, zod throws on missing required vars. - Binary market = one Move publish. Slug must match
/^[a-z0-9_]+$/. Registry on disk is authoritative. - DUSDC is the only quote asset Predict accepts:
0xe95040…::dusdc::DUSDC. agent::pauseandresumeemit no events. Authoritative source issui.getObject(TradeAgent).is_active.

