From: Mark Friedenbach <mark@monetize.io>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Mining Hashrate Caps
Date: Thu, 17 Jul 2014 09:35:20 -0400 [thread overview]
Message-ID: <53C7D118.4050908@monetize.io> (raw)
In-Reply-To: <CAKaEYhJwOPGq44+PfENKSPV8JV2bODqNtNHCqXcnJjE2e28GOQ@mail.gmail.com>
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?
q=0.4
z=0 P=1
z=1 P=0.828861
z=2 P=0.736403
z=3 P=0.664168
z=4 P=0.603401
z=5 P=0.550625
z=6 P=0.50398
z=7 P=0.462301
z=8 P=0.424782
z=9 P=0.390828
z=10 P=0.359976
z=11 P=0.331858
z=12 P=0.306167
z=13 P=0.282649
z=14 P=0.261083
z=15 P=0.24128
z=16 P=0.223076
z=17 P=0.206324
z=18 P=0.190896
z=19 P=0.176676
On 07/17/2014 06:59 AM, Melvin Carvalho wrote:
> I noticed this article today.
>
> GHash Commits to 40% Hashrate Cap at Bitcoin Mining Summit
>
> http://www.coindesk.com/ghash-commits-40-hashrate-cap-bitcoin-mining-summit/
>
> Here's a quote from Satoshi when the mining arms race began:
>
> "We should have a gentleman’s agreement to postpone the GPU arms race as
> long as we can for the good of the network. It’s much easer to get new
> users up to speed if they don’t have to worry about GPU drivers and
> compatibility. It’s nice how anyone with just a CPU can compete fairly
> equally right now."
>
> Maybe outdated now, but I thought it was interesting.
>
>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
>
>
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
next prev parent reply other threads:[~2014-07-17 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 10:59 [Bitcoin-development] Mining Hashrate Caps Melvin Carvalho
2014-07-17 13:35 ` Mark Friedenbach [this message]
2014-07-17 15:45 ` David A. 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=53C7D118.4050908@monetize.io \
--to=mark@monetize.io \
--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