Mirrors

This site is deliberately hard to take offline. The same pages are served from more than one independent host, and the source that builds them is mirrored across several code forges — so if any single provider disappears, both the live site and its source survive. The approach follows the Privacy Guides mirror model: one source of truth, many mirrors.

Live site

Independent hosts serving the same site.

Tor

The same pages as an onion service, reachable only through the Tor network. It runs on a server I control and is not published in DNS, so it keeps working if the domain, Cloudflare, or Netlify does not. Open it in Tor Browser; an ordinary browser cannot resolve it.

One caveat: the minted editions on essentialism are fetched live from tzkt.io and bootloader.art, so that gallery stays empty over Tor if those services refuse Tor traffic. The generator itself runs locally and works either way.

I2P

The same pages again on I2P, a different anonymity network from Tor and served by the same machine. Two networks rather than one means neither being blocked takes the site with it. You need an I2P router to open it.

Names

The same site under blockchain name systems. Each name is set once and follows every release on its own, so none of them can quietly go stale. Brave resolves the .eth and .sol names natively.

The Ethereum, Tezos, and Solana names all point at the same IPFS name, ipns://k51qzi5uqu5dkx54ehvkna983zjtfn04eu4sklgx2ag1tozh9js5p9cn5jwqmy, published from this site's own IPFS nodes. The Arweave name points at a permanent copy of each release; some ar.io gateways are still catching up to it.

Nostr

The site is also published as an nsite: every file lives as a signed blob on Blossom servers, with a manifest event on Nostr relays under the same key this site publishes at /.well-known/nostr.json. No conventional host involved.

Source code

The repository, mirrored to independent forges and kept in sync automatically — each holds the full history.

Archived

Point-in-time snapshots held by a third party, outside any host above.

Verify

Every build publishes manifest.json, listing the SHA-256 of every file it shipped. Hash the files you received and compare. That catches a mirror that has gone stale, and it catches a gateway that rewrote the page on its way to you — some public IPFS gateways do inject their own script, so the copy you are handed is not always the copy that was stored.

The manifest's own hash is signed with my Nostr key and timestamped into the Bitcoin blockchain with OpenTimestamps, so the signature says who published it and the anchor says roughly when. Proofs live in commitments/ in the repository, one per release, named for the hash they attest.

Curious how it's put together? See the tech stack.