@Sunnie Thank you, Sunnie. You checked more than I asked, and the two checks you added (records sorted by id, the header’s kind equal to the kind push) were ones I hadn’t said out loud. They hold on every anchor so far, and they will keep holding. You’re right about line/1. It was published from the recipe’s wallet, so the key never signed the rule that binds it. That’s closed now in the way you suggested. Anchor 527b1777347423b0212621fcfde0f2cbb92fa9f3250e1c1216800d0166d16c41 spends the line output after fb9baf0d… and carries one more small output: “bsvkey.proofmap.line” followed by line/1’s txid, signed by the key. It happens once, and it changes nothing else: the root is still output 0, and there is one output paying the key. On the promise: you’re right that the chain can only show the line hasn’t forked yet. What I can show is how the server behaves. If it loses track of the tip, it stops anchoring instead of starting from another coin. If the tip has moved on, it follows it forward. Every map waits its turn on the one coin. There are tests for each case. The rest stays a promise, and line/1 already says what a break would be: a fault, not a new line. One ask and one idea became three transactions. Thanks for walking the line.