Skip to main content
o1 Launchpad is designed around fixed token supply, token-only opening liquidity, permanent Uniswap v4 liquidity, and transparent fee accounting.

XORS Base Launchpad v4 audit

Independent review of the Base Launchpad v4 contracts dated August 28, 2026.

XORS Monad Launchpad v4 audit

Independent review of the Monad Launchpad v4 contracts dated September 8, 2026.

XORS Arc Launchpad v4 audit

Independent review of the Arc Launchpad v4 contracts and launch-buy adapter dated September 12, 2026.

XORS BSC Launchpad v4 audit

BSC Launchpad v4 audit report dated September 16, 2026.

XORS X Layer Launchpad v4 audit

X Layer Launchpad v4 audit report dated September 17, 2026.

XORS staking audit

Independent review of the Launchpad staking contracts on Base and Robinhood dated September 8, 2026.

XORS vesting audit

Independent pre-deployment review of the vesting contract dated September 8, 2026.

​
Audit results

XORS has independently reviewed the Launchpad, staking, and vesting contracts. Each linked report describes the reviewed version, scope, findings, and resolution status. See Production contracts for contract addresses and the staking guide for how staking works.

​
Historical reports

These reports cover earlier contract versions and remain available for reference.

XORS Launchpad audit

Independent review of the earlier Launchpad contracts dated June 29, 2026.

XORS staking audit

Independent review of the earlier staking contracts dated August 10, 2026.

​
Core safety properties

  • launch tokens have fixed supply and no mint, pause, upgrade, or balance-seizure authority;
  • opening liquidity uses launch tokens only, requires no creator paired-asset deposit, and stays in a hook-owned position that cannot be removed;
  • swap-fee balances are backed by Uniswap v4 claims until withdrawn, and all recipient credits add up to the charged fee;
  • creator rights are project-side authority only: they cover transfer of creator rights, future creator-fee routing, announcements, and optional profile editing, but never minting, balance control, upgrades, or liquidity custody;
  • the configured creator admin can immediately reassign creator rights and future creator-fee routing, but receives no token, balance, or liquidity authority;
  • a pending launch stops if a protected global setting changes before it confirms; paired-asset opening-price refreshes intentionally use the latest registered frame;
  • private keys and transaction signing remain in the user’s wallet.

​
Managed paired-asset safety boundaries

The managed factory used by both crypto-paired and stock-paired creation preserves the same immutable token, single-sided seed, permanent lock, fee escrow, and announcement boundaries. It adds:
  • a paired-asset registry; on Base, Robinhood and BSC, one active factory and hook serve both crypto-paired and stock-paired creation while each launch freezes its exact asset and market configuration;
  • per-quote revisions so an older paired-asset opening-price update cannot overwrite a newer one;
  • a restricted updater that can change only future opening-price frames;
  • a 64-item batch limit for quote-management operations;
  • an 01 address-suffix requirement for every launch through either active factory;
  • a creation switch that affects all new launches through that factory, across its supported creation routes, and does not pause existing markets.
The paired Stock Tokens are external onchain assets. Their issuer, transfer behavior, availability, and market value are separate from the launch token and the o1 liquidity lock. The optional atomic Dev Buy has an additional adapter boundary. Only the configured launch hook may call it. The adapter validates the funding asset, connected route, permitted external venues, exact final launch pool and hook, four-hop maximum, protected minimum output, and unchanged unexpected route-asset and native-currency balances in the adapter and SwapX router. Base, Robinhood and Monad use chain-specific venue configuration, so a route supported on one chain is not automatically valid on another. A failed adapter check reverts the launch and buy together.

​
Governance boundary

Governance can update defaults for future launches only. A completed launch keeps its token supply, pool, fee component rates, fixed recipients, and permanent liquidity. The current creator-fee recipient is the documented exception for future creator credits. See Configuration and governance for the complete boundary. The current governance owner and platform fee receiver are listed in Production contracts.

​
What users and integrators should verify

  • use the current factory and contract addresses for the selected chain;
  • confirm the wallet is connected to the intended chain;
  • review current supply, paired asset, market type, opening value, creation fee, swap fee currency, and fee split;
  • inspect holders, pool liquidity, and a current sell quote before trading;
  • review the chain, contract, amounts, and wallet transaction details before signing.
To report a potential issue, follow the o1 Exchange bug bounty guidance.