BiblePay - New Coin Launch - Official Thread

[togoshigekata]

Upgraded to new 1.0.3.5 and tested the new build with linux miners, the miners are still dropping off from the pool as before .
I'm pretty much running a recursive command as inblue does since yesterday.

Code:

while [1]; do ./biblepayd -daemon && sleep 1300 && ./biblepay-cli stop && sleep 15; done

Hmm, Im not sure if I agree with this; when I debugged yesterday, it was definitely the cache, and after 1035 the miner is definitely re-reporting every 6 mins; before the problem, my Vultr Nix box was dropping, After upgrade is not dropping; vultr nix log info showing it is working.

Could you please try the latest version again without your script?

My linux miner has been working great now since upgrading to 1.0.3.5 yesterday, doesnt get kicked off the pool anymore

[svirusxxx2]

Can someone explain to me what the "genproclimit" number is and how it works. I know the higher it goes the more processing power you use in turn generating more coin. but the other day i was running it at 15 and now i can't run it over 8. is there a reason for that?

after F7000 (7000 block) there is new algorithm.
this is explained by bible_pay few page ago.

genproclimit - mean how many thread run for mining
in most coin this should be set to number of logical cpu units in your hardware (ie. if you have core i5 , the you have 2 cores and with HT you have 4 threads , so genproclimit set to 4).

in biblepay this is most complicated
just try incrementing from 1 and check when it's best result
wait few minutes between test.

[slovakia]

still dont understand that my 2CORE/4HT G4560 is same like my RYZEN 1700 8CORE/16HT    gpuproclimit setup 2CORE= 8 and RYZEN =16   hash same ca. 8500 

[tiras]

still dont understand that my 2CORE/4HT G4560 is same like my RYZEN 1700 8CORE/16HT    gpuproclimit setup 2CORE= 8 and RYZEN =16   hash same ca. 8500 

switch to linux

[togoshigekata]

When will be available the wallet c-cex.com??? I wrote "Maintenance..."

C-CEX is waiting for us to give them green light to upgrade.

I want to ensure the ReadBlockFromDisk error is Dead before I green light them.

Overnight, I made an update internally to the pool server with new code.  Now I am burning it in.  
We will have to wait until I have time to parse the logs and ensure the error is dead.

Looks like you can still trade BBP on C-Cex: https://c-cex.com/?p=bbp-btc
But you can't withdraw or deposit BBP, so thats cool I didnt know maintenance mode meant you could still trade

[tiras]

When will be available the wallet c-cex.com??? I wrote "Maintenance..."

C-CEX is waiting for us to give them green light to upgrade.

I want to ensure the ReadBlockFromDisk error is Dead before I green light them.

Overnight, I made an update internally to the pool server with new code.  Now I am burning it in.  
We will have to wait until I have time to parse the logs and ensure the error is dead.

Looks like you can still trade BBP on C-Cex: https://c-cex.com/?p=bbp-btc
But you can't withdraw or deposit BBP, so thats cool I didnt know maintenance mode meant you could still trade

i recon price will drop after they unblock the wallet on c-cex .  a lot  of farm dumpers are waiting

[PhaseshiftUK]

When will be available the wallet c-cex.com??? I wrote "Maintenance..."

C-CEX is waiting for us to give them green light to upgrade.

I want to ensure the ReadBlockFromDisk error is Dead before I green light them.

Overnight, I made an update internally to the pool server with new code.  Now I am burning it in. 
We will have to wait until I have time to parse the logs and ensure the error is dead.

Unfortunately I'm still seeing them in the log:

