Fees & Treasury

Two fee sources, both fixed by contract, neither adjustable after the fact for a given launch.

1. The launch fee

A flat fee, in the chain's native stablecoin, charged once when a token is created — paid directly to the treasury in the same transaction as the launch itself. See Supported Networks for the exact amount live on each chain.

2. Trading fees, split 70/20/10, forever

Every launch's locked position keeps earning real trading fees for as long as it's traded against — the position can never be withdrawn, so this fee stream never stops. collect() pulls whatever's accrued and splits it in whichever token(s) the fees actually came in: 70% to the creator, and the remaining 30% split between the treasury and a burn, depending on which side of the pair a given portion accrued in.

For fees denominated in the launch token itself, 20% goes to the treasury and 10% is sent to a burn address — permanently reducing supply, so every existing holder ends up owning a slightly larger share of what's left. No claim transaction, no per-wallet payout. For fees denominated in the paired asset (USDC/USDT0), the full 30% goes to the treasury instead — deliberately not swapped into the launch token first. Forcing a swap inside this contract to route that share into a burn would need a slippage guard against a brand-new token with no reliable price reference, and collect() is callable by anyone, so that swap could be sandwiched by whoever calls it. Not worth the risk for a cosmetic symmetry between the two sides.

Callable by anyone — there's nothing to protect, since the split itself and both payout addresses are fixed at the launch's creation and can never be redirected.

Who controls the treasury

The treasury address is immutable everywhere it's referenced — set once when a contract is deployed, with no function anywhere to change it afterward. On both chains Openlaunch currently runs on, that address is a real Safe (formerly Gnosis Safe) multisig, not a single wallet. Nothing in the protocol — not even the multisig's own owner-only admin functions elsewhere in the system — can redirect where launch fees or trading-fee splits go.

• Launch fees and fee-splits land in the multisig's balance directly — no intermediate contract holds funds on the way there.
• Moving funds out of the multisig requires the multisig's own signature threshold to be met — no single key can do it alone.
• See Supported Networks for the live treasury address and its current signer threshold on each chain.