BiblePay - TestNet Thread - Pool Testing for Proof of Bible Hash Pool (PoBh)

[inblue]

OK, now I'm also on 1009, but for some reason in some parts of the interface it shows 994 (hover over progress bar and in the information window).

But I can't mine, it says hashps is 0 and there is no activity on my CPU. Maybe because it still says synchronizing and 4 days behind?

Code:

getmininginfo
{
  "blocks": 1009,
  "currentblocksize": 0,
  "currentblocktx": 0,
  "difficulty": 0.0007747477227062956,
  "errors": "",
  "genproclimit": 12,
  "networkhashps": 7733395.331874545,
  "hashps": 0,
  "minerstarttime": "08-17-2017 14:49:57",
  "ratio": 0,
  "hc1": 0,
  "bhc2": 0,
  "pooledtx": 0,
  "testnet": true,
  "chain": "test",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "miningpulse": 0,
  "poolmining": false
}

Btw, I think you should put the letter after the version number in the About window, because now I'm not sure if I'm running the correct version of 1.0.2.1. The setup .exe file also only shows 1.0.2.1.

[1715028194]

1715028194

[1715028194]

1715028194

[1715028194]

1715028194

[1715028194]

1715028194

[bible_pay]

OK, now I'm also on 1009, but for some reason in some parts of the interface it shows 994 (hover over progress bar and in the information window).

But I can't mine, it says hashps is 0 and there is no activity on my CPU. Maybe because it still says synchronizing and 4 days behind?

Code:

getmininginfo
{
  "blocks": 1009,
  "currentblocksize": 0,
  "currentblocktx": 0,
  "difficulty": 0.0007747477227062956,
  "errors": "",
  "genproclimit": 12,
  "networkhashps": 7733395.331874545,
  "hashps": 0,
  "minerstarttime": "08-17-2017 14:49:57",
  "ratio": 0,
  "hc1": 0,
  "bhc2": 0,
  "pooledtx": 0,
  "testnet": true,
  "chain": "test",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "miningpulse": 0,
  "poolmining": false
}

Btw, I think you should put the letter after the version number in the About window, because now I'm not sure if I'm running the correct version of 1.0.2.1. The setup .exe file also only shows 1.0.2.1.

Yeah, I agree we need to know the distinct version.  Even on minor upgrades, I think Ill increment the version during the next build.

So, I had some issues over here while reindexing, and found a bug in BBP in our reindex routine, which is fixed but is unfortunately in your version, but we have a way to get around it.  I pruned the blocks 1225+ out of the chain, reindexed with the unreleased version, and restarted again.

Could you now please try unbanning me and restarting yet again and see if you sync to 1225 now?

[inblue]

OK, synced now. But something strange is happening. First it started to mine, using too much of my CPU (100%, computer barely responding), but showing a very small hash rate (about tenth of what I normally have - 15k instead of 150k). Then after 2 minutes, it completely stopped without me doing anything - getgenerate / biblepay-generate was still true but hashps was 0. Then after 2 more minutes it just started mining again on its own. Again 100% CPU.

Then I tried to lower genproclimit, but that did nothing, CPU still on 100%. Finally, hashps showed 0 again, but this time CPU was still at 100% and I couldn't stop it, like it was stuck, so I quit the client. And sometime in between I found one block. No errors in debug.log except two stale block errors.

[bible_pay]

OK, synced now. But something strange is happening. First it started to mine, using too much of my CPU (100%, computer barely responding), but showing a very small hash rate (about tenth of what I normally have - 15k instead of 150k). Then after 2 minutes, it completely stopped without me doing anything - getgenerate / biblepay-generate was still true but hashps was 0. Then after 2 more minutes it just started mining again on its own. Again 100% CPU.

Then I tried to lower genproclimit, but that did nothing, CPU still on 100%. Finally, hashps showed 0 again, but this time CPU was still at 100% and I couldn't stop it, like it was stuck, so I quit the client. And sometime in between I found one block. No errors in debug.log except two stale block errors.

Good deal,  all these things 'should' (lol) be explainable.
The bad blocks at the end of the chain-> my issue, since I had a rogue version mine a few with DGW parameters that were non-allowable.
The re-index-> an unintended or inherited bug (will be fixed in the next version).
The jerky mining-> Ensure you have in your master biblepay.conf (even though we are in testnet, modify the main one in \biblepaycore) to not do any pool mining by putting an x in front of pool (ie xpool).
Ensure setgenerate is pretty low, since we are using a new hashing algo in testnet (ie setgenerate 5).

So I finally see the nodes in my peers list are not being kicked off.  I realize we will have a few problems with this build, but it should shed light on what needs adjusted.

As far as the khashps being lower, the 100% biblepay algo is about 50-80% slower than the algo in prod (because there are no x11 hashes involved).

Let me grab a few blockhashes and see if we match.

[bible_pay]

11:28:11

showblock 1242


11:28:11

