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

[bible_pay]

Yep, that'd be me. If there's anything specific you need included let me know. I should have some time this afternoon, I'll clean up the source a little and put it on github. It's trivial so you wouldn't have any trouble customizing the reports.

Well, I finally got around to doing that. The source code is at https://github.com/happy-merchant/biblepay_rpc

Just a warning, I'm a hobbyist programmer at best so it's probably not the greatest program ever, but if you just need to dump some block times it gets the job done. It uses BitcoinLib so it can easily access the generic data in the blocks, but it'd take a little effort to access the Biblepay-specific stuff.

Nice job- I was able to load it in vs2017.
I dont have bitcoinlib though, but I do have bitnetc#, and I can follow what you did, thats cool.
Ill keep it in case I need it.

[1713959695]

1713959695

[1713959695]

1713959695

[1713959695]

1713959695

[1713959695]

1713959695

[jaapgvk]

I've been mining on the testnet for a few days now. Seems to me that everything's going smoothly. Here are my stats:

{
  "blocks": 441,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 0.0002436484762696088,
  "errors": "",
  "genproclimit": 3,
  "networkhashps": 19361.95353484886,
  "hashps": 498.9153255443148,
  "minerstarttime": "08-25-2017 15:31:08",
  "ratio": 2,
  "hc1": 78714290,
  "bhc2": 157431656,
  "pooledtx": 0,
  "testnet": true,
  "chain": "test",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "miningpulse": 2791,
  "poolmining": false
}

If you need to test anything, just let me know

[bible_pay]

Thanks JaapG and Happy,

No, I dont have anything except I do want to compile a new windows version, and enable the pool again against testnet, and ensure the poolmining works in f7000.  Thats a huge test, as the entire pool would fail if we issued a mandatory and everyone went down at block 7000.  So let me get that done next and ask for help.

As far as the release, all we really need to do is put a ticket in at ccex, and ask them to shut us down before block 7000.  Then we give them as many days as they feel necessary to upgrade.  So I think what we should do is announce it around block 6200 or so.  Hopefully it wont interfere with Septembers auction.   Either way, that does not give us much time to finish testing here, so lets try to ramp up finalization on f7000 over the next 3 days.

And finally here is one paragraph I pasted earlier:
 Please be honest and open, is there anything that makes you nervous about f7000, or something that I need to triple check while tweaking the final pool settings? The latest code does include the readytomine backoff that shoud allow the pool to breathe much easier.

[bible_pay]

Alrighty guys here is what I need help with in testnet currently.
We only have one person in testnet (I think thats Happy).
We need a few pool testers.  Im looking at the current released version of f7000 (for download) and it is 1023.  That client is OK to test in testnet for today, as I primarily just need to test compatibility with the latest pool and the almost latest version of f7000.  The only unreleased feature in 1024 is the enhanced readytomine packet, and we dont need to test that today (that takes 12 hours for a release, and Ill be traveling).
So for now, please grab a linux or win 1023 build or higher, and set it to pool mine against testnet.

I set one box up so far and see myself in the leaderboard.  We also have to ensure the pool payments are correct in f7000, so we have to wait til we (pool) mine one in testnet.

Ill set up one more box against testnet in a few minutes.

Thanks.

 

[jaapgvk]

Alrighty guys here is what I need help with in testnet currently.
We only have one person in testnet (I think thats Happy).
We need a few pool testers.  Im looking at the current released version of f7000 (for download) and it is 1023.  That client is OK to test in testnet for today, as I primarily just need to test compatibility with the latest pool and the almost latest version of f7000.  The only unreleased feature in 1024 is the enhanced readytomine packet, and we dont need to test that today (that takes 12 hours for a release, and Ill be traveling).
So for now, please grab a linux or win 1023 build or higher, and set it to pool mine against testnet.

I set one box up so far and see myself in the leaderboard.  We also have to ensure the pool payments are correct in f7000, so we have to wait til we (pool) mine one in testnet.

Ill set up one more box against testnet in a few minutes.

Thanks.

 

It appears I can't connect to the testnet pool at the moment (1023):

{
  "blocks": 512,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 0.000495421334697053,
  "errors": "",
  "genproclimit": 1,
  "networkhashps": 38393.65118356409,
  "hashps": 388.0170883719339,
  "minerstarttime": "08-27-2017 21:50:31",
  "ratio": 1,
  "hc1": 294912,
  "bhc2": 589824,
  "pooledtx": 0,
  "testnet": true,
  "chain": "test",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "POOL DOWN-REVERTING TO SOLO MINING; POOL DOWN-REVERTING TO SOLO MINING; ",
  "miningpulse": 12,
  "poolmining": false
}


Conf:
poolport=80
pool=http://pool.biblepay.org
workerid=jaapvk_frotlaptop

[bible_pay]

Alrighty guys here is yself in the leaderboard.  We also have to ensure the pool payments are correct in f7000, so we have to wait til we (pool) mine one in testnet.

Ill set up one more box against testnet in a few minutes.

Thanks.

 

It appears I can't connect to the testnet pool at the moment (1023):

