📅 Original date posted:2017-01-25
📝 Original message:Assuming Alice is paying Bob with an old style time-locked tx. Under your proposal, after the hardfork, Bob is still able to confirm the time-locked tx on both networks. To fulfil your new rules he just needs to send the outputs to himself again (with different tx format). But as Bob gets all the money on both forks, it is already a successful replay
> On 25 Jan 2017, at 15:15, Natanael <natanael.l at gmail.com> wrote:
>
>
> Den 25 jan. 2017 08:06 skrev "Johnson Lau" <jl2012 at xbt.hk <mailto:jl2012 at xbt.hk>>:
> What you describe is not a fix of replay attack. By confirming the same tx in both network, the tx has been already replayed. Their child txs do not matter.
>
> Read it again.
>
> The validation algorithm would be extended so that the transaction can't be replayed, because replaying it in the other network REQUIRES a child transaction in the same block that is valid, a child transaction the is unique to the network. By doing this policy change simultaneously in both networks, old pre-signed transactions *can not be replayed by anybody but the owner* of the coins (as he must spend them immediately in the child transaction).
>
> It means that as soon as spent, the UTXO sets immediately and irrevocably diverges across the two networks. Which is the entire point, isn't it?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170125/2ead65d2/attachment-0001.html>;
Johnson Lau [ARCHIVE] /
npub1fy…p2mv9
2023-06-07 17:55:38
in reply to nevent1q…8hns
Author Public Key
npub1fyh6gqhg8zgyhhywkty047s64z2a7fjr307enrr3kqwtnk64plmsup2mv9Seen on
wss://relay.noswhere.comPublished at
2023-06-07 17:55:38Event JSON
{
"id": "8f21ae18839c042ee570ffcdcdf40a992b8b62e043ea15be7452623ffb6ff18f",
"pubkey": "492fa402e838904bdc8eb2c8fafa1aa895df26438bfd998c71b01cb9db550ff7",
"created_at": 1686160538,
"kind": 1,
"tags": [
[
"e",
"08564427a86ede87bab23151dbcfb043a11ce80299dd31e312bfe1aa29950657",
"",
"root"
],
[
"e",
"161eec7b2fb99847e3973210977d3f7f431c806b1059a61c307bd6dc47fb6a3b",
"",
"reply"
],
[
"p",
"f14f3c71a4e63a12c842e4a50471263ada4b6cfde093fcb6588693a726b9b018"
]
],
"content": "📅 Original date posted:2017-01-25\n📝 Original message:Assuming Alice is paying Bob with an old style time-locked tx. Under your proposal, after the hardfork, Bob is still able to confirm the time-locked tx on both networks. To fulfil your new rules he just needs to send the outputs to himself again (with different tx format). But as Bob gets all the money on both forks, it is already a successful replay\n\n\n\u003e On 25 Jan 2017, at 15:15, Natanael \u003cnatanael.l at gmail.com\u003e wrote:\n\u003e \n\u003e \n\u003e Den 25 jan. 2017 08:06 skrev \"Johnson Lau\" \u003cjl2012 at xbt.hk \u003cmailto:jl2012 at xbt.hk\u003e\u003e:\n\u003e What you describe is not a fix of replay attack. By confirming the same tx in both network, the tx has been already replayed. Their child txs do not matter.\n\u003e \n\u003e Read it again. \n\u003e \n\u003e The validation algorithm would be extended so that the transaction can't be replayed, because replaying it in the other network REQUIRES a child transaction in the same block that is valid, a child transaction the is unique to the network. By doing this policy change simultaneously in both networks, old pre-signed transactions *can not be replayed by anybody but the owner* of the coins (as he must spend them immediately in the child transaction). \n\u003e \n\u003e It means that as soon as spent, the UTXO sets immediately and irrevocably diverges across the two networks. Which is the entire point, isn't it? \n\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170125/2ead65d2/attachment-0001.html\u003e",
"sig": "d00b64ed16f9bdb3add9599af9d78d2ee2e7b22852974ab024216ef8cfaa56ce87c66df0136d048bbfe4692d607fd50a42c9b1b60b66ed4e7dd7049da2b11a96"
}