Re: [ANN] Blockle (BLK) – SHA-256, 15-Second Blocks, 1 000 000 000 Supply, 20 000 00

Quote from: Drawesome on Today at 01:52:38 AM

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

Code:

generatetoaddress 1 "my_blk1_address..."

while the wallet was locked returned

Code:

[ ]

immediately.

I unlocked the wallet using
Code:
```
walletpassphrase
```
(it returned
Code:
```
null
```
, indicating success).
Executing
Code:
```
generatetoaddress 1 "my_blk1_address..."
```
again with the wallet unlocked also returned
Code:
```
[ ]
```
immediately.
Interestingly, checking the debug.log shows a
Code:
```
CreateNewBlock()
```
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
Code:
```
setgenerate true 1
```
, but it returned the error
Code:
```
Method not found (code -32601)
```
Conclusion:
Based on these tests, it appears that CPU mining using the built-in console commands (
Code:
```
generatetoaddress
```
,
Code:
```
setgenerate
```
) is not functioning correctly in the Windows v1.3.0 build.
Code:
```
generatetoaddress
```
seems buggy (fails returning
Code:
```
[ ]
```
even though the log shows
Code:
```
CreateNewBlock
```
is executed), and
Code:
```
setgenerate
```
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
Code:
```
generatetoaddress
```
command?

Regards and best of luck with the Blockle project.

Hi there, thanks for the very detailed write-up and for helping us shake out these edge cases! A few things to clarify:

⸻

1) Why no new mainnet blocks?

Right now the only miners on mainnet are whoever runs external hashing hardware or pools—you won’t see your single-CPU attempts actually find a block at real-world difficulty (it’s astronomically unlikely). Until someone spins up a pool or runs enough hashpower, the chain will “stall” at block 2. That’s expected for a brand-new PoW network.

⸻

2) The console RPCs on Windows v1.3.0
   •   setgenerate was removed upstream in Bitcoin Core v0.21 (and we inherited that change).
   •   generatetoaddress on our mainnet build effectively becomes a no-op (it returns [] immediately) because block-on-demand is only enabled in RegTest mode. The fact that you see CreateNewBlock() in the log simply means the node built a template—it didn’t actually spin up a real hashing loop or solve the PoW.

TL;DR:
   •   On mainnet/testnet you must use an external miner (or pool) speaking the getblocktemplate / submitblock RPCs.
   •   On regtest, generatetoaddress N <addr> still works instantly (because difficulty is trivial).

⸻

3) How to CPU mine on mainnet/testnet
   1.   Point a miner (e.g. cgminer, cpuminer-opt, etc.) at your node’s RPC port:

miner --url http://rpcuser:rpcpass@127.0.0.1:9332 --user rpcuser --pass rpcpass

   2.   The miner will internally call getblocktemplate, do the work, then call submitblock when it finds a solution.

If you just want to experiment locally, you can start your node in regtest mode:

blockled -regtest
blockle-cli -regtest generatetoaddress 10 <your-regtest-address>

That will mine 10 blocks instantly.

⸻

Bottom line: what you saw in v1.3 on Windows is working as upstream-designed—there is no built-in CPU miner on mainnet, and generatetoaddress only really “mines” in regtest mode. I hope that clears things up, and thanks again for testing!