1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1YLXiG-0004Eq-EC
for bitcoin-development@lists.sourceforge.net;
Wed, 11 Feb 2015 13:52:20 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.180 as permitted sender)
client-ip=74.125.82.180; envelope-from=mh.in.england@gmail.com;
helo=mail-we0-f180.google.com;
Received: from mail-we0-f180.google.com ([74.125.82.180])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YLXiE-00061c-D3
for bitcoin-development@lists.sourceforge.net;
Wed, 11 Feb 2015 13:52:20 +0000
Received: by mail-we0-f180.google.com with SMTP id k11so3522099wes.11
for <bitcoin-development@lists.sourceforge.net>;
Wed, 11 Feb 2015 05:52:12 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.180.198.101 with SMTP id jb5mr19146740wic.92.1423662732329;
Wed, 11 Feb 2015 05:52:12 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.194.188.11 with HTTP; Wed, 11 Feb 2015 05:52:12 -0800 (PST)
In-Reply-To: <CAAt2M1_qj0r03=Ref9mN7bJLg-odep3m5teZ7JWDLC+zknQdQQ@mail.gmail.com>
References: <CAAO2FKEFxC_byt4xVJb0S-7yy0M7M-Av7MHUH-RBDuri_GAFtw@mail.gmail.com>
<CAAt2M1_qj0r03=Ref9mN7bJLg-odep3m5teZ7JWDLC+zknQdQQ@mail.gmail.com>
Date: Wed, 11 Feb 2015 14:52:12 +0100
X-Google-Sender-Auth: 9zDyquu1BUPJDiHL-mok7IrQssE
Message-ID: <CANEZrP2kB3H6SFdo3xCD1CxCyv5aB2BDH7Ad62a4iAJw8X1EHw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Natanael <natanael.l@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b624d1470cd82050ed04f84
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1YLXiE-00061c-D3
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposal: Requiring a miner's signature
in the block header
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Wed, 11 Feb 2015 13:52:20 -0000
--047d7b624d1470cd82050ed04f84
Content-Type: text/plain; charset=UTF-8
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/
--047d7b624d1470cd82050ed04f84
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra">If you're interested in wor=
king on mining decentralisation, chipping away at getblocktemplate support =
would be a better path forward. It's possible to have decentralised poo=
led mining - I know it sounds like a contradiction but it's not.</div><=
div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">I wrote abou=
t some of the things that can be done in this blog post:</div><div class=3D=
"gmail_extra"><br></div><div class=3D"gmail_extra"><a href=3D"https://blog.=
bitcoinfoundation.org/mining-decentralisation-the-low-hanging-fruit/">https=
://blog.bitcoinfoundation.org/mining-decentralisation-the-low-hanging-fruit=
/</a><br></div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_ext=
ra"><br></div></div>
--047d7b624d1470cd82050ed04f84--
|
