Openlaunch documentation
A launchpad and permissionless DEX. Every claim below is enforced in the contracts, not a policy promise — the point of this page is to explain exactly what that means and let you verify it yourself.
Openlaunch has not been formally audited. Informal review by the team's personal contacts has been used as a substitute, by deliberate choice, not oversight. Use accordingly.
What Openlaunch is
Two independent pieces that happen to live in one app: a launchpad for deploying new tokens with permanently locked liquidity and no team allocation, and a DEX (Uniswap v2 and v3, both fully permissionless) that anyone can use for any token pair, whether or not it ever passed through the launchpad.
The DEX doesn't need the launchpad, and the launchpad doesn't restrict what the DEX allows — they're deliberately not coupled to each other.
The core claims
- No hidden mint path. A launch token's full supply is fixed at creation. Nothing in its contract can mint more, ever.
- Liquidity is locked forever, not timelocked. Every launch's position lives in a vault contract with no
withdrawfunction anywhere in its bytecode — see How Launches Work. - No admin path to user funds. Almost nothing in the system has an owner at all — see Safety Model.
- Anyone can create a pool or launch a token. No permission, no curation, no allowlist.
Where to go next
- How Launches Work — the single-sided position, the permanent lock, anti-snipe protection, dev-buys.
- The DEX — V2 and V3 pools, fee tiers, how routing works.
- Fees & Treasury — what gets charged, where it goes, and who controls it.
- Supported Networks — live chains and real contract addresses.