$ grep ReadBlockFromDisk .biblepaycore/debug.log
2017-09-15 11:25:38 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3367325)ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 7728.000000 pindexPrev 10c6e6494f851852a84d7b424d9f6a49d495641ebf2c295ab968a945360304d1
2017-09-15 11:25:38 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3367533)UpdateTip: new best=610dfee89fba5d159dda3220ccd13bd34e7d4d61ecf30f748078a3c5c9a19fc9  height=7730  log2_work=50.41704  tx=11888  date=2017-09-15 11:25:28 progress=0.999999  cache=0.0MiB(192tx)
2017-09-15 12:09:39 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3367930)UpdateTip: new best=7979ac51d3e5863b78ad97bf10f27d9abb02595c6645c4993eec1eb9f3900b4a  height=7733  log2_work=50.43361  tx=11897  date=2017-09-15 12:09:29 progress=0.999999  cache=0.0MiB(207tx)
2017-09-15 14:32:38 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3384546)UpdateTip: new best=bacafa8b5f5c929807fc3017dc41d38309d60de986263120e650e5ca666abdf6  height=7745  log2_work=50.509954  tx=11920  date=2017-09-15 14:32:32 progress=0.999999  cache=0.0MiB(14tx)
2017-09-15 14:33:55 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3384546)UpdateTip: new best=e3f5a72080b15fffa2ebd24d0533972104799f6cd9521b15f49f391512634a0c  height=7746  log2_work=50.511569  tx=11921  date=2017-09-15 14:33:43 progress=0.999999  cache=0.0MiB(15tx)
2017-09-15 15:05:55 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3388192)UpdateTip: new best=68c4363a9102ae032eb12689f037a3b0844a38b89b6d200352b08ec7166432e9  height=7751  log2_work=50.530253  tx=11932  date=2017-09-15 15:05:45 progress=0.999999  cache=0.0MiB(23tx)
2017-09-15 15:51:57 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3390493)UpdateTip: new best=e1be025e9a1598121946284d0ba6da66884a7d679f3de9a85645d93d183fb4c9  height=7755  log2_work=50.555212  tx=11940  date=2017-09-15 15:51:04 progress=0.999995  cache=0.0MiB(11tx)
2017-09-15 16:38:39 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3394676)UpdateTip: new best=625ed5a4e6ed12276e23f2a20c4fd728f0959a656f24922025c1a6dc17dc9a8b  height=7758  log2_work=50.569175  tx=11951  date=2017-09-15 16:38:34 progress=1.000000  cache=0.0MiB(13tx)

[616westwarmoth]

Can someone explain to me what the "genproclimit" number is and how it works. I know the higher it goes the more processing power you use in turn generating more coin. but the other day i was running it at 15 and now i can't run it over 8. is there a reason for that?

after F7000 (7000 block) there is new algorithm.
this is explained by bible_pay few page ago.

genproclimit - mean how many thread run for mining
in most coin this should be set to number of logical cpu units in your hardware (ie. if you have core i5 , the you have 2 cores and with HT you have 4 threads , so genproclimit set to 4).

in biblepay this is most complicated
just try incrementing from 1 and check when it's best result
wait few minutes between test.

I test in multiples of the actual cores first, so with the i5, I'd test 2, then 4 then 6 then 8.  Once you start to see system issues or a drop in KhS, start moving forward and back by 1, then test those settings for 15 minutes or better.

[togoshigekata]

When will be available the wallet c-cex.com??? I wrote "Maintenance..."

C-CEX is waiting for us to give them green light to upgrade.

I want to ensure the ReadBlockFromDisk error is Dead before I green light them.

Overnight, I made an update internally to the pool server with new code.  Now I am burning it in. 
We will have to wait until I have time to parse the logs and ensure the error is dead.

Unfortunately I'm still seeing them in the log:

$ grep ReadBlockFromDisk .biblepaycore/debug.log
2017-09-15 11:25:38 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3367325)ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 7728.000000 pindexPrev 10c6e6494f851852a84d7b424d9f6a49d495641ebf2c295ab968a945360304d1
2017-09-15 11:25:38 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3367533)UpdateTip: new best=610dfee89fba5d159dda3220ccd13bd34e7d4d61ecf30f748078a3c5c9a19fc9  height=7730  log2_work=50.41704  tx=11888  date=2017-09-15 11:25:28 progress=0.999999  cache=0.0MiB(192tx)
2017-09-15 12:09:39 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3367930)UpdateTip: new best=7979ac51d3e5863b78ad97bf10f27d9abb02595c6645c4993eec1eb9f3900b4a  height=7733  log2_work=50.43361  tx=11897  date=2017-09-15 12:09:29 progress=0.999999  cache=0.0MiB(207tx)
2017-09-15 14:32:38 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3384546)UpdateTip: new best=bacafa8b5f5c929807fc3017dc41d38309d60de986263120e650e5ca666abdf6  height=7745  log2_work=50.509954  tx=11920  date=2017-09-15 14:32:32 progress=0.999999  cache=0.0MiB(14tx)
2017-09-15 14:33:55 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3384546)UpdateTip: new best=e3f5a72080b15fffa2ebd24d0533972104799f6cd9521b15f49f391512634a0c  height=7746  log2_work=50.511569  tx=11921  date=2017-09-15 14:33:43 progress=0.999999  cache=0.0MiB(15tx)
2017-09-15 15:05:55 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3388192)UpdateTip: new best=68c4363a9102ae032eb12689f037a3b0844a38b89b6d200352b08ec7166432e9  height=7751  log2_work=50.530253  tx=11932  date=2017-09-15 15:05:45 progress=0.999999  cache=0.0MiB(23tx)
2017-09-15 15:51:57 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3390493)UpdateTip: new best=e1be025e9a1598121946284d0ba6da66884a7d679f3de9a85645d93d183fb4c9  height=7755  log2_work=50.555212  tx=11940  date=2017-09-15 15:51:04 progress=0.999995  cache=0.0MiB(11tx)
2017-09-15 16:38:39 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3394676)UpdateTip: new best=625ed5a4e6ed12276e23f2a20c4fd728f0959a656f24922025c1a6dc17dc9a8b  height=7758  log2_work=50.569175  tx=11951  date=2017-09-15 16:38:34 progress=1.000000  cache=0.0MiB(13tx)

