🔍 Trust & Verify

🤓 the nerd stuff

AI-AUDITED, NOT FIRM-AUDITED. Every contract here was written and reviewed by specialized AI agents, and audited by at least two INDEPENDENT adversarial models before deploy — not by a paid security firm. The Burn Altar trio took two full adversarial rounds plus a structured security review, and every blocking finding was fixed before it went on chain; the whole project then gets a five-lens sweep (debug, health, optimize, QA, security) every week. Verified-on-SonicScan is a third, separate claim: the deployed bytecode matches this published source and anyone can read it. None of the three is a substitute for the others.

The LP Lock is the one place that could be misread, so it is spelled out: it is a flattened copy of OpenZeppelin 5.1.0's VestingWallet, and OpenZeppelin's library is audited — but the ~30 custom lines we wrapped around it are not. They were reviewed three separate times before deploy, which is a real thing and still not an audit. Nobody should ever describe that contract as "audited", including us.

BLAZE token — renounced, immutable. Ownership was transferred to the zero address. There is no owner-only function reachable on this contract: no mint, no pause, no blacklist, no parameter change. The 4.2B mint and both burn thresholds are permanent by construction, not by promise.

HeadorBlazed game, Blaze Faucet, BlazeDice, BlazePlinko, BlazeWheel, BlazeCrash, BlazeHiLo, BlazeMines and BlazeNotary — owner-controlled, pausable. All nine are owned by the deployer/treasury wallet (0xd500c0bd9c853d1a234d3c86420edac0331cf7a8) and all can be paused by the owner, halting user-facing functions at will — the game inherits OpenZeppelin's Pausable; the faucet implements its own paused flag with a setPaused() owner switch.

The game additionally exposes withdraw, emergencyWithdrawNative, emergencyWithdrawERC20, and owner setters for payout multiplier, burn percentage, and streak parameters.

None of this is disclosed as a bug — it is how a non-renounced contract works — but it means "trust the code" does not apply to these thirteen the way it does to the token, and any user-facing copy needs to keep that distinction rather than let the token's "renounced" story bleed over.

BlazePlinko is the narrowest of them: its payout curves are constant with no setter at all, so the one thing an owner most obviously could abuse on a casino contract is not reachable there — the owner can pause, move the bet limits and cooldown, switch resolver, and withdraw float that is not backing an open drop. Nothing else.

Note the bet ceiling is deliberately not capped: raising it cannot endanger a stake, because the contract already refuses any drop whose worst-case payout the float cannot cover.

BlazeWheel matches it: its 16-wedge table is likewise constant with no setter, so the same owner-cannot-re-price property holds. BlazeCrash matches it too: its crash-point formula and target bounds are likewise constant with no setter — and its bust burn split is hard-capped at 50% — so the same property holds there.

BlazeHiLo matches it too, and it is a session game so it needed an extra guardrail: its rung multipliers and the 209/210 house edge are likewise constant with no setter, and pausing it stops only NEW sessions — guess, resolve, cashOut, reclaim and forceSettle keep working so a pause can never trap a player's bank mid-ladder. Its bust burn split is hard-capped at 50% and its per-session payout cap (anti-grinding, see the Casino papers) can never be set below 0.1% of the float.

BlazeMines (Ember Field) inherits the whole HiLo shape: its multiplier arithmetic and the 209/210 edge are pure functions of the 25-tile board and the session's own wet-tile count — constants with no setter — and a pause stops only NEW digs; pick, resolve, cashOut and forceSettle keep working mid-dig. Same hard-capped 50% burn split, same ≥0.1% floor on the payout cap.

The Burn Altar (deployed 2026-08-27) is a different shape entirely — a pure burn sink. 100% of every sacrifice burns instantly, so the Altar never holds BLAZE and there is no owner power to withdraw BLAZE, no odds setter and no burn-split setter — the odds are constants. What the owner CAN do, exhaustively: pause NEW sacrifices only (VRF fulfilment and prize claims can never pause), set the cooldown within 4–60 seconds, cap the VRF callback gas, deposit prize NFTs into the vault and withdraw unreserved ones, and rescue non-vault strays — while anyone at all can call burnStrayBlaze(). A reserved or won prize is provably out of every owner's reach. Its two prize collections, Blaze Numbers and Sacred Flames, are win-only: their one minter is the Altar (write-once, locked 2026-08-27), the 4.2% royalty rate is a constant with no setter, and the single owner lever left is the royalty receiver address. The honest framing for all three: immutable odds, owner-curated vault, prizes beyond anyone's reach once won.

