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

[bible_pay]

Updated to the last wallet, added a worked on the website, and added that worker along with the other info to the config file in the testnet3 folder. But when I do a getmininginfo it says poolmining false.

Possibly see if anything is in the log that is revealing?
Also verify the config is set both in biblepay.conf and in the \testnet3 dir:

pool=http://pool.biblepay.org
genproclimit=10
poolport=80
workerid=r15


SIDE NOTE:  poolport is not really required, client defaults 80.

[1713457612]

1713457612

[1713457612]

1713457612

[1713457612]

1713457612

[1713457612]

1713457612

[1713457612]

1713457612

[1713457612]

1713457612

[FlyingFish]

On a side note, please check your HPS per miner in the leaderboard, and let us know if it is off so we can improve the pool.
I see flyingfish has a miner2 that is about 610 hps- you are a great candidate to help us test this out, is that what your getmininginfo hps shows flyingfish?

Miner2 is in a VPS and it floats around 580 hps with 4 threads, so the hashrate reporting is correct on both miners.

Running "biblepay-qt.exe -testnet" loads the main .conf file instead of the settings in the /testnet3 folder, as i have set different miner on each .conf file, but i guess this doesn't affect the main pool.

[bible_pay]

I just release v1002 of the pool (the little green box has the version in it when you log on).

These changes have been made:

- The pool is now smart enough to scan the last ten blocks once per minute and pick up any mined block credited to the pool, and distribute out its earnings (into block_distribution).  This should technically fix the bug where the pool misses mined blocks.  It rewards 0 for the tithe blocks, obviously.

- The Withdraw page now has an immature balance and a balance, to prevent people from withdrawing immature mined coins.  The maturity time is 24 hours.

I had to clear the block_distribution table so we can start over with a new baseline.

[Slkp]

wallet in test not sync.

[bible_pay]

wallet in test not sync.

Try:
addnode=node.biblepay.org
Restart

[Slkp]

wallet in test not sync.

Try:
addnode=node.biblepay.org
Restart

this is useless.cant sync last 22 hours

[bible_pay]

I noticed we had 7 people poolmining against Prod (ie the main chain), and that reminded me to enable our HEALTH_DOWN feature.

It is now enabled in prod, so if you try to pool mine against prod you will see HEALTH_DOWN in the getmininginfo, in field #2.

[marte1982]

i have stop pool mining i wait for stable upgrade please...

[bible_pay]

i have stop pool mining i wait for stable upgrade please...

Everything looks good now- please provide details.

Also, we are in sync.

[FlyingFish]

http://pool.biblepay.org/ is down since you mentioned version v1002 (error 403)

Even on the testnet, i got this with getmininginfo a few minutes ago

"poolinfo1": "",
 "poolinfo2": "",
 "poolinfo3": "HEALTH_DOWN",
 "poolmining": false

Edit: At the moment looks OK

"poolinfo1": "http://pool.biblepay.org",
 "poolinfo2": "e5a422be-e5cb-4ed9-803e-4bcfa12206c4",
 "poolinfo3": "",
 "poolmining": true

1 connection only and on block 295 (testnet)

[marte1982]

hi dev...i have HEALTH_DOWN in the getmininginfo, in field #2....what is my problem?  can you help me?  i must change my file.conf?  + my uncorfirmed  pool  balance is 0...before was more 4800

[bible_pay]

http://pool.biblepay.org/ is down since you mentioned version v1002 (error 403)

Even on the testnet, i got this with getmininginfo a few minutes ago

"poolinfo1": "",
 "poolinfo2": "",
 "poolinfo3": "HEALTH_DOWN",
 "poolmining": false

Edit: At the moment looks OK

"poolinfo1": "http://pool.biblepay.org",
 "poolinfo2": "e5a422be-e5cb-4ed9-803e-4bcfa12206c4",
 "poolinfo3": "",
 "poolmining": true

1 connection only and on block 295 (testnet)

Hi Guys-

