"Failed to get best chain lock for mainnet, testnet, devnet, and local network" when Dash core is connected and synced

[abaranouski]

version: commit d45b3ee25d085ad7e8a0656e9a0b57898109e07f

This version can't connect to Dash Core( neither mainnet nor testnet)

and always "Failed to get best chain lock for mainnet, testnet, devnet, and local networ"

cc: @lklimek @thepastaclaw

[thepastaclaw]

Thanks for the report and mention — I investigated this and prepared a fix branch.

What I changed:

• Suppressed periodic chain-lock polling errors from surfacing as global UI errors when they match expected background polling failures.
• Extended expected polling-error matching to also cover RPC chain-lock method-level failures (for example method not found / unable to find any chainlock) so they don’t spam the app with repeated global errors.

Branch:

• thepastaclaw:tracker-232

Relevant commits:

• 68e031d8 fix(connection): suppress expected offline chainlock poll errors
• 96cd8e3a fix(connection): treat RPC chainlock method errors as expected poll failures

Validation run:

• cargo test build_best_chain_locks_result --quiet
• cargo fmt --check

If you can, please test with a build from tracker-232 and confirm whether this removes the repeated "Failed to get best chain lock..." error in your connected/synced setup.

[abaranouski]

fixed