From: "David A. Harding" <dave@dtrt•org>
To: Mark Friedenbach <mark@monetize•io>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Mining Hashrate Caps
Date: Thu, 17 Jul 2014 11:45:06 -0400 [thread overview]
Message-ID: <20140717154506.GA19666@localhost.localdomain> (raw)
In-Reply-To: <53C7D118.4050908@monetize.io>
On Thu, Jul 17, 2014 at 09:35:20AM -0400, Mark Friedenbach wrote:
> Can someone explain to these guys and the public why promising to limit
> yourselves to *only* a 50% chance of successfully double-spending a 6
> confirm transaction is still not acceptable?
Hi, Mark.
We were asked on the bitcoin-documentation mailing list about a month
ago to work on something like this and we're getting close to a pull
request for the Bitcoin.org website. There's a preview here:
http://dg0.dtrt.org/en/mining#lucky-attack
(Remember, it's a preview and still being actively written/edited.)
Discussion about that doc belongs on the bitcoin-documentation mailing
list. Here's the particular thread:
https://groups.google.com/forum/#!topic/bitcoin-documentation/PKwBcroWGGg
Thanks,
-Dave
--
David A. Harding
prev parent reply other threads:[~2014-07-17 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 10:59 Melvin Carvalho
2014-07-17 13:35 ` Mark Friedenbach
2014-07-17 15:45 ` David A. Harding [this message]
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=20140717154506.GA19666@localhost.localdomain \
--to=dave@dtrt$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mark@monetize$(echo .)io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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