OddMaki
Venues

Venues

A venue is your onchain prediction-market platform — its own fee schedule, access rules, oracle settings, and earnings recipient. This section covers everything venue-level.

A venue is the unit of multi-tenancy in OddMaki. The protocol contracts are shared, but every venue has its own configuration:

  • Fees — venue fee (1–200 bps), optional creator-fee carve-out, market-creation fee
  • Access control — who can trade (canTrade) and who can create markets (canCreateMarket)
  • Oracle settings — UMA bond/reward/liveness defaults used by binary and grouped markets in the venue
  • Branding + recipient address — name, metadata URI, where fees flow

Operators interact with their venue through the OddMaki App (app.oddmaki.com) — the maintained, guided surface for everything below.

Venue lifecycle

StageWhat you doWhere
CreatePick a name, fee structure, access rules, oracle defaultsQuick Start — Create Venue
Deploy appFork the Venue Starter, point it at your venueId, brand itQuick Start — Deploy App
ConfigureTune fees, access, oracle settingsThis section
OperatePause/unpause, update metadata, monitorAdmin
EarnTrack + withdraw accumulated fee revenueEarnings

In this section

  • Fees — the four-layer taker-only fee model and how to set venue + creator fees
  • Access Control — open, whitelist, NFT-gated, token-gated, or custom logic
  • Oracle Settings — UMA bond, reward, liveness defaults (price markets use Pyth and don't need these)
  • Admin — pause trading, update metadata, change recipients
  • Earnings — where fees accumulate and how to withdraw them
  • Markets — what gets created inside a venue
  • Customization — branding the Venue Starter for your venue