bostrom — the cold copy

bostrom halted at height 25,120,712 on 2026-08-05 08:55 UTC. everything it was — every particle, the burial datasets, the whole archive node, the index — is in Filecoin Onchain Cloud in two copies on two providers, addressable by content. this page lets anyone check that from a browser: the checks below fetch from the providers directly and hash what arrives. nothing here trusts this server. receipts: cyberia-to/apparatus · audit/filecoin

what is there

setwhatpiecesbytescopies · data setsledger

a ledger is one JSON row per piece: offset, bytes, sha256, the piece CID and both retrieval URLs. a piece is ≤ 1016 MiB. the two providers are main.ezpdpz.net and pdp.lotus.dedyn.io; the piece URL is https://<provider>/piece/<pieceCID>; a particle is https://<provider>/ipfs/<cid>?format=raw.

check 1 — a particle, by its CID, from both providers

3,217,835 particles were pinned on cybernode's IPFS; every one is in Filecoin with IPFS indexing. a random one from a sample of 2,000, or paste any CID the old gateway served. the browser fetches the raw block from each provider and checks that its sha256 is the CID's hash.


check 2 — a burial dataset, through the Filecoin-backed gateway, against the manifest's sha256

manifest.json carries a sha256 for every burial file (balances, delegations, passports, the state export…). the browser fetches the file by its CID through gateway.ipfs.cybernode.ai — a gateway that reads only from the Filecoin providers — and hashes it.


check 3 — a piece of the archive, from both providers, against the ledger

the archive node's 4.3 TB are 4,345 pieces of a tar stream; the ledger names each piece's sha256. pick a random piece: the first MiB is fetched from both providers (a range request), then — if you let it — the whole piece is streamed and hashed in the browser (≈ 1 GiB; a few minutes). the particle sets are CARs: for them every block is hashed against its own CID as the piece streams. the smallest set, io's last 57 pins, is one 22 MiB piece and checks in seconds.


restore

fetch a ledger, fetch its pieces in order from either provider, check each sha256, concatenate, tar x. the archive's manifest (every file with size, mode, mtime; 338 MB) and its ledger are themselves one piece: . the index dump restores with pg_restore.