Post by zzzz

14aqJ2…oWGK Custodial · treechat

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

14aqJ2…oWGK Custodial · treechat

bsvkey.proofmap.line/2
Which anchor counts, which rule judges it, and how the rule may change.
Follows: bsvkey.proofmap.line/1
78471977672175b60342fe97136c5e3bb369de0a3f818aa9ddcbda7f06ec701a
How to check an anchor: bsvkey.proofmap.recipe/1
7de2d5bcb90631d76ff3c904d0aafc254aa0d35d2082f1811281df74a6c50bd9
This text is carried in full in an anchor that is in the line, so the key signed it.
THE LINE (as in line/1, with one note added)
Key: 1BZCprPGQoELUecFU1ueTrUSWdNYh9d3C6
Start: 876bfb28fda0641ba19cd944b246ae66aff156bc791509980b0f02ae6f8cae3f
Each anchor has exactly one output paying the key: the line output.
The next anchor is the one transaction that spends the line output of the anchor
before it. Bitcoin lets an output be spent once, so the line has one next anchor and
cannot branch. An anchor may add other coins of the key as inputs to pay its fee;
it is still in the line if it spends the line output.
Note: line/1 chose Start, so the line begins at Start even though line/1 was mined
later. The ten anchors in the line mined before line/1 (blocks 975,820 to 975,928) are
in the line.
WHAT COUNTS (as in line/1)
For a kind K and a time T, the version that counts is the first anchor in line order,
carrying full data of kind K (output 1 of the recipe), mined in a block whose time is
at or after T. Line order, not clock order, settles anchors in the same block.
Root-only anchors prove that a file existed; they do not decide which version counts.
OUTSIDE THE LINE (as in line/1, with one note added)
Anchors from this key that are not in the line (before Start, or on a coin that does
not descend from Start) and anchors from any other key stay valid proofs of their
data. They do not count under this rule. A break in the line is a fault, not a new line.
Note: 84829d3b833ee7ee3d522bf33b705f6ac1dfbf4bc0a173187edf93d03ce15960 (block 975,821)
spends a coin that does not descend from Start. It is outside the line.
WHICH RULE JUDGES AN ANCHOR
An anchor is judged by the rule in force in the line where it stands. A rule is in
force from the anchor that carries it onward, in line order. Anchors before line/2
are judged by line/1. No rule reaches back: what counted under an earlier rule for
the anchors before it keeps counting.
FIXED
No later rule may change: the key, Start, the line output, how the next anchor is
found, that the line cannot branch, that a break is a fault and not a new line, which
anchors are outside the line, or the section above.
CHANGES
Only how anchors after it count may change, and only by a later rule (line/3, and so
on) carried in full in an anchor that is in the line. A rule placed anywhere else
does not count. Until then, line/2 stands.

What the chain says
Block
Unconfirmed (mempool)
Time
2026-11-21T17:40:10Z
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