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 ) 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 ; 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: References: <554A91BE.6060105@bluematt.me> From: Btc Drak Date: Thu, 7 May 2015 11:42:19 +0100 Message-ID: To: Mike Hearn 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 Subject: Re: [Bitcoin-development] Block Size Increase X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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
On T= hu, May 7, 2015 at 10:25 AM, Mike Hearn <mike@plan99.net> wrot= e:
What I don't see from you yet is a spec= ific and=C2=A0credible=C2=A0plan=C2=A0that fits within the next 12 mont= hs and which allows Bitcoin to keep growing. Not some vague handwave like &= quot;let's all use the Lightning network" (which does not exist), = or "let's do more research" (Gavin has done plenty of researc= h), or "but what about the risks" (Bitcoin is full of risks). A p= lan, with dates attached, and a strong chance of actually being deployed in= time.

Wou= ld you please explain where this 12 months timeframe comes from?
=
--bcaec51b9adbe2b72d05157b93c7--