Ecosystem
Ecosystem
The deployable surfaces that make up the OddMaki ecosystem — protocol contracts, the official dApp, the white-label Venue Starter, the TypeScript SDK, and the indexer subgraph.
The OddMaki ecosystem is a small set of cleanly separated surfaces that you mix and match depending on what you're building.
| Surface | What it is | Who uses it |
|---|---|---|
| OddMaki Protocol | The onchain contracts (EIP-2535 Diamond + 21 facets) | Direct callers via viem/Foundry; the rest of the surfaces all delegate to this |
| OddMaki dApp | The official frontend at app.oddmaki.com — venue creation, market creation, settings, earnings | Venue operators — the recommended UI for everything venue-level |
| Venue Starter | A white-label Next.js 15 app you fork to give your venue its own branded trading frontend | Venue operators who want their own product surface |
SDK (@oddmaki-protocol/sdk) | TypeScript client wrapping the contracts and subgraph | Bots, scripts, custom UIs, CI/CD |
| Subgraph | The Graph indexer covering markets, orders, fills, positions, and analytics | Anyone reading historical data; the SDK uses it internally for analytics queries |
All five share the same data model — a fill recorded by a bot via the SDK is the same fill the dApp renders, the same fill the subgraph indexes.
In this section
- Protocol — the Diamond proxy architecture, the 21 facets, the storage namespaces, the upgrade mechanism
- Contracts — deployed addresses for Base mainnet and Base Sepolia (Diamond, CTF, USDC, UMA, Pyth)
- OddMaki dApp — what app.oddmaki.com does, who it's for, where it fits
- Venue Starter — what the starter is, what's in it, when to fork it
- SDK Reference — module-by-module reference for
@oddmaki-protocol/sdk - Subgraph — endpoints, schema highlights, common queries
Related sections
- Quick Start — wire all five together end-to-end in ~30 minutes
- Customization — once you've forked the Venue Starter, how to brand and extend it