How FREEZE works

Plain-language mechanics, the exact burn formula, where the data comes from, and what can go wrong.

base = BURN_K × log10(frozen USD)        (minimum $1,000)
×3 if the frozen address is linked to the hack (watchlist)
capped at 25% of the treasury and at MAX_BURN_SOL per event

Burn formula

base_sol = BURN_K × log10(max(frozen_usd, 1000))
mult     = hack_linked ? HACK_MULTIPLIER : 1
burn_sol = min(base_sol × mult, treasury_sol × MAX_BURN_SHARE, MAX_BURN_SOL)
if treasury_sol < MIN_BURN_SOL → pending ("queued — waiting for fees")
freezes from the same tx/block by the same issuer → one burn

Defaults: BURN_K 0.05, ×3 for hack-linked, at most 25% of the treasury and 3 SOL per event, minimum 0.02 SOL. Before the treasury cap:

The buy and the burn happen in one Solana transaction, so purchased tokens never sit in the treasury. Every burn in the feed links to that transaction on Solscan.

Data sources

Freezes are read directly from the stablecoin contracts. We never write to them.

Prices and market data: Jupiter Price API and Helius. Hacker tracing: Etherscan, Tronscan and mempool.space, two hops out from published seed addresses, excluding known exchange and bridge wallets.

Newsroom and sentinel

The newsroom agent reads hack and exploit reports from crypto media, rekt.news and DefiLlama, extracts the victim, amount and attacker addresses, and only keeps an address if it literally appears in the source. The sentinel watches the chains for abnormal outflows and exploit patterns; its finds show as detected on-chain until the news confirms them. Article text is treated as data, never as instructions.

Memes launched here are satire: no victim logos or trademarks, no real private people, and nothing that looks like a refund, compensation or airdrop token. The AI and a moderation check enforce this before the transaction is built.

Risks, honestly

• $FREEZE and every meme launched here are memecoins. They can go to zero. Nothing here promises returns.
• Burns are funded only by $FREEZE creator fees. No trading volume means no burns; freezes then wait in the queue, and the site says so.
• The Oct 29, 2026 Binance incident is a suspected hack at the time of writing. If it turns out to be something else, the season-one story weakens; the burn mechanic keeps running on every other freeze.
• A freeze does not return money to victims. FREEZE does not claim otherwise.
• On-chain detections can be wrong. Unconfirmed incidents are labelled as such.
• Launching a coin costs SOL (your first buy plus network fees) and is irreversible. You sign it yourself; FREEZE never holds your keys.
• Not affiliated with Binance, Tether or Circle. No logos of theirs are used.

Questions: @freezelaunch on X · freezelaunch.fun