Describe the bug
After installing KDX 2.12.3, I have kdx running over some time, the log message showing
""2023-05-14 21:25:41.058 [INF] PROT: Accepted block e042af0482bc5a7d2f8cff4afb997daf0e0e936a7a88039ed6fa19377032ac89 via relay
2023-05-14 21:25:41.095 [INF] PROT: Accepted block 1be3b5ee7c8447b92c58f614eca4bf3a7b274cede83e0a304dcc5002409699d7 via relay
2023-05-14 21:25:41.443 [INF] PROT: Accepted block 67b381634514eaa5a21a4e361b2415ab6b5829d2af71df8becedb8485e794e4b via relay
2023-05-14 21:25:43.970 [INF] CMGR: Connecting to [2402:800:6374:bd0b:24a4:91bc:fe96:2147]:16111
2023-05-14 21:25:44.384 [INF] BDAG: Processed 15 blocks and 0 headers in the last 10.86s (29 transactions, 2023-05-14 21:25:47.872 -0600 MDT)
2023-05-14 21:25:44.384 [INF] PROT: Accepted block 952998ed0fb430c15ea0cab3092b199e3879570c6dd39d13022d61784f4e0389 via relay"
And I can see it connected to p2p address as well. I use kaspactl can use rpc port to query block information correctly. But from the KDX Kaspa tab, the status is always connecting. I tried to downgrade to v2.12.2, same thing.
To Reproduce
Steps to reproduce the behavior:
windows 10, download the exe, remove the .kdx folder, and the ones under AppData
run kdx
3 See error
Expected behavior
After block syched, I should see connected, and number peers, DAG status, difficulty, etc.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: windows 11 pro. 10.0.22621 Build22621
Wallet version: v2.12.3
Additional context
Add any other context about the problem here.
Kaspad database has been corrupted, delete datadir and resync under settings. If issue persists, check the stability of your system, might be hardware issues.
Describe the bug After installing KDX 2.12.3, I have kdx running over some time, the log message showing ""2023-05-14 21:25:41.058 [INF] PROT: Accepted block e042af0482bc5a7d2f8cff4afb997daf0e0e936a7a88039ed6fa19377032ac89 via relay 2023-05-14 21:25:41.095 [INF] PROT: Accepted block 1be3b5ee7c8447b92c58f614eca4bf3a7b274cede83e0a304dcc5002409699d7 via relay 2023-05-14 21:25:41.443 [INF] PROT: Accepted block 67b381634514eaa5a21a4e361b2415ab6b5829d2af71df8becedb8485e794e4b via relay 2023-05-14 21:25:43.970 [INF] CMGR: Connecting to [2402:800:6374:bd0b:24a4:91bc:fe96:2147]:16111 2023-05-14 21:25:44.384 [INF] BDAG: Processed 15 blocks and 0 headers in the last 10.86s (29 transactions, 2023-05-14 21:25:47.872 -0600 MDT) 2023-05-14 21:25:44.384 [INF] PROT: Accepted block 952998ed0fb430c15ea0cab3092b199e3879570c6dd39d13022d61784f4e0389 via relay" And I can see it connected to p2p address as well. I use kaspactl can use rpc port to query block information correctly. But from the KDX Kaspa tab, the status is always connecting. I tried to downgrade to v2.12.2, same thing.
To Reproduce Steps to reproduce the behavior:
Expected behavior After block syched, I should see connected, and number peers, DAG status, difficulty, etc.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context Add any other context about the problem here.