📅 Original date posted:2022-02-16
📝 Original message:> What do you mean by monotone in the context of sponsor transactions?
I take this to mean that the validity of a sponsor txn is
"monotonically" true at any point after the inclusion of the sponsored
txn in a block.
> And when you say tx-index, do you mean an index for looking up a
> transaction by its ID? Is that not already something nodes do?
Indeed, not all nodes have this ability. Each bitcoind node has a map
of unspent coins which can be referenced by outpoint i.e.(txid, index),
but the same isn't true for all historical transactions. I
(embarrassingly) forgot this in the prior post.
The map of (txid -> transaction) for all time is a separate index that
must be enabled via the `-txindex=1` flag; it isn't enabled by default
because it isn't required for consensus and its growth is unbounded.
> > The current consensus threshold for transactions to become invalid
> > is a 100 block reorg
>
> What do you mean by this? The only 100 block period I'm aware of is
> the coinbase cooldown period.
If there were a reorg deeper than 100 blocks, it would permanently
invalidate any transactions spending the recently-matured coinbase
subsidy in any block between $new_reorg_tip and ($former_tip_height -
100). These invalidated spends would not be able to be reorganized
into a new replacement chain.
How this differs in practice or principle from a "regular" double-spend
via reorg I'll leave for another message. I'm not sure that I understand
that myself. Personally I think if we hit a >100 block reorg, we've got
bigger issues than coinbase invalidation.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20220216/d93aabca/attachment.html>;
James O'Beirne [ARCHIVE] /
npub1dp…ymz3t
2023-06-07 23:04:21
in reply to nevent1q…6sgn
Author Public Key
npub1dpdfw74plzm03mzglkdegp3hqn6qs9yffqefa5kh98mru49nrg7szymz3tPublished at
2023-06-07 23:04:21Event JSON
{
"id": "e2937f87e563203de03bed3b366aa4b50502012c6424bff52ca0ba5f804194cb",
"pubkey": "685a977aa1f8b6f8ec48fd9b94063704f408148948329ed2d729f63e54b31a3d",
"created_at": 1686179061,
"kind": 1,
"tags": [
[
"e",
"c703681c72b4e4669ca1bb5b15d757a9761db34f49baa03e75c29c4c1b65c0d1",
"",
"root"
],
[
"e",
"13bbd263a93799c79d4861cd4d905e9ef9d5cde69b1e9821da3ecd9765318b3e",
"",
"reply"
],
[
"p",
"3030ec2d70259fdd55ba8e063740c139c3daaa618f86e3fae34cebcb73c742ba"
]
],
"content": "📅 Original date posted:2022-02-16\n📝 Original message:\u003e What do you mean by monotone in the context of sponsor transactions?\n\nI take this to mean that the validity of a sponsor txn is\n\"monotonically\" true at any point after the inclusion of the sponsored\ntxn in a block.\n\n\u003e And when you say tx-index, do you mean an index for looking up a\n\u003e transaction by its ID? Is that not already something nodes do?\n\nIndeed, not all nodes have this ability. Each bitcoind node has a map\nof unspent coins which can be referenced by outpoint i.e.(txid, index),\nbut the same isn't true for all historical transactions. I\n(embarrassingly) forgot this in the prior post.\n\nThe map of (txid -\u003e transaction) for all time is a separate index that\nmust be enabled via the `-txindex=1` flag; it isn't enabled by default\nbecause it isn't required for consensus and its growth is unbounded.\n\n\u003e \u003e The current consensus threshold for transactions to become invalid\n\u003e \u003e is a 100 block reorg\n\u003e\n\u003e What do you mean by this? The only 100 block period I'm aware of is\n\u003e the coinbase cooldown period.\n\nIf there were a reorg deeper than 100 blocks, it would permanently\ninvalidate any transactions spending the recently-matured coinbase\nsubsidy in any block between $new_reorg_tip and ($former_tip_height -\n100). These invalidated spends would not be able to be reorganized\ninto a new replacement chain.\n\nHow this differs in practice or principle from a \"regular\" double-spend\nvia reorg I'll leave for another message. I'm not sure that I understand\nthat myself. Personally I think if we hit a \u003e100 block reorg, we've got\nbigger issues than coinbase invalidation.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20220216/d93aabca/attachment.html\u003e",
"sig": "fb5875146259444e094fa7079b3baefa0a4d7aaac1aa7681960d1893782fff283d2309fd63955412f8d188abd7d84efe0093b8ac43424ee806238cbc3f35fd06"
}