Expert Studio
Launch your qToken
Build the rules. See their impact. Review, then launch.
Relaunch an existing token
Create a new QHooks pool for an existing token. Its supply and contract stay unchanged; review the liquidity, permissions and fees in Relaunch.
Open Relaunch →Your token details
Replace the name and ticker below with these homepage details? Other settings stay unchanged.
Token configuration
Select chain
Choose where you’ll launch your token. Each chain is an independent launch.
Token details
Start with 1 billion tokens, all in the pool and no team reserve. Adjust the supply or pool allocation if you want a different launch.
Start price & liquidity
Start with tokens only. Optional quote liquidity is added after initialization at the selected price. Amounts are limits; unused assets stay in your wallet.
Advanced settings
Pool configuration
Pool rules
Your wallet and a separate post-quantum key authorize protected pool actions. Create or restore and verify your key in the next step.
Continue in this tab. Your settings stay in this page. Connect on your selected chain, then create or restore your quantum key.
Wallet & quantum-key backup
Your token settings stay here while you connect and protect your liquidity.
The second key protects creator controls only; transfers and swaps aren’t quantum-protected.
Connect on your chain
Choose the matching network in your wallet before connecting.
Each chain has separate balances, contracts and fees. Selecting a chain does not bridge assets.
Your Lab recipe
Your quantum key
One key, specific controls
- With your wallet: authorize fee claims, graduation and protected policy actions.
- Cannot: transfer holders’ tokens, sign their swaps or rewrite launch blocks.
- Losing either key freezes protected creator controls, never the token. Trading and transfers continue under the launch rules.
- The encrypted file and passphrase are both needed to restore. QHooks cannot reset them.
Your connected wallet and this second key authorize protected pool actions. QHooks cannot reset either key.
Create a key, enter your passphrase and download its encrypted backup. Then select the saved file and use Test restore. It restores the key in memory and checks a local challenge; no funds or transaction.
At least 16 characters. Store your passphrase separately from your backup.Create or restore your key after connecting.
Public quantum key
Review & launch
Review these settings any time. Connect, verify your key backup and add an image before preparing a launch. Each transaction shows its network fee before approval.
Your qToken is launched.
- Chain
- Token contract
- Pool controller
QWallet is a separate account workflow. This pool is managed below with your launch wallet and matching quantum key.
Prepare your quote asset
Wrap an exact amount of native currency into the pool's quote asset, and keep some for network fees. The wrapped amount stays in your wallet.
Manage your launch
Claim fees, graduate or withdraw. Every protected action needs both keys.
Advanced action configuration
Bring your launch to life
Review each deployment and liquidity transaction separately. Configuration is fixed once you start; graduation-policy changes follow your notice period.
Confirmed contract addresses
Next transaction
Select the next step to prepare your transaction.
Saved launch progress
Public progress contains no private key.
Save or import configuration
Public token and pool settings only. Quantum keys and transaction consent are never included.
How launch protection works
SLH-DSA-SHA2-128s and your EVM wallet jointly authorize pool initialization, graduation-policy changes, fee claims, migration and destination withdrawals. The token remains a standard ERC20; ordinary transfers, swaps and assets outside these contracts work without the second key.
A flat platform launch fee (0.0002 ETH; 0.0007 BNB on BNB Chain) is paid once, before the first launch transaction. You fund initial liquidity and pay network fees for each transaction. Trading uses your configured LP fee plus the separately disclosed protocol surcharge. Liquidity values can fall; no yield or return is guaranteed.
Contracts are not independently audited. Keep your encrypted key backup, its passphrase and the separate public launch-progress file. Do not send tokens directly to contract addresses to initialize liquidity.