📅 Original date posted:2014-10-28 📝 Original message:Matt, You're right, ...

Tom Harding [ARCHIVE] /

npub1mse…mwjy

2023-06-07 15:26:58

in reply to nevent1q…8a80

📅 Original date posted:2014-10-28
📝 Original message:Matt,

You're right, thanks. Without double-spend relay, miner won't know that
some txes conflict with anything. I'll add that first-double-spends are
relayed per #4570.

Miner has to be very careful including a double-spend in his block -- he
hopes:

- that based on his measured time offset from the first spend he
received, at most a tiny fraction of the network will delay his block

- that not too many nodes saw an earlier spend that he didn't see,
which could increase that fraction

- that most other nodes saw his tx. Any who didn't will only learn
about it by receiving his block, and they will assign it the time when
they receive the block. That's likely to be more than T (30 seconds)
after an earlier spend, so they would delay the block.

The best course of action is intended to be for miner to exclude fast (<
2 hours) double spends completely.

On 10/27/2014 1:17 PM, Matt Corallo wrote:
> miners are incentivized to go connect to everyone on the network and
> look for double-spends
>
> On 10/27/14 19:58, Tom Harding wrote:
>> https://github.com/dgenr8/out-there/blob/master/ds-dep-win.md

Author Public Key

npub1msef5qkfwz4t7qacwxz775wgdtlytph78g2g2z903x90874u263sypmwjy

Show more details

Published at

2023-06-07 15:26:58

Kind type

1 Short Text Note

Event JSON

{ "id": "22e2fae2d7ff5eac59217da542a9fb320bd8e42d0a3091a386a8f3570c00c4a9", "pubkey": "dc329a02c970aabf03b87185ef51c86afe4586fe3a148508af898af3fabc56a3", "created_at": 1686151618, "kind": 1, "tags": [ [ "e", "e74239e906de2305dfdbe18a7ea8d1ac2c0b35e66c965ed70a3538c1b7174f36", "", "root" ], [ "e", "eadee7a90c036dc3576f062c22e412f660295be2ffa336de6d2f47823814ff2a", "", "reply" ], [ "p", "cd753aa8fbc112e14ffe9fe09d3630f0eff76ca68e376e004b8e77b687adddba" ] ], "content": "📅 Original date posted:2014-10-28\n📝 Original message:Matt,\n\nYou're right, thanks. Without double-spend relay, miner won't know that \nsome txes conflict with anything. I'll add that first-double-spends are \nrelayed per #4570.\n\nMiner has to be very careful including a double-spend in his block -- he \nhopes:\n\n - that based on his measured time offset from the first spend he \nreceived, at most a tiny fraction of the network will delay his block\n\n - that not too many nodes saw an earlier spend that he didn't see, \nwhich could increase that fraction\n\n - that most other nodes saw his tx. Any who didn't will only learn \nabout it by receiving his block, and they will assign it the time when \nthey receive the block. That's likely to be more than T (30 seconds) \nafter an earlier spend, so they would delay the block.\n\nThe best course of action is intended to be for miner to exclude fast (\u003c \n2 hours) double spends completely.\n\n\nOn 10/27/2014 1:17 PM, Matt Corallo wrote:\n\u003e miners are incentivized to go connect to everyone on the network and\n\u003e look for double-spends\n\u003e\n\u003e On 10/27/14 19:58, Tom Harding wrote:\n\u003e\u003e https://github.com/dgenr8/out-there/blob/master/ds-dep-win.md", "sig": "28079a020c59bcd593f50622cbfe2392fc184074f99f7787f9306d5e2618e9e1f469c0317fbc4dbeb9dc92f1b432ef321183ec26fdef6b0c7e1f51c41ca37e71" }