What It Does

The deflation lives in the pool, not the token — so you never touch your contract. You deploy a v4 hook, initialize a pool for your token against ETH, and from then on the hook intercepts every swap:

• Burns a fixed cut of the token on every buy and sell. Supply only goes down, and it can't be turned off.
• Skims a fixed cut of the ETH to your treasury on the same trades — your project earns from volume instead of selling tokens.
• Both-sided by design. There's no untaxed leg for flow to route around, so a day of only-buys still burns and a day of only-sells still funds the treasury.
• Ownerless and immutable. No admin key, no upgrade path, no rug — the numbers you set are the numbers it runs on forever.

Why Projects Want It

• Scarcity that's real, not promised. A visible, on-chain burn on every trade — not a whitepaper line.
• A treasury that grows with the chart. Fund development, buybacks, or LP straight from trading volume, in ETH.
• A reason to hold. A permanent deflation story gives traders a thesis instead of just a ticker.
• Zero migration risk. Holders keep the exact token they have. Nothing about your existing contract changes.

The same engine that runs $SMURF's 20% furnace — packaged so any token can light one. This is what's coming.

The thesis

SmurfSwap launches two pools for the same token and locks a 13-point wedge between them: a cheap fee pool (Pool A) and an expensive burn pool (Pool B) whose burn always sits 13 points above the fee. That price gap is not a bug — it's the engine.

Arbitrageurs can't resist a standing gap. They buy the cheap side and sell the expensive side, over and over, and every leg of that loop destroys supply — Pool A's fees get burned, Pool B burns directly on both buys and sells. The result is three things at once:

The one law: volume is driven by how often the gap reopens past friction — not how big it is. Keep the fee low and the wedge permanent, and every bit of organic flow re-triggers the arb loop, forever. The old way — a burn that decays to zero — kills the wedge and the engine dies. SmurfSwap's wedge never decays to zero.

Case study — SMURF

SmurfSwap is a productization of something that already happened, by accident, to $SMURF on Robinhood Chain. Two pools existed with a burn gap between them. In the numbers, on-chain:

The arb loop was ferocious while the gap stood — then the burn decayed to zero, the gap collapsed, and volume fell off a cliff. That single flaw is what SmurfSwap fixes: the wedge is permanent, the burn is both-sided (no untaxed leg to route around), and the fee can step down in place so liquidity stays burned/locked while the engine keeps running.

What this does for $SMURF

SmurfSwap runs on SMURF. Every single launch burns a fixed fee of SMURF — the utility sink. Launch a hundred coins, and a hundred launch-fees of SMURF are destroyed forever, on top of the platform's ETH revenue from every furnace's fees.

• SMURF is the fuel. You spend & burn SMURF to light a furnace — new token or existing.
• Deflation compounds. Launchpad volume → SMURF burned. SmurfSwap makes SMURF more deflationary the more it's used.
• Treasury in ETH. The platform takes 20% of each Pool-A fee in ETH — never bags of random launch tokens (those get burned).

What you need to launch

1. Hold SMURF for the launch fee (it gets burned on launch — the sink).
2. Pick your two knobs: the Pool fee % and the day-one burn %. The 13-pt spread and both-sided burn are locked automatically.
3. Choose a mode: launch a brand-new token, or paste an existing token address to make it deflationary (works even if it has no burn() — the furnace routes to the dead address).
4. Mine the hook — your browser finds the special 0x…CC address (a second or two).
5. Launch — both pools initialize. Then seed liquidity and burn/lock the LP like any launchpad; the dynamic fee means you never have to move it to change fees later.

Burns are permanent and immutable. There is no owner and no off-switch — what you set is what it does, forever.