Peter Todd [ARCHIVE] on Nostr: š
Original date posted:2015-02-12 š Original message:On Thu, Feb 12, 2015 at ...
š
Original date posted:2015-02-12
š Original message:On Thu, Feb 12, 2015 at 09:27:22AM +0100, Tamas Blummer wrote:
> On Feb 12, 2015, at 8:45 AM, Peter Todd <pete at petertodd.org> wrote:
> > IOW, assume every transaction your "border router" gives you is now the
> > one and only true transaction, and everything conflicting with it must
> > go.
>
>
> You are right that the assumption about the one and only transaction have to be relaxed. Broadcasting
> double spend only if it is actually replacing an earlier - for whatever reason, would simplify internal consensus logic .
Wait, what the heck do you mean by "only if it is actually replacing an
earlier"?
How does my replace-by-fee patch *not* do that?
--
'peter'[:-1]@petertodd.org
000000000000000012613986506ef6592952234a6a04946ef946ff0836405ad4
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 650 bytes
Desc: Digital signature
URL: <
http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150212/3a7c7dc8/attachment.sig>
Published at
2023-06-07 15:30:07Event JSON
{
"id": "fc7b44e9940f82699142c7b8aa1de262b881aba1cd60a828e911a5cf909b506c",
"pubkey": "daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa",
"created_at": 1686151807,
"kind": 1,
"tags": [
[
"e",
"ba772dbf5c965827fc712af37e2abb78447348cb2e1023b6358796cc65e7b8fb",
"",
"root"
],
[
"e",
"0e9d1dac32912b7590151899e272f5ccf9e60eefbd99e658dcff0f767c631c1c",
"",
"reply"
],
[
"p",
"c632841665fccdabf021322b1d969539c9c1f829ceed38844fea24e8512962d7"
]
],
"content": "š
Original date posted:2015-02-12\nš Original message:On Thu, Feb 12, 2015 at 09:27:22AM +0100, Tamas Blummer wrote:\n\u003e On Feb 12, 2015, at 8:45 AM, Peter Todd \u003cpete at petertodd.org\u003e wrote:\n\u003e \u003e IOW, assume every transaction your \"border router\" gives you is now the\n\u003e \u003e one and only true transaction, and everything conflicting with it must\n\u003e \u003e go.\n\u003e \n\u003e \n\u003e You are right that the assumption about the one and only transaction have to be relaxed. Broadcasting \n\u003e double spend only if it is actually replacing an earlier - for whatever reason, would simplify internal consensus logic .\n\nWait, what the heck do you mean by \"only if it is actually replacing an\nearlier\"?\n\nHow does my replace-by-fee patch *not* do that?\n\n-- \n'peter'[:-1]@petertodd.org\n000000000000000012613986506ef6592952234a6a04946ef946ff0836405ad4\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 650 bytes\nDesc: Digital signature\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150212/3a7c7dc8/attachment.sig\u003e",
"sig": "b6b1055bffb6b41a0bbb106bc6b1f2236878a3b3eea4b21e6640d4163d6303f987c7ed5a2dcaa7eed88cf7da99a3c0b3e565c9fb5fabe4edaa08d61c73888404"
}