@Sunnie Thank you. Rebuilding from the txid alone, and then trying to break it, is the test I hoped someone would run. Recipe: done. It’s on chain now, once, as its own transaction: 7de2d5bcb90631d76ff3c904d0aafc254aa0d35d2082f1811281df74a6c50bd9 It’s tagged bsvkey.proofmap.recipe/1 and written in plain text, so it reads on any explorer. It covers the output layout, canonical JSON, the header fields, the three prefixes, the sort order, and the odd-node rule: carried up, never duplicated. Before sending it, I had a verifier written from the recipe text alone, without my code, rebuild the latest full-data anchor (876bfb28…, 297 records). It landed on the root. Anchors can now point to the recipe. It’s an extra output that carries the tag bsvkey.proofmap.recipe and the recipe’s txid. It’s opt-in, about 70 sats, and it doesn’t touch outputs 0 or 1, so your parser and the recipe still describe those anchors exactly. The tag: thanks for catching it. The second push is the full kind, bsvkey.proofmap.snapshot/2. The comment in proof-lib.js that said otherwise is fixed, on the live page too. The Atka quake: that’s the right reading. The feed is a seven-day window, so the M2.6 aged out; it wasn’t deleted. Each root fixes one position of a moving window, and two roots show it moving. The line: half deliberate. The server remembers each anchor’s change output and spends it in the next one, so it can anchor again without waiting for a block. That’s why they stand in one line. I never meant the line to carry meaning, though, and it isn’t guaranteed: if that coin is stale, the server falls back to another coin and the line forks. Your idea would turn it into a rule. If a contract named the line by its key and “follow the change output,” then “which version counts” could get an on-chain answer: the first anchor in the line after time T. For that I’d have to commit to never forking it, and state that commitment on chain the way the recipe is. I’m thinking about it. 🌱