MIME-Version: 1.0
In-Reply-To: <CAPg+sBhykn8BU1LAr1izH0z6nFuOv0PzWjuqq7YJX5r35LDa9Q@mail.gmail.com>
References: <1736097121.90204.1471369988809@privateemail.com>
	<201608161937.20748.luke@dashjr.org>
	<20160816194332.GA5888@fedora-21-dvm>
	<CAMZUoKkAkGRFxpyGMxQMz76L7uW6fsQAYVxkrxi5MQCiBtNnqw@mail.gmail.com>
	<CAPg+sBi30SgHHXCyipbNpiMRHYWPCRYz6ejQYKrDg3MLJp39EQ@mail.gmail.com>
	<CAMZUoKktS=Ku4kpD0bocR4X__ZpWXrkPkdOyXBaYxjq+mr9Pmw@mail.gmail.com>
	<CAPg+sBhykn8BU1LAr1izH0z6nFuOv0PzWjuqq7YJX5r35LDa9Q@mail.gmail.com>
From: "Russell O'Connor" <roconnor@blockstream.io>
Date: Mon, 5 Sep 2016 10:55:10 -0400
Message-ID: <CAMZUoKnNHkUtiwT=PKg25HmiEFZQfXxY8P2G=QZ+NJZBQDTTcg@mail.gmail.com>
To: Pieter Wuille <pieter.wuille@gmail.com>
Content-Type: multipart/alternative; boundary=94eb2c03f16c1bd909053bc3df5b
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] New BIP: Dealing with OP_IF and OP_NOTIF
 malleability in P2WSH
Precedence: list

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

For sake of example, suppose we have a marginal fee rate of 50 satoshis per
byte.  At that rate reducing the size of the witness data by 1 byte is
approximately equivalent from a miner and relayer's perspective as a
replace by fee that increases the fee by 50 satoshis.  In both cases miners
get an extra potential of 50 satoshis in revenue.

So in this sense replacing witness data with smaller witness data can pay
for its own relay cost as much as RBF can simply by requiring that the
smaller witness be smaller enough to cover the same RBF threshold.

On Tue, Aug 16, 2016 at 6:39 PM, Pieter Wuille <pieter.wuille@gmail.com>
wrote:

> On Aug 17, 2016 00:36, "Russell O'Connor" <roconnor@blockstream.io> wrote:
>
> > Can I already do something similar with replace by fee, or are there
> limits on that?
>
> BIP125 and mempool eviction both require the replacing transaction to have
> higher fee, to compensate for the cost of relaying the replaced
> transaction(s).
>
> --
> Pieter
>

--94eb2c03f16c1bd909053bc3df5b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>For sake of example, suppose we have a marginal fee r=
ate of 50 satoshis per byte.=C2=A0 At that rate reducing the size of the wi=
tness data by 1 byte is approximately equivalent from a miner and relayer&#=
39;s perspective as a replace by fee that increases the fee by 50 satoshis.=
=C2=A0 In both cases miners get an extra potential of 50 satoshis in revenu=
e.<br><br></div><div>So in this sense replacing witness data with smaller w=
itness data can pay for its own relay cost as much as RBF can simply by req=
uiring that the smaller witness be smaller enough to cover the same RBF thr=
eshold.<br></div><div><div class=3D"gmail_extra"><br><div class=3D"gmail_qu=
ote">On Tue, Aug 16, 2016 at 6:39 PM, Pieter Wuille <span dir=3D"ltr">&lt;<=
a href=3D"mailto:pieter.wuille@gmail.com" target=3D"_blank">pieter.wuille@g=
mail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span cl=
ass=3D""><p dir=3D"ltr">On Aug 17, 2016 00:36, &quot;Russell O&#39;Connor&q=
uot; &lt;<a href=3D"mailto:roconnor@blockstream.io" target=3D"_blank">rocon=
nor@blockstream.io</a>&gt; wrote:</p>
<p dir=3D"ltr">&gt; Can I already do something similar with replace by fee,=
 or are there limits on that? </p>
</span><p dir=3D"ltr">BIP125 and mempool eviction both require the replacin=
g transaction to have higher fee, to compensate for the cost of relaying th=
e replaced transaction(s).</p><span class=3D"HOEnZb"><font color=3D"#888888=
">
<p dir=3D"ltr">-- <br>
Pieter</p>
</font></span></blockquote></div><br></div></div></div>

--94eb2c03f16c1bd909053bc3df5b--