When I noticed the prod users mining against the pool I accidentally shut down the pool both TestNet and Main with HEALTH_DOWN.

It took me 10 minutes to fix the problem, so for a while it was busted, but everything is fixed now.


The block distributions are looking 100% accurate now since a couple hours ago.

[FlyingFish]

hi dev...i have HEALTH_DOWN in the getmininginfo, in field #2....what is my problem?  can you help me?  i must change my file.conf?

It means you are on the main chain.

Check the block count.

[marte1982]

wallet is sincro  is okk...but  {
  "blocks": 2144,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 0.001515689064373363,
  "errors": "",
  "genproclimit": 10,
  "network_khashps": 2812.859580438268,
  "hashps": 3812.064713273046,
  "minerstarttime": "08-07-2017 19:43:10",
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "HEALTH_DOWN",
  "poolmining": false
}
   

file conf

poolport=80
pool=http://pool.biblepay.org
workerid=rana666
gen=1
genproclimit=10
addnode=node.biblepay.org


+ balance pool  now is 0  ...before was more 4800

[bible_pay]

wallet is sincro  is okk...but  {
  "blocks": 2144,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 0.001515689064373363,
  "errors": "",
  "genproclimit": 10,
  "network_khashps": 2812.859580438268,
  "hashps": 3812.064713273046,
  "minerstarttime": "08-07-2017 19:43:10",
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "HEALTH_DOWN",
  "poolmining": false
}
   

file conf

poolport=80
pool=http://pool.biblepay.org
workerid=rana666
gen=1
genproclimit=10
addnode=node.biblepay.org


+ balance pool  now is 0  ...before was more 4800

You are mining against main chain

Start wallet in testnet mode

We currently have 299 blocks in testnet (not 2000)


Balance was updated to 0 when I found users mining against main chain, at that point I shut down MAIN and reset balances.

Try mining against testnet now.

[Slkp]

{
  "blocks": 301,
  "currentblocksize": 0,
  "currentblocktx": 0,
  "difficulty": 0.0003173418615508064,
  "errors": "",
  "genproclimit": 1,
  "network_khashps": 153.8013017058758,
  "hashps": 0,
  "minerstarttime": "1-1-1970 00:00:00",
  "pooledtx": 0,
  "testnet": true,
  "chain": "test",
  "biblepay-generate": false,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "poolmining": false
}
this is right info or not?

[marte1982]

sorry dev..bat what is file conf.  for testnet?  thanks for your support

[bible_pay]

{
  "blocks": 301,
  "currentblocksize": 0,
  "currentblocktx": 0,
  "difficulty": 0.0003173418615508064,
  "errors": "",
  "genproclimit": 1,
  "network_khashps": 153.8013017058758,
  "hashps": 0,
  "minerstarttime": "1-1-1970 00:00:00",
  "pooledtx": 0,
  "testnet": true,
  "chain": "test",
  "biblepay-generate": false,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "poolmining": false
}
this is right info or not?

Yes, and I apologize, I accidentally shut the GUI down for about 30 mins earlier without realizing, looks like everything is up now, now Im going to just let it run for a few hours and see how everyones hash distribution turns out in block_distribution.

[bible_pay]

sorry dev..bat what is file conf.  for testnet?  thanks for your support

You basically have to create the biblepay.conf in the root (where the blocks file is) and clone it into the \testnet3 folder.

Then start qt like this:

biblepay-qt -testnet

Then ensure you have a green background when you boot, and that it is mining against the pool (with getmininginfo).

[bible_pay]

Btw guys, to show everyone the pool is 100% honest, I added a command to the RPC to allow people to audit the pool:

if you type 'run subsidy blockheight', it will show the payee address and subsidy.  The pools address will be clearly seen and repeating block to block and will also be in the About page of the pool.

So, people can easily see the pool has every block its been paid in its block_distribution report.

Im going to run the pool free of fees to get us started.

I might add a 'tithe' % later when we get close to opensource it - something like a mixture of tithe% and poolfee% (thats for people who run pools in the future, to customize the fees).