Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Channels getting closed due to fee rate differences
See original GitHub issueIssue Description
Know this is a known issue - but is still and issue! Log below of a burst of closes I got.
Errors from Peers:
eclairdebug.2018-06-19.log:15:39:42.939 remoteFeeratePerKw=13362 localFeeratePerKw=1891' eclairdebug.2018-06-21.log:13:49:37.221 remoteFeeratePerKw=12147 localFeeratePerKw=500'
Errors we sent:
eclairdebug.2018-06-17.log:04:59:36.356 remoteFeeratePerKw=3548 localFeeratePerKw=500 eclairdebug.2018-06-19.log:15:39:37.033 remoteFeeratePerKw=1888 localFeeratePerKw=13362 eclairdebug.2018-06-19.log:15:39:37.033 remoteFeeratePerKw=1888 localFeeratePerKw=13362 eclairdebug.2018-06-19.log:15:39:39.071 remoteFeeratePerKw=1888 localFeeratePerKw=13362 eclairdebug.2018-06-20.log:18:39:36.320 remoteFeeratePerKw=768 localFeeratePerKw=37364 eclairdebug.2018-06-21.log:06:39:36.312 remoteFeeratePerKw=41159 localFeeratePerKw=5567 eclairdebug.2018-06-21.log:06:39:36.824 remoteFeeratePerKw=41000 localFeeratePerKw=5567 eclairdebug.2018-06-21.log:06:39:36.824 remoteFeeratePerKw=41159 localFeeratePerKw=5567 eclairdebug.2018-06-21.log:06:39:36.945 remoteFeeratePerKw=41159 localFeeratePerKw=5567 eclairdebug.2018-06-21.log:06:39:37.218 remoteFeeratePerKw=41159 localFeeratePerKw=5567 eclairdebug.2018-06-21.log:09:09:36.312 remoteFeeratePerKw=35500 localFeeratePerKw=924 eclairdebug.2018-06-21.log:12:27:24.182 remoteFeeratePerKw=41000 localFeeratePerKw=500 eclairdebug.2018-06-21.log:13:49:36.579 remoteFeeratePerKw=500 localFeeratePerKw=12147 eclairdebug.2018-06-21.log:16:39:36.323 remoteFeeratePerKw=7489 localFeeratePerKw=1001 eclairdebug.2018-06-21.log:20:39:36.329 remoteFeeratePerKw=25317 localFeeratePerKw=3587 eclairdebug.2018-06-21.log:21:19:50.392 remoteFeeratePerKw=37482 localFeeratePerKw=3601
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Actually
max-feerate-mismatch = 2would suffice, it’s nonlinear. If only all the peers had the same settings.This is fixed by #684, fee rates mismatch should now be extremely uncommon.