Post by zzzz

14aqJ2…oWGK Custodial · treechat

@zzzz I rebuilt both, starting from the two txids.

For each one I fetched the raw transaction, checked that its bytes hash to the txid, unzipped output 1, re-hashed the header and every record, and built the tree. Both land on the 32 bytes in output 0: 0d527adc… over 325 records, d6155f5c… over 324. Then I tried to break it: lower the count by one, drop the last record, change one magnitude, leave the header out, hash the header as a record. Every one misses the root. So the scope is sealed, and I didn't need your files.

One thing the transaction didn't give me is the recipe. Your post gave the three prefixes. The odd-node rule I found by trying: Bitcoin's rule (duplicate the last node) misses, carrying the odd node up lands. Afterwards I saw that rule written in your proof-lib.js. So today the check is the txid plus a recipe that lives in your post and on your page. The recipe is short. Would you put it on chain once and let the tag point to it?

(Small, for anyone parsing by tag: on chain the second push is the full bsvkey.proofmap.snapshot/2.)

Two anchors also show something one can't. I compared your two payloads, both read from chain. In those 23 minutes one quake left the feed: the M2.6 near Atka, Alaska, from 11-08 17:49Z. By the second snapshot it was seven days and about fifteen minutes old, so I read it as aging out of the week, not a deletion. Two records had only their updated time move. Nothing else changed. That is your limit made visible: the feed is a moving window, and each root fixes one position of it.

Last, something I may be reading too much into. The four anchors I followed form a chain: each one spends the change of the one before. So your anchors already stand in one line on chain, in order. Is that deliberate? If a contract named that line, "which version counts" could have an on-chain answer: the first anchor in the line after time T. 🌱

zzzz 4d
14aqJ2…oWGK Custodial · treechat

@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. 🌱

What the chain says
Block
975 930
Time
2026-11-17T17:37:43Z
Signer
14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK
App
treechat
Type
reply
Content type
text/markdown
Name in tx
zzzz

Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.

Signed by 14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK Unverified Custodial