From: Jeff Garzik <jgarzik@bitpay•com>
To: Mark Friedenbach <mark@monetize•io>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Decentralizing ming
Date: Thu, 17 Jul 2014 12:14:41 -0400 [thread overview]
Message-ID: <CAJHLa0PWF38N0-CFY9b3FzFdN2NfLduWHCeCQHXQOKirDYn0Pw@mail.gmail.com> (raw)
Define acceptable. The 40% thing is marketing and a temporary
solution. And people come down on both sides of whether or not
marketing "40%" is a good idea.
I think it is a baby step that is moving in the right direction. You
want the numbers and sentiment moving in that direction (down, versus
"own the market! </IPO>").
The more critical piece is fleshing out the various proposals and
technical solutions for decentralized transaction selection and other
aspects of SPOF-proofing mining.
Historical note: On one hand, Satoshi seemed to dislike the early
emergence of GPU mining pools quite a bit. On the other hand, Satoshi
noted that the network would probably devolve down to a few big
players if we ever reached VISA/MC transaction levels. Satoshi
clearly never figured this part out :)
Today, there is consensus on the need for a "keep bitcoin free and
open" technical solution, but it remains to be seen how much we
engineers can really do to make life fair. Making transaction
selection a bit more independent from hashpower seems one step. There
are several other proposals floating about.
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
next reply other threads:[~2014-07-17 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 16:14 Jeff Garzik [this message]
2014-07-17 17:22 ` slush
2014-07-18 10:41 ` Mike Hearn
2014-07-18 10:43 ` Mike Hearn
2014-07-18 13:44 ` Jeff Garzik
2014-07-19 0:51 ` Emin Gün Sirer
2014-07-19 0:54 ` Emin Gün Sirer
2014-07-18 13:39 ` Jeff Garzik
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=CAJHLa0PWF38N0-CFY9b3FzFdN2NfLduWHCeCQHXQOKirDYn0Pw@mail.gmail.com \
--to=jgarzik@bitpay$(echo .)com \
--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