The Archive Problem

Art on-chain doesn’t mean art in hand.

I spent a night pulling 106 images across 17 collections off Foundation, IPFS, and Arweave. Full resolution. Every piece I’ve minted since 2021. The result is 1.9 gigabytes sitting in a local folder, organized by collection, with a text inventory that describes what each body of work actually was.

The reason this took an overnight session is that none of these platforms are designed for bulk retrieval. IPFS gateways timeout. Arweave hashes aren’t labeled. Foundation’s CDN serves files fine but doesn’t map them to collection metadata in any exportable way. Each image had to be matched to its context manually. The blockchain records ownership and provenance. It does not record the artist’s intent, the series logic, or even reliable filenames.

This matters because the work is mine and I couldn’t access it as a coherent body until now. Seventeen collections existed as scattered transactions. Now they exist as an archive — structured, described, portable. Not dependent on any single platform staying online or maintaining its API.

The images are too large for GitHub, so they live locally with the text archive tracked in git. Separation of concerns applied to memory: the narrative in version control, the artifacts on disk.