BlazeLpLock (The LP Lock) is a fourteenth contract of a different shape again — a timelock, not a dapp. Nobody interacts with it and it holds no BLAZE: it holds the treasury's LP tokens for the two BLAZE/wS pools. Its owner powers, exhaustively: 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. Before the cliff a release pays out exactly zero, to everyone, including us. After it, release() is permissionless — anyone can call it — and it can only ever pay the beneficiary.

The measured numbers, taken off the chain on 2026-08-31 rather than promised in advance. The cliff is 47,304,000 seconds — 547.5 days, about 18 months — and duration() is 0, which makes it a clean cliff rather than a drip. It opens at 2028-03-01 06:10:55 UTC. On Shadow, 9.999973% of the LP was burned to 0x…dEaD and 89.999757% locked; on Equalizer it is a clean 10.000000% and 90.000000%. Shadow's missing 0.00027% is the DEX's own protocol cut, minted to Shadow's factory during the adds — it dilutes our share without ever having been ours. The treasury holds zero LP on both pairs.

The guarantee is about WHEN, not about WHO — read it precisely. transferOwnership is a real power and we are not going to describe the lock as something nobody controls. What the owner cannot do: move the LP before the cliff, shorten the cliff, pause it, rescue anything out of it, or point a release at some third party. What the owner can do: hand the lock to a different address, which changes which address collects the LP in March 2028. Time is guaranteed by the code. Destination is not.

What the lock proves, and what it does not. It proves the seeded liquidity cannot be pulled out from under a trade before the cliff opens, and that 10% of each pool's LP is burned to 0x…dEaD permanently. Both facts are read live off the chain on 📈 The Price rather than asserted here. It does not mean the price is defended, and it says nothing about the tokens outside the pools: the treasury is still unlocked and could sell into those pools at any time, as could the game floats — the page prints what each of those would do to the price, in percent. One more limit, disclosed because it is the kind of thing that gets discovered later: the lock cannot claim Equalizer's swap fees. That venue routes fees to a separate contract only the LP holder can claim from, and the LP holder is now a timelock with no claim function — so those fees are stranded for good. Shadow's fees need no claim; they stay in the pool's own reserves.

🤓 the nerd stuff

BLAZE trades on two owner-seeded volatile BLAZE/wS pools — Shadow legacy and Equalizer classic — opened at a ratio the treasury chose rather than one a market discovered. It still promises zero monetary value and makes zero financial promises: nothing here is an investment, and nothing about it should be represented as one. What the pools do not change: the token's ownership is renounced, 10% of each pool's LP is burned to 0x…dEaD and the remainder sits in a verified timelock. What they also do not change: the treasury and the game floats are unlocked, disclosed, and could be sold into those pools at any time. Every one of those figures is read live on 📈 The Price, next to what it would cost to move the price in either direction.

🤓 the nerd stuff

BLAZE's contracts are enrolled in Sonic's Fee Monetization (FeeM) program under project ID 91 — registered contracts earn back roughly 90% of the gas fees their transactions generate, paid to the contract owner. Enrollment has two steps and they are not the same thing: every contract calls registerMe() itself, but the project side still has to be approved. BlazeToken, HeadorBlazed and BlazeFaucet are approved and accruing; the newer contracts have self-registered and are pending approval. Self-registration is not accrual, and we are not going to write it as though it were.

See feem.soniclabs.com for how the program works generally. Accrued fee revenue is earmarked for the BLAZE liquidity pools, which now exist — but stated plainly, the treasury paid for that liquidity out of its own pocket, not out of FeeM: accrual scales with usage, which is currently very light, and it has funded none of it so far. The pools themselves are on 📈 The Price.