The wall
Token ids were handed out in payment order, so laying the collection out in id order is laying it out in time order. Each tile is one Credit at its true 8 by 8 resolution, drawn from the contract's own data rather than from an image.
Why it has stripes
Which of the four plates a Credit prints is decided by the second its payment was made: take the second, mod fifteen, add one, and read the result as a four bit mask over cyan, magenta, yellow and black. Second 0 gives C, second 1 gives M, second 2 gives CM, and so on to CMYK. Fifteen seconds and the cycle repeats.
So the texture is a clock. Where payments poured in faster than one a second, many Credits share a second and the wall goes solid. Where they trickled, the color jumps every tile. The banding is the mint's own traffic, drawn by the work.
How each tile is drawn
The transaction id is hashed with SHA-256 into 256 bits, which is four 8 by 8 grids, one per plate. A cell shows the subtractive mix of whichever plates are both active and set there. Two values, the payment second and the transaction id, are enough to reproduce any Credit exactly.
Both are readable straight off the contract through 0x2d9c77e1(id) and 0x82829f74(id), at 64 hex characters each instead of the 8KB of base64 SVG that tokenURI returns. That is the difference between four megabytes and roughly a gigabyte, and it is why this page exists at all.
What is exact and what is not
Plate selection, bit counts and colors were derived from the contract and checked against it: the plate rule is pure across 5,961 sampled tokens, and computed bit counts matched the published trait on every token tested. The one approximation is the Print trait, which nudges individual plates out of register on about 12% of the collection. Those tiles are drawn in register here.
Not affiliated
A reading of a work by Jack Butcher. Not his site. Sells nothing, takes nothing.