Introduction
Flipit is the native token launch and trading layer for LitVM. It connects token creation, zkLTC bonding, automatic graduation, permanent initial liquidity, and post-graduation Swap in one lifecycle.
The product is designed around a simple flow: Create → Raise zkLTC → Graduate → Trade.
What Flipit connects
| Layer | What it does |
|---|---|
| Creator | Defines a token name, ticker, metadata and target market cap. |
| LaunchManager | Creates the fixed-supply token, isolated sale, creator fee vault and canonical pool. |
| LaunchSale | Holds one launch's bonding-curve inventory and zkLTC reserve. |
| Pool | Becomes the TOKEN/wzkLTC market after graduation. |
| SwapRouter | Hides native wrapping and routes zkLTC/token and token/token swaps. |
| PermanentLiquidityLock | Holds the initial LP shares without a withdrawal path. |
| CreatorVesting | Releases the creator token allocation after graduation according to the fixed schedule. |
| Flipit backend | Persists metadata and launch records, verifies receipts and serves fast Explore/Search data. |
zkLTC-native UX
Users interact with zkLTC. WrappedZkLTC is internal protocol plumbing used by pools and the router; normal Flipit UI does not expose it as a separate market asset.
Current testnet
| Property | Value |
|---|---|
| Network | LitVM LiteForge |
| Chain ID | 4441 |
| Native asset | zkLTC |
| RPC | https://liteforge.rpc.caldera.xyz/http |
| Explorer | https://liteforge.explorer.caldera.xyz |
| EVM target | Shanghai |
Engineering status
The current contracts are a testnet engineering baseline. The repository security notes explicitly state that they should not be treated as audited mainnet software yet.