Feedback-ID: i525146e8:Fastmail
Date: Mon, 20 Jun 2022 19:49:55 -0400
From: Peter Todd <pete@petertodd.org>
To: Antoine Riard <antoine.riard@gmail.com>,
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <YrEHo+3XLDNgIOnz@petertodd.org>
References: <CALZpt+GOh-7weEypT9JrzcwthZJqHOfj7sf9FMuqi5_FZv0g7w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature"; boundary="kKaqn7yZhg3ljyFL"
Content-Disposition: inline
In-Reply-To: <CALZpt+GOh-7weEypT9JrzcwthZJqHOfj7sf9FMuqi5_FZv0g7w@mail.gmail.com>
Subject: Re: [bitcoin-dev] Playing with full-rbf peers for fun and L2s
 security
Precedence: list


--kKaqn7yZhg3ljyFL
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Jun 13, 2022 at 08:25:11PM -0400, Antoine Riard via bitcoin-dev wro=
te:
> For that reason, I believe it would be beneficial to the flourishing of
> multi-party funded transactions to fix the Dos vector by seeing a subset =
of
> the network running full-rbf and enabling propagation of honest multi-par=
ty
> transactions to the interested miners, replacing potential non-signaling
> double-spend from a malicious counterparty. Moving towards that direction,
> I've submitted a small patch against Bitcoin Core enabling it to turn on
> full-rbf as a policy, still under review [3]. The default setting stays
> **false**, i.e keeping opt-in RBF as a default replacement policy. I've
> started to run the patch on a public node at 146.190.224.15.

BTW I changed one of my OTS calendars to issue fee-bumping txs without the
opt-in RBF flag set as an experiment. I also made sure txs would propagate =
to
the above node. As of right now, it's up to 32 replacements (once per block=
),
without any of them mined; the calendars use the strategy of starting at the
minimum possible fee, and bumping the fee up every time a new block arrives
without the tx getting mined. So that's evidence we don't have much full-rbf
hash power at this moment.

You can see the current status at: https://alice.btc.calendar.opentimestamp=
s.org/

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

--kKaqn7yZhg3ljyFL
Content-Type: application/pgp-signature; name="signature.asc"

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

iQEzBAEBCgAdFiEEFcyURjhyM68BBPYTJIFAPaXwkfsFAmKxB50ACgkQJIFAPaXw
kfssOQf/eW5GHdnNQOlre3ofR/S2NAraTUu1Vpve5TadPoaNnPsgq73pbO6v3zbU
5xFABCyCeaTxOqB0Co+Y0weTC1HF1ncLlBR58/38YWG0/w5oyRXL2EY0w8hYrOYH
UuzfzPieyNM7JITqFTIv7ljUOzuRSZV5h/JV4f/OW+W9kbW8Mgx8elbVKU4TRP5V
8e31dU3AwEDo2tchk9gcfLIKR8A/m0q3M9ReYqU6JCa4DQXzbq4WfITceadTvcrN
wiitywKUMm+Z9gBwZTEBecNWHAT+2sNlp6brsjPCykVfRKOTSD0cfdOrMfoO5vvh
GDDRiMHsO5eCsf/ABKPqQcmrOzMYsA==
=iYAf
-----END PGP SIGNATURE-----

--kKaqn7yZhg3ljyFL--