Design Rationale#
Section purpose:
design/answers WHY the protocol is built this way — the trade-offs behind each architectural decision. how-it-works/ describes how the protocol behaves. Neither section is a how-to; for step-by-step instructions see For Traders or the SDK docs.
Seesaw makes a handful of deliberate design choices that shape how the protocol behaves. This section explains the reasoning behind them — useful background if you are integrating with Seesaw, building tooling, or just want to understand why the protocol works the way it does.
| Topic | What it covers |
|---|---|
| Order Book Design | Why YES and NO trade on a single canonical book, and how it's stored on-chain |
| Price Oracle | Why Pyth is the exclusive oracle, and how prices are sampled |
| Market Durations | Why markets run on fixed, configurable epochs |
| On-Chain Program | Why the program is built for low compute and zero-copy access |
For the user-facing explanation of how trading works, see How It Works. For technical references, see Architecture.