Wrong confirmation timestamps when using Fulcrum as Electrum node #1585
Description
As reported in our Discord server, the transaction timestamps, as shown on Home and Transactions panel, can be wrong when using Fulcrum as the Electrum node option. This doesn't affect the time to recovery shown in the Coins panel since that is based on the confirmation block height.
It looks like there may be a bug in the BDK crate we're using when making batch requests to Fulcrum (bitcoindevkit/rust-electrum-client#129), possibly due to BDK assuming the batch results are in the same order as the request and therefore mixing up block times. Judging by the comment in the issue, this bug was fixed in BDK 1.0.0-beta.2, but we're currently using BDK 1.0.0-alpha.13. Our master branch is now using the same version of rust-electrum-client as BDK 1.0.0-beta.2, but I suspect the problem is in the bdk_electrum crate, which we're still using an older version of.
Unfortunately, we haven't been able to upgrade to the latest BDK version yet due to a slowdown in Electrum syncing there (see #1555 (comment)).
A workaround is to use a different Electrum node, e.g. electrs, but otherwise, this issue will not affect the functioning of the timelocks, only how transaction times are displayed.