$BITMEME

BITMEME

A fair-launch memecoin that burns until it reaches 21,000,000.

Genesis 100,000,000,000 Target 21,000,000 Team allocation 0% Liquidity 100% in pool
Supply burned 0.000%
100,000,000,000 21,000,000

Live

SupplyAwaiting launch
Tokens burnedAwaiting launch
Burned %Awaiting launch
FDVAwaiting launch
PriceAwaiting launch
Next burn windowAwaiting launch

Burn feed

Tokenomics

Genesis supply
100,000,000,000
Final target
21,000,000
Team allocation
0%
Liquidity
100% of supply in pool
Pool
BITMEME/WETH — Uniswap V4 via Doppler, permanent
Chain
Robinhood Chain
Swap fee
0.7% — 95% to engine + treasury
Fee denomination
WETH only

The Engine

  1. When FDV stays at or above $1,000,000 for a full 15-minute window, a burn cycle executes.
  2. 50% of creator fees are spent buying BITMEME from the pool — bought tokens are burned on-chain immediately, so totalSupply() verifiably decreases.
  3. The other 50% funds development from the treasury.
  4. Buys are chunked (≈1% price-impact cap). The engine never sells and never holds tokens between transactions.
  5. Supply is hard-floored at 21,000,000 — burns never go below it.

Burn epochs

Each epoch burns half of the excess above the 21,000,000 target: 100B → 50B → 25B → 12.5B → … The final approach is asymptotic by design. No completion date is promised — the engine runs as long as fee income funds it.

Treasury

Every fee claim splits 50 / 50: half to the burn engine, half to the Bitmeme Treasury.

Treasury income is WETH-only — development spending therefore creates zero sell pressure on the token. The treasury address is published at launch (TBA).

Phases

  1. UPCOMING
    Phase 0 — Fair launchBITMEME launches on Bankr: 100% of supply in the pool, 0% team, fee stream to the treasury Safe.
  2. UPCOMING
    Phase 1 — Engine contractThe immutable burn-engine contract is built, its test suite published, and the code open-sourced.
  3. UPCOMING
    Phase 2 — Fee-stream migrationAfter a 7-day public review, the fee stream moves to the immutable engine contract. From that moment the rules live in bytecode.
  4. ONGOING
    Burn epochsThe engine buys and burns toward 21,000,000, epoch by epoch, as long as fee income funds it.

Rules & Spec

The burn rules are designed to live in an immutable, permissionless contract: anyone can trigger a qualifying cycle, nobody can change the rules, and the only human-held power is an emergency fee-stream valve whose use is publicly disclosed. AI systems monitor and report — they do not move funds.

Contract addresses: TBA at launch.