summaryrefslogtreecommitdiff
path: root/ec/bf5f2a4f4405b3f582b01991b748d2aae3f5e9
blob: a22553bc0e2128df8c18b44544e8b5add8568851 (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
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <btcdrak@gmail.com>) id 1YqJGv-0001OY-5F
	for bitcoin-development@lists.sourceforge.net;
	Thu, 07 May 2015 10:43:17 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.216.53 as permitted sender)
	client-ip=209.85.216.53; envelope-from=btcdrak@gmail.com;
	helo=mail-vn0-f53.google.com; 
Received: from mail-vn0-f53.google.com ([209.85.216.53])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1YqJGt-0004lK-9A
	for bitcoin-development@lists.sourceforge.net;
	Thu, 07 May 2015 10:43:17 +0000
Received: by vnbg7 with SMTP id g7so2764240vnb.11
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 07 May 2015 03:43:09 -0700 (PDT)
X-Received: by 10.52.142.115 with SMTP id rv19mr2431215vdb.78.1430995389821;
	Thu, 07 May 2015 03:43:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.63.5 with HTTP; Thu, 7 May 2015 03:42:19 -0700 (PDT)
In-Reply-To: <CANEZrP3wGWHdz+ut6pvke5TJJsc1rTFt8sn2KziX35oL5LAsyg@mail.gmail.com>
References: <554A91BE.6060105@bluematt.me>
	<CANEZrP3wGWHdz+ut6pvke5TJJsc1rTFt8sn2KziX35oL5LAsyg@mail.gmail.com>
From: Btc Drak <btcdrak@gmail.com>
Date: Thu, 7 May 2015 11:42:19 +0100
Message-ID: <CADJgMzsCyHm7DZhSqq1OTujz+0U9Dzj2jNEKsOn3Jj0noMCKpg@mail.gmail.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: multipart/alternative; boundary=bcaec51b9adbe2b72d05157b93c7
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	1.0 HK_RANDOM_FROM         From username looks random
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.6 HK_RANDOM_ENVFROM      Envelope sender username looks random
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(btcdrak[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-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
	0.0 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1YqJGt-0004lK-9A
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Block Size Increase
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, 07 May 2015 10:43:17 -0000

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

On Thu, May 7, 2015 at 10:25 AM, Mike Hearn <mike@plan99.net> wrote:

> What I don't see from you yet is a *specific and credible plan* that fits
> within the next 12 months and which allows Bitcoin to keep growing. Not
> some vague handwave like "let's all use the Lightning network" (which does
> not exist), or "let's do more research" (Gavin has done plenty of
> research), or "but what about the risks" (Bitcoin is full of risks). A
> plan, with dates attached, and a strong chance of actually being deployed
> in time.
>

Would you please explain where this 12 months timeframe comes from?

--bcaec51b9adbe2b72d05157b93c7
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">On T=
hu, May 7, 2015 at 10:25 AM, Mike Hearn <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:mike@plan99.net" target=3D"_blank">mike@plan99.net</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:s=
olid;padding-left:1ex"><div dir=3D"ltr"><div><div class=3D"gmail_extra"><di=
v class=3D"gmail_quote"><div>What I don&#39;t see from you yet is a <b>spec=
ific and=C2=A0credible=C2=A0plan</b>=C2=A0that fits within the next 12 mont=
hs and which allows Bitcoin to keep growing. Not some vague handwave like &=
quot;let&#39;s all use the Lightning network&quot; (which does not exist), =
or &quot;let&#39;s do more research&quot; (Gavin has done plenty of researc=
h), or &quot;but what about the risks&quot; (Bitcoin is full of risks). A p=
lan, with dates attached, and a strong chance of actually being deployed in=
 time.</div></div></div></div></div></blockquote><div><br></div><div><span =
style=3D"color:rgb(51,51,51);font-family:&#39;Helvetica Neue&#39;,Helvetica=
,Arial,sans-serif;font-size:14px;line-height:17px;white-space:pre-wrap">Wou=
ld you please explain where this 12 months timeframe comes from?</span><br>=
</div></div></div></div>

--bcaec51b9adbe2b72d05157b93c7--