Post
Topic
Board Announcements (Altcoins)
Re: BiblePay | 10% Charity | POW/POBH CPU Mining *novel* | Sanctuaries
by
bible_pay
on 05/07/2019, 02:02:05 UTC
wallet running on win 10 64bit

I have this in my wallet configuration

addnode=explorer.biblepay.org
genproclimit=256
gen=1
minersleep=0

but my cpu is only using 10-25% and genproclimit is still 1..  i tried several values.. like 4, 16..  restart pc after but no efffect. Whats wrong?

getinfomining...
blocks": 129551,
  "currentblocksize": 1502,
  "currentblocktx": 1,
  "difficulty": 2070.207305034551,
  "errors": "",
  "pooledtx": 0,
  "chain": "main",
  "genproclimit": 1,
  "networkhashps": 383570.8021583835,
  "hashps": 756.1588006589133,
  "minerstarttime": "07-04-2019 00:23:29",
  "hashcounter": 35825303,
  "pooledtx": 0,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "abninfo": "",
  "gsc_errors": "",
  "poolmining": false,
  "pool_url": "",
  "required_abn_weight": 100000


When I attempted to set my miner to genproclimit 60+ it gave constant warnings that 60 was the highest it could go.
I don't know if that's the case anymore since I've then figured out how to to set the appropriate threads (I use 7 for 7 threads, 8 puts my CPU at 100% and locks it up.) Intel core i7, 4790k, quad core w/ 8 threads.

Other than verifying you are synced with this same chain hash:
https://chainz.cryptoid.info/bbp/
(As that would make you go to 99% error ratios on the pool if you are out of sync)

Could you also post your 'exec getabnweight 100000' results?

The pool also requires you to have unspent ABN weight for each new block created.

Thanks.

PS I see you already have minersleep=0, so like JSheets said, double check the biblepay.conf is in the same directory as your last timestamp modified debug.log.  If that wasn't it we can work through the getabnweight, to see if your miner is stopping and starting.  You can restart your miner with 'setgenerate true 5' and quickly look at getmininginfo for errors.  (Or check your log for errors).