MIME-Version: 1.0
From: Daniel Lipshitz <daniel@gap600.com>
Date: Sun, 11 Dec 2022 22:24:00 +0200
Message-ID: <CACkWPs_F94t9Q8TfyYYGxQANUT78SWFGkTOh6qRwnt=6ct7aig@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="00000000000065295005ef932b89"
Subject: [bitcoin-dev] A proposal for Full RBF to not exclude Zero Conf use
	case
Precedence: list

--00000000000065295005ef932b89
Content-Type: text/plain; charset="UTF-8"

Intro
Currently there is a significant use case of 0-Conf acceptance of
transactions. Merchants and service providers are fully aware of the risks
related to 0-conf. Full RBF if it would be significantly enabled would most
likely make 0-conf not possible and significantly limit this current use
case. A primary motivation for full RBF is to enable an increase of fee of
trxs and enable faster acceptance in Block should it be required.

Motivation
To enable full RBF adoption without this impeding the 0-conf use case. This
can be done by enabling the primary use of case full RBF i.e increase the
fee, while keeping the outputs of TRX1 to be included within TRX2.

Method
TRX1 is the trx first published and held in Mempool, TRX2 is the trx which
comes to replace TRX1.

In order for a TRX2 to  replace TRX1 in the Mempool it will require the
following

   - 1. Outputs (addresses and amounts) are the same TRX1 and TRX2

Or


   - 2. TRX2 Outputs include Outputs of TRX1 i.e TRX2 has additional
   Outputs to TRX1

Both cases would require the addition of at least one Input in order to
increase the fee.

In such a case 0-conf acceptance of TRX1 will result in a harmless double
spend since TRX1 will not be included in the valid UTXO set; however
the address beneficiaries of TRX1 will still be credited by TRX2.

This rule would enable the increasing of network fees post publication of
trx without the loss of 0-conf use case.

Drawbacks
Does require access to another Input inorder to take advantage of Full RBF.


Summary
Access to OptinRBF and FullRBF(with above limitation) would give actors
full access to increasing fees as an option. The 0-conf whose risks are
very much understood in the market can continue to exist as is, with the
0-conf ongoing choices being continuing to be available to actors.
________________________________

Daniel Lipshitz
GAP600| www.gap600.com
Phone: +44 113 4900 117
Skype: daniellipshitz123
Twitter: @daniellipshitz

--00000000000065295005ef932b89
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Intro</div><div>Currently there is a significant=C2=
=A0use case of 0-Conf acceptance of transactions. Merchants and service pro=
viders are fully aware of the risks related to 0-conf. Full RBF if it would=
 be significantly enabled would most likely make 0-conf not possible and si=
gnificantly=C2=A0limit this current=C2=A0use case. A primary motivation for=
 full RBF is to enable an increase of fee of trxs and enable faster=C2=A0ac=
ceptance in Block should it be required.</div><div><br></div>Motivation<div=
>To enable full RBF adoption without this impeding=C2=A0the 0-conf use case=
. This can be done by enabling the primary use of case full RBF i.e increas=
e the fee, while keeping the outputs of TRX1 to be included within TRX2.</d=
iv><div><br></div><div>Method</div><div>TRX1 is the trx first published and=
 held in Mempool, TRX2 is the trx which comes to replace TRX1.=C2=A0</div><=
div><br></div><div>In order for a TRX2 to=C2=A0 replace TRX1 in the Mempool=
 it will require the following=C2=A0</div><div><ul><li>1. Outputs (addresse=
s and amounts) are the same TRX1 and TRX2</li></ul><blockquote style=3D"mar=
gin:0 0 0 40px;border:none;padding:0px"><div>Or</div></blockquote><div><ul>=
<li>2. TRX2 Outputs include Outputs of TRX1 i.e TRX2 has additional Outputs=
 to TRX1</li></ul></div><span style=3D"font-size:12.8px">Both cases would r=
equire the addition of at least one Input in order to increase the fee.=C2=
=A0</span></div><div><span style=3D"font-size:12.8px"><br></span></div><div=
><span style=3D"font-size:12.8px">In such a case 0-conf acceptance of TRX1 =
will result in a harmless double spend since TRX1 will not be included in t=
he valid UTXO set; however the=C2=A0address beneficiaries of TRX1 will stil=
l be credited by TRX2.</span></div><div><span style=3D"font-size:12.8px"><b=
r></span></div><div><span style=3D"font-size:12.8px">This rule would enable=
 the increasing of network fees post publication of trx without the loss of=
 0-conf use case.</span></div><div><span style=3D"font-size:12.8px"><br></s=
pan></div><div><span style=3D"font-size:12.8px">Drawbacks=C2=A0</span></div=
><div><span style=3D"font-size:12.8px">Does require access to another Input=
 inorder to take advantage of Full RBF.=C2=A0</span></div><div><br></div><d=
iv><span style=3D"font-size:12.8px"><br></span></div><div><span style=3D"fo=
nt-size:12.8px">Summary</span></div><div><span style=3D"font-size:12.8px">A=
ccess to OptinRBF and FullRBF(with above limitation) would give actors full=
 access to increasing fees as an option. The 0-conf whose risks are very mu=
ch understood in the market can continue to exist as is, with the 0-conf on=
going choices being continuing to be available to actors.<br>______________=
__________________</span><br><div><div dir=3D"ltr" class=3D"gmail_signature=
" data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><div dir=3D"ltr"><div=
 style=3D"font-size:12.8px"><br></div><div style=3D"font-size:12.8px"><font=
 face=3D"tahoma, sans-serif">Daniel Lipshitz</font></div><div style=3D"font=
-size:12.8px;color:rgb(0,0,0)"><font face=3D"tahoma, sans-serif">GAP600|=C2=
=A0<a href=3D"http://www.gap600.com/" target=3D"_blank">www.gap600.com</a><=
/font></div><div style=3D"font-size:12.8px;color:rgb(0,0,0)"><font face=3D"=
tahoma, sans-serif">Phone:=C2=A0</font><span style=3D"font-family:tahoma,sa=
ns-serif;font-size:12.8px">+44 113 4900 117</span></div><div style=3D"font-=
size:12.8px;color:rgb(0,0,0)"><font face=3D"tahoma, sans-serif">Skype: dani=
ellipshitz123</font></div><div style=3D"font-size:12.8px;color:rgb(0,0,0)">=
<font face=3D"tahoma, sans-serif">Twitter: @daniellipshitz</font></div></di=
v></div></div></div></div></div>

--00000000000065295005ef932b89--