📄️ Overview
YES/NO prediction markets on Solana — the Classic (zero-sum) and Yield (capital-loss) variants, the Crucible Pool relationship, the on-chain lifecycle, and program IDs.
📄️ Creating Markets
The 5-step binary market creation flow — Classic (admin review) vs Yield (instant-live), the AI oracle analysis pass, liquidity seeding, and the seed / bot / kalshi_import / polymarket source types.
📄️ Backing & Settlement
How binary backings are placed and settled — the oracle_status lifecycle, Classic pro-rata payouts minus 2% commission, Yield 35%-forfeit / 65%-return settlement, the dispute (ML-3) path, and refund / timeout handling.
📄️ Crucible Pool
The Crucible Pool — a weekly pro-rata pool funded exclusively by binary YIELD-market forfeitures (50/50 split), with participant eligibility, epoch cadence, and claim mechanics. Separate from Echo / Forge / Seam / Core.
📄️ Oracle Resolution
How binary YES/NO markets resolve — M-of-N consensus oracle submissions, category-driven sources, confidence scoring, the dispute and admin path, and how third-party (Kalshi via DFlow, Polymarket data-only) resolution differs from native settlement.
📄️ Program & API
The binary markets on-chain surface — magma_binary_vault program ID, PDA seed table, instruction list, key account fields — plus the REST /v1/binary/* surface (503 / coming post-TGE) and SDK helpers (getBinaryVaultProgram, PDA derivation, uuidToMarketId).
📄️ Mainnet Checklist
What must change before binary markets go to mainnet — oracle threshold ≥3, 48h/72h timelocks, Kamino yield wiring, dispute bond, Squads multisig, and external audit.