Architecture

Overview

Strike's protocol is composed of six core contracts:

MarketFactory (singleton)
  │
  ├── Creates markets (EIP-1167 clones)
  ├── Manages protocol parameters
  └── Admin controls
       │
       ▼
┌──────────────────────────────────────────────────────┐
│  Per-Market Contracts (isolated state per market)     │
│                                                       │
│  OrderBook ←→ BatchAuction ←→ ClaimSettlement        │
│      │              │                                 │
│      ▼              ▼                                 │
│  SegmentTree    BatchResult storage                   │
│  (per-side)     (per-batch)                          │
└──────────────────────────────────────────────────────┘
       │                    │
       ▼                    ▼
    Vault              OutcomeToken
  (collateral)        (ERC-1155)
       │                    │
       ▼                    ▼
  PythResolver ──→ Redemption
       │
  Pyth Oracle (on-chain)

Contract Relationships

Contract	Role	Pattern
MarketFactory	Deploys + registers markets	Singleton
OrderBook	Order placement, cancellation, storage	Per-market (EIP-1167 clone)
BatchAuction	Clearing algorithm, batch results	Integrated with OrderBook
Vault	Collateral custody, locks, accounting	Singleton
OutcomeToken	ERC-1155 YES/NO tokens	Singleton
PythResolver	Oracle verification, resolution	Singleton (called per-market)
SegmentTree	Price-level aggregate volumes	Library (used by OrderBook)
FeeModel	Fee calculation, bounties	Library or singleton

Design Principles

Per-market isolation. Each market's orderbook state is isolated via EIP-1167 minimal proxy clones. This prevents cross-market contention and bounds worst-case gas costs to a single market's depth.

Bounded iteration. No contract function iterates over an unbounded set. Segment trees provide O(log N) operations. Claim and prune functions take explicit order ID arrays from the caller.

Lazy settlement. Batch clearing writes only aggregate results (clearing price, fill fractions, total volume). Individual fills are computed and settled when traders call claimFills(). This keeps clearBatch() gas cost constant regardless of order count.

Permissionless operations. Clearing, resolution, and pruning are all callable by anyone. Economic incentives (resolver bounty, pruner bounty) ensure they happen without relying on trusted operators.