Increase channel-jamming capital requirements by not counting dust HTLCs



Summary:

Eugene, from Crypt-iQ, has proposed a simple mitigation to increase the capital requirement of channel-jamming attacks. This would prevent an unsophisticated attacker with low capital from jamming a target channel. He believes that this mitigation is free and has no downsides besides code-writing. Eugene suggests that in a commitment transaction, dust HTLC outputs should be trimmed. The reason for the 483 HTLC limit each side has in the spec is to prevent commitment transactions from growing unreasonably large and to ensure they are still valid transactions that can be included in a block. If dust HTLCs are not included in this calculation since they are not on the commitment transaction, we still allow 483 (x2) non-dust HTLCs to be included on the commitment transaction. Eugene proposes that there could be a configurable limit on the number of outstanding dust HTLCs, but the point is that it does not affect the non-dust throughput of the channel. This raises the capital requirement of channel-jamming so that each HTLC must be non-dust, rather than spamming 1 sat payments. Eugene is interested in hearing other opinions on his proposal.


Updated on: 2023-06-03T03:57:28.273234+00:00