Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

BOLT 2: peers need to check each other's dust limit #696

Closed
rustyrussell opened this issue Nov 6, 2019 · 0 comments · Fixed by #894
Closed

BOLT 2: peers need to check each other's dust limit #696

rustyrussell opened this issue Nov 6, 2019 · 0 comments · Fixed by #894
Labels
bug

Comments

@rustyrussell
Copy link
Collaborator

Because HTLCs below this amount are not enforceable, the peer could grief you by setting it high the dropping to chain. The miners will benefit, not them, but it's still a potential loss.
t-bast added a commit that referenced this issue Aug 11, 2021
@t-bast
Peers need to check each other's dust limit
58e7ec0 
Since HTLCs below this amount will not appear in the commitment tx, they
are effectively converted to miner fees. The peer could use this to grief
you by broadcasting its commitment once it contains a lot of dust HTLCs.

Fixes #696
@t-bast t-bast mentioned this issue Aug 11, 2021
Merged
t-bast added a commit that referenced this issue Aug 31, 2021
@t-bast
Peers need to check each other's dust limit
3b4b5f8 
Since HTLCs below this amount will not appear in the commitment tx, they
are effectively converted to miner fees. The peer could use this to grief
you by broadcasting its commitment once it contains a lot of dust HTLCs.

Fixes #696
t-bast added a commit that referenced this issue Sep 15, 2021
@t-bast
Peers need to check each other's dust limit
a19d5fb 
Since HTLCs below this amount will not appear in the commitment tx, they
are effectively converted to miner fees. The peer could use this to grief
you by broadcasting its commitment once it contains a lot of dust HTLCs.

Fixes #696
t-bast added a commit that referenced this issue Oct 6, 2021
@t-bast
Peers need to check each other's dust limit (#894)
8f2104e 
Since HTLCs below this amount will not appear in the commitment tx, they
are effectively converted to miner fees. The peer could use this to grief
you by broadcasting its commitment once it contains a lot of dust HTLCs.

Add network dust thresholds computation details, as implemented in Bitcoin
Core's default relay policy.

Drop non-segwit support in shutdown: this allows dust limit to go as low
as 354 sats without creating relay issues with default node policies.

We add a requirement that dust limit cannot be lower than 354 sats.
This ensures implementers don't have to figure this subtlety on their own.

Fixes #696 and #905
@bitromortac bitromortac mentioned this issue Oct 22, 2021
Merged
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Peers need to check each other's dust limit lightning/bolts
1 participant
@rustyrussell