Contract Addresses

The OddMaki protocol is a single EIP-2535 Diamond deployment — one address fronts every facet. External dependencies (Gnosis CTF, USDC, UMA, Pyth) are separate onchain contracts.

Base Mainnet (Chain ID: 8453)

The canonical production deployment.

The SDK defaults to Base mainnet when no chain is specified:

import { createOddMakiClient } from '@oddmaki-protocol/sdk';
import { base } from 'viem/chains';

const client = createOddMakiClient({
  chain: base,
  walletClient,
});

Base Sepolia Testnet (Chain ID: 84532)

For integration work and pre-deployment testing.

Pass baseSepolia from viem/chains when constructing the client to target the testnet.

Testnet faucets: grab free Sepolia ETH from the Base faucets, and mint test USDC from the Circle USDC faucet (pick "Base Sepolia").

Subgraph

Subgraph endpoints, schema highlights, and query examples now live on the dedicated Subgraph page.

External Protocol Dependencies

The Diamond interacts with these external contracts; their addresses are set at deploy time and readable via ProtocolFacet:

Read the current wiring at any time:

const pyth = await client.priceMarket.getPythContract();
// ProtocolFacet also exposes getUmaOracle(), getConditionalTokens(), etc.

Verifying the Diamond

All facets are deployed as separate verified contracts. To inspect:

1. Open the Diamond address on BaseScan (or Sepolia BaseScan for testnet).
2. Use the Diamond loupe to list all facets:

const facets = await publicClient.readContract({
  address: diamondAddress,
  abi: DiamondLoupeFacetABI,
  functionName: 'facets',
});

Each entry returns (facetAddress, selectors[]). Click through to each facet address on BaseScan to view verified source.

What's Next

• Architecture → — the 21-facet layout in detail
• SDK Reference → — how the SDK wraps these addresses