📅 Original date posted:2015-07-24
📝 Original message:
Hi Anthony,
If we're presuming everyone uses OP_CSV in the long-term, you can
overload nLockTime with values below current unixtime as a
filter/counter. It should be enough bits of entropy no matter the size
(even in the billions of transactions in a single channel) Since both
parties are signing the nLockTime value, it's safe to use that as an
identifier in the Commitment Transaction.
--
Joseph Poon
Joseph Poon [ARCHIVE] /
npub1ej…p9cq8
2023-06-09 12:43:44
in reply to nevent1q…qfcy
Author Public Key
npub1ej6vep7y2km5l6awukffelg8yeppkth2vjkjk9jypd5w336rxggs3p9cq8Published at
2023-06-09 12:43:44Event JSON
{
"id": "0d8c7054fe1f11e4874c7d786390b14566806af02252a0d5c46f6aeab45fd675",
"pubkey": "ccb4cc87c455b74febaee5929cfd0726421b2eea64ad2b16440b68e8c7433211",
"created_at": 1686314624,
"kind": 1,
"tags": [
[
"e",
"70bc73032209813d1efbd8c41b490ea29a02fc5941bbed8bed53cf49c33f8564",
"",
"root"
],
[
"e",
"adac6571190c3c391bd4723c1aebd16b3b0247e41eebbb2b940843dccfe36031",
"",
"reply"
],
[
"p",
"f0feda6ad58ea9f486e469f87b3b9996494363a26982b864667c5d8acb0542ab"
]
],
"content": "📅 Original date posted:2015-07-24\n📝 Original message:\nHi Anthony,\n\nIf we're presuming everyone uses OP_CSV in the long-term, you can\noverload nLockTime with values below current unixtime as a\nfilter/counter. It should be enough bits of entropy no matter the size\n(even in the billions of transactions in a single channel) Since both\nparties are signing the nLockTime value, it's safe to use that as an\nidentifier in the Commitment Transaction.\n\n-- \nJoseph Poon",
"sig": "0b1255e3b7dbcdb9c1dde980617ec76b6c3c35c6901a0ade714f9da2c7162bbb3c564db9af950b54b8aa1e35035a156014e32ad6a1f77f5c8219f00a5f3bd1fe"
}