10101: Cannot accept value that would put our exposure to dust HTLCs
Our users currently can’t fund their 10101 wallet because of that error.
2023-05-03 09:50:28 | {"timestamp":"2023-05-03T09:50:28.484712603Z","level":"INFO","fields":{"message":"Cannot accept value that would put our exposure to dust HTLCs at 10201000 over the limit 5000000 on counterparty commitment tx","log.target":"lightning::ln::channel","log.module_path":"lightning::ln::channel","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-8ffd0e8d14b5d2cc/6df5761/lightning/src/ln/channel.rs","log.line":2842},"target":"lightning::ln::channel"}
-- | --
2023-05-03 09:50:28 | {"timestamp":"2023-05-03T09:50:28.484820391Z","level":"INFO","fields":{"message":"Cannot accept value that would put our exposure to dust HTLCs at 10201000 over the limit 5000000 on holder commitment tx","log.target":"lightning::ln::channel","log.module_path":"lightning::ln::channel","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-8ffd0e8d14b5d2cc/6df5761/lightning/src/ln/channel.rs","log.line":2852},"target":"lightning::ln::channel"}
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 18 (16 by maintainers)
Commits related to this issue
- fix: Remove constraint on min amount Receiving min 50k sats was an arbitrary amount and did at most only mitigate the chances of preventing https://github.com/get10101/10101/issues/580. Given that t... — committed to get10101/10101 by holzeis a year ago
- Merge #836 #856 836: Replace fee rate fallbacks in settings with constant r=luckysori a=luckysori The fallbacks were only ever used if we could never get an answer from the fee rate server. As such,... — committed to get10101/10101 by bors[bot] a year ago
- Merge #856 856: fix: app cannot receive payment with open position r=luckysori a=holzeis - **Remove stop-gap on receiving payment with open position**: It seems a change in the past fixed that issue... — committed to get10101/10101 by bors[bot] a year ago
Strictly speaking: this not a bug but by design 😅🙈
I rebased the draft PR. However, after reading a bit into LDK discord and roadmap, I concluded that we can’t do much about it until anchor outputs land and LDK (and our DLC fork is updated afterwards.). At this stage there is hope they will land in upcoming 116 release (by the end of Q2). I subscribed to relevant threads, and will update the ticket when it lands.
In the meantime, marking it as ‘blocked’
Increasing the invoice size to 50k does not solve that issue. Reopening, for the anchor output fix.
I think it is an issue until we have anchor outputs: when adding HTLCs we have to account for the TX fee and if we can’t use CPFP to bump the fee, the reserved fee amount might render the remaining amount below dust limit. That’s what makes HTLCs fail
Not just you 🙈
Ah, ok, so this ticket gets resolved once we upgrade to anchor outputs. Let’s keep it then 😃