ThunderChain stalls at 2 blocks despite following startup protocols #47
Description
Bug Description
ThunderChain is not progressing beyond 2 blocks even after following all official startup procedures as outlined in the Telegram group. The application consumes excessive system resources and fails to sync additional blocks.
⸻
Environment
• OS: Macos M1 air
⸻
Steps to Reproduce
1. Start ThunderChain and allow it to run for 10–30 minutes.
2. Close the application while not in the console tab.
3. Reopen ThunderChain.
4. Repeat the process with different runtime durations as instructed.
⸻
Expected Behavior
The node should sync progressively and add more blocks beyond the initial two.
⸻
Actual Behavior
The node starts from 0 blocks and stalls at 2 blocks indefinitely. No further syncing occurs, even after prolonged runtimes and multiple relaunch attempts.
⸻
Additional Information
• Console output logs are attached.
• ThunderChain shows high CPU and RAM usage in the Activity Monitor (screenshot attached).
• All recommended protocols from the Telegram group were followed precisely.
⸻
Attachments
• Console output logs
• Screenshot from Activity Monitor
⸻
console output after getting two blocks:
2025-04-08T22:38:08.914873Z WARN thunder::miner:105: confirm BMM: received new block without our BMM commitment side_hash=78c6415009e7256360f94f2376543d13fd14459dcd52cad32ca5f74c2908e415 main_height=107266 main_hash=000000ade9d5e0609dfb7617c94c182da0623a12eb999607f3b406df1f7d5efb bmm_commitment=none 2025-04-08T22:38:08.915751Z DEBUG thunder::miner:133: confirm BMM: verification failed block_hash=78c6415009e7256360f94f2376543d13fd14459dcd52cad32ca5f74c2908e415 2025-04-08T22:38:08.921766Z DEBUG thunder_app::app:69: finished wallet update
sometimes no blocks:
2025-04-08T22:35:59.691876Z ERROR thunder::node::net_task:907: Peer connection error addr=172.105.148.135:4009 err="Heartbeat timeout" 2025-04-08T22:35:59.692968Z INFO thunder::net:254: remove active peer: disconnected addr=172.105.148.135:4009 2025-04-08T22:35:59.693393Z WARN thunder::node::net_task:898: Connection to peer closed addr=172.105.148.135:4009
### console output when it was running in the activity monitor