What version are you using?

Looks like dev commited version 1.0.3.5b 14 hours ago, which has potential fix for readblock error
https://github.com/biblepay/biblepay/commits/master

[tiras]

When will be available the wallet c-cex.com??? I wrote "Maintenance..."

C-CEX is waiting for us to give them green light to upgrade.

I want to ensure the ReadBlockFromDisk error is Dead before I green light them.

Overnight, I made an update internally to the pool server with new code.  Now I am burning it in. 
We will have to wait until I have time to parse the logs and ensure the error is dead.

Unfortunately I'm still seeing them in the log:

$ grep ReadBlockFromDisk .biblepaycore/debug.log
2017-09-15 11:25:38 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3367325)ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 7728.000000 pindexPrev 10c6e6494f851852a84d7b424d9f6a49d495641ebf2c295ab968a945360304d1
2017-09-15 11:25:38 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3367533)UpdateTip: new best=610dfee89fba5d159dda3220ccd13bd34e7d4d61ecf30f748078a3c5c9a19fc9  height=7730  log2_work=50.41704  tx=11888  date=2017-09-15 11:25:28 progress=0.999999  cache=0.0MiB(192tx)
2017-09-15 12:09:39 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3367930)UpdateTip: new best=7979ac51d3e5863b78ad97bf10f27d9abb02595c6645c4993eec1eb9f3900b4a  height=7733  log2_work=50.43361  tx=11897  date=2017-09-15 12:09:29 progress=0.999999  cache=0.0MiB(207tx)
2017-09-15 14:32:38 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3384546)UpdateTip: new best=bacafa8b5f5c929807fc3017dc41d38309d60de986263120e650e5ca666abdf6  height=7745  log2_work=50.509954  tx=11920  date=2017-09-15 14:32:32 progress=0.999999  cache=0.0MiB(14tx)
2017-09-15 14:33:55 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3384546)UpdateTip: new best=e3f5a72080b15fffa2ebd24d0533972104799f6cd9521b15f49f391512634a0c  height=7746  log2_work=50.511569  tx=11921  date=2017-09-15 14:33:43 progress=0.999999  cache=0.0MiB(15tx)
2017-09-15 15:05:55 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3388192)UpdateTip: new best=68c4363a9102ae032eb12689f037a3b0844a38b89b6d200352b08ec7166432e9  height=7751  log2_work=50.530253  tx=11932  date=2017-09-15 15:05:45 progress=0.999999  cache=0.0MiB(23tx)
2017-09-15 15:51:57 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3390493)UpdateTip: new best=e1be025e9a1598121946284d0ba6da66884a7d679f3de9a85645d93d183fb4c9  height=7755  log2_work=50.555212  tx=11940  date=2017-09-15 15:51:04 progress=0.999995  cache=0.0MiB(11tx)
2017-09-15 16:38:39 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3394676)UpdateTip: new best=625ed5a4e6ed12276e23f2a20c4fd728f0959a656f24922025c1a6dc17dc9a8b  height=7758  log2_work=50.569175  tx=11951  date=2017-09-15 16:38:34 progress=1.000000  cache=0.0MiB(13tx)

What version are you using?

Looks like dev commited version 1.0.3.5b 14 hours ago, which has potential fix for readblock error
https://github.com/biblepay/biblepay/commits/master

strange ...
I've upgraded it on linux just 2 hours ago and it shows  "wallet_fullversion": "1.0.3.5",     although in git v1.0.3.5.b was commited 15 hours ago

[PhaseshiftUK]

When will be available the wallet c-cex.com??? I wrote "Maintenance..."

C-CEX is waiting for us to give them green light to upgrade.

I want to ensure the ReadBlockFromDisk error is Dead before I green light them.

Overnight, I made an update internally to the pool server with new code.  Now I am burning it in.  
We will have to wait until I have time to parse the logs and ensure the error is dead.

Unfortunately I'm still seeing them in the log:
<snip>

What version are you using?

Looks like dev commited version 1.0.3.5b 14 hours ago, which has potential fix for readblock error
https://github.com/biblepay/biblepay/commits/master

I think I have the latest version - I downloaded and compiled it on my Linux box this morning (UK time).  From the debug.log:

