The Playbook
How this house publishes a collection, in fourteen acts, everything we learned building 生涯, written down so the next artist inherits the method instead of the summary. If someone gave you this address, that was the point.
01
The work decides everything
Before contracts, before pages, before a single render: what is the work, and why is it monumental to someone who has never held a wallet? For 生涯 the answer was one sentence: a ridgeline and a price chart are the same object. And one consequence: you cannot buy the finished work, you can only outlive its writing. Every later decision gets tested against that sentence. If you cannot write yours yet, stop here; nothing downstream will supply it.
02
Choose the medium as part of the concept
The substrate is not a printing decision made at the end. It is conceptualised with the work. 生涯 is pictures about light on water, so it was made for brushed aluminium, where white is never printed and the bright passages stay bare metal: outdoors, the picture answers the actual sun. Pick the surface that makes your concept physical, prove the sizes early (we render print masters at 200 dpi and proofed the maximum format before promising it), and be honest about its limits: metal mutes what paper flatters, and a print in the sun is planned in seasons, not decades. And decide the physical's terms before pricing anything, because included with every token, redeemable, or exhibition-only reprice the whole collection differently. Ours: every token carries the right to redeem its print once, at cost plus margin, chip-certified. The physical is opt-in, and the curation bar gets its collector-facing payoff.
03
Build a truthful engine
If the work is generative, the engine must be deterministic and seed-addressable: sixty-six characters are the entire picture, at any size, forever. Rarity must be honest: the published odds are the real distribution, not a fiction enforced by an upstream tool. Every declared trait must provably change pixels (our test suite holds a seed, overrides one dimension, and compares digests, and a trait that does nothing is a failing test). Annotations are never paint: anything the site draws over a render is an overlay; no file carries it. And the engine must refuse what its data cannot honour rather than quietly shrink the request. 生涯's ranges are cut from the chain's daily history, which grows one range every birthday, and a genesis painted one range short with no error is the failure a truthful engine exists to make impossible. And publish only the rarity figure that measures something: a single trait's marginal probability is a fact a buyer can use, while the product of twelve dimensions puts every piece at one in millions. Ours came out at one in fourteen million, and quoting it would have been a number that sounds like scarcity while describing nothing. If your collection would blush at a statistic, do not let a marketplace be the one to compute it for you.
04
Hang the whole pool in public
Before anything is chosen, show everything the engine painted: every candidate, its seed and its traits on the plaque, with a print-scale master to put your nose against. The pool is that room for 生涯: 240 candidates, the process section that shows one seed under five skies, and the proof that the pictures survive wall size. The pool costs you nothing, since the engine is private and the seeds are yours, and it buys the one thing that cannot be faked later: the audience watched the work exist before the choosing.
05
Curate in the open: the engine never curates
A generative collection is judged on the pieces a human kept, not on its average output. So the choosing is a tool, not a mystery: click keeps, shift-click kills, and when the cut is done the verdicts are published as a committed file the site reads: the pool grows its Kept room and the preview walls re-hang themselves from the real selection. Provenance of the curation is part of the work. Say the sentence out loud on every page where selection appears: the engine paints; it never curates. This is the famous generative pipeline run in reverse. Art Blocks curates the algorithm and lets collectors roll blind seeds at mint; here the algorithm runs first, a human curates the outputs, and only what survives the physical bar, good enough for two metres of brushed aluminium, becomes a token. The mint is a gallery purchase of a known work; the one blind roll left is the genesis, a single quotation of the ritual being inverted. And cap the cut with a number that carries lore (ours: seventy-two, Ethereum's genesis supply in miniature), promised as a ceiling before the choosing starts and final the moment it ends.
06
Speak Basel, not Denver
Write every public page for someone from the art world, not the protocol world. Teach a word before using it, or translate it away: blocks become pages of the ledger, escrow becomes the show's fund, a harmonic mean becomes a published formula, testnet becomes a rehearsal network. Give the currency exactly one gloss (ether, Ξ, Ethereum's own money), then use it freely. The test: read every sentence at an imaginary art-fair booth. If it needs a parenthesis you would not say aloud, rewrite it. And keep the craft nouns honest: for generative work, the engine is the painter, which holds the brush, and the human is the artist, who holds the system and the choice. “Painted by” belongs to the machine; “chosen by” belongs to the person; implying handcraft is the one overclaim an honest house cannot afford. The mechanism is our worked example: art first, mechanics second, nothing unexplained.
07
The genesis ritual: the date is the work
Open with one piece, on a day that means something to the work itself (生涯 opens on Ethereum's birthday, the one day of the year the landscapes move). Make the seed unshoppable: publicly name a page of the ledger that has not been written yet, and let whatever number it carries become the picture. No one has seen it; no one can steer it; anyone can verify it afterward. The vernissage is the room where this happens, and the same file that mints goes to print the same day.
08
Contracts in order of boredom
Deploy the most boring audited contract that serves the moment, and nothing more. The genesis mints on a standard Transient Labs 1/1 contract in the artist's name: creator-owned, audited, Story Inscriptions for the ritual, zero experimental surface. Multi-metadata (ERC-7160, where collectors pin eras of a living work) earns its place only when the living collection ships. T.R.A.C.E. certifies the physicals, a chip in the mounted print, a certificate token referencing the parent, and it never carries the artwork itself. And experimental machinery never rides a deadline, and sometimes it never rides at all. Ours did not: the clock, the freeze and the market contracts were written, tested and published, and then not deployed.
09
Be willing to not ship the clever part
We built a pool where every piece carried a standing offer, and selling into it stopped the writing forever. It was the best idea in the project. It is not deployed, because a paid ticket drawing for a prize is a lottery in most legal frameworks and a verifiable random draw does not change that: a question for counsel, not for code. The tell that this is the right call: nothing about the art needed it. The pictures are the same pictures. If your mechanism is load-bearing for the work, you have a mechanism problem, not an art project. Publish it unbuilt, holding nobody's money, and say plainly why.
10
Name the twenty-year commitments before minting
A living work is a promise with a maintenance schedule. Write down, before the collection mints: who runs the daily data pipeline the pictures are drawn from, and from which canonical source; where the state images are served and who pays for the hosting; which engine version is frozen (tagged and checksummed, since one changed line is a different picture); who holds the owner keys (a multisig, not a laptop); and which rituals recur: for 生涯, a new range every July 30 for twenty years, risen in the data before it can rise in the paint. If a commitment has no named owner, it is not a feature, it is a future apology.
11
Sort the evening by what cannot be undone
On the day, rank every act by reversibility and treat the list as the schedule. Token metadata on a Transient Labs contract can be updated, so a wrong attribute is embarrassing rather than fatal. A Story Inscription cannot. That means the mint is not the point of no return, and the checks worth slowing down for belong before the inscription rather than before the transaction. One specific trap, because we walked into it: commit the engine before you paint, then never re-derive the commitment from HEAD again. We committed a copy change an hour after the paint, and following our own instruction to re-run git rev-parse HEAD would have inscribed a commit that never touched the picture. Name what painted, not what is newest.
12
Rehearse the run you cannot repeat
The genesis paint is a two-minute window you get once, with a seed that does not exist until minutes before. So rehearse the whole export beforehand against a deliberately fake seed. Ours was 0xdeadbeef…, written to a directory named so nobody could ever confuse it with the work, and run it end to end at full size: the staleness gate, the print master, the colour proof, the checksums. That rehearsal is what surfaced the one real decision of the evening (the token file was larger than marketplace previews reliably handle) while there was still time to think about it. Rehearse the expensive irreversible act; skipping the cheap reversible one costs less, though it still costs something: we skipped the testnet contract rehearsal and met the first-token-id question live on mainnet.
13
Build the room so it cannot lie
A page about a work that does not exist yet will be wrong at some point on the day, so make being wrong impossible instead of remembering to fix it. Hold the facts the ritual produces as constants that start null (the block, the hash, the seed, the token id) and let every sentence and every table row key off them. Nothing renders until it is true: no placeholder, no bracketed [N], no “coming soon”. Ours flipped from plan to record by filling two nulls, with no prose rewritten under adrenaline. Then verify the rendered artifact, not the toolchain: our build compiled clean while the page still advertised a market room we had just cancelled, because the phrase lived in a shared navigation component. A green build tells you the code is valid, never that the page is honest.
14
Inscribe the argument, not the announcement
Transient Labs contracts let anyone attach permanent text to a contract or a token, and almost nobody uses it for anything. We read every inscription on Ethereum to check: 2,725 across 876 contracts, a quarter of them one-liners, and only 3% past 500 words. Marketplaces render the token and leave the argument in the transaction log. This is free shelf space for the one thing a JPEG cannot carry, and the bar to clear is embarrassingly low.
Write two texts, because they are different objects. The collection story goes on the contract and says what the body of work is. Write it before the mint, since it is about the work rather than the token. And check that your own site can actually see it: ours could not. We wrote “the Reading Room picks it up automatically” into four documents before opening the file that would have said otherwise, where a single hardcoded contract address had been sitting the whole time. A claim repeated confidently starts sounding verified. The room now reads a list of contracts including our own, so the sentence is true, but it became true by someone checking rather than by anyone asserting it harder. The creator story goes on the token and does the job nothing else can: it puts the derivation on chain. Seed, block, timestamp, engine version, commit hash, archive checksum, image checksum, byte count. Ours closes by telling the reader how to reproduce every one of them, which turns “you can check us” from a character reference into arithmetic.
Two disciplines. Verify every number against the emitted files and against the chain before you paste, never after: an inscription cannot be edited, so one wrong checksum is a permanent false claim sitting on an otherwise honest picture. And compose both days early, in files in the repo beside the contract, where they can be read twice and argued with. Nothing meant to outlive you should be typed into a form field at midnight.
Appendix: the first genesis, worked
July 30, in practice
Acts 07, 03 and 02, at full size: the announcement that names the unwritten page, the print order, the rehearsal that catches surprises a day early, and the evening itself, in order. This is no longer a template. It happened on 30 July 2026, and the real numbers are in it. Where we departed from the plan, it says so.
A. The announcement
site + socials, the morning ofTomorrow, the twelfth range rises.
Tomorrow, July 30, Ethereum turns eleven, and in every landscape of 生涯 a new mountain range is born at the shore.
The genesis piece will be painted tomorrow, from a page of the ledger that has not been written yet: block 25,644,500. When the chain writes that page, the sixty-six characters it carries become the seed, and the seed is the entire picture. No one has seen this work. No one can: not a collector, not a market, not us. The picture cannot be shopped for or steered. It can only be received.
Tomorrow the engine paints it, the piece is minted with Transient Labs, and the same file is ordered from WhiteWall, printed at full scale on brushed aluminium, where the bright passages stay bare metal and the picture answers the actual sun.
The evening is at ikigailabs.xyz/vernissage. Every step can be verified afterward. That is the point of doing it this way.
The short version
Tomorrow Ethereum turns eleven and the twelfth range rises. The genesis of 生涯 will be painted from block 25,644,500, a page of the ledger not yet written. No one has seen this picture. No one can. ikigailabs.xyz/vernissage
Picking the block: what we did
The plan said height plus ~7,400, about twenty-four hours of pages. On the day we named 25,644,500: 125 blocks out, twenty-five minutes. The guarantee is identical either way: nobody can know a hash twenty-five minutes early any more than a day early. What the long version buys is witnesses, not proof. Pick a round number, so it reads as chosen in advance rather than fished for. Derive only after 64 confirmations, and publish block, hash and seed verbatim in one breath.
B. The WhiteWall order
placed July 30, from the print masterProduct: Impression directe sur Alu Dibond brossé, Format libre. In the configurator: “Taille & recadrage de l'image” → Format libre → the exact centimetres. No crop, no border, and image optimisation off, since the file is already final.
Size, the seed decides: the Format trait the seed draws sets the canvas, and the order follows the draw. Standing 135 × 180 · Square 140 × 140 · Wide 180 × 135 · Panorama 176 × 99 cm. The ratios are WhiteWall's own families, so every order is a standard menu click. The genesis and the exhibition dozen ride the full 190 × 145 sheet in format libre.
File: the engine's print master at 200 dpi, converted to sRGB JPEG at quality ~90. The maximum formats are proven at 200 dpi: five-figure pixel editions painted in about two minutes each.
Finishing: no frame, no hanging system, because the vineyard mounts are custom to the expo. Add rails only if the first hang turns out to be indoors.
Budget and timing: expect roughly 800-900 € at the maximum free formats (the 180 × 135 standard lists at 723,95 €); production plus delivery to France is about a week, so the first physical exists before the first week is out.
The one check: brushed aluminium prints no white by design. That is the concept. Confirm no white-ink or under-printing option is selected anywhere in the configurator, and proof a small format per register before any two-metre order that isn't the genesis.
The soft-proof: WhiteWall publishes the printer profile for the brushed surface (Butler Finish), and the export scripts render a -proof.jpg beside every master through it: the metal's muting, judged on screen before the order. Eyes only: the upload file stays plain sRGB, never converted to the profile.
C. The ten-minute rehearsal
Transient Labs on Sepolia: we skipped it- 01Rehearsal ether in the artist wallet; open the Transient Labs app; switch the network to Sepolia.
- 02Deploy a throwaway ERC721TL from their factory, named REHEARSAL, artist wallet as owner. Note that the factory flow completes and how long it takes.
- 03Mint one token with any test image and metadata. Record the first token id: this single number settles whether the lore says “token #0” or “the first token”.
- 04Read it back: the tokenURI on Sepolia Etherscan, and the image rendering on a testnet marketplace.
- 05Update the token’s metadata once, confirming the update flow exists and where the lock/freeze switch lives. Do not lock the rehearsal token.
- 06Write a Story Inscription on the token; confirm it renders. The genesis story is written this way on the 30th.
- 07Note where royalties are configured and the default basis points.
- 08Anything that blocks for more than ten minutes: screenshot it and message Transient Labs support the same evening, not on the 30th.
Ten minutes when nothing surprises you, which is the only acceptable amount of surprise the day before a genesis.
We did not do this. The genesis was minted without the rehearsal, so step 03, what number the first token actually carries, was answered live on mainnet instead of on a testnet the day before. It cost nothing this time. It is still the cheapest act in the playbook, and the only one we skipped.
D. The evening itself
July 30, in order- 01The named page is written. Wait out 64 confirmations, then publish the derivation in one breath (block, hash, seed, all three verbatim) so anyone can check the picture’s origin against the ledger.
- 02Raise the twelfth range. The landscapes are cut from the chain’s daily history, compiled into the engine, and on the birthday that table is one range short until it is rebuilt through the day itself. Rebuild, and do not paint until the gate says twelve ranges standing. The engine refuses a stale table outright: a genesis one range short, delivered without an error, is the exact failure the gate exists to make impossible.
- 03Paint, in one command. From the seed and the block number, the export emits the token image, the print master with its soft-proof, and the token’s name, description and attributes ready to paste: the description is the vernissage’s own wording, and the attributes are the ritual’s four facts plus the engine’s twelve declared traits, each one proven to change pixels. A receipt carries the checksum of every file.
- 04Mint. Create the genesis contract in the Transient Labs app (Ethereum mainnet, artist wallet), pin the image and metadata through their tooling, and mint the piece.
- 05Order the metal. The same run’s master goes to WhiteWall: judge the colour on the soft-proof, upload the plain file.
- 06Inscribe. The Story Inscription carries the ritual, the block, the day, and the engine commitment: the painter’s exact version, committed and checksummed, so what opens at collection time is provably what painted the genesis.
- 07Hang it. The piece gets its own permanent room: the seed, the block, the picture and the engine commitment, at an address that will still mean this piece after the next opening takes the vernissage index. Write that URL into the token’s external link, then announce.
A derivation, one rebuild, one command, and hand acts, nothing composed under adrenaline.
If you are an artist reading this
The method is the offer. We bring the engine discipline, the rooms, the contracts in order of boredom, and the patience; you bring the work and the sentence it stands on. Every act above is negotiable except the honest ones, and those are most of them.