KOLAN docs · mainnet
Buy with a paid time window.
KOLAN uses one native-BNB/KOLAN v4 pool. It launched with token-only concentrated liquidity; buyers supply the pool's BNB and the launch position is permanently locked.
The contracts are deployed and source-verified on BNB Chain. No third-party audit was commissioned; using the protocol remains risky.
Fixed tokenomics
| Total supply | 1,000,000,000 KOLAN |
|---|---|
| Permanent launch liquidity | 850,000,000 KOLAN (85%) |
| Community lock | 100,000,000 KOLAN (10%), at least 180 days |
| Team lock | 50,000,000 KOLAN (5%), at least 365 days |
| Pool parameters | 0.3% fee · tick spacing 60 · range 158280–172200 |
Window lifecycle
1. Open
A buyer chooses a principal, premium, duration, minimum token amount and deadline. A successful call buys and escrows KOLAN for a unique window.
2. Undo
Before expiry, only the owner can cancel. The contract sells the escrowed KOLAN and returns the actual BNB output. It does not guarantee the original principal.
3. Keep or receive
The owner can accept early. After expiry, anyone may trigger finalization, but the purchased tokens must still go only to the owner.
Payment split
| Component | During window | On Undo | On Keep |
|---|---|---|---|
| Purchase principal | Swapped in official pool | Current sale proceeds returned | Purchased KOLAN delivered |
| Window premium | Reserved for buyback | Buys and burns KOLAN | Buys and burns KOLAN |
| Protocol tax | Paid to treasury | Not returned | Not returned |
| Gas | Paid to network | Not returned | Not returned |
Intended contract guarantees
- One window can close only once.
- Only its owner may cancel before expiry.
- Third-party expiry execution cannot redirect tokens.
- Total token supply never increases after deployment.
- The project supplies no BNB reserve or BNB launch liquidity.
- The permanent locker exposes no liquidity-removal function.
Risks and limitations
- No third-party audit is planned for the first release.
- Smart-contract bugs may cause partial or total loss.
- Undo can return less BNB than the original purchase because there is no reserve.
- Low liquidity can cause severe slippage and volatile pricing.
- MEV and transaction ordering may change execution compared with a quote.
- Any test or deployment result applies only to the stated bytecode and network.
Deployment status
| Network | BNB Chain mainnet (56) |
|---|---|
| Token | 0xe2ae…4576 |
| Hook | 0xA408…AA80 |
| Official pool | Initialized; launch liquidity permanently locked |
| Source verification | Complete on BscScan |
| Third-party audit | Not commissioned |