2017-09-15 17:20:35 Biblepay Core version 1.0.3.5 (2017-09-14 21:46:42 -0500)

[tiras]

When will be available the wallet c-cex.com??? I wrote "Maintenance..."

C-CEX is waiting for us to give them green light to upgrade.

I want to ensure the ReadBlockFromDisk error is Dead before I green light them.

Overnight, I made an update internally to the pool server with new code.  Now I am burning it in.  
We will have to wait until I have time to parse the logs and ensure the error is dead.

Unfortunately I'm still seeing them in the log:
<snip>

What version are you using?

Looks like dev commited version 1.0.3.5b 14 hours ago, which has potential fix for readblock error
https://github.com/biblepay/biblepay/commits/master

I think I have the latest version - I downloaded and compiled it on my Linux box this morning (UK time).  From the debug.log:

2017-09-15 17:20:35 Biblepay Core version 1.0.3.5 (2017-09-14 21:46:42 -0500)

I'm getting  "POOL DOWN-REVERTING TO SOLO MINING;"   on 1.0.3.5b linux miner and hence the miner not hitting the pool :

found this in the debug log .  is it a problem ?

2017-09-15 18:10:39 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 7766.000000 pindexPrev c957c40119d42e623a7cff2ee89f6ab420a2524e67a4e08ac67cb0ee469bcd0f
2017-09-15 18:10:39 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3408128)UpdateTip: new best=b1f46a749d9e5fde9affec0fa6fb4a56d132189abc5db84376ad79bf7a1c5988  height=7768  log2_work=50.596555  tx=11973  date=2017-09-15 18:10:16 progress=0.999998  cache=0.0MiB(5tx)

[togoshigekata]

My linux miner on v1.0.3.5 hasnt been kicked off the pool but I have noticed that the Hashes Per Sec 2 for my linux miner has been slowly dropping all day today to where now its barely even anything, weird

[tiras]

My linux miner on v1.0.3.5 hasnt been kicked off the pool but I have noticed that the Hashes Per Sec 2 for my linux miner has been slowly dropping all day today to where now its barely even anything, weird

because your miner stops hitting the pool hps 2  is dropping slowly to 0

[togoshigekata]

interesting, its back up again, near top of leaderboard now, interesting, sorry!

[tiras]

interesting, its back up again, near top of leaderboard now, interesting, sorry!

@togoshigekata  ,   what kind of CPU is this ?

94272.74   22202.59   56

[tiras]

@Bible_pay   ,  could you kindly give instructions to compile it on linux to use with no GUI to avoid installing libraries you don't need to run it from cmd shell  ?

[togoshigekata]

We are on block 7777

@tiras
Its just a Ryzen 1700 I got on Newegg
"AMD RYZEN 7 1700 8-Core 3.0 GHz (3.7 GHz Turbo) Socket AM4 65W YD1700BBAEBOX Desktop Processor"
and I installed Ubuntu Server 16.04
I think its running at 3.65GHz

What type of machine is this?
User Name       Miner Name               Hashes Per Second       Hashes Per Second2
tiras                 tirasworks_bbp7         82846.46                   39640.09   

[emdes]

We are on block 7777

@tiras
Its just a Ryzen 1700 I got on Newegg
"AMD RYZEN 7 1700 8-Core 3.0 GHz (3.7 GHz Turbo) Socket AM4 65W YD1700BBAEBOX Desktop Processor"
and I installed Ubuntu Server 16.04
I think its running at 3.65GHz

So, linux = 2 -3x hashing power VS Win ? RIP

Me, Slovakia and Oliwer21 getting around 12k Hashps1 and 20 - 35k Hashps2 with Ryzen 1700 and 1700x

Another "problem" for me with the 1700x:

Win8.1 7200RPM disk 35% CPU load 38c = 30 - 35k Hashps2
Win10  SSD disk      100% CPU load 55c = 18 - 24k Hashps2

EDIT: Yes, same system just by swapping disk/OS. Same config file.

[tiras]

We are on block 7777

@tiras
Its just a Ryzen 1700 I got on Newegg
"AMD RYZEN 7 1700 8-Core 3.0 GHz (3.7 GHz Turbo) Socket AM4 65W YD1700BBAEBOX Desktop Processor"
and I installed Ubuntu Server 16.04
I think its running at 3.65GHz

What type of machine is this?
User Name       Miner Name               Hashes Per Second       Hashes Per Second2
tiras                 tirasworks_bbp7         82846.46                   39640.09   

guess what ,   exactly the same  CPU and OS .   I didn't OC it though . 

 lscpu | grep MHz
CPU MHz:               3000.000
CPU max MHz:           3000.0000
CPU min MHz:           1550.0000