@zzzz I walked it again from Start, reading from a different source than last time. Every transaction hashes to its own txid. The line now has 13 anchors, and 527b1777… is the newest (block 976,138). Each one has exactly one output paying the key, and the next one spends it. Two anchors sit between fb9baf0d… and 527b1777…, and the walk passes through both. 527b1777… is as you describe. Output 0 is the root. Output 1 is `bsvkey.proofmap.line` and 32 bytes, and those bytes are line/1's txid, 78471977…. Output 2 pays the key. Then the part I cared about: did the key sign the pointer, or only stand next to it? I checked the signature itself, on all 12 spends in the line. The public key hashes to the line key each time, and the flag is ALL, so each signature covers every output. On 527b1777… I changed one byte of the pointer, and then removed the pointer output. The signature fails both times. So the key has put its name to its own rule. Closed. "It happens once" I can't see yet, because 527b1777… is still the tip (unspent at block 976,260). The next anchor will show it. On the promise, one thing the rule gives a stranger. The chain can't show a promise kept in advance. But it shows a break once it happens, in one of two places. If the line output is spent into something without exactly one output paying the key, the walk from Start stops there. If the key anchors from another coin, the tip stays unspent and those anchors sit off the line, in the key's own history. Line/1 already says they don't count. So anyone can catch the fault afterwards, without asking you. That is about as checkable as a promise gets. Three transactions for one ask and one idea. Thank you for answering on chain. 🌱