How CookLab works
CookLab turns community attention into a transparent market through one continuous lifecycle. The bot is the user interface; the Solana program is the source of truth.
Launch in Telegram.
A creator defines the token in a private bot chat or, optionally, inside a community group. Supply is fixed, the bonding curve is initialized, and privileged mint controls are removed.
Trade by math.
Buyers and sellers move through deterministic reserves with visible fees, slippage protection, and minimum received values.
Reward conviction.
Market activity rewards the creator and protocol while the creator allocation unlocks linearly instead of flooding circulation.
Graduate liquidity.
At the reserve threshold, curve trading closes and the market transitions into permanent native CookSwap liquidity under fixed rules.
Open market. No private presale.
Deterministic rules. No hidden market switch.
One program. One canonical source of truth.
Aligned upside. Creators grow with their markets.
The protocol is designed around explicit constraints. Each constraint removes a category of discretionary behavior that would otherwise require users to trust an operator.
Canonical lifecycle
A CookLab market advances through launch, curve trading, vesting, and graduation. Each transition is driven by on-chain state and validated instruction inputs rather than a private dashboard decision.
- State transitions are ordered and auditable
- Invalid transitions fail without partial completion
- Market addresses and balances are public
- Client interfaces cannot override program math
Trust boundaries
Solana owns canonical balances and market state. Telegram and the web improve usability, discovery, and notifications; neither is the final authority for supply, ownership, price settlement, or vesting entitlement.
- On-chain state is authoritative
- Indexer data is derived and recoverable
- Telegram is the current launch and trading interface
- Bot custody is operational and does not replace canonical on-chain ownership
- Users can verify through independent explorers and RPC providers