Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Z4QMD-00006s-9Q for bitcoin-development@lists.sourceforge.net; Mon, 15 Jun 2015 09:07:05 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.50 as permitted sender) client-ip=74.125.82.50; envelope-from=mh.in.england@gmail.com; helo=mail-wg0-f50.google.com; Received: from mail-wg0-f50.google.com ([74.125.82.50]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Z4QMC-0003Wg-8Y for bitcoin-development@lists.sourceforge.net; Mon, 15 Jun 2015 09:07:05 +0000 Received: by wgv5 with SMTP id 5so63259777wgv.1 for ; Mon, 15 Jun 2015 02:06:58 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.59.98 with SMTP id y2mr7000732wjq.42.1434359218225; Mon, 15 Jun 2015 02:06:58 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.28.14.196 with HTTP; Mon, 15 Jun 2015 02:06:58 -0700 (PDT) In-Reply-To: <20150615044342.GB13286@muck> References: <20150615044342.GB13286@muck> Date: Mon, 15 Jun 2015 11:06:58 +0200 X-Google-Sender-Auth: armL95VCAKsZO6Y8D-ir_syx69U Message-ID: From: Mike Hearn To: Peter Todd Content-Type: multipart/alternative; boundary=047d7ba978a0aec8b405188ac733 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: 1Z4QMC-0003Wg-8Y Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] comments on BIP 100 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: Mon, 15 Jun 2015 09:07:05 -0000 --047d7ba978a0aec8b405188ac733 Content-Type: text/plain; charset=UTF-8 > StrawPay hasn't published any details of their work publicly; if they > wanted credit on the mailing list they should have done that. > There's a brief discussion here: https://www.reddit.com/r/Bitcoin/comments/2r3ri7/strawpay_cheap_and_secure_micropayments/ But yes, they are developing it before publishing more details that may be subject to change post-implementation experience anyway. > I'm genuinely looking forward to a concrete fork proposal. Any ETA on > when the blocksize increase code will go in Bitcoin XT? > Great! I am waiting for Gavin to finish writing the patches. Once he has a patch and there's been some time for review, I guess it will go in, assuming no other issues. --047d7ba978a0aec8b405188ac733 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

=
StrawPay hasn't published any details of their work pu= blicly; if they
wanted credit on the mailing list they should have done that.

There's a brief discussion here:

<= /div>
=C2=A0 =C2=A0https://www.reddit.com/r/= Bitcoin/comments/2r3ri7/strawpay_cheap_and_secure_micropayments/

But yes, they are developing it before publishing mo= re details that may be subject to change post-implementation experience any= way.
=C2=A0
I'm genuinely looking forwa= rd to a concrete fork proposal. Any ETA on
when the blocksize increase code will go in Bitcoin XT?
=C2=A0
Great!=C2=A0 I am waiting for Gavin to finish writing th= e patches. Once he has a patch and there's been some time for review, I= guess it will go in, assuming no other issues.

--047d7ba978a0aec8b405188ac733--