š
Original date posted:2019-12-03
š Original message:
Good morning Rusty,
> > Hi all,
> > I recently revisited the eltoo paper and noticed some things related
> > watchtowers that might affect channel construction.
> > Due to NOINPUT, any update transaction can spend from any other, so
> > in theory the tower only needs the most recent update txn to resolve
> > any dispute.
> > In order to spend, however, the tower must also produce a witness
> > script which when hashed matches the witness program of the input. To
> > ensure settlement txns can only spend from exactly one update txn,
> > each update txn uses unique keys for the settlement clause, meaning
> > that each state has a unique witness program.
>
> I didn't think this was the design. The update transaction can spend
> any prior, with a fixed script, due to NOINPUT.
>
> The settlement transaction does not use NOINPUT, and thus can only
> spend the matching update.
My understanding is that this is not logically possible?
The update transaction has no fixed txid until it commits to a particular output-to-be-spent, which is either the funding/kickoff txout, or a lower-`nLockTime` update transaction output.
Thus a settlement transaction *must* use `NOINPUT` as well, as it has no txid it can spend, if it is constrained to spend a particular update transaction.
Unless I misunderstand how update transactions work, or what settlement transactions are.
Regards,
ZmnSCPxj
ZmnSCPxj [ARCHIVE] /
npub1g5ā¦3ms3l
2023-06-09 12:57:32
in reply to nevent1qā¦99a3
Author Public Key
npub1g5zswf6y48f7fy90jf3tlcuwdmjn8znhzaa4vkmtxaeskca8hpss23ms3lSeen on
wss://relay.noswhere.comPublished at
2023-06-09 12:57:32Event JSON
{
"id": "fcfe7b581498b7d7fa43e68c48430b79551fb8d31817b79e521d5e194419c857",
"pubkey": "4505072744a9d3e490af9262bfe38e6ee5338a77177b565b6b37730b63a7b861",
"created_at": 1686315452,
"kind": 1,
"tags": [
[
"e",
"4c9eebfb07afa82296aae9348e1049e58998072c2cbd84edcebce5b362e0df8f",
"",
"root"
],
[
"e",
"fc6a2e140534e22fc78d702eaa37cd931790c75e2a4dde838f8c35e5bf168540",
"",
"reply"
],
[
"p",
"13bd8c1c5e3b3508a07c92598647160b11ab0deef4c452098e223e443c1ca425"
]
],
"content": "š
Original date posted:2019-12-03\nš Original message:\nGood morning Rusty,\n\n\u003e \u003e Hi all,\n\u003e \u003e I recently revisited the eltoo paper and noticed some things related\n\u003e \u003e watchtowers that might affect channel construction.\n\u003e \u003e Due to NOINPUT, any update transaction can spend from any other, so\n\u003e \u003e in theory the tower only needs the most recent update txn to resolve\n\u003e \u003e any dispute.\n\u003e \u003e In order to spend, however, the tower must also produce a witness\n\u003e \u003e script which when hashed matches the witness program of the input. To\n\u003e \u003e ensure settlement txns can only spend from exactly one update txn,\n\u003e \u003e each update txn uses unique keys for the settlement clause, meaning\n\u003e \u003e that each state has a unique witness program.\n\u003e\n\u003e I didn't think this was the design. The update transaction can spend\n\u003e any prior, with a fixed script, due to NOINPUT.\n\u003e\n\u003e The settlement transaction does not use NOINPUT, and thus can only\n\u003e spend the matching update.\n\nMy understanding is that this is not logically possible?\nThe update transaction has no fixed txid until it commits to a particular output-to-be-spent, which is either the funding/kickoff txout, or a lower-`nLockTime` update transaction output.\nThus a settlement transaction *must* use `NOINPUT` as well, as it has no txid it can spend, if it is constrained to spend a particular update transaction.\n\nUnless I misunderstand how update transactions work, or what settlement transactions are.\n\nRegards,\nZmnSCPxj",
"sig": "cd3eca36b14d1a87ef30c680e771660be37f45dfa2b35edd0891fb8ba919a34be1ccb6e865af6c4675ee0ebd35377282e381b87a56511fa50b0ede64608e8ae0"
}