🪙 Tokenomics

🤓 the nerd stuff

4,200,000,000 BLAZE was minted to the deployer at construction time, 18 decimals, standard ERC-20. Token contract: 0x63cdf20e2169cc52cc27455735bf2d870b8105fa, verified on SonicScan. Ownership is renounced to the zero address (0x0) — there is no owner-only function reachable on this contract at all. Current supply is approximately 4.18B (roughly 18.4M burned so far, about 0.44% of the original mint).

🤓 the nerd stuff

The burn comes out before the allowance does. transferFrom() burns first and then calls super.transferFrom(from, to, amount - burnAmount), so an approval is spent by the post-burn figure, not by the amount you asked for.

Two things follow, and both surprise people: spending an approval by transferring leaves 0.042% of every transfer stranded in it, and a transfer slightly larger than the remaining approval still goes through. If you are integrating BLAZE, budget for both.

Auto burn tax: 0.042% of every transfer (burnPercentage = 42, divided by 100000). It only applies while totalSupply() > 3,180,000,000 (3.18e9 — Fantom's historical max supply, hardcoded as maxSupply in the contract). Once total supply falls to or below that line, the auto-burn tax stops applying to transfers.

Manual burn: anyone can call burn(amount) on their own balance at any time — except it reverts once totalSupply() ≤ 21,000,000 (Bitcoin's max supply, hardcoded as disableBurnSupply), with the contract's own revert message reading "Burn function is disabled below 21 million tokens."

Both paths are active today — current supply (~4.18B) is well above both the 3.18B auto-burn cutoff and the 21M manual-burn floor.

A quirk worth knowing: the contract's own circulatingSupply() and totalBurnPercentage() view functions hardcode the original 4,200,000,000 mint as the denominator — they don't re-read it from anywhere.

The site's own displayed burn percentage is computed differently: totalBurned / totalSupply() (the live, shrinking denominator), while the contract's totalBurnPercentage() uses totalBurned / 4.2e9 (the original mint, fixed forever).

The gap between the two numbers is small today (~0.002 percentage points) but it widens as supply keeps falling — if the site and SonicScan ever look like they disagree on the burn percentage, this is why. Neither number is wrong; they're just answering slightly different questions.

🤓 the nerd stuff

No sale, no presale, no VC allocation, no pre-mint team carve-out. 60,900,005 BLAZE (about 1.45% of supply) was airdropped to 8,259 wallets across six weekly distribution rounds in March–April 2025, targeting OG Fantom and Sonic NFT collections plus faucet claimants. The full history is in the Token Distribution Journal.

Where the rest lives today (measured on-chain 2026-08-31, after the pools were seeded, against a total supply of 4,181,362,828 BLAZE). The single biggest pile is no longer the treasury — it is the liquidity: about 2.49B BLAZE (~59.5%) sat inside the two BLAZE/wS pools as reserves on that date, where anybody can trade against it. We cannot withdraw it: the LP the treasury minted is 10% burned and 90% locked until 1 March 2028, and the burned tenth never comes back. That is a statement about our own LP — the pools are permissionless, so anyone else can add liquidity and pull it out again at will. The live figure and the live per-pool split are further down in 🔥 Deflation, told straight (see also 📈 The price, below).

Roughly 1.053B BLAZE (~25.2%) is left in the deployer / treasury wallet (0xd500c0bd9c853d1a234d3c86420edac0331cf7a8) — down from ~2.55B before seeding. It is unlocked and it funds everything else.

The rest has already been sent out to fund the dapps — about 575M (~13.8%) in total, sitting in nine contracts:

• Faucet — 1,312,000 BLAZE (~0.03%), cut from ~999.6M on 2026-08-31 to fund the pools
• BlazeHiLo (card ladder) — ~250.0M (~6.0%)
• BlazeCrash — ~113.1M (~2.7%)
• BlazeWheel — ~53.0M (~1.27%)
• BlazePlinko — ~52.1M (~1.25%)
• BlazeDice — ~51.3M (~1.23%)
• HeadorBlazed (coin flip) — ~35.7M (~0.85%)
• BlazeMines (ember dig) — ~20.0M (~0.48%)
• BlazeNotary — 210 BLAZE (the retained half of sealing fees)

The 🗿 Burn Altar holds zero BLAZE by design — every sacrifice burns in full inside the same transaction, so there is no float to hold and no BLAZE for its owner to withdraw.

~18.4M has burned so far. The treasury balance is not locked and not vested — the wallet can move it at any time, same as any other owner-controlled fund. The game floats are not locked either: each contract's owner can withdraw down to what it still owes on unresolved bets.

The pooled BLAZE is the one pile that behaves differently, and only in a specific way. The BLAZE sitting in a pair's reserves belongs to whoever holds that pair's LP tokens — and the treasury holds zero of those now: of the LP it minted, 10% was burned and 90% is timelocked until 2028. So the reserves cannot be withdrawn by us. Two things that does not mean. They can still be traded away by anyone buying, which is what a pool is for. And they can be withdrawn by anyone else who holds LP: the pairs are permissionless, somebody who is not the treasury has already added liquidity to the Equalizer pool, and that LP is unlocked and theirs. The live split per pool is in 🔥 Deflation, told straight.

That's a deliberate honesty call, not an oversight: the token contract itself is trustless, but treasury custody is not, and pretending otherwise would be a false claim.

🤓 the nerd stuff

Both pairs are volatile v2-style pairs (stable = false). They have to be: BLAZE charges 0.042% on every transfer and can never exempt anyone, and Uniswap-v3-style pools reject a sell of a token like that outright. Two venues rather than one is deliberate redundancy, and the cost of it is that the two can disagree for a while until an arbitrage bot closes the gap.

The blended opening rate across both pools is 248,683 BLAZE per wS — 0.53% away from the 250,000 we were aiming at, because two price re-trues were skipped during the seeding session and one add had to be redone. We are publishing the number that landed, not the number we planned. The 0.83% gap between the two pools is smaller than the ~1.54% in fees and transfer tax an arbitrageur would pay to close it, so it can sit there honestly rather than being an edge somebody is about to take.

Shadow's burn reads 9.999973%, not a clean 10%, and that is not a rounding fudge. Shadow's factory mints itself a small protocol cut of LP during an add, which dilutes our share without ever touching our balance; the missing 0.00027% is the DEX's, and never was ours. We print the measured number rather than the tidy one, because a proof that has been rounded is not a proof.

What moves it, in order of how much it can move it. The spot price is just wS reserve ÷ BLAZE reserve, so anything that changes a reserve changes the price:

• Anyone trading. A buy takes BLAZE out and puts wS in; a sell does the reverse. Selling q BLAZE into a BLAZE reserve of x multiplies the price by (x / (x + q))².
• The treasury, which is still unlocked. At ~1.053B BLAZE it is the biggest holder outside the pools, and selling all of it would take the price down roughly 50%. We publish that number rather than wait to be asked.
• The seven game floats (about 575M BLAZE, tradeable only as players win it): roughly −34% if all of it were sold.
• Every free BLAZE already in wallets — the genuine public float, about 60.7M — is roughly −4.7%.
• A buyer with a budget. Depth cuts both ways: doubling the price across both pools costs on the order of a few thousand wS. Cheap to pump is the flip side of hard to dump.

What cannot move it. 10% of each pool's LP was burned to 0x…dEaD and the rest sits in BlazeLpLock (0x2c7cc1E993eeffb168BB2A6901247432004EF85A, verified on SonicScan) — a flattened OpenZeppelin 5.1.0 VestingWallet with duration = 0, which makes it a clean cliff rather than a drip. The cliff is 47,304,000 seconds (547.5 days, ≈18 months) and it opens at 2028-03-01 06:10:55 UTC. Before then a release pays out exactly zero, to everyone, us included. So the liquidity cannot be withdrawn out from under a trade before that date. The token contract stays renounced throughout — no mint, no pause, no tax change, no blacklist.

What the lock is not. Its whole owner-power list is transferOwnership — there is no pause, no setter, no rescue and no early release, and renounceOwnership() is overridden to revert (in OpenZeppelin 5.x the beneficiary is the owner, so renouncing would strand the LP at the zero address forever). Read that precisely: the guarantee is about when, not about who. The owner cannot pull the LP early and cannot point a release at a stranger, but the owner can transfer the lock, which changes which address collects at the cliff. It is also audited by AI agents, not by a paid security firm — OpenZeppelin's VestingWallet is; the ~30 custom lines wrapped around it here are not, they were reviewed three times before deploy and that is a different thing.

Every figure above is read live off the chain, per pool, on 📈 The Price — including the reserves, the burned and locked LP shares, the lock's countdown, and what each of those sell-side numbers would do at today's depth rather than at seeding depth. The opening ratio is stamped there too, because it is the one number that can never move.

The reconciling sentence, which is on the page and in the footer of every page on this site: there is a price now, and there is still no promise of value. The faucet still gives BLAZE away for free, and the whole point of this token is that losing all of it costs you nothing you would notice.

Put a number on it, since we can now. At roughly $0.00000011 a token, a 420 BLAZE bet — the biggest any of our games accepts — is worth about $0.00005. That is less than one hundredth of one cent. Blowing an entire faucet claim is not a financial event. That is the design, it has not changed, and nothing on this site should ever be read as a reason to expect a profit. BLAZE is a practice token with a price tag on it, not an investment. 🧯

🤓 the nerd stuff

Live, right now:

• Total supply: — BLAZE
• Burned since the mint: — BLAZE (— of the original 4,200,000,000 — the same denominator the contract's own totalBurnPercentage() uses, not the shrinking one the home page shows)
• Auto-burn tax (0.042% per transfer): —
• Manual burn(): —
• Left before the auto-burn stops: — BLAZE

reading the chain…

The two thresholds are hardcoded and there is no setter for either. The auto-burn tax applies only while totalSupply() > 3,180,000,000 (Fantom's max supply); below that line every transfer moves its full amount forever. burn() reverts once totalSupply() ≤ 21,000,000 (Bitcoin's max supply). The token's ownership is renounced to 0x0, so nobody — us included — can move either line or change the 0.042%.

What actually burns, page by page. These are the only four paths, and they are all in verified source:

• Every transfer, everywhere — 0.042%, taken before the allowance is spent (see the burn-paths section above).
• The seven casino tables — 50% of a losing bet is burned; the other half stays in that table's float. A win burns nothing.
• 🗿 The Burn Altar — 100% of every sacrifice, burned inside the same transaction. The altar holds no BLAZE at all, so there is none for an owner to withdraw.
• 🔥📜 The Eternal Flame — half of a BLAZE sealing fee is burned, half is retained. The 1 S lane burns nothing (it is not BLAZE).

The burn pace, with its as-of block on the stamp above. Two clocks, and they do not agree — which is the point:

reading…

Why the two clocks disagree by so much. The since-launch figure averages over a period when there were no games and no altar — most of it is transfer tax on a token nobody was using. The short windows are dominated by casino losses and altar sacrifices, which is a completely different regime. Neither is a forecast. If people stop playing tomorrow the pace falls back toward the first number, and if a whale feeds the altar it jumps past the second. That is what "consumable, not a law" means in practice.

And the liquidity is not part of the burn story. The — BLAZE sitting in the two pools right now is not burned — it is tradeable, by anyone, forever. What is locked is the LP, and only the LP the treasury minted: 10% of that burned to 0x…dEaD and 90% held in BlazeLpLock (0x2c7cc1E993eeffb168BB2A6901247432004EF85A) until 2028-03-01 06:10:55 UTC. The repo carries tools/verify-lp-lock.js so the whole claim can be re-checked from scratch instead of believed.

The pools are permissionless: anyone can add or remove liquidity. Somebody who is not the treasury already has. Their LP is not burned, is not in our lock, and is theirs, not ours — they can withdraw it whenever they like. So the four shares below are read live off each pair rather than written down, they always sum to 100%, and the fourth one is the honest answer to "is the whole pool locked?" — no, and here is exactly how much of it is not. 🤝

reading the pools…

Verified, and AI-audited — not firm-audited. Fourteen BLAZE contracts have their source published and matched on SonicScan. That proves the code running is the code you can read. Every one of them was also written and audited by specialized AI agents — independent adversarial rounds before each deploy, a full sweep every week — but not by a paid security firm, and this is a $0 practice token, so read the 🔍 Trust & Verify paper for the full owner-power list before you trust any of it with anything you would miss. 🧯