Topic: BiblePay - TestNet Thread - Pool Testing for Proof of Bible Hash Pool (PoBh) - page 10. (Read 13211 times)
August 17, 2017, 01:50:26 PM
i can't believe what i'm seing on this project. a new shitcoin in the making...well, good luck with this
August 17, 2017, 01:39:09 PM
What version must be used for pool mining?
August 17, 2017, 01:17:59 PM
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.
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.
August 17, 2017, 01:09:17 PM
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.
August 17, 2017, 01:06:14 PM
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.
August 17, 2017, 12:49:19 PM
So the project is in full swing? Are you forecast when it will be listed on coinmarketcap?
August 17, 2017, 12:29:45 PM
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.
August 17, 2017, 12:27:21 PM
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.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.
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.
August 17, 2017, 12:22:53 PM
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.
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.
August 17, 2017, 12:08:38 PM
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?
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.
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
}
{
"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?
August 17, 2017, 10:55:01 AM
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?
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.
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
}
{
"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.
August 17, 2017, 10:48:41 AM
I downloaded the Windows version, ran it with -testnet flag (I got green background) and immediately upon opening I found 7 blocks in 2 seconds, and now it says I am on block 7. 
Difficulty is 0.000279. I found a new chain somehow? I don't know how to access the test chain with 1248 blocks.
But after a few seconds mining stopped by itself and I couldn't restart it with setgenerate because I couldn't connect to the network.
Although I could do this in the Peers window:
https://i.imgur.com/WqnKJpg.png
I thought my client banned the main node, but after I restarted it, the ban came back, so it probably means my node is banned.
Also, these are the error messages from the debug.log, maybe they can help you:
Difficulty is 0.000279. I found a new chain somehow? I don't know how to access the test chain with 1248 blocks.But after a few seconds mining stopped by itself and I couldn't restart it with setgenerate because I couldn't connect to the network.
Although I could do this in the Peers window:
https://i.imgur.com/WqnKJpg.png
I thought my client banned the main node, but after I restarted it, the ban came back, so it probably means my node is banned.
Also, these are the error messages from the debug.log, maybe they can help you:
Code:
2017-08-17 14:00:07 ERROR: ContextualCheckBlockHeader : incorrect proof of work at 1226
2017-08-17 14:00:07 Misbehaving: 97.99.69.33:40001 (0 -> 100) BAN THRESHOLD EXCEEDED
2017-08-17 14:00:07 ERROR: invalid header received 00001d88f29397bee28457a5da46b5b729f9b581161e628d2000cf100e55ac72
2017-08-17 14:00:07 ProcessMessages(headers, 1945 bytes) FAILED peer=2
2017-08-17 14:00:07 Misbehaving: 97.99.69.33:40001 (0 -> 100) BAN THRESHOLD EXCEEDED
2017-08-17 14:00:07 ERROR: invalid header received 00001d88f29397bee28457a5da46b5b729f9b581161e628d2000cf100e55ac72
2017-08-17 14:00:07 ProcessMessages(headers, 1945 bytes) FAILED peer=2
Thanks, Yeah, testnet allows mining without peers and without a chain, so that part is good.
The node will reorganize anyway once it finds a longer chain.
I think the problem here is my testnet node was mining on the prior version and mined some blocks that are not allowed anymore and I never rebooted, therefore they were not checked again.
Ok, I deleted my chain on that node and restarted.
Could you please unban me and then restart again and lets see how far we get? It took me back to block 1009 (thats about 4 days ago when we were all poolmining in testnet).
August 17, 2017, 10:03:21 AM
I downloaded the Windows version, ran it with -testnet flag (I got green background) and immediately upon opening I found 7 blocks in 2 seconds, and now it says I am on block 7. Difficulty is 0.000279. I found a new chain somehow? I don't know how to access the test chain with 1248 blocks.
But after a few seconds mining stopped by itself and I couldn't restart it with setgenerate because I couldn't connect to the network.
Although I had the option to unban your main node in the Peers window:
I thought my client banned the main node, but after I restarted it, the ban came back, so it probably means my node is banned.
Also, these are the error messages from the debug.log, maybe they can help you:
Difficulty is 0.000279. I found a new chain somehow? I don't know how to access the test chain with 1248 blocks.But after a few seconds mining stopped by itself and I couldn't restart it with setgenerate because I couldn't connect to the network.
Although I had the option to unban your main node in the Peers window:
I thought my client banned the main node, but after I restarted it, the ban came back, so it probably means my node is banned.
Also, these are the error messages from the debug.log, maybe they can help you:
Code:
2017-08-17 14:00:07 ERROR: ContextualCheckBlockHeader : incorrect proof of work at 1226
2017-08-17 14:00:07 Misbehaving: 97.99.69.33:40001 (0 -> 100) BAN THRESHOLD EXCEEDED
2017-08-17 14:00:07 ERROR: invalid header received 00001d88f29397bee28457a5da46b5b729f9b581161e628d2000cf100e55ac72
2017-08-17 14:00:07 ProcessMessages(headers, 1945 bytes) FAILED peer=2
2017-08-17 14:00:07 Misbehaving: 97.99.69.33:40001 (0 -> 100) BAN THRESHOLD EXCEEDED
2017-08-17 14:00:07 ERROR: invalid header received 00001d88f29397bee28457a5da46b5b729f9b581161e628d2000cf100e55ac72
2017-08-17 14:00:07 ProcessMessages(headers, 1945 bytes) FAILED peer=2
August 17, 2017, 09:34:07 AM
1021c testers: I found two issues that will need fixed regardless in this version, so I had to push a commit.
If you are on linux, please get 1021d. If not please wait til the morning for the Windows release.
If you are on linux, please get 1021d. If not please wait til the morning for the Windows release.
Alright 1021d is now available for download on biblepay.org.
(Windows).
Please try to solomine against testnet; we are on block 1248.
I see part of the problem for us testing up til now: My external testnet node keeps banning anyone connecting to it on a prior version, since the diff adjustment has changed thereby banning every connection on the external IP. Let this be a lesson for me to increment the network minimum version (IE make it a mandatory for testnet) in the future.
For now lets try to deal with it and get past it - I will try to keep unbanning the peers unless it is impossible.
Let me know if anyone can mine on testnet past 1249.
August 16, 2017, 10:31:37 PM
1021c testers: I found two issues that will need fixed regardless in this version, so I had to push a commit.
If you are on linux, please get 1021d. If not please wait til the morning for the Windows release.
If you are on linux, please get 1021d. If not please wait til the morning for the Windows release.
August 16, 2017, 10:26:51 PM
i cant login on pool. everytime i clicked login it redirects me to login page. this was working last night
Just click logout-login. August 16, 2017, 10:12:56 PM
i cant login on pool. everytime i clicked login it redirects me to login page. this was working last night
August 16, 2017, 08:56:10 PM
Love the idea of Bibble pay hope dev it will great success for your project, i am looking closely how will evolve the development.
August 16, 2017, 08:54:10 PM
PS Btw guys, the windows version on biblepay.org is 1021c, so anyone can jump in and help on testnet now.
Tried doing a completely clean install of the 64-bit Windows release of 1021c, but it's still not working on testnet for me. Don't know if it'll help, but I uploaded the debug log to pastebin at https://pastebin.com/di2U3wMf
-edit-
Updated to a new pastebin debug log, since it started throwing a bunch of errors after I posted the first.
And I believe BBP was off the screen.
Ok, it does load in testnet mode for me from win64 bit.
Could you please try reloading now that I have the node up and let me know if it syncs to 1230+?
Then we can try mining a block. I just mined a few from Nix and a few from windows.
The errors in your log appear to be OK- its that same old occasional cannot create block; I will look at that. But it shouldnt affect our testing.
EDIT: PS, I see that two nodes were banned on the testnet external node; I just unbanned them.
August 16, 2017, 08:45:51 PM
PS Btw guys, the windows version on biblepay.org is 1021c, so anyone can jump in and help on testnet now.
Tried doing a completely clean install of the 64-bit Windows release of 1021c, but it's still not working on testnet for me. Don't know if it'll help, but I uploaded the debug log to pastebin at https://pastebin.com/di2U3wMf
-edit-
Updated to a new pastebin debug log, since it started throwing a bunch of errors after I posted the first.
Let me check this out for a while.
Jump to: