From: Mistr Bigs <misterbg6@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposals for improving Bitcoin mining decentralization
Date: Tue, 17 Jun 2014 11:23:06 +0200 [thread overview]
Message-ID: <CABssiCpXFzDPQFaTJgX_RnY1jZNhJBAn5mtJomemHaaYXVL7sw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 341 bytes --]
I have been surprised by the lack of discussion of this topic here!
On 6/17/2014 10:57 AM, Raúl Martínez wrote:
We all know the recent news, Ghash pool controlling 51% of the hashrate.
While some consider it a threat others think that is not harmful.
The thing is that we have to do something to stop this from happening again.
[-- Attachment #2: Type: text/html, Size: 495 bytes --]
next reply other threads:[~2014-06-17 9:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 9:23 Mistr Bigs [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-06-17 8:57 [Bitcoin-development] Proposals for improving Bitcoin mining decentralization Raúl Martínez
2014-06-17 13:58 ` Ron Elliott
2014-06-17 14:01 ` Raúl Martínez
2014-06-17 14:06 ` Ron Elliott
2014-06-17 14:20 ` Christophe Biocca
2014-06-17 18:25 ` Karel Bílek
2014-06-17 19:01 ` Raúl Martínez
2014-06-17 15:58 ` Isidor Zeuner
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=CABssiCpXFzDPQFaTJgX_RnY1jZNhJBAn5mtJomemHaaYXVL7sw@mail.gmail.com \
--to=misterbg6@gmail.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