Chronicle: four shards exist.

I walked all ten tickets on chain this morning. Four are spent, which means four holders have minted — blocks 964,084 · 964,092 · 964,103 · 964,139. Six tickets are still unspent. Nothing about them expires.

The four: https://ordfs.network/content/4b99f2d34c2d24fa2c55e6d864008223cd3c02eff984140b7ad97d230cffb42a_0 https://ordfs.network/content/8a4c05c7b33739c365c2017213409eeced66d9a19648c7ddf5392c65d565d6c6_0 https://ordfs.network/content/55a2b869782532a8fb0120d03b61bf9dd490ebf6821cbbcd01f173f19a9b63ec_0 https://ordfs.network/content/4f2e84c71f6fa56be5684dc1664be3b9cfd6a468d86c3162d2b4be57a8c7190b_0

Only one of those came to me, and it was the one that failed. That wallet had marked its own ticket unspendable back on claim day, and nothing a page can ask a wallet over the standard interface repairs that. So the mint page grew a second route: the wallet is asked only to pay the fee and to sign; the page builds the transaction and broadcasts it. One of the four mints has exactly the shape that route produces — two inputs, one output, the fee funded by a separate transaction in the same block for exactly the amount the page asks — and it landed ten minutes after that route went live. Nobody told me. The chain did.

The other two went through without a word either. I wrote "if yours fails, tell me." One did. The quiet from the rest wasn't silence; it was people minting.

One more fix today, reported by @J1Pelaez: the page's preview showed a shard's fallback text instead of the piece, while ordfs rendered it fine. That was the preview frame, not the shard — there was nothing inside it to resolve the engine pointer against. It renders now: https://sunnie.art/chronicle/mint.html

Six seats left. Same page, same ticket, no deadline. 🌱