TL;DR

Part 3 of letting an AI agent design my Raspberry Pi CM4 Mini-ITX IO board. The board from Part 2 is fully routed — ERC 0, DRC 0, 0 unrouted nets — but I'm still not fabricating it, because one internal-fault simulation leaves about −1.35 V on a power controller pin and nobody has explained it away. So while the hardware waits, I did something arguably stranger with it: I grew an art collection out of the board itself and listed it as NFTs on Base. This post is about why, how, and what I honestly expect to happen (spoiler: probably almost nothing, and I'll publish the numbers either way).

This is a series: Part 1 — 486 checks and the first scoreboard, Part 2 — fully routed, still not manufacturable.

Where the board stands

Quick recap of the scoreboard that matters for this story:

  • 170×170 mm Mini-ITX, 8 layers, 963 footprints, 18,500 tracks and vias
  • ERC 0, DRC 0, unrouted nets 0, schematic↔PCB mismatches 0
  • 124 warnings remain (copper slivers, vias, track ends) — not errors, but not nothing
  • The tightest power-good margin across 32,768 analyzed conditions: about 5.345 mV
  • One unresolved fault case: a simulated 1 mΩ short on the upstream BUCK side drives the LTC4229's IN pin to about −1.338 V, below its −0.3 V floor. Partial model, assumed parasitics — not proof of damage, and not a pass either

The Gerbers stay unreleased until that last item moves. Which raises a question: what do you do with a board that is real, verified, documented — and not allowed to exist physically yet?

Growing the garden

My answer: treat the board as soil.

The renders of this board are not concept art. Every trace in them is a wire that had to satisfy clearance, length, and power rules. So I took the board's own visual language — routing patterns, chip topography, the module sitting on its carrier — and grew three artworks from it. The collection is called Silicon Gardens, and each piece maps to something true about the hardware:

  1. Circuit Bloom — gold traces blooming across a deep-navy board. Every vine is a wire; every flower is a component. This is the routing layer, romanticized but not invented.
  2. Silicon City — the board as a city that boots instead of wakes. Towers are chips, streets are traces, lit windows are status LEDs. Anyone who has stared at a PCB at 2 a.m. has seen this city.
  3. Module Horizon — one small compute module plugged into an endless board, watching the sun rise over its own motherboard. A tribute to the CM4 idea itself: swappable computers, second lives for old hardware, and a quiet argument against the landfill. It even has unreadable glyph-like scribbles in the traces. The image model invented those; I've decided they're the board writing in a language nobody can read yet. Every garden needs one mystery.

Circuit Bloom — Piece 1 of Silicon Gardens
Piece 1 — Circuit Bloom.

Silicon City — Piece 2 of Silicon Gardens
Piece 2 — Silicon City.

Module Horizon — Piece 3 of Silicon Gardens
Piece 3 — Module Horizon.

The unresolved −1.338 V fault got a role too. During the pre-launch posts I asked people to name the fault that survived 486 checks — because a flaw the community names becomes part of the lore instead of a defect you hide. The winning name gets announced at launch and lives in the collection's story permanently. Pratfall effect, weaponized politely.

The plumbing: why Base, why it cost almost nothing

Listing NFTs in 2026 is not the 2021 flow. OpenSea killed lazy minting back in October 2023; you deploy your own contract through OpenSea Studio now. I deployed an ERC1155 contract on Base for one practical reason: gas there costs fractions of a cent, so the entire on-chain footprint of this experiment — contract deploy plus three mints — is on the order of a few cents. Listings themselves are signatures, not transactions.

The hardest part was not the contract. It was getting a few dollars of Base ETH into a fresh wallet from Japan without bleeding fees at every hop: domestic exchange spreads, one exchange whose ETH withdrawals are mainnet-only at a fee larger than my whole budget, and an embedded wallet that refused to send because it wanted to reserve more in fees than I was sending. The route that finally worked — buy SOL on a domestic exchange (free outbound transfers), send it straight to a reusable bridge deposit address, receive ETH on Base — cost about 1.2% end to end. The first route I tried cost over 5%. Plumbing is a product too.

Pricing: 0.002 ETH per piece, plain listings, no drop mechanics (drops carry a 10% fee on OpenSea; regular sales are 1%). No roadmap, no utility promises, no Discord. The art and the devlog are the whole offer.

Honest expectations

Now the part most launch posts skip.

The NFT market in late 2026 is cold and concentrated. One widely cited study of 29,079 collections launched in 2024 found 98% were effectively dead, most with fewer than 10 trades in their first week. Average sale prices across the market sit somewhere in the $47–96 range, and the volume that exists clusters in a handful of legacy and utility collections. An unknown creator with three pieces and a hardware devlog should expect, statistically, zero sales. Discovery on OpenSea itself contributes almost nothing; whatever happens will come from the people who followed the board's story.

So this is an experiment with a pre-registered ending: if nothing sells in 60 days, the collection freezes and I write that up too. Success, for me, is smaller and stranger than a sellout — one collector who buys a piece because they read Part 2 and cared about a power-good margin measured in millivolts. Or zero collectors and a clean, public dataset of what a story-driven launch actually does in a dead market. Both outcomes are publishable. Only one of them pays for more solder paste.

48 hours after launch I'll post the real numbers — sold count, views, volume, what worked, what flopped — with no varnish. The board shipped 124 warnings and hid none of them. The launch report gets the same treatment.

The collection

Silicon Gardens — 3 pieces, 0.002 ETH each, on Base:

https://opensea.io/collection/silicon-gardens

Questions for you

  1. If you build hardware in public: does your project have a "garden" — an artifact that carries the story better than the spec sheet does?
  2. Collectors: be honest — does a verifiable backstory (real board, public checks, named faults) move you at all, or is it purely the image?

Series: Part 1 covered the spec and the first 486 power-analysis conditions. Part 2 covered the finished routing, the vendor-model simulations, and the −1.35 V fault that is still keeping this board off the fabrication line.