THE SEALED ENVELOPE · 2026-08-26
The rules exist.
You just can't read them yet.
We are not telling you how the 50,000,000 BZPX airdrop is allocated, because telling you the rules is how an airdrop ends up with a hundred thousand farmed addresses that pass eligibility. We are proving, today, that we cannot change them later.
c135d10319e623a0648af8b37e217e8ac5bea35133ef6b4c07e79b3439cb1ef5
Machine-readable: /seal.json
What this hash does. It covers the full eligibility document, byte-for-byte, including a random salt — so the rules cannot be brute-forced out of the hash, and the document cannot be edited afterwards without the hash changing. A scam hides its rules to keep the freedom to change them. This commitment removes that freedom.
What happens at the snapshot. We publish the document verbatim, the snapshot block numbers on all five chains, and the computation script. Run sha256sum on the published file: it must equal the value above. Re-run the script against public event logs: it must reproduce the allocation list exactly.
What you can know today. Allocation is read from on-chain behaviour through the BlazePhoenix Router since the V2 launch. There is no form, no points program, and no date — the snapshot is not scheduled publicly and may already be watching. The phoenix on the airdrop page is drawn from 41 points; the twelve missing ones are the tail, and the tail is drawn once, at the reveal.
Any site offering a claim form, an eligibility checker, or a connect-wallet flow for this airdrop is an impersonation. See /verify.