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
93
94
95
96
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1X7oKw-0004H1-3E
for bitcoin-development@lists.sourceforge.net;
Thu, 17 Jul 2014 16:15:14 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com
designates 209.85.212.177 as permitted sender)
client-ip=209.85.212.177; envelope-from=jgarzik@bitpay.com;
helo=mail-wi0-f177.google.com;
Received: from mail-wi0-f177.google.com ([209.85.212.177])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1X7oKr-0002yd-Ib
for bitcoin-development@lists.sourceforge.net;
Thu, 17 Jul 2014 16:15:13 +0000
Received: by mail-wi0-f177.google.com with SMTP id ho1so3122474wib.4
for <bitcoin-development@lists.sourceforge.net>;
Thu, 17 Jul 2014 09:15:02 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc
:content-type;
bh=BNP7PW3b+XPIHaxqSxy7uqEvmTQqq/H5ybA7GOmanaY=;
b=mK6scW0E1/bRjFdvUdy8a0ljJ8yWv8zc0FvAfZKeCcY7DBvwqDlzxZ/eAR8orNScMA
O8tDc4b5HbAkrh1xEzqVJFrMxo92aWgBQuGF+d140Jk6wFwfJ/zK5TGgmCV8FHGl0CyU
cYMGx9WIo9OZC6FEPWkckJstANgOo9x2pSjKcjn8fuKOuXcSnNvgp1UuKKjayToQ9upZ
eeID/FWzutybxOEunNAigxQojlsucSyxdnZGof4jHgaHqSpoJk8SUHmbB+LXziyJIg9H
/BcbX4d00ae8R0c8lVFtSbTjz+1+DWeDlo3E975g6XKtgC4PfrQC8fnzDkCDDqXV09dc
DiOg==
X-Gm-Message-State: ALoCoQl/1ID/UEduwQqMdHv7CpeQrzgs5tDJJK7kD3Kllnn2ZTrtGvbTfLPF1TC8J9y30cAoRYyZ
X-Received: by 10.194.205.65 with SMTP id le1mr46767177wjc.67.1405613702206;
Thu, 17 Jul 2014 09:15:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.5.67 with HTTP; Thu, 17 Jul 2014 09:14:41 -0700 (PDT)
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Thu, 17 Jul 2014 12:14:41 -0400
Message-ID: <CAJHLa0PWF38N0-CFY9b3FzFdN2NfLduWHCeCQHXQOKirDYn0Pw@mail.gmail.com>
To: Mark Friedenbach <mark@monetize.io>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
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 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
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: 1X7oKr-0002yd-Ib
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Decentralizing ming
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: Thu, 17 Jul 2014 16:15:14 -0000
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/
|