{
  "blocks": 512,
  "currentblocksize":
  "poolinfo2": "",
  "poolinfo3": "POOL DOWN-REVERTING TO SOLO MINING; POOL DOWN-REVERTING TO SOLO MINING; ",
  "miningpulse": 12,
  "poolmining": false
}


Conf:
poolport=80
pool=http://pool.biblepay.org
workerid=jaapvk_frotlaptop

Possibly try to copy your config up to your %appdata%\biblepaycore\biblepay.conf file
instead of the \testnet3 directory.

It is working for me on 2 machines.

If not, try to clone one of your working machines settings or create a new workerid?

[bible_pay]

The pool is getting pounded again.  I had to lower the max supported threadcount to 15 temporarily to give the server room to breathe.

Ill take a look at ways to upgrade the server tomorrow.  We will need to ask everyone to upgrade to the latest version also, as it contains more efficient pool communications.  More on that tomorrow.

[inblue]

The pool is getting pounded again.  I had to lower the max supported threadcount to 15 temporarily to give the server room to breathe.

To me it seems it doesn't have to do with that, because it's still inaccessible, even though all big miners have reverted to solo mining. So maybe a DoS attack?

[616westwarmoth]

The pool is getting pounded again.  I had to lower the max supported threadcount to 15 temporarily to give the server room to breathe.

Ill take a look at ways to upgrade the server tomorrow.  We will need to ask everyone to upgrade to the latest version also, as it contains more efficient pool communications.  More on that tomorrow.

If there are any Linux gurus lurking about, a easy to use pre-compiled (or easier to compile) Biblepay Wallet package would be a great selling point.

[inblue]

If there are any Linux gurus lurking about, a easy to use pre-compiled (or easier to compile) Biblepay Wallet package would be a great selling point.

Well, I have a compiled biblepayd on my Ubuntu 16.04 x64 and I'm willing to share it, but I have no idea if that's usable on any other system? I don't have biblepay-qt as I don't use it.

[bible_pay]

The pool is getting pounded again.  I had to lower the max supported threadcount to 15 temporarily to give the server room to breathe.

To me it seems it doesn't have to do with that, because it's still inaccessible, even though everyone has reverted to solo mining. So maybe a DoS attack?

Its slow because its getting hit with 400 requests per second right now, and I can actually see the record count per second.  It can handle about 250 or so and appear to be OK from the user perspective.

We need everyone to upgrade to 1023 until the next version is out.  If anyone is out tonight please upgrade to 1023- this is not the optimal version but its better than 1022 down for the pool.

[616westwarmoth]

If there are any Linux gurus lurking about, a easy to use pre-compiled (or easier to compile) Biblepay Wallet package would be a great selling point.

Well, I have a compiled biblepayd on my Ubuntu 16.04 x64 and I'm willing to share it, but I have no idea if that's usable on any other system? I don't have biblepay-qt as I don't use it.

I'm not sure what it takes to do a package on Ubuntu. I got a linux version running on 16.04 but I wasn't sure if there was a guru around that might be able to really do it justice (no offense at all intended to you).

[quocevil]

can i ask 1 question : what happen with tBiblepay coin. I run test and have 7.000.000 tbiblepay. Is that have value?

[bible_pay]

can i ask 1 question : what happen with tBiblepay coin. I run test and have 7.000.000 tbiblepay. Is that have value?

Hi,
No, the testnet coins are all worthless; just for testing.

[jaapgvk]

Possibly try to copy your config up to your %appdata%\biblepaycore\biblepay.conf file
instead of the \testnet3 directory.

It is working for me on 2 machines.

If not, try to clone one of your working machines settings or create a new workerid?

1. I misspelled my worker-id in the conf file :,)
2. When I corrected that, I still couldn't poolmine weirdly enough.
3. I deleted everything (incl my appdata biblepay folder) and did a fresh installation. i still couln't poolmine.
4. I copied the testnet3 folder from another miner, and now it's mining just fine

[jaapgvk]

Please be honest and open, is there anything that makes you nervous about f7000, or something that I need to triple check while tweaking the final pool settings? The latest code does include the readytomine backoff that shoud allow the pool to breathe much easier.

I saw your question earlier, but sadly I don't have enough knowledge to provide you with an in depth answer. All is going well in testnet as far as I can see, and I'll help you as best as I can, but that's all I can contribute at the moment

[tiras]

is it possible to use multiple machines to solo mine in a single wallet i.e. sort of combine hashpower ? 

[tiras]

is  the pool down atm?

[inblue]

is it possible to use multiple machines to solo mine in a single wallet i.e. sort of combine hashpower ? 

Yes, just copy the encrypted wallet.dat file to each machine. That way I only had the wallet running in the taskbar on my home PC (not mining) and I got notifications when one of the remote machines found a block.

[616westwarmoth]

I didn't know at first you could pool mine without copying the wallet.  However, I am glad I did, since anytime the pool goes down, you'll be mining to the same wallet solo.  The only potential downside is getting notifications on more than one machine of activity.  But I'd recommend that as a normal course of action.