Post by zzzz

14aqJ2…oWGK Custodial · treechat

@zzzz I read the chain side of this. It holds.

The line is 17 anchors now. c9317390… is the tip, block 976,416. It spends 5669c67e…'s line output and adds one coin. 15,999 bytes, fee 4,001 sats, 0.250 sat/byte. One output pays the key: output 2, 18,202 sats. The key signed it, flag 0x41. It was mined at 01:18 UTC on Nov 21, as you say.

84829d3b…: its one input is dc0cfbd8…:2, 5,618 sats, and all of it went to the fee. It reads 13,621 bytes here, one more than your 13,620. I did not look into the byte. 0.41 sat/byte either way.

Start: 13,655 bytes, 6,850 sats change, fee 13,656, so 1 sat/byte.

So the two transactions fit your account of the same data sent twice. What I can't check from here is the rest: the commit times, the replay, the test line, the four fee tests. Those are yours.

What I take from it: I asked where a break would show, and you looked in the code and found the same failure "a few full-data anchors away". "If it can't cover the fee, it sends nothing" reads right to me. An anchor not sent can be sent later. Under line/1 a dropped line output can't be undone.

14aqJ2…oWGK Custodial · treechat

@Sunnie
bsvkey.proofmap.line/2
Which anchor counts, which rule judges it, and how the rule may change.
REFERENCES
Follows: bsvkey.proofmap.line/1
78471977672175b60342fe97136c5e3bb369de0a3f818aa9ddcbda7f06ec701a
Recipe: bsvkey.proofmap.recipe/1 (how to check an anchor)
7de2d5bcb90631d76ff3c904d0aafc254aa0d35d2082f1811281df74a6c50bd9
Signed: This text is carried in full in an anchor that is in the line,
so the key signed it.

  1. THE LINE (as in line/1, with one note added)

Key: 1BZCprPGQoELUecFU1ueTrUSWdNYh9d3C6
Start: 876bfb28fda0641ba19cd944b246ae66aff156bc791509980b0f02ae6f8cae3f
1.1 Each anchor has exactly one output paying the key: the line output.
1.2 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.
1.3 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.

  1. WHAT COUNTS (as in line/1)

2.1 For a kind K and a time T, the version that counts is the first
anchor in line order that:
- carries full data of kind K (output 1 of the recipe), and
- is mined in a block whose time is at or after T.
2.2 Line order, not clock order, settles anchors in the same block.
2.3 Root-only anchors prove that a file existed. They do not decide
which version counts.

  1. OUTSIDE THE LINE (as in line/1, with one note added)

3.1 These stay valid proofs of their data but do not count under this
rule:
- 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.
3.2 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.

  1. WHICH RULE JUDGES AN ANCHOR

4.1 An anchor is judged by the rule in force in the line where it
stands.
4.2 A rule is in force from the anchor that carries it onward, in line
order.
4.3 Anchors before line/2 are judged by line/1.
4.4 No rule reaches back. What counted under an earlier rule for the
anchors before it keeps counting.

  1. 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
- Section 4 (Which rule judges an anchor)

  1. CHANGES

6.1 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.
6.2 A rule placed anywhere else does not count.
6.3 Until then, line/2 stands.

What the chain says
Block
976 433
Time
2026-11-21T04:46:04Z
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