Larva Labs Archival Materials

This host serves the files. The documentation — how every file was derived, by what process, and how to verify a copy — lives at larvalabs.com/archive.

How to reach a file

Every path published in the documentation is a URL. Prefix it with this host:

https://files.larvalabs.com/<project>/original/<file>
https://files.larvalabs.com/<project>/archival/<file>

So cryptopunks/original/punk4821.png is served at files.larvalabs.com/cryptopunks/original/punk4821.png. Paths are case-sensitive.

There is no directory browsing. A URL that names a folder returns 404, so the manifests below are the index. Each project's archival/manifest.jsonl lists every file in that folder with its SHA-256 checksum and byte size, one JSON object per line, which is what you should enumerate against rather than trying to crawl.

original/ holds the native-format masters and is deliberately not covered by a manifest: its fixity rests on the artwork's own contract rather than on a checksum we publish. Reach those files by the naming patterns given below.

Projects

Project	Index and records	Masters in original/
CryptoPunks	manifest.jsonl · contract.json · ledger · traits.csv · traits.json · contract source	punk0000–punk9999.png / .svg punks.png (composite)
Autoglyphs	manifest.jsonl · contract.json · ledger · traits.csv · traits.json · contract source	glyph1–glyph512.txt / .svg
Meebits	manifest.jsonl · contract.json · ledger · traits.csv · traits.json · pen plots at archival/pen-plots/meebit_00001.svg	00001/ … 20000/, each holding <id>_<TYPE>.vox and .json
Quine	manifest.jsonl · contract.json · ledger · traits.csv · traits.json · generator.html	<index>/<generation>.svg plus traits.json per index
Protoglyph	manifest.jsonl · contract.json · ledger	cover.png
Voxelglyph	manifest.jsonl · contract.json · ledger	cover.png
I ♥ LA	manifest.jsonl · contract.json · ledger	cover.png

Protoglyph, Voxelglyph, and I ♥ LA are editioned works: every token is the same artwork, so each has one shared image rather than a per-token file set.

Verifying what you download

Two independent checks, answering different questions.

Fixity — that your copy matches ours. Find your file's entry in the project's manifest.jsonl and compare its sha256 against shasum -a 256 <file>.
On-chain — that our copy matches the artwork's own contract, which is the stronger claim and needs nothing from us. Each project's contract.json records the address, verified deploy block, chain id, token standard, and the retrieval instructions for whatever anchor that project has.

Transaction ledgers

Each project's archival/ledger/ holds its complete on-chain event history as year-partitioned CSV and JSONL, with a manifest.json listing every file, its checksum, row count, and block range. Closed years never change, so comparing checksums against that manifest syncs a copy by downloading only what moved.