Hello Blockle team (OP) and community,
Thanks for the announcement, the project looks interesting. I've been testing Blockle shortly after launch using the pre-compiled Windows wallet (version
v1.3.0.0-g7ff64311...) available from the
Blocklechain/Windows-Wallet GitHub repository, running on Windows 10 x64.
I wanted to share my initial experience, especially regarding attempts at CPU mining, in case it's helpful as feedback or for other users:
1. Sync and Network Status:The wallet synced quickly to block 2, which matches the official explorer found at
https://explorer.blockle.org/ . However, both my node and the explorer seem to indicate that the last block (block #2) was mined quite some time ago (over 17 hours at the time of my testing). My node successfully connects to peers (I had 2 active connections), and the
debug.log file shows messages like '
Potential stale tip detected', indicating it's aware of the lack of new blocks.
2. CPU Mining Attempt (Console):I attempted to mine using the CPU via the Debug Console within the
blockle-qt.exe wallet:
- Generating a receiving address worked correctly after restarting the wallet.
- I encrypted the wallet for security.
- Executing
generatetoaddress 1 "my_blk1_address..."
while the wallet was locked returned
immediately.
- I unlocked the wallet using (it returned , indicating success).
- Executing
generatetoaddress 1 "my_blk1_address..."
again with the wallet unlocked also returned immediately.
- Interestingly, checking the debug.log shows a entry matching the exact time of this second attempt[/b], suggesting the node does prepare the block template, but the RPC command fails or terminates before initiating the mining process.
- I tried the alternative command , but it returned the error
Method not found (code -32601)
, indicating this command has been removed in this version.
Conclusion:
Based on these tests, it appears that CPU mining using the built-in console commands (, ) is not functioning correctly in the Windows v1.3.0 build. seems buggy (fails returning even though the log shows is executed), and no longer exists.
Additionally, the observation that the main network seems stalled at block 2 for many hours is also worth noting.
I hope this detailed information is helpful to the team and community. Is this a known issue with the Windows build or the command?
Regards and best of luck with the Blockle project.