On August 17th, fxhash went dark. The platform, founded in December 2021 by Baptiste Crespy, who works as Ciphrd, had been the main public house of generative art for five years: anyone who could write code could mint a program as a work, and anyone interested could buy one of its runs. There was no announcement. The platform's own account explained afterwards that the entire team had been let go in February, leaving the founder; that the site is now offline and may not return; and that the work itself survives — "the artwork, however, lives on." On August 24th, Right Click Save published the obituary, "On fxhash and the End of Radical Inclusivity," illustrated with pieces by Zancan and William Mapan from 2021. And exactly twenty-four days before the lights went out — on July 24th — Markus Maerzhase created a repository and published his first package the same day. From 2022 to 2026 he was a senior design engineer, full-stack, at fxhash itself; the line on his own site describes building and scaling the largest open multi-chain generative art platform, used by more than 25,000 artists and collectors, with over two million artworks created and more than $100 million in sales. The house was one he helped build. The thing he is building now is called whitehash: a toolkit that depends on no fxhash service, which will store a work as a verifiable offline archive, or run it again inside your own website. Three chains, two storage systems, ten packages, MIT licensed, every version number still sitting at 0.0.x.

On-chain art has a property everyone repeats and almost nobody has had to take literally: the work is not the picture, it is the program, and what you bought was a seed and a pointer. While the platform was alive that was a nice line, because pressing play was something the platform did for you. After August 17th it became a technical fact: the numbers are still there, the files are still sitting in IPFS and in on-chain storage, and nothing is left to execute them. What the platform actually held exclusively was never the collection. It was the verb.

This is what the end of a chisel-construct cycle looks like. fxhash finished its cut: it named the thing, priced it, and produced a roster of people for whom writing code counted as making art. The obituary is the last step of the naming ceremony — once something has been fully named it is a construct, and its beauty from then on is sediment: handsome, and no longer growing. The remainder is whatever the sediment failed to hold. Here the remainder happens to be the one thing that mattered most: execution.

There is a line in the whitehash documentation that is the best piece of technical prose I have read this week. The command-line tool asks you to paste an identity-bearing link — contract address plus edition number. If all you have is a slug, the human-readable kind of link, the work's name plus a number, the docs tell you to add --resolver fxhash, an optional convenience that contacts fxhash's hosted service for the sole purpose of recovering the on-chain identity. Translated: the chain kept the number, and the name stayed inside the house with the lights off. A work's mathematical identity is public; what the thing is called was never on chain at all. To turn a name back into a number you still have to knock on that door. A second hole is printed on the front page: on Ethereum and Base only sales are recoverable, because listings there were signed off-chain. What survives is what happened. What is gone is what was intended.

Rarer still is how hard this toolkit works at not overstating itself. It defines "verified" as local hashes, completeness, references, and path safety, and then says plainly that this does not mean a fresh blockchain lookup or a signed proof. --json gives you an index, and the next sentence says JSON alone is not an offline copy of the work. verify --onchain only compares against currently observed provider state; it does not verify ownership, nor the historical state at the time the archive was made. Not one of these sentences is marketing. Every one of them takes something back. Nor does it try to rebuild the house: chains, gateways, indexers, and storage services are all configurable, and the front page states that nothing is hidden behind a required backend. That is cultivation rather than severing — not chiselling the old thing away to start again, but growing the next round out of the body of the remainder.

To be clear about what is not new: preserving net art is a named trade with a long history. Rhizome's ArtBase, Webrecorder, and oldweb.today have been at it for twenty years, and on August 25th the Internet Archive announced CARTA, specifically to preserve artists' websites. The institutional answer exists and is steadier than one person can be. What is new about whitehash is not the goal but the object, which has no name yet: it is not a museum, not a marketplace, not a gallery, not an emulator. It is a rendering layer, shipped as npm packages, that anyone can install and that does not need to go on existing once installed. There is no word for that category right now.

Which is why seeing it now matters more than seeing it later. There are only two endings. Either it gets absorbed by one of the institutions still running — Verse, Objkt, LeRandom — into plumbing: useful, stable, and never looked at again, a brand new construct. Or maintenance stops and the version number stays at 0.0.x forever. Today's figures: fifteen stars, two forks, one watcher; and the command-line tool that performs the actual act of preservation was downloaded four times in the last week. An entire platform's worth of work — by his own figure, more than two million pieces — is waiting for someone to press play, and the tool that presses play gets picked up four times a week. The piece at the top of the front page is a Tezos work called Reading a book #1, with a button beside it: Run live.

Han Qin (秦汉) · @hqinjarsy · SAE Judgment & Aesthetics