Browse Source

Bidirectional spam prevention update

Add note that short-lived controlled spam is too cheap for the attacker.
We probably need to change the forward fee to account for this (TODO).
master
t-bast 4 years ago
parent
commit
a85cb1b43a
No known key found for this signature in database GPG Key ID: BE5D342AD368C13A
  1. 3
      spam-prevention.md

3
spam-prevention.md

@ -248,6 +248,9 @@ Drawbacks:
ban them; stealing upfront fees should never be worth losing channels.
* If the forward upfront payment is a network constant (1 msat?), do we need to add a mechanism to
upgrade it?
* Short-lived `controlled spam` is still free for the attacker: we should probably make the forward
upfront payment a decrementing value at each hop (committed inside the onion) to penalize this
type of attacks
### Web of trust HTLC hold fees

Loading…
Cancel
Save