Launch a Token

tip

A token is deployed in one transaction. You pay a small flat creation fee, pick how fees should be routed, optionally pre-buy from the bonding curve to anchor your supply, and the Factory takes care of the rest.

What you pick at launch

Choice	What it means
Name, symbol	Standard ERC20 metadata.
Description, image	Free-form text and an on-chain image URI, stored on the token itself.
Community fee share	A number from 0 to 100. The share of post-graduation coin-side fees that flows into your token's Staking Vault. Set once at launch and immutable after. If you enable a staking vault, this must be greater than zero.
Staking vault	Optional. Off by default. When on, a dedicated ERC4626 vault is deployed alongside the token so holders can stake and earn yield from trading fees.
Alternative fee recipient	Optional. An address that receives the creator-side fees instead of your wallet (a multisig, a treasury, a splitter, or the staking vault itself).
Salt	A short value that - together with your wallet - determines the token's final address. Each (creator, salt) pair can only be used once.
Creator pre-buy	Optional. Extra ETH sent along with the creation fee is used to buy from the bonding curve in the same transaction, with the resulting tokens transferred to you.

Deterministic addresses

The Factory uses CREATE3 behind the scenes, which means your token's final address is a function of your wallet and the salt you pick - not of the deployed code. In practice that means you can publish your token's address before the deploy transaction is even mined, and you can recover it deterministically from those two inputs.

Two duplicate-launch protections are in place:

• The same (creator, salt) pair cannot be re-used.
• The same (name, symbol, description, image) tuple is rejected, no matter the salt.

Creator pre-buy

To prevent post-launch sniping, you can buy from the bonding curve inside the same transaction that deploys your token. Send extra ETH along with the creation fee and the Factory routes it into a buy on your behalf, transferring the resulting tokens straight to your wallet.

The amount is capped:

• Default cap: 15% of the bonding-curve supply.
• Hard cap: 25%. The protocol admin cannot raise the cap any higher.

If your requested pre-buy would push past the cap, the deploy reverts before any state changes.

Fee routing - three ways

When you launch, you decide where the creator slice of your token's fees should land:

1. To your wallet - the default. Leave the alternative fee recipient blank.
2. To a custom address - useful for multisigs, treasuries, splitter contracts, or a friend.
3. To a community Staking Vault - set the vault flag on and a non-zero community fee share. The Factory spins up a dedicated ERC4626 vault for your token and routes a portion of post-graduation coin-side fees into it. Anyone who stakes the token earns yield as trades happen on the AMM.

The recipient can be handed off later, but only by whoever currently holds it. You can set the alternative fee recipient once while it is still unset; once set, only the current recipient can pass it on.

What happens in your deploy transaction

1. The Factory validates your fees, parameters, and the duplicate-launch guard.
2. The token is deployed at its CREATE3-deterministic address.
3. The token mints the 200M LP reserve to itself and asks the Liquidity Manager to create its Algebra V4 pool (and the small 5% POL pool, if it's enabled on the Factory).
4. If you opted into a staking vault, the vault and its cooldown escrow are deployed and wired into the pool's fee plugin.
5. If you sent a pre-buy, the Factory executes the buy and forwards the tokens to you.
6. A CoinDeployed event is emitted with the full token metadata so indexers and the frontend can pick the token up immediately.

Your token is now live on the bonding curve, tradable on factory.cyphereth.com.

Pause behaviour

The protocol admin can pause new deployments and bonding-curve trading at the same time, as a safety lever. Tokens that have already graduated are unaffected - they continue to trade on the AMM independently of the Factory's pause state.