Architecture
Flipit separates immutable protocol execution from application discovery and metadata infrastructure.
On-chain architecture
Creator
|
v
LaunchManager
|-- TokenFactory -> LaunchToken (fixed supply)
|-- FeeVault (creator)
|-- LaunchSale (isolated escrow)
`-- PoolFactory -> canonical TOKEN/wzkLTC Pool
Users buy/sell
|
v
LaunchSale
|
`-- sold == curveSupply
|
v
Graduation
|-- exact zkLTC liquidity
|-- wrap -> wzkLTC
|-- bootstrap Pool
|-- initial LP -> PermanentLiquidityLock
|-- creator tokens -> CreatorVesting
|-- creator proceeds -> creator FeeVault
`-- protocol proceeds -> protocol FeeVault
After graduation
|
v
SwapRouter
Application architecture
Browser / wallet
| \
| \ direct transactions
v v
Next.js LiteForge contracts
|
v
PostgreSQL read layer
^
|
Fastify launch service + chain worker
The backend stores metadata and fast application state, verifies launch receipts and reconciles chain data. It does not sign user transactions or replace contract state as the final authority.
Design principles
- immutable protocol contracts;
- isolated launch reserves;
- native zkLTC UX;
- price-continuous graduation;
- permanent initial LP;
- fixed-supply launch tokens without admin token controls;
- provider-independent event surface;
- backend reads optimized for product responsiveness while critical execution remains on-chain.