Docs & rules

The Rulebook

Every rule here is code. Same rules for every token, every wallet, every slot.

Rules v1Enforced on-chain

Check my wallet Start reading ↓

Hand turning a page of an open book with a blue bookmark

1%Wallet cap

2Buyers per slot

50%Fees to burn

0Dev allocation

01 Protection

Protection at launch

Wallet capMax 1% of supply per owner, across all token accounts. Selling does not give it back.
ClusterLinked wallets count as one buyer. One cluster, one budget.
Buyers per slotAt most 2 different buyers per Solana slot.
One walletPayer, buyer and receiver are the same wallet.
Guarded buysBuys go through GuardRouter. Other routes are rejected by the hook.
Sealed configRules are hashed and sealed before the first buy. Nobody can change them.
EndsAt the deadline or when the curve fills. Then the pool moves to DAMM v2.

Sells are never blocked.

02 Analysis

How we link wallets

Wallet check

Funding-linked

Wallet B got its SOL from wallet A, directly or through a short hop. A and B are one cluster.

Time-linked

Wallets that keep buying in the same slots across launches. Also one cluster.

AttestationThe classifier signs your cluster ID. Your buy carries it. The program checks the signature.
ExpiryEach attestation lives about a minute. Expired means fetch a new one.
Only for buysSells and transfers never ask the classifier.

ONE_BUYER

First wallet takes the cluster. The rest are rejected.

SHARED_CAP

All wallets in the cluster share one budget.

Check my wallet Request review

03 Rejections

Why a buy fails

Wallet cap reached

You bought your full 1%. Wait for the end of protection.

Cluster taken

Another wallet in your cluster already bought.

Attestation expired

Sign again. Takes one click.

Slot full

Two buyers already landed in this slot. Retry.

04 Fees

Where fees go

Platform fees

50%Buyback & burn

50%Treasury

0%LP · not in v1

FeeRouterProject fees land in one program account. Split is fixed at launch.

Platform feeShown separately, never mixed with project fees.

Every lamport, in order01 / 06

01Available
02Claimed
03Distributed
04Waiting
05Spent
06Burned

Trading fees collect in the pool.

FeeRouter claims them in one program call.

Split 50 / 50 by the sealed config.

The buyback half waits for migration.

Swapped for the token, with a price guard.

Burned in the same transaction.

Also on the ledgerTreasury paidSurplusLeftover burnLP added / locked

05 Migration

After the curve

Graduated tokens

MigrationDBC pool moves to Meteora DAMM v2. The hook is removed.
BuybackStarts only after migration. Runs with a price guard.
BurnSwap and burn happen in one transaction. No tokens sit in between.

06 Direct & SDK

Direct clients & SDK

Same rulesBots and direct clients go through GuardRouter too. No side door.

You needA fresh attestation and your own wallet as payer and receiver.

// guarded buy
const att = await api.attest(
  wallet, mint)
const tx = await buildGuardedBuyTx(ctx, {
  launch, wallet, amountIn, minOut,
  attestation: att })
await wallet.signTransaction(tx)

pnpm add @clear/sdkProgram IDs Status

07 FAQ

Questions

Can the creator change the rules?

No. Config is sealed before the first buy. Check the hash on the token page.

Is there a dev allocation?

No. Creators buy on the curve like everyone else, under the same cap.

I was put in the wrong cluster

Open a review. A person looks at it.

Can I sell during protection?

Yes. Always.

What if the curve never fills?

Protection ends at the deadline. Buys open to everyone.