From dave at dtrt.org Sat Apr 4 16:05:46 2020 From: dave at dtrt.org (David A. Harding) Date: Sat, 4 Apr 2020 12:05:46 -0400 Subject: [Lightning-dev] Proof-of-closure as griefing attack mitigation In-Reply-To: References: <3N2W7o-6QbX0lG38elnlTiG5bcgI5yRhSORS7ibxgZEtLe2mGyI4gW6jVK1IP6cXF-F97uSDWTlKIygsCcx_yUkIiYt2COYBTRLTLH3ofV0=@protonmail.com> Message-ID: <20200404160546.wvukhbcooyl3tott@ganymede> On Fri, Apr 03, 2020 at 02:51:15AM +0000, ZmnSCPxj via Lightning-dev wrote: > Ah, right, E knows the revocation for the unilateral close of EE, > because it is a self-channel, sigh. And by this revocation clause it > can claim the money immediately and put it into a channel as well. If it's a self channel, E can also just RBF replace the close transaction with a minimally-sized 1-input, 1-output transaction. In addition, if typical mempools are full and the closing transaction feerate is very low (i.e. because anchor outputs are meant to be used) E may also be able to create a close transaction that will be dropped from typical mempools in the near future and may never confirm, allowing E to continue using the channel in attacks against its other peers. -Dave -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: