summaryrefslogtreecommitdiff
path: root/6d/c98b5019361e606a3147b5b618a1bc209e92cb
blob: bfbe1dce273f59309368ba23552f4e231251ab16 (plain)
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
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mh.in.england@gmail.com>) id 1YyL9p-0000CC-Ff
	for bitcoin-development@lists.sourceforge.net;
	Fri, 29 May 2015 14:21:09 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.212.170 as permitted sender)
	client-ip=209.85.212.170; envelope-from=mh.in.england@gmail.com;
	helo=mail-wi0-f170.google.com; 
Received: from mail-wi0-f170.google.com ([209.85.212.170])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1YyL9o-0002VK-LA
	for bitcoin-development@lists.sourceforge.net;
	Fri, 29 May 2015 14:21:09 +0000
Received: by wicmc15 with SMTP id mc15so17472923wic.1
	for <bitcoin-development@lists.sourceforge.net>;
	Fri, 29 May 2015 07:21:02 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.157.168 with SMTP id wn8mr15393236wjb.79.1432909262653; 
	Fri, 29 May 2015 07:21:02 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.194.143.9 with HTTP; Fri, 29 May 2015 07:21:02 -0700 (PDT)
In-Reply-To: <CAE-z3OXEGcUYYAsqqrVMQw=XA=5dt9u7XHDmuzhMJ8OkZ+k3yg@mail.gmail.com>
References: <16096345.A1MpJQQkRW@crushinator>
	<CABsx9T3-zxCAagAS0megd06xvG5n-3tUL9NUK9TT3vt7XNL9Tg@mail.gmail.com>
	<CANEZrP3VCaFsW4+gPm2kCJ9z7oVUZYVaeNf=_cJWEWwh4ZxiPQ@mail.gmail.com>
	<CABsx9T21zjHyO-nh1aSBM3z4Bg015O0rOfYq7=Sy4mf=QxUVQA@mail.gmail.com>
	<CANEZrP2BaKwhpPgcUHWAHswOmUeFLgEk4ysrn4+73qNzWDJ=yQ@mail.gmail.com>
	<CABsx9T3nCJ-w_v-yEbEE2Ytb+xC65mhYqhoAhoOHw9tkPpG0TA@mail.gmail.com>
	<CANEZrP1qH+zucYsGrMgnfi99e61Edxaj+xm=u_xYXga1g0WzJQ@mail.gmail.com>
	<CAE-z3OVmw+0doCe0hmYE6A1D61h0AUh4Mtnf5Fg1e4zQBkpraQ@mail.gmail.com>
	<CANEZrP0psA7hcJdKdA-r01UEt7ig3O-9vjwBMqKSEq-csu0hPQ@mail.gmail.com>
	<CABsx9T23r_y2R9OEgqb3AAZf47Hh8BUJncjxxmPp5v_9uKEiqQ@mail.gmail.com>
	<CAE-z3OXEGcUYYAsqqrVMQw=XA=5dt9u7XHDmuzhMJ8OkZ+k3yg@mail.gmail.com>
Date: Fri, 29 May 2015 16:21:02 +0200
X-Google-Sender-Auth: pQH3XEWqlEodTKBMnvnkzV21eiY
Message-ID: <CANEZrP15X2JbMazMN7Rw2oxums6X-D3m5zBP02YoqTa6UTzfHQ@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Tier Nolan <tier.nolan@gmail.com>
Content-Type: multipart/alternative; boundary=089e0122e968988fcf0517392fd4
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: 1YyL9o-0002VK-LA
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposed alternatives to the 20MB step
	function
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: Fri, 29 May 2015 14:21:09 -0000

--089e0122e968988fcf0517392fd4
Content-Type: text/plain; charset=UTF-8

>
> The measure is miner consensus.  How do you intend to measure
> exchange/merchant acceptance?
>

Asking them.

In fact, we already have. I have been talking to well known people and CEOs
in the Bitcoin community for some time now. *All* of them support bigger
blocks, this includes:

   - Every wallet developer I have asked (other than Bitcoin Core)
   - So far, every payment processor and every exchange company

I know Gavin has also been talking to people about this.

There's a feeling on this list that there's no consensus, or that Gavin and
myself are on the wrong side of it. I'd put it differently - there's very
strong consensus out in the wider community and this list is something of
an aberration.

--089e0122e968988fcf0517392fd4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><div=
 class=3D"gmail_quote"><div>The measure is miner consensus.=C2=A0 How do yo=
u intend to measure exchange/merchant acceptance?<br></div></div></div></di=
v></blockquote><div><br></div><div>Asking them.</div><div><br></div><div>In=
 fact, we already have. I have been talking to well known people and CEOs i=
n the Bitcoin community for some time now. <b>All</b>=C2=A0of them support =
bigger blocks, this includes:</div><div><ul><li>Every wallet developer I ha=
ve asked (other than Bitcoin Core)</li><li>So far, every payment processor =
and every exchange company</li></ul><div>I know Gavin has also been talking=
 to people about this.</div></div><div><br></div><div>There&#39;s a feeling=
 on this list that there&#39;s no consensus, or that Gavin and myself are o=
n the wrong side of it. I&#39;d put it differently - there&#39;s very stron=
g consensus out in the wider community and this list is something of an abe=
rration.</div></div></div></div>

--089e0122e968988fcf0517392fd4--