PINNED IDENTIFIERS
Content identifiers are derived from the bytes themselves. Change a single pixel in a single unit and the directory identifier changes, which makes silent art swaps impossible rather than merely discouraged.
VERIFY IT YOURSELF
With an IPFS node, these three commands confirm the run independently of this website and of any gateway.
The first lists 9,999 entries. The second prints one unit's metadata. The third re-derives the directory identifier from your own copy of the files — if it matches what is printed above, the art is what was pinned.
AUDIT GATES — 17 OF 17 PASSED
| id continuity | Ids run 1 to 9,999 with no gaps and no duplicates, in both the image set and the metadata set. |
| file integrity | Every image decodes as a valid PNG. Every metadata file parses as valid JSON. No zero-byte or truncated files. |
| frame geometry | All 9,999 frames measure exactly 512×512, produced by nearest-neighbour enlargement from the 32×32 authored grid. |
| image uniqueness | All 9,999 image hashes are distinct — zero duplicate groups. |
| trait uniqueness | All 9,999 six-axis combinations are distinct, drawn from a space of 34,560. |
| metadata linkage | Every metadata file's image field resolves to the pinned image directory plus its own id. Checked on all 9,999, zero violations. |
| pin parity | Every per-file identifier was recomputed locally and compared against the pinning service: 9,999 of 9,999 matched on both sets. |
REPRODUCIBILITY
The generator is seeded with 4663 and has no other source of randomness. Running it again produces the same 9,999 units in the same order, with identical bytes. The build is a function of its seed, not of the day it happened to run.
Metadata was regenerated after pinning so that every image field points at the real image directory identifier rather than a placeholder. That regeneration is why the metadata identifier differs from the image one — they are two separate directories.