Date: Sat, 19 Jun 2021 03:36:53 -1000
From: "David A. Harding" <dave@dtrt.org>
To: Antoine Riard <antoine.riard@gmail.com>
Message-ID: <20210619133653.m2272jgna5geuuki@ganymede>
References: <CALZpt+FF_TT_K3wjWhhaDE6Ue=RAsM2JWO7-mYjm5LtHqJvNmg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature"; boundary="rzkc565rjzyfsifh"
Content-Disposition: inline
In-Reply-To: <CALZpt+FF_TT_K3wjWhhaDE6Ue=RAsM2JWO7-mYjm5LtHqJvNmg@mail.gmail.com>
User-Agent: NeoMutt/20180716
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
 "lightning-dev\\\\@lists.linuxfoundation.org"
 <lightning-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] [Lightning-dev] Waiting SIGHASH_ANYPREVOUT and
	Packing Packages
Precedence: list


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

On Fri, Jun 18, 2021 at 06:11:38PM -0400, Antoine Riard wrote:
> 2) Solving the Pre-Signed Feerate problem : Package-Relay or
> SIGHASH_ANYPREVOUT
>=20
> For Lightning, either package-relay or SIGHASH_ANYPREVOUT should be able =
to
> solve the pre-signed feerate issue [3]
>
> [...]
>
> [3] I don't think there is a clear discussion on how SIGHASH_ANYPREVOUT
> solves pinnings beyond those LN meetings logs:
> https://gnusha.org/lightning-dev/2020-06-08.log

For anyone else looking, the most relevant line seems to be:

  13:50 < BlueMatt> (sidenote: sighash_no_input is *really* elegant here
  - assuming a lot of complicated logic in core to do so, you could
  imagine blind-cpfp-bumping *any* commitment tx without knowing its
  there or which one it is all with one tx.......in theory)

That might work for current LN-penalty, but I'm not sure it works for
eltoo.  If Bitcoin Core can rewrite the blind CPFP fee bump transaction
to refer to any prevout, that implies anyone else can do the same.
Miners who were aware of two or more states from an eltoo channel would
be incentivized to rewrite to the oldest state, giving them fee revenue
now and ensuring fee revenue in the future when a later state update is
broadcast.

If the attacker using pinning is able to reuse their attack at no cost,
they can re-pin the channel again and force the honest user to pay
another anyprevout bounty to miners.  Repeat this a bunch of times and
the honest user has now spent more on fees than their balance from the
closed channel.

Even if my analysis above is wrong, I would encourage you or Matt or
someone to write up this anyprevout idea in more detail and distribute
it before you promote it much more.

> package-relay sounds a reasonable, temporary "patch".

Even if every protocol based on presigned transactions can magically
allow dynamically adding inputs and modifying outputs for fees, and we
also have a magic perfect transaction replacement protocol, package
relay is still fundamentally useful for CPFP fee bumping very low
feerate transactions received from an external party.  E.g. Alice pays
Bob, mempool min feerates increase and Alice's transaction is dropped,
Bob still wants the money, so he submits a package with Alice's
transaction plus his own high feerate spend of it.

Package relay is a clear improvement now, and one I expect to be
permanent for as long as we're using anything like the current protocol.
=20
> # Deployment timeline
>=20
> So what I believe as a rough deployment timeline.

I don't think it's appropriate to be creating timelines like this that
depend on the work of a large number of contributors who I don't believe
you've consulted.  For details on this point of view, please see
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-July/014726.ht=
ml

Stuff will get done when it gets done.

-Dave

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

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

iQIzBAEBCgAdFiEEgxUkqkMp0LnoXjCr2dtBqWwiadMFAmDN8vUACgkQ2dtBqWwi
adMBXg//dk/8r3qubbw1Un64QAH7uk6SrY+F0HAuz5P1ddYOqhrI5DXVYtoVBCz7
mB60+hBRKFh/pFy1znVYehBD31wGj80KnIsGvkqlj1gcKg2SK1iGqTjejogvbF6h
9Au83yQWoaTtiK5AHYxuTk1Tjy0jV0tWkZjNQUjv/nI41Q27MR3v67B43VxUDImT
s7LENIkWmVK+xnewa3No461jG6apVkTp3iRGVXtsnwGCbHwEmZ0+3KZ5cMamCaOY
xeeVH1VT85I3ZFRyEo/stUd7t7jp5cLzsmFNmaAPrmzxEg2+wMzYDUf+Df08+nnS
MHryfHw9nJhgEq9U4Opcq4IpRoulplUTblM4ZOtf3hqEASDZQFg0DKzOp1Poeh22
jnGXZYYiQRcTgjEM80DH1GPv5R7T2//60YVYyB5SNx1YvjMuiTq4cC5Cg/4R/J9C
Ghtxy4Wp3KnBgXtuAhI2vjVxJJg+pF0MjM+xce5A4qgVv+lNKmo+h9UgCC1bSbRh
g231lJFkbh0SvbmVd9ynZCZYqDweLrm0A02jVh00y+mkrDHEbMctgDzY9h6e7C6S
arwHBtog7Y5n7VoHBrHmmWTX3TPAut1BNFasAmJW6DVn6WbPDvLocIEbzq26hVB/
6/Wt0p/Ul2dpL5dCbSb62ew4NGsERl2Di/Ezcbiz38jyeymkNiU=
=LTcF
-----END PGP SIGNATURE-----

--rzkc565rjzyfsifh--