Status
What runs on Solana mainnet today, how settlement activates for each Pair Instrument route, and how to verify every statement on this page on-chain. Updated 4 October 2026.
Summary
PairStreet launches and trades Pair Markets on Solana mainnet today. Settlement into each Pair Asset activates per instrument route.
The protocol has two layers that activate on different schedules. The launch and market layer (creating the coin, attaching the 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., splitting creator fees, trading) is live for every 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.. The settlement layer (the Pair VaultPair VaultThe account that receives settlement value allocated to one Pair Market, holds it until conversion, and holds the acquired Pair Asset until it is allocated to holders., 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., reward epochs and claims) is implemented as an engine and activates instrument by instrument, as each instrument’s provider route and vault custody come online.
This page separates four things the rest of the documentation also keeps apart: protocol capability, instrument availability, provider activation and settlement status.
Figure summary: The twelve-station Pair lifecycle. Creator, token launch, Pump and Solana market, Pair Market and economic flow run on Solana mainnet today. Pair Vault, Pair Router, provider, Pair Asset, reward epoch, eligible holders and claim activate per Pair Instrument as its settlement route comes online.
Live on Solana mainnet
| Capability | Status | What runs |
|---|---|---|
| Pair Market launch | Live | Pump create_v2 with create_fee_sharing_config, built by PairStreet and signed in one wallet prompt. Confirmation verifies the transaction on-chain and registers the Pair Market. |
| Creator-fee split | Live | Locked on-chain at launch with Pump update_fee_shares: 50% creator, 25% protocol, 25% 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.. On-chain: creator 50%, treasury 50%. Pump locks the config after it is set. |
| Creator-fee distribution | Live | Pump’s permissionless distribute_creator_fees, triggered by anyone from the market page. |
| Trading | Live | Buys and sells on the Pump bonding curve with a 0.5% PairStreet fee on the SOL side, transferred to the treasury in the same transaction. |
| Pair Instrument catalog | 44 instruments | Bonds, housing, real estate, credit, equities, sectors, commodities, rates and funds. Creators pair with any active instrument. |
| Eligibility Engine | Live | Country and region rules evaluated per instrument from the request’s edge country, before launch and before claims. |
| Pair Requests | Live | Requests for instruments not yet listed, aggregated with one count per voter and ranked by demand. |
| Market data indexing | Live | Pump curve reads (price, reserves, progress, graduation), DexScreener, GeckoTerminal candles, Jupiter prices and quotes. Throttled, cached, last good value kept on failure. |
| Search | Live | Instruments, markets, creators, categories, countries and Pair Requests. |
| Analytics | Live | “What is crypto buying?”: Pair Markets aggregated by instrument, category and country. |
| Activity | Live | TOKEN_CREATED and PAIR_SELECTED at launch, PAIR_REQUESTED for requests. Settlement events go live with settlement. |
Launch was validated end to end against the real Pump programs cloned from mainnet onto a local validator before release. Every launch and trade is built server-side as an unsigned transaction and signed in the user’s wallet; PairStreet never holds a user key. See Pump and Solana and Protocol Economics.
Settlement status per instrument route
Five instruments have onchain Pair Assets with live ONCHAIN_SWAP quotes from Jupiter today. They are issuer tokens that PairStreet references through public onchain routes. The other 38 are listed by the PairStreet Pair Registry: creators pair with them today, and the settlement asset connects when each provider route activates.
| Instrument | Pair Asset | Issuer | Route | Settlement |
|---|---|---|---|---|
| U.S. Dollar Yield | USDY | Ondo Finance | Route ready | Quotes live; execution activates with Pair Vault custody |
| Mexican Government Bonds | CETES | Etherfuse | Route ready | Quotes live; execution activates with Pair Vault custody |
| UK Government Gilts | GILTS | Etherfuse | Route ready | Quotes live; execution activates with Pair Vault custody |
| Gold | XAUt0 | Tether Gold | Route ready | Quotes live; execution activates with Pair Vault custody |
| Gold (PAX Gold) | PAXG | Paxos | Route ready | Quotes live; execution activates with Pair Vault custody |
| 38 registry instruments | Per route | PairStreet Pair Registry | Activates per route | Listed for pairing; settlement activates with the provider route |
| Brazilian Treasury Bonds | TESOURO | Etherfuse | Provider unavailable | Closed to new markets until the provider route returns |
The registry instruments include Tokyo Residential, Japan Government Bonds, Swiss Government Debt, NYC Municipal Debt, U.S. Housing and Global Banking. Tokyo Residential is a Pair Instrument representing the target financial exposure configured for the Pair Market; the asset delivered to holders is defined when its provider route connects. See Pair Instruments and Providers.
Protocol components
Each component of the settlement layer, with what exists in the codebase and what activates it.
| Component | Status | Detail |
|---|---|---|
| Pair Router: ONCHAIN_SWAP | Route ready | Plans acquisitions with live Jupiter quotes for SPL instruments. Execution activates with Pair Vault custody. |
| Pair Router: PROVIDER_API, RFQ, ISSUER_MINT, BROKER_ROUTE | Architecture | Interfaces defined in the router and provider contract; each activates with a provider that implements it. See Pair Router. |
| Settlement engine | Activates per route | Implemented: vault balance, router plan, acquisition, Pair Asset in vault, reward epoch. Every step writes ledger rows, and the read model is rebuilt from the ledger in tests. See Settlement. |
| Reward engine | Activates per route | Implemented and tested: time-weighted, average and snapshot methods, exact largest-remainder allocation, Merkle root and proofs. Live claims activate with settlement. See Holder Rewards. |
| Holder indexing | In integration | Live holder balances from a Helius webhook or Geyser stream of Pump program events, feeding live reward weights. |
| PumpSwap routing | In integration | Trading for graduated markets through PumpSwap. The trade panel builds bonding-curve trades today. |
| Pair Vault custody | Activates per route | Activates per instrument route. Custody models program_pda and multisig are planned; the schema also defines provider_custody for routes where the provider holds the asset. |
| Onchain Merkle distributor | Planned | Pays claims against each epoch’s allocation root from the Pair Vault. Activates with settlement. |
| $STREET | Planned | The PairStreet protocol token. Not launched; no contract address exists. Planned protocol economics: treasury-executed buybacks from protocol revenue. |
| Treasury multisig | Planned | The treasury is a single PairStreet-controlled wallet today. |
| Public versioned API | Planned | Versioned paths, API keys and stability guarantees. See Coming API. |
| Audit | Not yet audited | Audit status: not yet audited; an audit precedes Pair Vault program activation. PairStreet deploys no custom onchain program today: it composes Pump’s programs, the Pump fees program and System transfers. |
Operating model today
- User keys
- Never held. Transactions are built server-side, simulated by the client and signed in the user’s wallet.
- Onchain programs
- Pump, the Pump fees program and the System program. No PairStreet program is deployed.
- Treasury
- Single-signer wallet. Receives trading fees and the treasury share of creator fees.
- Ledger
- Postgres. Every financial row carries ledger_mode; production reads and writes live rows only.
- Rate limits
- Per IP, per server instance. A shared store is planned.
Details and the threat model are in Security; recovery behavior is in Failure Modes.
Recently shipped
This release.
- ·On-chain creator-fee split. Every launch creates a Pump fee-sharing config for its mint and sets creator 50%, treasury 50% in the same wallet prompt. Pump then locks the split. If the split transaction does not land, the market shows “Split pending” and the creator finishes it with “Lock fee split”. Anyone can pay out accrued fees with “Distribute creator fees”.
- ·Trading fee. 0.5% of the SOL side of every trade built by PairStreet, paid to the treasury in the trade transaction. A fee too small to fund a treasury below Solana’s rent-exempt minimum is skipped so the trade always proceeds.
- ·Documentation. This site, at docs.pairstreet.xyz.
How to verify
Every live claim on this page can be checked on-chain without trusting PairStreet.
- Step 01TREASURYOpen the treasury5XAwPtXHkA2F68tEj5ZAZePJfJWH4tzGkeQiqK5ggfRg. Trading fees arrive as System transfers inside trade transactions; the treasury share of creator fees arrives through Pump’s
distribute_creator_fees. - Step 02PROGRAMSCheck the programsPump 6EF8rrecthR5Dkzon8Nwu78hRvfCKubJ14M5uBEwF6P, Pump fees pfeeUxB6jkeY1Hxd7CsFCAjcbHA9rWtchMGdZ6VojVZ and PumpSwap AMM pAMMBay6oceH9fJKBRHGP5D4bD4sWpmSwMn52FMfXEA. PairStreet deploys no program of its own: launches and trades compose these Pump programs with Solana’s standard programs.
- Step 03PER MINTRead a market’s fee-sharing configOn any market page, the Creator fees panel shows “Locked on-chain” and links the mint’s fee-sharing config account to the explorer. Its shareholders are the creator at 5,000 bps and the treasury at 5,000 bps. The same data is returned by
GET /api/markets/<mint>/fees, read from chain on each call. - Step 04LAUNCHInspect the launch transactionThe market detail carries
launchTxSignature. On the explorer it shows Pumpcreate_v2andcreate_fee_sharing_configsigned by the creator and the mint. - Step 05TRADEInspect a tradeA PairStreet buy or sell contains the Pump instruction and a transfer to the treasury equal to 0.5% of the SOL side. The only exception is the rent guard described above, which skips a fee too small to fund an unfunded treasury account.
The HTTP endpoints used above are listed in API, and the stored fields in Schemas.