BiblePay - New Coin Launch - Official Thread

[cryptocurrencyfreak]

What is the difference between Hashes Per Second and Hashes Per Second2

[cryptocurrencyfreak]

Some of my miners still crash / stop reporting to pool with this:

Code:

2017-09-14 03:15:32 ProcessMessages(version, 109 bytes) FAILED peer=527
2017-09-14 03:15:41 peer=528 using obsolete version 70707; disconnecting
2017-09-14 03:15:41 ProcessMessages(version, 109 bytes) FAILED peer=528
2017-09-14 03:15:42 peer=529 using obsolete version 70707; disconnecting
2017-09-14 03:15:42 ProcessMessages(version, 109 bytes) FAILED peer=529
2017-09-14 03:16:01 peer=531 using obsolete version 70707; disconnecting
2017-09-14 03:16:01 ProcessMessages(version, 109 bytes) FAILED peer=531
2017-09-14 03:16:32 peer=534 using obsolete version 70707; disconnecting
2017-09-14 03:16:32 ProcessMessages(version, 109 bytes) FAILED peer=534
2017-09-14 03:16:52 socket recv error Connection timed out (110)
2017-09-14 03:16:55 socket recv error Connection timed out (110)
2017-09-14 03:16:58 peer=536 using obsolete version 70707; disconnecting
2017-09-14 03:16:58 ProcessMessages(version, 109 bytes) FAILED peer=536
2017-09-14 03:17:09 peer=537 using obsolete version 70707; disconnecting
2017-09-14 03:17:09 ProcessMessages(version, 109 bytes) FAILED peer=537
2017-09-14 03:17:17 peer=538 using obsolete version 70707; disconnecting
2017-09-14 03:17:17 ProcessMessages(version, 109 bytes) FAILED peer=538
2017-09-14 03:17:34 peer=541 using obsolete version 70707; disconnecting
2017-09-14 03:17:34 ProcessMessages(version, 109 bytes) FAILED peer=541
2017-09-14 03:17:36 peer=542 using obsolete version 70707; disconnecting
2017-09-14 03:17:36 ProcessMessages(version, 109 bytes) FAILED peer=542
2017-09-14 03:17:38 peer=543 using obsolete version 70707; disconnecting
2017-09-14 03:17:38 ProcessMessages(version, 109 bytes) FAILED peer=543
2017-09-14 03:17:39 socket recv error Connection timed out (110)
2017-09-14 03:17:44 peer=544 using obsolete version 70707; disconnecting
2017-09-14 03:17:44 ProcessMessages(version, 109 bytes) FAILED peer=544
2017-09-14 03:17:48 peer=546 using obsolete version 70707; disconnecting
2017-09-14 03:17:48 ProcessMessages(version, 109 bytes) FAILED peer=546
2017-09-14 03:17:52 socket recv error Connection timed out (110)
2017-09-14 03:17:53 peer=548 using obsolete version 70707; disconnecting
2017-09-14 03:17:53 ProcessMessages(version, 109 bytes) FAILED peer=548
2017-09-14 03:17:54 peer=549 using obsolete version 70707; disconnecting
2017-09-14 03:17:54 ProcessMessages(version, 109 bytes) FAILED peer=549
2017-09-14 03:18:01 peer=550 using obsolete version 70707; disconnecting
2017-09-14 03:18:01 ProcessMessages(version, 109 bytes) FAILED peer=550
2017-09-14 03:18:20 peer=551 using obsolete version 70707; disconnecting
2017-09-14 03:18:20 ProcessMessages(version, 109 bytes) FAILED peer=551

[richus]

When the sync on solo mining. The same day sit without pay???

[tiras]

Ubuntu miners dropped from pool still happen. Any clue?

I believe that was just before the pool upgraded to 1.0.3.4.  Should be good now.

This message was found with miner 1.0.3.4 to pool 1.0.3.4. Actually it happened since 1.0.3.1, and weird issue is some miners do not have this problem at all... Any other info do you want me to provide so that you can trace the issue?

don't know if it helps but at the "hanged" status
it show this :

