Your liquidity.
Your next move.
Launching or managing a token on a supported network? Choose your chain and open the launch workspace. This separate workspace preserves projects on local chain 31337.
Start your pool, set its graduation policy, and move your liquidity when the time is right. Protected changes require your wallet and your quantum key.
Integration notes
local chain 31337 only · not independently audited. Use disposable local accounts and assets. Create a launch setup first.
Continue your launch.
Open your saved setup and restore its dedicated graduation key.
Make the next move.
Fund the source pool, schedule a policy change, migrate, or claim a payout.
Keep control.
Review the exact action, approve with both keys, and accept the network estimate before sending.
Open your local setup.
No setup loaded. Wallet connection and transactions are always explicit.
Restore your second key.
Use the encrypted graduation backup you verified during setup. This is separate from QWallet and QPool backups. The passphrase and secret key stay in the client.
No quantum key loaded.
There is no key rotation or recovery in this version. Losing either key can permanently prevent protected actions.
Choose what happens next.
Load a setup to choose an action.
All amounts use exact base-unit integers. No transaction is sent by filling the form or preparing an action. Source principal cannot be withdrawn before graduation.
Review, approve, then send.
Exact structured action
Exact transaction and estimate
Prepare an action to review its current network estimate.
Save or recover public action progress
Public journals contain configuration, public signatures and transaction progress—not your private key, encrypted backup or passphrase. Importing a journal can check or recover a transaction; it cannot sign or resend one.
Two keys. One deliberate move.
Bootstrap, policy changes, migration, fee claims and destination exits use wallet plus SLH-DSA-SHA2-128s authorization. Token allowances use your ordinary wallet; ordinary token transfers are not quantum-protected. Fees here mean accrued trading fees, not guaranteed yield.
Migration stays within the fixed token pair and manager on the same EVM chain. There is no bridge. The local RPC must support the read-only state overrides used to check exact hook runtime code. Service fees are off.
