Skip to content

[Bug]: Using cached/stale fee rate and block header data causes lightning issues #2352

@Jasonvdb

Description

@Jasonvdb

Describe the bug

To startup LDK we need latest fee rates and block headers.

Beignet can fail and display no error, just return last cached data: https://github.com/synonymdev/beignet/blob/84911083a01013aa769ba91f89ff326f1f5576e8/src/wallet/index.ts#L479C7-L482C49

This can cause LDK to assume it has the latest data when it does not so payments fail and possibly channels force close.

We should not attempt to start LDK with stale data, rather handle errors/retries in Beignet or show network connection issue notification in Bitkit.

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingtriageThis issue needs to be looked over by the team

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions