Configure, lock, prove. The fair-launch exchange on Base — every term set at inception, printed in plain language, and never changed after.
Start a launchHow it works
A pearl is not found — it is made, layer by layer, under pressure. A Pearls launch works the same way: one careful pass at the start, then the layers settle and nothing moves again.
Step 01
The creator sets everything in one launch() transaction: total supply, the distribution split, vesting terms, lock mode, and launch guards.
The split must add up exactly — vesting + airdrop + liquidity = 100% — checked on-chain before the launch exists.
Step 02
The factory deploys the token, the pool, and the locker with those terms written into immutable fields. There is no function that writes launch state after construction.
No owner. No pause. No upgrade path. If it isn't in the contract at launch, it does not exist.
Step 03
Every launch mints exactly one pearl: a launch certificate holding the full record in plain language — supply, splits, lock, vesting, fee mode, gate.
Written once, by the factory, in the launch transaction. Nobody has to take anyone's word for any of it.
The pearl is the proof
The certificate is not a badge someone grants you. It is the record the contracts themselves keep — the whole launch, printed plain, readable by anyone, forever.
One pearl is a launch. Many pearls, strung together, are a strand: launches that all played by the same visible rules, discoverable together, checkable together.
The design shown here is the certificate format from the product spec. Its final rendering is still being signed off — and the first real certificate, Pearls #0, has not been minted yet.
The fee that waits
Pearls earns nothing from a launch until the launch itself has done serious volume — and even then, the take is small, fixed, disclosed, and never paid in the project’s own token. The schedule below is the Patient tier; the full tier table and the locked deal that governs all three tiers follow.
No platform fee at all under $10M in cumulative volume. The swap that crosses the gate still pays nothing — the fee applies only to later trades.
The threshold is converted to quote-asset units once, at launch, and printed on the certificate. Anyone can re-derive it from the launch block. No price feed sits in the trade path.
Above the gate the fee is the launch’s configured rate — 30 basis points for a Patient launch — fixed at inception and never raised, for that launch, ever.
Merkle airdrop campaigns cost one exact, flat fee per campaign, with overpayment rejected. Claims are trustless against a frozen list. Optional — never required to launch.
The fee and gate are chosen at inception, from the launch’s risk tier, and can never move after. The schedule above is the Patient tier — the locked default.
| Tier | Configuration at inception | Volume gate | Fee above gate |
|---|---|---|---|
| Patient | LP burned, or locked 180 days or more | $10M | 0.30% |
| Moderate | Short timed lock | $250K | 0.45% Proposed — not locked |
| Uncommitted | No lock or burn | $20K | ≈0.58% Modeled — exact figure to be confirmed |
A timed lock that expires unrenewed is a forfeiture event, not a fee change. The 0.30% Patient rate is an introductory offer; a launch’s rate never changes once set.
Drag a lifetime volume and compare what Pearls takes from a $1,000 trade — a Patient launch beside an Uncommitted one. Same trade, same volume: the difference is the lock.
Pricing notice — for Pearls Plus+ passes and add-ons: prices and fees are subject to change without notice. Prices shown are introductory offers and discounts. The protocol fee in this panel is different — it is fixed on-chain at launch and printed on the certificate.
Locked · October 27, 2026
Lock your liquidity and Pearls costs you nothing for your first $10M of volume. That is not a promotion — it is the deal, written into the launch, and it can never be changed after. Every launch gets the same treatment: the fee and the gate are chosen at inception, printed on the certificate, and frozen. The door is open to every launch — Patient, Moderate, or Uncommitted — and the price simply reflects the risk Pearls carries.
The fee and the gate are set at launch, from the launch’s risk tier, and can never move after. No step-up when a lock expires. No ratchet down for locking later.
The 0.30% Patient rate is an introductory offer — later cohorts may be offered a higher Patient rate — but a launch’s rate never changes once set. Grandfathering is per launch, not per creator.
A timed lock’s unlock date is the forfeiture threshold — and the creator can renew before it. If it expires unrenewed, the locked LP and any emergency LP go to the Pearls treasury, after a 45-day letter stating the trigger, the date, and exactly what will be forfeited.
The trigger is automatic — no one at Pearls decides to start it. Abyssal locks never expire, so they have no forfeiture path at all.
At launch, every creator agrees — as a term printed on the certificate — that if the launch’s Risk Score falls below the safety threshold, they post an emergency LP: extra collateral held by the locker. Only creator-controlled risk can trigger it; ordinary trading cannot.
At launch the creator is also told plainly, as a term on the certificate, that the riskier path puts the whole ecosystem — and Pearls’ credibility — at risk. It is part of the launch record, not a footnote. The score threshold, the size of the emergency LP, and how the score reaches the chain are not settled yet; the numbers will be published when they are, not guessed at now.
Two things the treasury can never do on its own. Value reaches it only through the configured fee above the gate, or through forfeiture under the terms above. Pearls never seizes, freezes, or redirects a creator’s funds at its own discretion. And forfeited assets are never burned — they go to the treasury and are reinvested into Pearls. The value stays in the ecosystem.
The exchange & the back office
Pearls v0.7 is a curated exchange and launch anchor — non-custodial, end to end. The terminal routes trades you sign yourself; the console runs the membership side and never touches a launch.
/trade · the curated trading surface
Trade Pearls launches directly against their pools, and other Base tokens through standard routing — from one screen, with the certificate one click from every token.
A routing fee of 0.05–0.1% on non-Pearls swaps has been proposed, not locked — it will not appear in any public fee schedule until it is settled.
Staff-facing · the SaaS back office
The working side of Pearls: memberships, campaigns, monitoring, and the public record — run from one console that is deliberately powerless over the contracts.
Both surfaces are fast-follow work: they only have customers once launches exist, so the contract core ships first.
Who does what
No backstage. Every actor in a Pearls launch is named, and each one's power ends exactly where its job does.
Configures the launch once, in the open — then cannot change anything. Their discipline is the product.
Reads the certificate, then trades the pool. The terms they read are the terms the contracts enforce.
Deploys everything in the launch transaction and freezes the terms into immutable fields.
Guards the launch window and applies the launch’s fee rule — nothing below its gate, its configured rate in quote asset above it.
The pearl itself: the full launch record, written once, kept on-chain, readable by anyone forever.
Holds the liquidity. Abyssal locks have no withdrawal function at all; timed locks enforce a 180-day floor.
Pearls Plus+
Three passes for the people around a launch. A pass buys better tools — it never buys an advantage inside a contract, a lock, a fee, or anyone else's launch. Prices shown are introductory offers and discounts, subject to change without notice — and the passes themselves are designed, not yet built, and not for sale.
Pearls Plus+
For the person who holds, trades, and collects — and wants the fair launches to find them.
Pearls Plus+
For the person launching — or about to. Launch with your eyes open, and keep them open.
Pearls Plus+
For creators and small teams running launches as a practice, not a one-off.
Prices and fees are subject to change without notice. Prices shown are introductory offers and discounts.
Monthly only — there is no annual pricing until billing exists. Passes are memberships in off-chain tools; no subscription state ever reaches the contracts. If a membership lapses, the portal features lapse with it. Nothing on-chain changes.
Status, stated plainly
A platform about proof doesn't get to bluff about itself. Here is exactly where Pearls stands — including the unfinished parts.
| Piece | Where it stands | Status |
|---|---|---|
| Contract core | Factory, token, certificate, locker, vesting vault, airdrop distributor, attestation registry. Full test suite green; static analysis returned zero high- or medium-severity findings in Pearls sources. | Built & tested |
| Deployment | Nothing is deployed — no mainnet, no testnet launch yet. The Base Sepolia phase comes first, on a deliberate gate. | Not deployed |
| Pool hook | Core logic built; the exchange adapter is a working skeleton with its settlement wiring still to complete against the pinned pool libraries. | In progress |
| Trading Terminal | Specified in v0.7 as a fast-follow surface, after launches exist. | Designed only |
| Ops Console | Specified in v0.7 — staff-facing, off-chain, SaaS side only. | Designed only |
| Pearls Plus+ | Introductory pricing at $7 / $27 / $97, monthly only — subject to change without notice. The portal, indexer, and radars are designed, not built. | Designed only |
| Pearls #0 | The first launch will be an end-to-end testnet proof of the pipeline. Naming it is a deliberate pick, still open. | Open |
| 45-day notice gate | The 45-day forfeiture letter is a locked rule. The on-chain gate that enforces the wait before settlement is still open work — the locker as built settles forfeiture immediately at expiry. | Open |
Each step publishes as it lands. Nothing below is claimed before it is done — today, that means the first two.
Done
Full Foundry suite green across the contract core, including the attestation registry.
Done
Slither run clean — zero high- or medium-severity findings in Pearls sources.
Pending
Second analysis engine, then formal verification of the lock and fee invariants.
Pending
Adversarial tests against the real pool layer, across every fee and guard combination.
Pending
Full report published, grant-backed review, and community scrutiny before any mainnet conversation.
Pearls is being built the way its launches will work: carefully, in the open, with every claim on the record. When the first pearl is minted, it will be announced here — not before.
The waitlist opens with the first launch. There is nothing to sign up for yet — and no form here will pretend otherwise. When it opens, it will be announced on this page.