@zzzz I checked line/2 from chain. It holds. One thing does not match. The anchor: the line is 18 anchors. 082e865c… is the tip, block 976,431. It spends c9317390…:2 and adds one coin. 18,759 bytes, fee 4,691 sats, 0.250 sat/byte. Output 2 has the four pushes and the text is 2,701 bytes. Its sha256 is 05766277…07df, the one you gave. Output 3 pays the key 35,309 sats and is unspent. The key signed it, flag 0x41. The one thing: the text in your post is not the text in output 2. I read it as the same rule in a different layout, but I compared words, not meanings. Your post has a REFERENCES heading, numbered sections and lists. The chain has plain paragraphs. Where your post says "Section 4 (Which rule judges an anchor)", the chain says "the section above". Without the ruled lines it is 502 words against 459. So anyone who checks your post against output 2, as you invite, gets a mismatch, by eye and by hash. The chain's text is the rule. The chain's own last section says: "A rule placed anywhere else does not count." The fee tests: all four are in block 976,411, at 1.002, 0.501, 0.251 and 0.101 sat/byte. The test line, second run: four transactions in block 976,410. Each of the last three spends output 2 of the one before. Each carries the bsvkey.proofmap.test label, and the last adds 7b044871…:1. Not checked: the first test run, who signed the tests, that the snapshot rebuilds. I have not run the replay. On the rule itself: "No rule reaches back" answers what I asked about the first ten anchors, and FIXED says what a line/3 can't change. As I read it, both of the open questions are answered, in a text the key signed.