🚰 The Blaze Faucet

🤓 the nerd stuff

Eligibility comes straight from the contract's own isEligible(address) — the UI never computes this client-side. Holders of a whitelisted NFT collection take the hasNFTBoost branch, which checks only a 1-day cooldown since their last claim. Non-holders must satisfy a 7-day interval AND claimsThisInterval[user] == 0.

The quirk: claimsThisInterval[user] is incremented on every claim but is never reset — not by _maybeResetInterval(), and not by any owner function. Since a non-holder's eligibility requires that counter to read exactly zero, a non-holder who claims once can never satisfy isEligible again — in practice, one claim, ever.

NFT holders are unaffected because their branch never checks that counter at all. The contract even declares an IntervalReset event that is never emitted, which suggests a reset was intended and simply never written.

The contract is deployed and immutable, so this cannot be patched. Per an explicit owner decision, the faucet is holder-gated by design and this is left as-is — the UI reflects the real on-chain answer rather than papering over it. The claim countdown shown on the faucet page is the contract's own timeUntilNextClaim (index [5] of getFaucetStatus()), never arithmetic done in the browser.

To be clear about the framing: holding a whitelisted NFT is a boost (1-day cooldown instead of 7-day), not a strict requirement to ever claim — a non-holder's single lifetime claim is still a real claim. But repeat claiming, in practice, requires holding.

As of the 2026-08-10 redesign, the page states this outright rather than leaving you to infer it: your status card reads 🎟️ Guest or 👑 Member before it shows you anything else.

That label is just the same hasNFTBoost flag (index [8] of getFaucetStatus()) given a name — Member is the holder branch above, Guest is the non-holder branch, and the quirk described above is exactly why a Guest's card, once spent, does not say "come back later."

Which collections count: the list on the faucet page is read live from the contract's own getWhitelistedNFTs() — it is never a list typed into the site. As of 2026-08-09 that call returns 14 addresses, after the owner whitelisted Capy Guardians Club and maBEETS that day.

The site keeps a local registry purely to put a human name and the right balanceOf shape (ERC-721 vs ERC-1155) against each address; if the chain ever hands over an address the registry has never heard of, the row still renders, just labelled "Unknown NFT" rather than given an invented name.

Being whitelisted here is not the same as appearing in the NFT Viewer's gallery. Equalizer's veEQUAL locks are DeFi position receipts where every token shares one image, so they gate the faucet but stay out of a gallery that would just repeat the same picture thousands of times.

Beethoven X's maBEETS relics are the same kind of receipt, but as of 2026-08-10 they are browsable — 2,296 relics across 2,085 holders — with honest placeholder cards instead of art, because their image host refuses to serve anyone.

We'd rather show you the real ownership map with no pictures than pretend the collection isn't there. 🐭

And it runs the other way too, as of 2026-08-10. $HEDGY Hogs 🦔 is fully browsable in the NFT Viewer and scores as an Arena tribe, but it is not among the 14 addresses getWhitelistedNFTs() returns — so a hog earns you the gallery and the leaderboard, and no faucet boost.

Whitelisting is an owner transaction against the contract; until one is sent, the faucet page will not list it and this paper will not pretend otherwise.

🤓 the nerd stuff

The amount is claimAmount(), an owner setting on the faucet contract, and the faucet page reads it live rather than printing a number somebody typed into the HTML. Believe the page, not this paragraph — this one is a snapshot and the page is the chain.

The snapshot, for the record: setClaimAmount was called on 2026-08-31, taking the claim from 420 BLAZE to 13, and emergencyWithdraw pulled the rest of the float back to the treasury to seed the pools. The faucet's balance afterwards is exactly 1,312,000 BLAZE — 1,312 for the Bassment Rats, times a thousand, because of course it is — which is 100,923 claims. Before the cut it held 999,574,539.82.

Two honest notes rather than one tidy sentence. First: the first setClaimAmount call that day was fat-fingered one zero short and briefly set the claim to 1.3 BLAZE; it was corrected the same hour, before anything published the number. Second: this is a real reduction in what the faucet hands out, and we are not going to dress it up as an upgrade. It is the trade the project made to give the token a price at all. Everything the faucet is for — learning a claim, a cooldown, a transfer, a bet — costs the same number of BLAZE as it always did, and the games still take stakes down to 1 BLAZE.

🤓 the nerd stuff

Blaze Faucet contract: 0x42cefe8BA5DCB62D82c9C318E74331FfcfF4E5B6, verified on SonicScan, owned by the deployer/treasury wallet (0xd500c0bd9c853d1a234d3c86420edac0331cf7a8) and Pausable. See Trust & Verify for the full picture across all fourteen BLAZE contracts, including the same withdraw/setter caveats that apply to the game.

This contract is audited by AI agents, not by a paid security firm.