From: Mike Hearn <mike@plan99.net>
To: Natanael <natanael.l@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposal: Requiring a miner's signature in the block header
Date: Wed, 11 Feb 2015 14:52:12 +0100 [thread overview]
Message-ID: <CANEZrP2kB3H6SFdo3xCD1CxCyv5aB2BDH7Ad62a4iAJw8X1EHw@mail.gmail.com> (raw)
In-Reply-To: <CAAt2M1_qj0r03=Ref9mN7bJLg-odep3m5teZ7JWDLC+zknQdQQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 391 bytes --]
If you're interested in working on mining decentralisation, chipping away
at getblocktemplate support would be a better path forward. It's possible
to have decentralised pooled mining - I know it sounds like a contradiction
but it's not.
I wrote about some of the things that can be done in this blog post:
https://blog.bitcoinfoundation.org/mining-decentralisation-the-low-hanging-fruit/
[-- Attachment #2: Type: text/html, Size: 754 bytes --]
next prev parent reply other threads:[~2015-02-11 13:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 8:54 [Bitcoin-development] Proposal: Requiring a miner's signature in the block header Hector Chu
2015-02-11 9:25 ` Natanael
2015-02-11 13:52 ` Mike Hearn [this message]
2015-02-12 13:56 Ittay
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=CANEZrP2kB3H6SFdo3xCD1CxCyv5aB2BDH7Ad62a4iAJw8X1EHw@mail.gmail.com \
--to=mike@plan99.net \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=natanael.l@gmail.com \
/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