Terms and disclosures
What this platform does, what it cannot do, and what we can do with money that passes through it. Read section 2 before you commit funds.
Nothing here is investment advice or a recommendation to buy or sell anything. Tokens launched here can and often do go to zero. Only commit what you can lose entirely.
1What this is
A launchpad. You deploy an ERC-20, it is paired against a decentralised exchange, and the liquidity position is either burned or held in our locker under a timelock, whichever you chose at launch (section 9). The contracts are public and immutable once deployed. We do not custody your token and cannot mint, freeze or claw back anyone's balance.
We are not a broker, an exchange or an investment adviser, and we do not vet the merit of any project that launches here. Liquidity that chose LOCK rather than BURN sits in our locker until its unlock time, and can only ever be released to its beneficiary (section 9).
2Money we can retain and redeploy
Funds committed through this platform that nobody claims or acts on for 90 days are retained by us. After that we can redeploy them, including by buying back a token when holders vote for it.
A passing buyback vote authorises that; it does not move anything by itself. We execute buybacks by hand and no contract compels us to. If that is not acceptable, do not commit funds here.
3Governance is a signal, not an instruction
Your eligibility to vote and the weight of your vote are on-chain facts we read. The count itself is ours, made off-chain by our server. A passed vote is a weighted record of what holders want. It does not execute.
Vote weight is meant to be your balance at the proposal's block, but public RPC providers keep roughly 25 minutes of history, so that read usually fails and we fall back to your live balance. Moving tokens to a second wallet and voting again is therefore possible, and is normal rather than an exploit.
A community takeover vote to redirect a creator's fee stream cannot be executed on-chain at all. The rewards contract only lets the creator hand it over, so if a creator disappears nobody can redirect it, including the holders who voted to.
4Badges are our opinion, not a guarantee
KYC means an identity document was checked. It says nothing about whether a project is honest or a token is a good idea.
Vetted means we formed a favourable view of the team's intent. That is our opinion. It is not an endorsement of the token, not a prediction, and not investment advice. We can be wrong and we can be deceived.
The application fee buys a review. It never buys a badge, and paying it does not entitle you to one.
5Paid promotion
Campaigns on the creator desk are paid promotion: the project paid those people to post about its token. We label it wherever it appears, and we do not rank creators by what a token's price did.
6Safety tools are evidence, not a verdict
The scanner reports what it can read on-chain and from public sources: holder concentration, liquidity state, taxes, contract authorities, verified source, and patterns consistent with coordinated buying. A clean scan is not a safe token and an alarming one is not proof of intent. Checks that cannot run are reported as unknown rather than as passes.
A verified dApp listing is a snapshot plus ongoing monitoring of the contract's code and upgrade pointers. It fails automatically if those change. It does not make a dApp safe to use.
7Taxes, fees and what they actually catch
A creator tax applies to trades. On a Uniswap v3 launch, the sell tax only applies to sells routed through this app. Sells through Uniswap directly, through an aggregator, or through any other router pay nothing, and holder dividends funded by that tax are reduced accordingly. Choose the v2 or hook-based venue if you need the tax on every route. A bonding curve on a chain whose graduation venue is v2 becomes a v2 token the moment it graduates, and everything below then applies to it.
On a v2 / PancakeSwap launch the tax is charged by the token on every transfer into and out of the pair. That is what makes it apply to every route, and it has a consequence that is easy to read as a broken app: a sell sent through a router's plain swapExactTokensForTokens reverts instead of paying the tax. Sells have to go through swapExactTokensForTokensSupportingFeeOnTransferTokens, which is what this app uses and what most aggregators offer as an option rather than a default. Buys are unaffected. Nobody can switch this off: it is a property of every transfer-taxed token on a v2 pair.
The same tax applies to liquidity. That includes adding and removing liquidity. Adding liquidity to a taxed token mints you fewer LP tokens than the amounts you sent are worth - about 2% fewer at a 2% tax - and the difference goes to the liquidity providers already there. Removing liquidity pays out the token side net of the same rate. Neither reverts and neither warns you first, and we cannot switch it off for one leg.
A v2 / PancakeSwap pair is a shared pool. Anyone can add liquidity to it, including before a launch graduates into it. Burning or locking the LP puts the launch's own liquidity beyond reach - all of it, always - but says nothing about liquidity somebody else put in, which stays theirs and can be withdrawn at any time. A launch whose venue was co-funded that way can therefore see its pool shrink without anybody breaking a lock. The graduation contract publishes the exact split.
We take a platform fee per trade. Network gas is yours and is not refundable, including when a transaction reverts.
When a graduation into a v2 pair ends holding more quote than the fixed graduation ratio can put into the pool - which happens when somebody parked liquidity in the pair at a price nobody chose - that surplus is ours. The pool is funded with the whole raise first; only what is left on top of it, and only quote a third party put into the venue, is taken as platform revenue. It is emitted on-chain with every migration.
If you select a dividend token, holders are paid in that token. Some tokens, including most tokenised real-world assets, restrict who may receive them, and some can freeze individual addresses. A holder who is not permitted to receive that token cannot claim. We do not control that and cannot override it.
8What is public, and what "private" means here
Your trades are public on-chain. Anyone can read them, and anyone can compute your profit and loss from them.
The PnL setting on your profile controls whether we publish it. It cannot make your trading private: turning it off removes it from our pages and our API, not from the blockchain.
9A lock is a date, not custody
Burned is final. The position is sent to an address nobody controls, and nobody, including us, can retrieve it. It is the only disposition that depends on nothing at all.
Locked means our locker holds it for its beneficiary. Releasing it takes no recipient: it pays the beneficiary and nobody else, so we cannot withdraw that LP or send it anywhere, including to ourselves. The one power we keep is the date - we can push the unlock time further out at any time, without the creator's agreement. So the date is ours and the money is not.
The beneficiary is the creator, and only the beneficiary can reassign it. Where a launch had no creator wallet and the platform launched it, the beneficiary is us, and that lock is recorded on-chain as platform custody. Every lock is public at /lock with its amount, unlock date and beneficiary. If you need liquidity that nobody can ever withdraw, the answer is burn, and we say so on the launch form.
Both lockers work this way. A bonding curve that graduates onto a Uniswap-v2 or PancakeSwap pair puts its LP in a second locker under the same rule, and the proof page names which of the two is holding a given position.
10Availability, and things outside our control
This is software provided as-is, with no warranty. Blockchains reorganise, RPC providers fail, price feeds go stale, and third-party exchanges change without notice. We may be unable to display accurate data, or any at all.
We cannot submit your token to any third-party aggregator or guarantee it appears on one. They crawl on-chain activity on their own schedule. Testnet launches do not appear anywhere.
Smart contracts can contain defects. Ours have been reviewed internally and parts of them are pending external audit; a token page will say when a venue is not audited. An audit reduces risk and does not remove it.
11Your responsibilities
You are responsible for the security of your wallet and keys. We will never ask for your seed phrase or private key, and there is nowhere on this site to enter one. Anyone asking you for one, in our name or any other, is stealing from you.
You are responsible for complying with the law where you live, including securities, sanctions and tax law. Launching a token may carry obligations we cannot advise you on.
12Changes
We can change these terms. Material changes will be shown in the app rather than only published here. Continuing to use the platform after a change means you accept it.
If anything above is ambiguous, treat the more cautious reading as the correct one and ask before committing funds.