Provenance
Every question about mint fairness has the same answer: nobody chooses. Here is how to check that yourself, without trusting us.
1. The art was locked before launch
All 3,333 Ninjas were generated once from the seed x1-ninja-genesis, hashed together, and that provenance hash was committed on-chain before the first mint. Changing any image, trait or ordering after the fact would change the hash.
Published provenance (this site, release.json)
18f30353004279f361cd629ebddc6c0a1383b8965fba5cf22e77d64705e2ff8e
On-chain provenance (read live from the program)
18f30353004279f361cd629ebddc6c0a1383b8965fba5cf22e77d64705e2ff8e
✓ MATCH — the on-chain hash equals the published hash
2. The program deals the Ninjas
At each mint the program draws the image itself from the Ninjas still unminted, using the chain's recent slot hashes. The draw happens inside the program, in the mint transaction. There is no allowlist of images and no reserve, and the team mints through the same instructions as everyone else. A slot hash isn't verifiable randomness: someone who can predict it or order transactions, such as a validator, could influence which Ninja they get. The litepaper sets out those limits.
3. Check any mint
Every NFT's record is a public account: it stores the mint order (serial) and which image the program drew. Open any Ninja's page and follow its explorer link — the record, the metadata URI (https://arweave.net/bioFuEdBNDqoinProFB6X3jTJPILZLhfbrZct7wKrVs/NNNN.json) and the art are all immutable and independently hosted.
Mint program
Drop account
Metadata base URI (Arweave, immutable)
https://arweave.net/bioFuEdBNDqoinProFB6X3jTJPILZLhfbrZct7wKrVs ↗
Short version: the art was frozen and fingerprinted before launch, the fingerprint is on-chain, and the program deals each Ninja at mint. Nobody, the team included, can swap the art or choose from a list.