Schemas

PairStreet stores each Pair MarketPair MarketThe canonical pairing of an internet asset with a financial Pair: TOKEN × PAIR INSTRUMENT, plus the Pair Vault, configuration and accounting that connect them. as two separate histories. The internet market (the coin, its Pump curve, trades, candles and holders) lives in tokens, token_markets, trades and holder_balances. The financial Pair (the instrument, the vault, settlements, purchases and rewards) lives in pair_markets and the ledger tables beneath it. The two never share a row. Market cap describes the first history; Pair ValuePair ValueThe current tracked value of Pair Assets associated with a Pair Market according to PairStreet accounting: Σ quantity × reference price. Independent of the token's market cap. describes the second.

The schema is Postgres, defined with Drizzle. Three conventions hold across every table:

*_raw

Integer base-unit amounts as numeric(40,0), read as decimal strings. No floating-point drift in balances or allocations.

*_usd

numeric(24,6) read as numbers. Display and aggregation values, never the source of truth for a balance.

ledger_mode

Every financial row carries live or dev_simulated. Production reads and writes live rows only. See Ledger modeLedger modeEvery financial ledger row carries live or development. Production reads and writes live rows only..

Table pair_markets. One row per token (token_id is unique): the canonical TOKEN × PAIR INSTRUMENTPair InstrumentThe financial exposure a Pair Market is paired with, such as Tokyo Residential or Swiss Government Debt. A catalog object with a provider, an eligibility policy and a status. relationship. The aggregate columns are a read model maintained by the Pair engine from the ledger tables.

Live markets register with status settlement_disabled (shown as “Settlement pending”) and nextSettlementAt null. Each instrument’s settlement route and vault custody activate the status change to active. See Pair Markets for the lifecycle.

The configuration column holds the rules that turn trading activity into Pair Asset for holders. New markets get PairStreet’s default configuration; the feeSplit block is written from the chain by the fee-split sync after launch.

{
  "economicSources": [
    { "source": "creator_fees", "bps": 2500 },
    { "source": "launch_economics" }
  ],
  "rewardMethodology": "time_weighted_balance",
  "settlementCadenceSec": 3600,
  "excludeCreator": true,
  "excludeLiquidityAccounts": true,
  "excludedWallets": [],
  "feeSplit": {
    "creatorBps": 5000,
    "protocolBps": 2500,
    "pairVaultBps": 2500,
    "treasury": "5XAwPtXHkA2F68tEj5ZAZePJfJWH4tzGkeQiqK5ggfRg",
    "status": "locked",
    "sharingConfig": "<sharing-config-pda>",
    "shareholders": [
      { "address": "<creator-wallet>", "shareBps": 5000 },
      { "address": "5XAwPtXHkA2F68tEj5ZAZePJfJWH4tzGkeQiqK5ggfRg", "shareBps": 5000 }
    ],
    "checkedAt": "<timestamp>"
  }
}

On-chain there are two shareholders. The 50/25/25 split is the accounting view: the treasury’s 50% is protocol revenue (25%) plus the market’s Pair Vault reservePair Vault reserveThe 25% share of a Pair Market's creator fees earmarked for its Pair Vault. Held by the PairStreet treasury until the market's settlement route activates. (25%). That is why economicSources lists creator_fees at 2,500 bps. See Protocol Economics.

Table pair_instruments. The catalog of financial exposures a creator can pair with. 44 instruments today. The slug is the stable human key used in URLs and the API; the id is a UUID.

Example record

The Tokyo Residential record as the catalog stores it. Tokyo Residential is a Pair Instrument representing the target financial exposure configured for the Pair Market. It is listed by the PairStreet Pair Registry, so mintAddress is null and verification is listed: settlement into a Pair Asset activates when its provider route connects.

