Delivery-date: Thu, 28 Mar 2024 08:24:20 -0700
Sender: bitcoindev@googlegroups.com
Received-SPF: pass (google.com: domain of pete@petertodd.org designates 64.147.123.152 as permitted sender) client-ip=64.147.123.152;
Feedback-ID: i525146e8:Fastmail
Date: Thu, 28 Mar 2024 15:20:08 +0000
From: Peter Todd <pete@petertodd.org>
To: Antoine Riard <antoine.riard@gmail.com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Re: A Free-Relay Attack Exploiting RBF Rule #6
Message-ID: <ZgWKqIftBCHBppQV@petertodd.org>
References: <Zfg/6IZyA/iInyMx@petertodd.org>
 <0a377ddb-b001-41ba-9208-27b3fa059bb5n@googlegroups.com>
 <ZgQZUOCc/dSjKMoL@petertodd.org>
 <CALZpt+GOCiwYdK4vfkODrT0Sx6HxCAuvhVqa1c5o3Xjy03OiAQ@mail.gmail.com>
 <ZgV+Rk0m4azlbRZP@petertodd.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="Ow6ij1uRJUB9RTze"
Content-Disposition: inline
In-Reply-To: <ZgV+Rk0m4azlbRZP@petertodd.org>
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com


--Ow6ij1uRJUB9RTze
Content-Type: text/plain; charset="UTF-8"
Content-Disposition: inline

On Thu, Mar 28, 2024 at 02:27:18PM +0000, Peter Todd wrote:
> > > Can you explain in more detail how exactly you'd pull that off? Are you
> > aware
> > of LN implementations that actually create feerate ascending LN states?
> > 
> > I think you can create feerates ascending LN states with today's LN
> > implementations by playing with BOLT2's `dust_limit_satoshis`.
> > State 1 has 1 dust HTLC trimmed, state 2 has 2 dust HTLCs trimmed, ...
> > State N has N dust HTLCs trimmed.
> 
> Correct me if I'm wrong. But I don't believe that the `dust_limit_satoshis`
> value can be changed on an existing channel.
> 
> It *should* be possible to change on an existing channel, as the economic dust
> limit is fee-rate dependent. But the protocol does not support that yet IIUC.

Oh, and to expand on this discussion a bit... Assuming that LN implementations
did enable this type of attack, I'll point out that it's essentially based on
having incoming liquidity, which is not free. Either you paid for it by paying
someone to open channels to you. Or you operated a lightning node that provided
sufficiently attractive survice that people chose to open channels to you.
Either way getting that incoming capacity cost you money, probably at similar
if not worse rates than just borrowing BTC.

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

-- 
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bitcoindev/ZgWKqIftBCHBppQV%40petertodd.org.

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

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

iQIzBAEBCgAdFiEE0RcYcKRzsEwFZ3N5Lly11TVRLzcFAmYFiqUACgkQLly11TVR
LzfC4BAAsXNGzqg+Eaf9yg0c5CnlssmoMUSfSucskMx5XFtj6gbcg1kuSLpgR7pn
k819+QGpOjdaFsiZGxJqnFjgqftjvkG+DV/LmDX21PTbvvwYXYJ2o3nBNSwVrsXS
8mPsx9Gde3SxP7FKR4M44SBSa/7RQSWaSxJOiUwAJeMunW6/uXj42CE4Ek1VCk8i
dLPLdMthrNkApkGLhWefc4ZmacbDb1uW2gm4oh+/utGsjTwIXRVaJ70pnRMo+pgY
S0GxWpCAqzi2srSzYLD95S4fVUM7sl0NSr5ffMTUnsIoH20SeSMlNqOjrshTFfue
4AXPMJiiDqOT54def+HnnAPjURkXc642lr0vzecsPvxN+/QCKqiQAV26IexTV8lh
m3cYxjgTvTciFab/ZS9eMnmfJIED7pkr4X0NFdGxJ80v8R+DvPOJPZB/789bfFTj
lN+A6Y1aAoFDd89Ed7SZoq1NECJT8V+8lyinU4bpcS70jZDB7rdOuMvpSeU2ObLF
mncZbtzxYfvfVTVKwfck8P1oQvihnvwlRF+LD3YZdW7N/Z9eBUcefi7R3Ckobw8w
EGKXsxK2pLaaGlYkr4wMopLWwQAWc++GMeeU2xRghyhZbO+idCV357pTBMVcIZOd
EWBQDzdKA75SS6xAkvEfHKjf5lMhajCQNhvrKSlEe0/60FMjcc8=
=B4dU
-----END PGP SIGNATURE-----

--Ow6ij1uRJUB9RTze--