From: Tom Harding <tomh@thinlink.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] DS Deprecation Window
Date: Mon, 27 Oct 2014 19:26:48 -0700 [thread overview]
Message-ID: <544EFEE8.4000000@thinlink.com> (raw)
In-Reply-To: <544EA85E.8010400@bluematt.me>
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
next prev parent reply other threads:[~2014-10-28 2:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 19:58 [Bitcoin-development] DS Deprecation Window Tom Harding
2014-10-27 20:17 ` Matt Corallo
2014-10-28 2:26 ` Tom Harding [this message]
2014-10-28 2:36 ` Gregory Maxwell
2014-10-28 17:38 ` Tom Harding
2014-11-06 23:50 ` Tom Harding
2014-10-28 6:24 ` Thomas Zander
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=544EFEE8.4000000@thinlink.com \
--to=tomh@thinlink.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox