
🔥 Milestone Burn Policy
COCK uses a milestone-based burn mechanism that applies equally across Base, BSC, BESC, Roburna, and all future deployments.
All burns are:
On-chain
Public
Irreversible
Fully verifiable
Liquidity Lock Policy 🔓
All Liquidity Pool (LP) tokens are LOCKED.
We chose to lock liquidity instead of burning it because $COCK has ongoing liquidity funding through token activity. Locking provides the same safety guarantees as burning, while allowing future liquidity additions to also be locked — ensuring strong, transparent, and sustainable liquidity over the long term.
This ensures:
Liquidity cannot be removed while locked
LP tokens are held in a time-locked smart contract
Rug pulls are not possible
Liquidity remains secured in the pool
All future LP additions will also be locked and publicly verifiable
Liquidity is never reduced or withdrawn, and all liquidity actions are performed with full transparency.
🚫 Where Burns Come From
Token burns are executed only from:
✅ Burn Wallet
✅ Dev Wallet (if needed for larger milestone burns)
Token burns are NEVER sourced from the Liquidity Pool.
No COCK will ever be removed from LP for burning.
✅ Phase 1 — Proof & Trust Burns
Milestone | Burn |
|---|---|
Liquidity lock confirmed | 1% of total supply |
First 1,000 holders | 1% of total supply |
First 7 days live | 1% of total supply |
✅ Phase 2 — Traction Burns
Market Cap | Burn |
|---|---|
$50,000 | 1% |
$100,000 | 1.5% |
$250,000 | 1.5% |
$500,000 | 2% |
✅ Phase 3 — Momentum Burns
Market Cap | Burn |
|---|---|
$1,000,000 | 2.5% |
$2,500,000 | 2.5% |
$5,000,000 | 3% |
✅ Phase 4 — Legacy Burns
Market Cap | Burn |
|---|---|
$10,000,000 | 3% |
$25,000,000 | 4% |
$50,000,000 | Final Community Burn |
Final burn size and timing are decided by community vote.
⚠️ Burn Safety Rules
To protect long-term sustainability:
Maximum total burned supply will not exceed 15–20%
No surprise or emergency burns
All burns are announced in advance
All burns are verifiable
No overlap of milestone events
✅ Official Transparency Statement
All burns are milestone-based and identical across every chain deployment.
Burns are executed only from the Burn Wallet or Dev Wallet — never from LP.
Liquidity is locked.
Any change to this policy requires public notice and community discussion.