Date: Mon, 11 Dec 2017 13:19:43 -0500
From: Peter Todd <pete@petertodd.org>
To: Luke Dashjr <luke@dashjr.org>,
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <20171211181943.GA9855@savin.petertodd.org>
References: <AE14915B-37DF-4D94-A0B1-E32A26903807@sprovoost.nl>
	<201712051939.33238.luke@dashjr.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="yrj/dFKFPuw6o+aM"
Content-Disposition: inline
In-Reply-To: <201712051939.33238.luke@dashjr.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
Cc: Matt Corallo <matt@chaincode.com>
Subject: Re: [bitcoin-dev] BIP-21 amendment proposal: -no125
Precedence: list


--yrj/dFKFPuw6o+aM
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Dec 05, 2017 at 07:39:32PM +0000, Luke Dashjr via bitcoin-dev wrote:
> On Tuesday 05 December 2017 7:24:04 PM Sjors Provoost wrote:
> > I recently submitted a pull request that would turn on RBF by default,
> > which triggered some discussion [2]. To ease the transition for merchan=
ts
> > who are reluctant to see their customers use RBF, Matt Corallo suggested
> > that wallets honor a no125=3D1 flag.
> >=20
> > So a BIP-21 URI would look like this:
> > bitcoin:175t...45W?amount=3D20.3&no125=3D1
> >=20
> > When this flag is set, wallets should not use RBF, regardless of their
> > default, unless the user explicitly overrides the merchant's preference.
>=20
> This seems counterproductive. There is no reason to ever avoid the RBF fl=
ag.=20
> I'm not aware of any evidence it even reduces risk of, and it certainly=
=20
> doesn't prevent double spending. Plenty of miners allow RBF regardless of=
 the=20
> flag, and malicious double spending doesn't benefit much from RBF in any =
case.

I'll second the objection to a no-RBF flag.

--=20
https://petertodd.org 'peter'[:-1]@petertodd.org

--yrj/dFKFPuw6o+aM
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJaLsw6AAoJECSBQD2l8JH7vjEH/Avdd65/GfHZuAq/ERJC3tTL
MlF/e2gGDQAjSVOgr4ar7aP1/qDEH3W3vBmv4904ZIndmiU/fiQm3MYR0k6VmpkW
aOoMwcQCXEwssiCGq+Cxfs6nqMQUBcIB+PTg+lzOtfyZFXabISAIluK/+3gzB6HD
igt5J1G8rm6ISWVoxJnhMsovtwF/5oAZgPh+e9LKRUoI8RQMU5GZkwaZOIiZrGda
eBf7e4TYLPOCD5054w6FMQeQJDRc6eubLMKn/Z4CC+Pr+uLn0KLE9s1Km0v5ml+P
+YhjnVySRuvzBAOe0XXOPIhCC90hcsJQl+CTYDzb5Vgb4WJop5U9+ZTSjIwTt+A=
=W3U7
-----END PGP SIGNATURE-----

--yrj/dFKFPuw6o+aM--