Code:

 ./biblepay-cli getmininginfo
{
  "blocks": 7525,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 458.2992323872484,
  "errors": "",
  "genproclimit": 16,
  "networkhashps": 50686908803.63249,
  "hashps": 44608.43711820188,
  "minerstarttime": "09-14-2017 02:38:44",
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVt
rHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS
; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJ
fhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; ",

  "poolinfo2": "RMC_09-14-2017 03:21:58; RMC_09-14-2017 03:22:40; RMC_09-14-2017 03:21:55; RMC_09-14-2017 03:22:28;
 RMC_09-14-2017 03:22:29; RMC_09-14-2017 03:21:40; RMC_09-14-2017 03:22:05; RMC_09-14-2017 03:22:39; RMC_09-14-2017
 03:21:26; RMC_09-14-2017 03:22:22; RMC_09-14-2017 03:22:37; RMC_09-14-2017 03:21:28; ",
 
  "poolinfo3": "CFW 09-14-2017 03:21:57; CFW 09-14-2017 03:22:39; CFW 09-14-2017 03:21:54; CFW 09-14-2017 03:22:27;
 CFW 09-14-2017 03:22:28; CFW 09-14-2017 03:21:38; CFW 09-14-2017 03:22:03; CFW 09-14-2017 03:22:37; CFW 09-14-2017
 03:21:23; CFW 09-14-2017 03:22:20; CFW 09-14-2017 03:22:35; CFW 09-14-2017 03:21:25; ",
  "miningpulse": 3745,
  "poolmining": true
 

after daemon restarted it starts submitting solutions again  :

Code:

  ./biblepay-cli getmininginfo
{
  "blocks": 7525,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 458.2992323872484,
  "errors": "",
  "genproclimit": 16,
  "networkhashps": 50686908803.63249,
  "hashps": 36221.69811320755,
  "minerstarttime": "09-14-2017 03:25:54",
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVt
rHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS
; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJ
fhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqi
NUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2
LdHVjWVtrHSELMS; ",

  "poolinfo2": "Submitting Solution 09-14-2017 03:26:23; Submitting Solution 09-14-2017 03:26:24; Submitting Soluti
on 09-14-2017 03:26:06; Submitting Solution 09-14-2017 03:26:19; Submitting Solution 09-14-2017 03:26:17; Submittin
g Solution 09-14-2017 03:26:24; Submitting Solution 09-14-2017 03:26:07; Submitting Solution 09-14-2017 03:26:07; S
ubmitting Solution 09-14-2017 03:26:07; RMC_09-14-2017 03:25:55; Submitting Solution 09-14-2017 03:26:17; Submittin
g Solution 09-14-2017 03:26:16; Submitting Solution 09-14-2017 03:26:15; Submitting Solution 09-14-2017 03:25:59; S
ubmitting Solution 09-14-2017 03:26:18; Submitting Solution 09-14-2017 03:26:01; ",

  "poolinfo3": "",
  
  "miningpulse": 36,
  "poolmining": true

[seasonw]

Ubuntu miners dropped from pool still happen. Any clue?

I believe that was just before the pool upgraded to 1.0.3.4.  Should be good now.

This message was found with miner 1.0.3.4 to pool 1.0.3.4. Actually it happened since 1.0.3.1, and weird issue is some miners do not have this problem at all... Any other info do you want me to provide so that you can trace the issue?

don't know if it helps but at the "hanged" status
it show this :

Code:

 ./biblepay-cli getmininginfo
{
  "blocks": 7525,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 458.2992323872484,
  "errors": "",
  "genproclimit": 16,
  "networkhashps": 50686908803.63249,
  "hashps": 44608.43711820188,
  "minerstarttime": "09-14-2017 02:38:44",
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVt
rHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS
; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJ
fhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; ",

  "poolinfo2": "RMC_09-14-2017 03:21:58; RMC_09-14-2017 03:22:40; RMC_09-14-2017 03:21:55; RMC_09-14-2017 03:22:28;
 RMC_09-14-2017 03:22:29; RMC_09-14-2017 03:21:40; RMC_09-14-2017 03:22:05; RMC_09-14-2017 03:22:39; RMC_09-14-2017
 03:21:26; RMC_09-14-2017 03:22:22; RMC_09-14-2017 03:22:37; RMC_09-14-2017 03:21:28; ",
 
  "poolinfo3": "CFW 09-14-2017 03:21:57; CFW 09-14-2017 03:22:39; CFW 09-14-2017 03:21:54; CFW 09-14-2017 03:22:27;
 CFW 09-14-2017 03:22:28; CFW 09-14-2017 03:21:38; CFW 09-14-2017 03:22:03; CFW 09-14-2017 03:22:37; CFW 09-14-2017
 03:21:23; CFW 09-14-2017 03:22:20; CFW 09-14-2017 03:22:35; CFW 09-14-2017 03:21:25; ",
  "miningpulse": 3745,
  "poolmining": true
 

after daemon restarted it starts submitting solutions again  :

Code:

  ./biblepay-cli getmininginfo
{
  "blocks": 7525,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 458.2992323872484,
  "errors": "",
  "genproclimit": 16,
  "networkhashps": 50686908803.63249,
  "hashps": 36221.69811320755,
  "minerstarttime": "09-14-2017 03:25:54",
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVt
rHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS
; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJ
fhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqi
NUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2
LdHVjWVtrHSELMS; ",

  "poolinfo2": "Submitting Solution 09-14-2017 03:26:23; Submitting Solution 09-14-2017 03:26:24; Submitting Soluti
on 09-14-2017 03:26:06; Submitting Solution 09-14-2017 03:26:19; Submitting Solution 09-14-2017 03:26:17; Submittin
g Solution 09-14-2017 03:26:24; Submitting Solution 09-14-2017 03:26:07; Submitting Solution 09-14-2017 03:26:07; S
ubmitting Solution 09-14-2017 03:26:07; RMC_09-14-2017 03:25:55; Submitting Solution 09-14-2017 03:26:17; Submittin
g Solution 09-14-2017 03:26:16; Submitting Solution 09-14-2017 03:26:15; Submitting Solution 09-14-2017 03:25:59; S
ubmitting Solution 09-14-2017 03:26:18; Submitting Solution 09-14-2017 03:26:01; ",

  "poolinfo3": "",
  
  "miningpulse": 36,
  "poolmining": true

I also noticed this circumstance, submission right away after restarting the daemon. It is weird.
Anyway, I was testing a method, I will update here if it will solve this issue.

[616westwarmoth]

Thanks dev for the quick attention to the issues today!  Its that sort of strength that doesn't get recognized that has the potential to take this coin places.

[ronnieppatel]

Reliable investments are done.Any updates on the bounty?

[deepcryptomine]

Thanks dev for the quick attention to the issues today!  Its that sort of strength that doesn't get recognized that has the potential to take this coin places.

Yes I agree. Also the community is pretty strong and its growing. The way you guys brought up the issues and suggestions are amazing. I spend all day at work and don't get a time to look at the thread and issues. By the time I come home, the solution or work around has already been delivered. I upgraded to latest wallet and it wasn't syncing someone mentioned to restart the wallet again and that worked.

[cryptocurrencyfreak]

Unfortunately I have removed all of my miners. They will mine for an hour or so and then crash with previous posted errors. I have completely installed from scratch, including removing the profile folder with same results. Hope to mine again when these issues are solved.

[PhaseshiftUK]

<snip image>
Ubuntu miners dropped from pool still happen. Any clue?

I believe that was just before the pool upgraded to 1.0.3.4.  Should be good now.

This message was found with miner 1.0.3.4 to pool 1.0.3.4. Actually it happened since 1.0.3.1, and weird issue is some miners do not have this problem at all... Any other info do you want me to provide so that you can trace the issue?

I can confirm that I have the same issue running 1.0.3.4 on Debian Linux.

Lots of:

2017-09-13 23:46:28 socket recv error Connection reset by peer (104)
2017-09-13 23:48:35 socket recv error Connection reset by peer (104)
2017-09-13 23:50:42 socket recv error Connection reset by peer (104)
2017-09-13 23:52:49 socket recv error Connection reset by peer (104)
2017-09-13 23:54:57 socket recv error Connection reset by peer (104)
2017-09-13 23:57:04 socket recv error Connection reset by peer (104)
2017-09-13 23:59:11 socket recv error Connection reset by peer (104)
2017-09-14 00:01:18 socket recv error Connection reset by peer (104)
2017-09-14 00:03:25 socket recv error Connection reset by peer (104)
2017-09-14 00:05:32 socket recv error Connection reset by peer (104)
2017-09-14 00:07:40 socket recv error Connection reset by peer (104)

And still have:

2017-09-13 23:07:35 ProcessNewBlock : ACCEPTED
2017-09-13 23:07:54 socket recv error Connection reset by peer (104)
2017-09-13 23:08:06 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 7361.000000 pindexPrev 271c540a2ff535f1a76095333af4be559dc03344063a8240cbe6c57f2b319383
2017-09-13 23:08:06 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3213187)^M
** ProcessGetData:Cannot load block from disk.^M
2017-09-13 23:08:08 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 7335.000000 pindexPrev 7c8ebea50332103b657ffae35b44a568473db479abe1ddda751e856d3101e618
2017-09-13 23:08:08 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3202733)^M
** ProcessGetData:Cannot load block from disk.^M
2017-09-13 23:08:10 UpdateTip: new best=3fa7e67c94be8d98ab261a3e4bd987d9109d5581d7cbdcc8197875e400ac38aa  height=7496  log2_work=49.133899  tx=11543  date=2017-09-13 23:08:06 progress=1.000000  cache=0.0MiB(38tx)
2017-09-13 23:08:10 ProcessNewBlock : ACCEPTED
2017-09-13 23:10:01 socket recv error Connection reset by peer (104)
2017-09-13 23:11:48 UpdateTip: new best=88b6821089d7bca250e5319957b5489ba79625d479a6674003a4da980b9a8424  height=7497  log2_work=49.135977  tx=11545  date=2017-09-13 23:11:40 progress=0.999999  cache=0.0MiB(40tx)
2017-09-13 23:11:48 ProcessNewBlock : ACCEPTED

It still seems to think it is submitting to the pool, but the pool is not showing or counting it (phaseshift.w2):

$ ../biblepay/bin/biblepay-cli getmininginfo
{
  "blocks": 7550,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 441.3595706618963,
  "errors": "",
  "genproclimit": 8,
  "networkhashps": 45819800310.70996,
  "hashps": 56562.73997076839,
  "minerstarttime": "09-13-2017 22:43:42",
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; ",
  "poolinfo2": "RMC_09-14-2017 07:06:21; RMC_09-14-2017 07:12:12; RMC_09-14-2017 07:06:53; ",
  "poolinfo3": "CFW 09-14-2017 07:06:20; CFW 09-14-2017 07:12:11; CFW 09-14-2017 07:06:51; ",
  "miningpulse": 52683,
  "poolmining": true
}

On the plus side, the error below seems to not happen any more when stopping biblepay under Linux with 1.0.3.4:

"terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
terminate called recursively"

[inblue]

Code:

2017-09-14 07:08:46 socket send error An established connection was aborted by the software in your host machine.  (10053)

While syncing, this error shows up just after block 7012, and then it stops syncing and has 0 peers. I started with a completely clean directory of course. Then after a while it syncs a few more blocks and then stops with another error:

Code:

2017-09-14 07:11:24 socket recv error An existing connection was forcibly closed by the remote host.  (10054)

Edit: spamming this command into the console multiple times syncs it eventually:

Code:

addnode "pool.biblepay.org" "onetry"

[x5650]

Is normal to have all of the cores (CPU X5650 genproclimit=6) at less than 60% load while mining?

[inblue]

Is normal to have all of the cores (CPU X5650 genproclimit=6) at less than 60% load while mining?

X5650 has 6 cores and 12 threads. You need to increase genproclimit to 12 if you want 100%.

[slovakia]

im tested my Ryzen 1700 every setups with genproclimit from 8 to 24 and still have hashpower 3839.95   6785.13 

[x5650]

I did it before updates and got less HPS with more cores enabled.
Now i made another try and:
      
genproclimit=6 i got 6235,17HPS and 18649,49HPS2 at less than 60% load for miner.

genproclimit=12 i got 5961,53HPS and 14035,45HPS2 at less than 80% load for miner.

[inblue]

Hahaha, we have some comedians here. Gave me a good chuckle.

[rangnatht]

Very nice concept... Hope this coin become more valuable when it's hits exchange

[seasonw]

Hahaha, we have some comedians here. Gave me a good chuckle.

Haha   this is funny, hope liugang saw that message, lol~~

[canonical]

Just catching up on the thread. Installed the new biblepay on my workers, all working now. Great work dev.

Biblepay is probably the most interesting coin I follow. Not a typical clone of another coin, biblehash is genuinely interesting, dev is communicative and actually knows what they're doing. 👍

Wasn't aware of public beta-testing on the main chain. Will definitely volunteer next time you put the call out.

[schyter]

My wallet hasnt been able to sync for the past 2 days. what could be the problem?