{
  "id": "<instrument-uuid>",
  "slug": "tokyo-residential",
  "name": "Tokyo Residential",
  "shortName": "Tokyo Residential",
  "symbol": "TKYRES",
  "description": "Exposure to Tokyo's residential property market: condominiums and rental housing across the 23 wards, tracked as a residential real-estate basket.",
  "category": "real_estate",
  "subcategory": "Residential",
  "country": "JP",
  "region": "asia",
  "providerId": "pairstreet-registry",
  "issuer": "PairStreet Pair Registry",
  "network": "solana",
  "mintAddress": null,
  "decimals": 6,
  "assetType": "housing_index",
  "settlementAsset": "<usdc-mint>",
  "status": "active",
  "verification": "listed",
  "isMock": false,
  "transferRestrictions": { "summary": "Onchain settlement asset connects when this Pair's provider route goes live." },
  "priceSource": "index-reference",
  "providerReference": "registry:tokyo-residential",
  "documentationUrl": null,
  "icon": "home",
  "heroImage": null,
  "referencePriceUsd": 100,
  "referencePriceAt": "<timestamp>",
  "searchTerms": "tokyo housing homes residential property real estate japan condo apartments rent japan",
  "metadata": {},
  "createdAt": "<timestamp>",
  "updatedAt": "<timestamp>"
}

Spec fields and where they live

provider

providerId, joined to pair_providers for name, kind and adapter.

restrictions

transferRestrictions on the instrument, plus eligibility rules in instrument_eligibility.

reference source

priceSource, with referencePriceUsd and referencePriceAt.

documentation

documentationUrl; the provider interface also returns issuer documents.

instrument_eligibility

pair_providers

id (stable slug, also the adapter registry key), name, kind (provider_kind), adapterKey (registry or spl-onchain today), website, description, isMock, status and createdAt. See Providers.

Table pair_vaults. One vault per Pair Market. A vault row is written when the market’s vault custody activates; until then a live market’s Pair Vault reserve accrues to the treasuryPairStreet treasuryThe protocol wallet that receives the protocol share and Pair Vault reserve of creator fees plus the 0.5% trading fee., earmarked per market, and the market detail API reports custodyModel: "pending". See Pair Vault.

pair_vault_fundings

A settlementSettlementOne turn of a Pair Market's flywheel: the Pair Vault balance is routed, the Pair Asset acquired, accounting finalized and a reward epoch funded. converts a vault’s settlement balance into the Pair Asset through the Pair RouterPair RouterThe execution layer that converts a Pair Vault's settlement balance into an acquisition plan for the Pair Asset and hands it to the right executor.. The plan is persisted for audit, and each acquisition is its own row. See Settlement.

A reward epochReward EpochA window over which acquired Pair Asset is allocated to eligible holders by their holder weight. Produces exact integer allocations and a Merkle root. divides the Pair Asset acquired in a settlement across eligible holders by holder weightHolder WeightA holder's share basis inside a reward epoch. Under the time-weighted method: the integral of balance over time held inside the epoch (token-seconds).. Allocations sum exactly to the pool, and the epoch stores a Merkle root over (wallet, amountRaw) leaves for an onchain distributor. See Holder Rewards.

Demand for instruments not yet in the catalog. Requests aggregate by a normalized key, and each voter counts once. See Pair Requests.

pair_request_votes holds one row per voter per request (requestId, voterKey, wallet, creatorIntent, note), unique on request and voter. The voter key is the wallet when one is connected, otherwise an anonymous visitor id.

The internet-market side, summarized. These tables are written by launch and kept current by the indexer.

tokens

id, mint (unique), name, symbol, description, imageUrl, website, twitter, telegram, creatorWallet, launchVenue (pump), decimals (6), totalSupplyRaw, metadataUri, launchTxSignature, ledgerMode, createdAt.

token_markets

Latest venue state, one row per token: bondingCurveAddress, ammPoolAddress, reserves (reserveQuoteRaw, reserveTokenRaw, realQuoteRaw), priceUsd, priceSol, marketCapUsd, liquidityUsd, volume24hUsd, volumeLifetimeUsd, change24hPct, holders, txns24h, bondingProgressPct, graduationStatus, graduatedAt, trendingScore, lastTradeAt, updatedAt.

trades

One row per trade: side, token and quote (lamport) amounts, USD value, price, signature, block time.

holder_balances

Balance per token and wallet, firstHeldAt, and excludedReason for accounts excluded from Pair rewards (creator, vault, curve or pool, configured).

supporting

wallets, creator_profiles, activity_events (see Events), protocol_metrics (daily snapshots for analytics), indexer_cursors, uploads and metadata_docs.

Every enum is defined once in the shared domain module and generated into Postgres. The API returns these exact strings.

Pair Market and token

Instrument and provider

Settlement, rewards and ledger

Categories, regions and asset types are listed with the Pair Instrument columns above. The HTTP shapes built from these tables are documented in API.