Quote from: kahir on January 16, 2017, 11:02:28 AM

how can i know my hashrate and the network hashrate ... also controlling the number of cores mining

Hi, you can change the number of threads in config.txt, that should roughly correspond to the number of cores.

I haven't paid much attention to the concept of hashrate so far, haven't found a use for it yet. However, I'll see if I can add it to the miner as an informative measure. We are using the concept of timestamp when creating new blocks, instead of nonce. We we might be resistant to ASIC by design, because nonce is random, but timestamp follows certain rules.

Network hashrate would then be derived from block speed propagation, average timestamps and difficulty.

EDIT: hashrate (rough estimate) code added for the next release:

Code:

2017-01-16 14:14:45,151 miner(100) Mining, 1 cycles passed in thread 1, difficulty: 33.8821780934, combined hashrate: estimating KH/s
2017-01-16 14:14:49,216 miner(100) Mining, 200 cycles passed in thread 1, difficulty: 33.8821780934, combined hashrate: 15.0001049042 KH/s
2017-01-16 14:14:53,160 miner(100) Mining, 400 cycles passed in thread 1, difficulty: 33.8821780934, combined hashrate: 13.0000114441 KH/s
2017-01-16 14:14:57,013 miner(100) Mining, 600 cycles passed in thread 1, difficulty: 33.8821780934, combined hashrate: 16.0000324249 KH/s
2017-01-16 14:15:00,753 miner(100) Mining, 800 cycles passed in thread 1, difficulty: 33.8821780934, combined hashrate: 16.9999599457 KH/s
2017-01-16 14:15:04,480 miner(100) Mining, 1000 cycles passed in thread 1, difficulty: 33.8821780934, combined hashrate: 13.0000114441 KH/s
2017-01-16 14:15:07,951 miner(100) Mining, 1200 cycles passed in thread 1, difficulty: 33.8821780934, combined hashrate: 16.0000324249 KH/s

https://github.com/hclivess/Bismuth/commit/0f5fd15d3f56080899a9328148cd81d060f4cf40