While testing #130, I started I bitcoin-core 30.2 that was still doing the IBD on miannet.
The UI was able to catch that the app was disconnected from bitcoin-core showing the error below:
But it was misleading because the real root cause was that my mainnet node was in IBD mode, shown by the error log and the CLI call:
2026-05-04T20:26:41.524653Z WARN jd_client_sv2::channel_manager: Waiting for initial template and prevhash from Template Provider...
2026-05-04T20:26:41.524686Z WARN jd_client_sv2::channel_manager: Is the Bitcoin node undergoing IBD?
./bitcoin-30.2/bin/bitcoin-cli getblockchaininfo
{
"chain": "main",
"blocks": 0,
"headers": 618163,
"bestblockhash": "000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f",
"bits": "1d00ffff",
"target": "00000000ffff0000000000000000000000000000000000000000000000000000",
"difficulty": 1,
"time": 1231006505,
"mediantime": 1231006505,
"verificationprogress": 7.401958172337937e-10,
"initialblockdownload": true,
"chainwork": "0000000000000000000000000000000000000000000000000000000100010001",
"size_on_disk": 293,
"pruned": false,
"warnings": [
]
}
While testing #130, I started I bitcoin-core 30.2 that was still doing the IBD on miannet.
The UI was able to catch that the app was disconnected from bitcoin-core showing the error below:
But it was misleading because the real root cause was that my mainnet node was in IBD mode, shown by the error log and the CLI call:
./bitcoin-30.2/bin/bitcoin-cli getblockchaininfo { "chain": "main", "blocks": 0, "headers": 618163, "bestblockhash": "000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f", "bits": "1d00ffff", "target": "00000000ffff0000000000000000000000000000000000000000000000000000", "difficulty": 1, "time": 1231006505, "mediantime": 1231006505, "verificationprogress": 7.401958172337937e-10, "initialblockdownload": true, "chainwork": "0000000000000000000000000000000000000000000000000000000100010001", "size_on_disk": 293, "pruned": false, "warnings": [ ] }