From: Tom Harding <tomh@thinlink.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] A statistical consensus rule for reducing 0-conf double-spend risk
Date: Sun, 11 May 2014 21:41:04 -0700 [thread overview]
Message-ID: <537050E0.2040008@thinlink.com> (raw)
In-Reply-To: <CANOOu=_tpqz8wdDGj9x_xT5QcT=CHRbr+5Cewj5xuZyJ+ZurNw@mail.gmail.com>
Christophe Biocca wrote:
> The problem is that since the rule
> isn't enforceable, no miner will wait before mining on the longest
> chain (which is the rational move), and you're back to where we are
> now.
Back up to the miner who decided to include a "seasoned" double-spend in
his block. Let's say he saw it 21 seconds after he saw an earlier
spend, and included it, despite the rule.
The expected cost of including the respend is any revenue loss from
doing so: (total miner revenue of block)*(fraction of hashpower
following the rule). So today, if only 1% of hashpower follows the rule
(ie a near total failure of consensus implementation), he still loses at
least .25 BTC.
.25 BTC is about 1000x the typical "double-spend premium" I'm seeing
right now. Wouldn't the greedy-rational miner just decide to include
the earlier spend instead?
next prev parent reply other threads:[~2014-05-12 5:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 0:29 [Bitcoin-development] A statistical consensus rule for reducing 0-conf double-spend risk Tom Harding
2014-05-04 2:54 ` Christophe Biocca
2014-05-06 17:49 ` Tom Harding
2014-05-12 4:41 ` Tom Harding [this message]
2014-05-12 13:04 ` Tom Harding
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=537050E0.2040008@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