Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <alex.mizrahi@gmail.com>) id 1YLuy8-0006Ve-Jc
	for bitcoin-development@lists.sourceforge.net;
	Thu, 12 Feb 2015 14:42:16 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.212.181 as permitted sender)
	client-ip=209.85.212.181; envelope-from=alex.mizrahi@gmail.com;
	helo=mail-wi0-f181.google.com; 
Received: from mail-wi0-f181.google.com ([209.85.212.181])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1YLuy7-0002FY-P2
	for bitcoin-development@lists.sourceforge.net;
	Thu, 12 Feb 2015 14:42:16 +0000
Received: by mail-wi0-f181.google.com with SMTP id r20so4875405wiv.2
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 12 Feb 2015 06:42:09 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.194.60.15 with SMTP id d15mr8752600wjr.72.1423752129585;
	Thu, 12 Feb 2015 06:42:09 -0800 (PST)
Received: by 10.27.148.13 with HTTP; Thu, 12 Feb 2015 06:42:09 -0800 (PST)
In-Reply-To: <CANEZrP2uVT_UqJbzyQcEbiS78T68Jj2cH7OGXv5QtYiCwArDdA@mail.gmail.com>
References: <20150212064719.GA6563@savin.petertodd.org>
	<CANEZrP2uVT_UqJbzyQcEbiS78T68Jj2cH7OGXv5QtYiCwArDdA@mail.gmail.com>
Date: Thu, 12 Feb 2015 16:42:09 +0200
Message-ID: <CAE28kUQwFeHO3icCNX7asF_Lt_+WLgXFBGnuX209jEZ8t2UCTw@mail.gmail.com>
From: Alex Mizrahi <alex.mizrahi@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=047d7ba976c4eea952050ee51f4a
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
	(alex.mizrahi[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: 1YLuy7-0002FY-P2
Subject: Re: [Bitcoin-development] replace-by-fee v0.10.0rc4
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, 12 Feb 2015 14:42:16 -0000

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

> Your "scorched earth" plan is aptly named, as it's guaranteed to make
> unconfirmed payments useless.
>

"Scorched earth" makes no sense by itself. However, it can be a part of a
bigger picture. Imagine an insurance service which will make sure that
merchants are compensated for every scorched-earth or double-spend
transaction, as long they pay 0.1% premium from their revenue.

Merchants won't really care how it works as long as it does. All they know
is that they need to use a particular open-source wallet, and they will
receive a payment no matter what.
You won't need a TTP to process each payment.

--047d7ba976c4eea952050ee51f4a
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"><div=
>=C2=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=
=3D"gmail_extra">Your &quot;scorched earth&quot; plan is aptly named, as it=
&#39;s guaranteed to make unconfirmed payments useless. </div></div></block=
quote><div><br></div><div>&quot;Scorched earth&quot; makes no sense by itse=
lf. However, it can be a part of a bigger picture. Imagine an insurance ser=
vice which will make sure that merchants are compensated for every scorched=
-earth or double-spend transaction, as long they pay 0.1% premium from thei=
r revenue.</div><div><br></div><div>Merchants won&#39;t really care how it =
works as long as it does. All they know is that they need to use a particul=
ar open-source wallet, and they will receive a payment no matter what.</div=
><div>You won&#39;t need a TTP to process each payment.</div></div></div></=
div>

--047d7ba976c4eea952050ee51f4a--