From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Wwdap-0005IB-Nd for bitcoin-development@lists.sourceforge.net; Mon, 16 Jun 2014 20:33:27 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.220.175 as permitted sender) client-ip=209.85.220.175; envelope-from=alexy.kot.all@gmail.com; helo=mail-vc0-f175.google.com; Received: from mail-vc0-f175.google.com ([209.85.220.175]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Wwdan-0002ck-WD for bitcoin-development@lists.sourceforge.net; Mon, 16 Jun 2014 20:33:27 +0000 Received: by mail-vc0-f175.google.com with SMTP id hy4so5493669vcb.34 for ; Mon, 16 Jun 2014 13:33:20 -0700 (PDT) X-Received: by 10.58.123.71 with SMTP id ly7mr17615379veb.11.1402950800491; Mon, 16 Jun 2014 13:33:20 -0700 (PDT) MIME-Version: 1.0 Sender: alexy.kot.all@gmail.com Received: by 10.58.225.35 with HTTP; Mon, 16 Jun 2014 13:32:40 -0700 (PDT) In-Reply-To: References: From: Alex Kotenko Date: Mon, 16 Jun 2014 21:32:40 +0100 X-Google-Sender-Auth: w-4wttsNq_t-ngy2k94Gw_61hz0 Message-ID: To: Mike Hearn Content-Type: multipart/alternative; boundary=089e0115f0a219cbcf04fbf9f073 X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (alexy.kot.all[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 X-Headers-End: 1Wwdan-0002ck-WD Cc: Bitcoin Dev , Lawrence Nahum Subject: Re: [Bitcoin-development] instant confirmation via payment protocol backwards compatible proto buffer extension 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, 16 Jun 2014 20:33:27 -0000 --089e0115f0a219cbcf04fbf9f073 Content-Type: text/plain; charset=UTF-8 True, enough philosophy. Once this BIP will be finalized - we will it's schedule implementation in XBTerminal. This is a solution to the problem we have, probably best one we have to date, so we will use it. 2014-06-16 19:09 GMT+01:00 Mike Hearn : > I think many of us feel it'd be better if this kind of thing were not > needed at all, however, the best way to ensure it doesn't end up being used > is to write code, not to try and block alternative approaches. If Bitcoin > is robust the market should sort it out. If it's robust for some > transactions and not others, that makes for a fun project for a future > generation of hackers to sort out. > > OK, enough philosophy - let's try and keep this thread just for discussion > of the BIP itself from now on. If you'd like to continue debating the > Future of Bitcoin please change the subject line and break it out into a > new thread. > --089e0115f0a219cbcf04fbf9f073 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
True, enough philosophy. Once this BIP will be= finalized - we will it's schedule implementation in XBTerminal. This i= s a solution to the problem we have, probably best one we have to date, so = we will use it.=C2=A0


2014-06-16 19:09 GMT+01:00 Mike Hearn <mi= ke@plan99.net>:
I think many of us feel it'd be better if this ki= nd of thing were not needed at all, however, the best way to ensure it does= n't end up being used is to write code, not to try and block alternativ= e approaches. If Bitcoin is robust the market should sort it out. If it'= ;s robust for some transactions and not others, that makes for a fun projec= t for a future generation of hackers to sort out.

OK, enough philosophy - let's try and ke= ep this thread just for discussion of the BIP itself from now on. If you= 9;d like to continue debating the Future of Bitcoin please change the subje= ct line and break it out into a new thread.

--089e0115f0a219cbcf04fbf9f073--