{
  "hash": "d988e253ce99a1228feb909a10ed4c53225f01c97f4b0ad3e8307ee27eaf0362",
  "confirmations": 1,
  "size": 1311,
  "height": 1242,
 
  "difficulty": 0.6529178808936711,
 
  "biblehash": "0000000007f5a4995e2e8587091a8cfce91f6acb8327b19f5c07bdab3ca7a5e3",
  "prayers": ""
}


Does your 1242 blockhash and diff agree, btw?


Let me know if you can mine a block also.

Diff should be very easy to mine one.

[luksbit]

So the project is in full swing? Are you forecast when it will be listed on coinmarketcap?

[bible_pay]

So the project is in full swing? Are you forecast when it will be listed on coinmarketcap?

Yeah, we have not hit any severe snags yet.  Im in no hurry as I dont think we are greed based, but I mentioned on the main thread anyone is welcome to reach out to coinmarketcap to have us listed.

[inblue]

Does your 1242 blockhash and diff agree, btw?

Yes, I have the same hash for block 1242.

But I have more strange things happening now. I restarted the client and it says block source not available and will not sync, even though it has one connection to your node (and I checked that it's not banned).

I didn't know what to do, so I tried to rebuild the index (the option from the wallet repair tab) and now the wallet won't start at all, the splash screen shows "Activating best chain..." and then it dies.

Btw, @bible_pay: Last post from luksbit got me thinking - do you think this forum topic should be in the announcements category? Because its purpose is testing buggy things, not to be a main topic for this coin for people to randomly find in the ann category. And maybe you should put the link to it in the OP of the main topic.

[inblue]

OK, I deleted testnet3 folder and now it's working again.

hashps was 0 for the first minute of mining, then it updated. Now after two blocks difficulty shows around 26 in qt or 2.6 in console.

[Duchess]

What version must be used for pool mining?

[majestymage]

i can't believe what i'm seing on this project. a new shitcoin in the making...well, good luck with this

[bible_pay]

Does your 1242 blockhash and diff agree, btw?

Yes, I have the same hash for block 1242.

But I have more strange things happening now. I restarted the client and it says block source not available and will not sync, even though it has one connection to your node (and I checked that it's not banned).

I didn't know what to do, so I tried to rebuild the index (the option from the wallet repair tab) and now the wallet won't start at all, the splash screen shows "Activating best chain..." and then it dies.

Btw, @bible_pay: Last post from luksbit got me thinking - do you think this forum topic should be in the announcements category? Because its purpose is testing buggy things, not to be a main topic for this coin for people to randomly find in the ann category. And maybe you should put the link to it in the OP of the main topic.

On the topic location, I dont have permissions to create subtopics yet, or to move topics.  I originally tried to make it a subtopic of Biblepay but couldnt.  (We have a dedicated forum on a private server already, but I dont want to enable it until we hit 1000 users).  Ill notify the mod to move it.

[happy_merchant]

Testnet's working fine for me now. Currently on block 1246 and solo mining.

[bible_pay]

Testnet's working fine for me now. Currently on block 1246 and solo mining.

10-4 to Happy and Inblue.
So lets let it run for a little while so we can get a feel for block times and diff changes.
Id like to ensure the block retarget still gives us 7 minute block times, and the diff doesnt rise in testnet.

The version we are testing has x-11 completely removed, except for the single hash required to store the block in the blockindex.  To see the ratio of hashes, you will see in getmininginfo the biblehash is now equal to the x11 hash. 

As happy said, that prevents any funny business with offloading x11, as the overhead to channel its value is more than the work required to solve it.

[NoxX]

So pool mining seems to be working fine, but is there a way to limit the CPU threads? Using all threads 100% makes my PC a bit sluggish... 

[inblue]

So pool mining seems to be working fine, but is there a way to limit the CPU threads? Using all threads 100% makes my PC a bit sluggish...  

Just put genproclimit=X (X being the number of threads) in your biblepay.conf, and you can experiment until you get the desired value by typing setgenerate true X in the console.

[bible_pay]

As far as testing in testnet, I see without the x11 component, a few changes need to be made to the diff algorithm (DGW).  In addition to that, the outer loop of the miner needs to be made a little more professional, since it technically wont need to be there in the next version.

I propose that we erase the testnet blocks, fix the outer loop, recreate a new windows version and test together from block 1.  This will give us a more accurate representation of how the difficulty will work, how the hashps will behave in prod after the cutover of the mandatory, and how the subsidy will pay.

Im working on this now, will notify when the new release is ready.

[NoxX]

So pool mining seems to be working fine, but is there a way to limit the CPU threads? Using all threads 100% makes my PC a bit sluggish...  

Just put genproclimit=X (X being the number of threads) in your biblepay.conf, and you can experiment until you get the desired value by typing setgenerate true X in the console.

Ah great, thank you! genproclimit=8 seems to do the trick for me.

Is the pool website down now? I can't login anymore, it worked a few minutes ago, but not anymore...

[inblue]

Is the pool website down now? I can't login anymore, it worked a few minutes ago, but not anymore...

Click logout then login again.

[NoxX]

Is the pool website down now? I can't login anymore, it worked a few minutes ago, but not anymore...

Click logout then login again.

Thanks again