How Flipit Works
A Flipit token moves through a small number of irreversible protocol stages.
1. The creator defines the launch
The creator supplies token metadata and a target market cap. The deployed LiteForge configuration fixes the rest of the economic structure: total supply, allocation percentages, curve multiple, launch duration and creator vesting schedule.
2. LaunchManager creates isolated components
A successful creation transaction deploys a fixed-supply LaunchToken, creator FeeVault and one LaunchSale, then creates the canonical pool in an unbootstrapped state.
The token's full fixed supply is transferred into its sale contract. Launch reserves are not pooled across launches.
3. Bonding uses native zkLTC
While the sale is active, buyers purchase curve tokens with native zkLTC. The sale tracks sold and curveReserve; sellers can return curve tokens before graduation and receive the quoted zkLTC output.
4. Full curve completion triggers graduation
When sold == curveSupply, graduation occurs inside the sale. The contract calculates the exact zkLTC required to open the pool at the final curve price, wraps that amount internally, bootstraps the pool, sends initial LP shares to PermanentLiquidityLock, creates creator vesting and distributes the post-liquidity remainder between creator and protocol fee vaults.
5. Swap takes over
A graduated token no longer uses the bonding curve. Flipit Swap routes:
zkLTC -> TOKEN
TOKEN -> zkLTC
TOKEN A -> TOKEN B (through wrapped zkLTC internally)
6. An expired launch can fail
If the immutable deadline passes before graduation, anyone can call expire(). The launch becomes Failed. Holders can then redeem curve tokens for their proportional share of the remaining zkLTC reserve.
Redemption follows ownership of the curve token. It is not an exact historical purchase-price refund. Transferred curve tokens carry the redemption claim with them.