Openlaunch

Safety Model

What has an owner, what doesn't, and what that owner can and can't reach.

Openlaunch has not been through a formal, paid audit. That was a deliberate decision, not an oversight — the substitute is informal review by the team's personal contacts. There are no code-enforced deposit caps and nothing here is gated on an audit happening later. Treat the contracts as unaudited software.

Almost nothing in this system has an owner

LaunchFactory is the only contract in the whole protocol with an owner at all. Every other contract — the launch token itself, the permanent lock vault, both DEX factories, the V2 router, the launch registry — has no admin concept anywhere in its code. There is no function to call, by anyone, that reaches into an existing launch, an existing pool, or a user's balance.

What the one owner can actually do

LaunchFactory's owner (the treasury multisig) has exactly two powers, both scoped to launches created after the owner acts:

  • Extend the banned name/ticker list.
  • Adjust default parameters (starting valuation, launch fee, anti-snipe window) for future launches.

Neither power reaches an already-existing launch. There is no path from the owner into locked funds, a deployed token, or another wallet's balance.

What's verifiably true, not just claimed

  • No hidden mint path — a launch token's supply is fixed once, at deployment.
  • No pause mechanism, on any contract — nothing can freeze trading or transfers.
  • No blacklist function — no address can ever be blocked from holding or trading a launch token.
  • No withdraw path on a launch's locked position — confirmed by the bytecode itself having no such function, not by a permission check that happens to deny it.

What is a genuine trust assumption, disclosed rather than hidden

  • The treasury multisig's own signers are trusted parties — a multisig reduces single-key risk, it doesn't eliminate the need to trust whoever holds the signing keys.
  • Each chain's DEX infrastructure (the V3 factory in particular) is currently owned by the same treasury multisig, which means it can — through Uniswap v3's own built-in mechanism — enable a protocol fee on swaps in the future. This is a dormant capability, not something active today.