BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

[bible_pay]

is this related to the abn problems?
seems I cannot pool mine without this happening after only a few minutes:

Code:

ContextualCheckBlockHeader::FAILED incorrect proof of work at 132806, block.nbits 469802878.000000, next work 459223285.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132806, block.nbits 469802878.000000, next work 459223285.000000 (code 16)

I dont see a miner by the name of Nipar, please share miner name.

nickname=nichaols1
miner names are  np-01F and np-L2-F

I also downloaded the windows version with the updated getabnweight version 2.7 and it still happens
thanks.

I made a change to the pool to attempt to reveal the problem, did it just resolve (try to 'setgenerate true N') on one of the nodes?

Waiting for the leader board to update and show only 1 miner

No, I mean to see if the problem miner now has a valid ABN?

"poolinfo5": "Internal ABN: Invalid 1563578281; ",
  "abninfo": "Mining with funded Valid ABN 475241571a003cb33dc9c3b71304aea27e6c6d2d1cf221178ef8a39a31ba2bc1; Mining with funded Valid ABN 475241571a003cb33dc9c3b71304aea27e6c6d2d1cf221178ef8a39a31ba2bc1; " and still produces that fail error

I think you are fixed;  it takes 3-5 mins for all errors to clear.

But the root of the issue was you couldn't get a valid ABN, now you have one.

Also, now if you drill into the leaderboard, you can see the health columns went to 100% now.

[Nipar]

is this related to the abn problems?
seems I cannot pool mine without this happening after only a few minutes:

Code:

ContextualCheckBlockHeader::FAILED incorrect proof of work at 132806, block.nbits 469802878.000000, next work 459223285.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132806, block.nbits 469802878.000000, next work 459223285.000000 (code 16)

I dont see a miner by the name of Nipar, please share miner name.

nickname=nichaols1
miner names are  np-01F and np-L2-F

I also downloaded the windows version with the updated getabnweight version 2.7 and it still happens
thanks.

I made a change to the pool to attempt to reveal the problem, did it just resolve (try to 'setgenerate true N') on one of the nodes?

Waiting for the leader board to update and show only 1 miner

No, I mean to see if the problem miner now has a valid ABN?

"poolinfo5": "Internal ABN: Invalid 1563578281; ",
  "abninfo": "Mining with funded Valid ABN 475241571a003cb33dc9c3b71304aea27e6c6d2d1cf221178ef8a39a31ba2bc1; Mining with funded Valid ABN 475241571a003cb33dc9c3b71304aea27e6c6d2d1cf221178ef8a39a31ba2bc1; " and still produces that fail error

I think you are fixed;  it takes 3-5 mins for all errors to clear.

But the root of the issue was you couldn't get a valid ABN, now you have one.

Also, now if you drill into the leaderboard, you can see the health columns went to 100% now.

So far so good, setgenerate false then true on both, errors cleared. watched the debug log for a bit.

and now it's doing it again:

2019-07-19 23:34:41 {PNB}: ACC  BibleMiner -- started thread 0.000000
2019-07-19 23:35:26 BibleMiner -- started thread 1.000000
2019-07-19 23:35:26 BibleMiner -- started thread 2.000000
2019-07-19 23:35:27 BibleMiner -- started thread 3.000000
2019-07-19 23:35:27 BibleMiner -- started thread 4.000000
2019-07-19 23:35:27 BibleMiner -- started thread 5.000000
2019-07-19 23:35:27  ** Started 6.000000 BibleMiner threads. **
2019-07-19 23:36:11 UpdateTip: new best=297f95c8a0694d9390977b6899cd882825b9565a830d1e570eb717c5172625f1 height=132814 version=0x2000000c log2_work=59.51361825 tx=1098411 date='2019-07-19 23:36:10' progress=1.000000 cache=0.0MiB(0txo)
2019-07-19 23:36:11 {PNB}: ACC
ContextualCheckBlockHeader::FAILED incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000 (code 16)
2019-07-19 23:36:29
ContextualCheckBlockHeader::FAILED incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000 (code 16)
2019-07-19 23:36:29
ContextualCheckBlockHeader::FAILED incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000 (code 16)
2019-07-19 23:36:29
ContextualCheckBlockHeader::FAILED incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000 (code 16)
2019-07-19 23:36:29
ContextualCheckBlockHeader::FAILED incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000 (code 16)
2019-07-19 23:36:30
ContextualCheckBlockHeader::FAILED incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000 (code 16)


this is the linux version of 1443 with getabnweight version 2.6
I am now also recieving a lot of stale blocks from the pool.


..

[bible_pay]

is this related to the abn problems?
seems I cannot pool mine without this happening after only a few minutes:

Code:

ContextualCheckBlockHeader::FAILED incorrect proof of work at 132806, block.nbits 469802878.000000, next work 459223285.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132806, block.nbits 469802878.000000, next work 459223285.000000 (code 16)

I dont see a miner by the name of Nipar, please share miner name.

nickname=nichaols1
miner names are  np-01F and np-L2-F

I also downloaded the windows version with the updated getabnweight version 2.7 and it still happens
thanks.

I made a change to the pool to attempt to reveal the problem, did it just resolve (try to 'setgenerate true N') on one of the nodes?

Waiting for the leader board to update and show only 1 miner

No, I mean to see if the problem miner now has a valid ABN?

"poolinfo5": "Internal ABN: Invalid 1563578281; ",
  "abninfo": "Mining with funded Valid ABN 475241571a003cb33dc9c3b71304aea27e6c6d2d1cf221178ef8a39a31ba2bc1; Mining with funded Valid ABN 475241571a003cb33dc9c3b71304aea27e6c6d2d1cf221178ef8a39a31ba2bc1; " and still produces that fail error

I think you are fixed;  it takes 3-5 mins for all errors to clear.

But the root of the issue was you couldn't get a valid ABN, now you have one.

Also, now if you drill into the leaderboard, you can see the health columns went to 100% now.

So far so good, setgenerate false then true on both, errors cleared. watched the debug log for a bit.

and now it's doing it again:

2019-07-19 23:34:41 {PNB}: ACC  BibleMiner -- started thread 0.000000
2019-07-19 23:35:26 BibleMiner -- started thread 1.000000
2019-07-19 23:35:26 BibleMiner -- started thread 2.000000
2019-07-19 23:35:27 BibleMiner -- started thread 3.000000
2019-07-19 23:35:27 BibleMiner -- started thread 4.000000
2019-07-19 23:35:27 BibleMiner -- started thread 5.000000
2019-07-19 23:35:27  ** Started 6.000000 BibleMiner threads. **
2019-07-19 23:36:11 UpdateTip: new best=297f95c8a0694d9390977b6899cd882825b9565a830d1e570eb717c5172625f1 height=132814 version=0x2000000c log2_work=59.51361825 tx=1098411 date='2019-07-19 23:36:10' progress=1.000000 cache=0.0MiB(0txo)
2019-07-19 23:36:11 {PNB}: ACC
ContextualCheckBlockHeader::FAILED incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000 (code 16)
2019-07-19 23:36:29
ContextualCheckBlockHeader::FAILED incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000 (code 16)
2019-07-19 23:36:29
ContextualCheckBlockHeader::FAILED incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000 (code 16)
2019-07-19 23:36:29
ContextualCheckBlockHeader::FAILED incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000 (code 16)
2019-07-19 23:36:29
ContextualCheckBlockHeader::FAILED incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000 (code 16)
2019-07-19 23:36:30
ContextualCheckBlockHeader::FAILED incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000 (code 16)


this is the linux version of 1443 with getabnweight version 2.6
I am now also recieving a lot of stale blocks from the pool.


..

What is the timestamp range of stale blocks in the log, did it continue?  I believe this is normal behavior.

[Nipar]

is this related to the abn problems?
seems I cannot pool mine without this happening after only a few minutes:

Code:

ContextualCheckBlockHeader::FAILED incorrect proof of work at 132806, block.nbits 469802878.000000, next work 459223285.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132806, block.nbits 469802878.000000, next work 459223285.000000 (code 16)

I dont see a miner by the name of Nipar, please share miner name.

nickname=nichaols1
miner names are  np-01F and np-L2-F

I also downloaded the windows version with the updated getabnweight version 2.7 and it still happens
thanks.

I made a change to the pool to attempt to reveal the problem, did it just resolve (try to 'setgenerate true N') on one of the nodes?

Waiting for the leader board to update and show only 1 miner

No, I mean to see if the problem miner now has a valid ABN?

"poolinfo5": "Internal ABN: Invalid 1563578281; ",
  "abninfo": "Mining with funded Valid ABN 475241571a003cb33dc9c3b71304aea27e6c6d2d1cf221178ef8a39a31ba2bc1; Mining with funded Valid ABN 475241571a003cb33dc9c3b71304aea27e6c6d2d1cf221178ef8a39a31ba2bc1; " and still produces that fail error

I think you are fixed;  it takes 3-5 mins for all errors to clear.

But the root of the issue was you couldn't get a valid ABN, now you have one.

Also, now if you drill into the leaderboard, you can see the health columns went to 100% now.

So far so good, setgenerate false then true on both, errors cleared. watched the debug log for a bit.

and now it's doing it again:

2019-07-19 23:34:41 {PNB}: ACC  BibleMiner -- started thread 0.000000
2019-07-19 23:35:26 BibleMiner -- started thread 1.000000
2019-07-19 23:35:26 BibleMiner -- started thread 2.000000
2019-07-19 23:35:27 BibleMiner -- started thread 3.000000
2019-07-19 23:35:27 BibleMiner -- started thread 4.000000
2019-07-19 23:35:27 BibleMiner -- started thread 5.000000
2019-07-19 23:35:27  ** Started 6.000000 BibleMiner threads. **
2019-07-19 23:36:11 UpdateTip: new best=297f95c8a0694d9390977b6899cd882825b9565a830d1e570eb717c5172625f1 height=132814 version=0x2000000c log2_work=59.51361825 tx=1098411 date='2019-07-19 23:36:10' progress=1.000000 cache=0.0MiB(0txo)
2019-07-19 23:36:11 {PNB}: ACC
ContextualCheckBlockHeader::FAILED incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000 (code 16)
2019-07-19 23:36:29
ContextualCheckBlockHeader::FAILED incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000 (code 16)
2019-07-19 23:36:29
ContextualCheckBlockHeader::FAILED incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000 (code 16)
2019-07-19 23:36:29
ContextualCheckBlockHeader::FAILED incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000 (code 16)
2019-07-19 23:36:29
ContextualCheckBlockHeader::FAILED incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000 (code 16)
2019-07-19 23:36:30
ContextualCheckBlockHeader::FAILED incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000 (code 16)


this is the linux version of 1443 with getabnweight version 2.6
I am now also recieving a lot of stale blocks from the pool.


..

What is the timestamp range of stale blocks in the log, did it continue?  I believe this is normal behavior.

the stale blocks are not recorded in the debug log.
however there is this:

2019-07-20 00:14:23
ContextualCheckBlock::ABN ERROR!  Block 132819.000000 does not meet anti-bot-net-minimum required guidelines: ReqABNHeight 128597.000000, BlockWeight 0.000000, RequiredWeight 125000.000000UpdateTip: new best=61a0212f43f1849d2f5556be625612edd8ed65d00c2271cd42bd5a30b0cf6894 height=132819 version=0x2000000c log2_work=59.51363320 tx=1098431 date='2019-07-20 00:14:17' progress=1.000000 cache=0.0MiB(0txo)
2019-07-20 00:14:23 {PNB}: ACC


...

[bible_pay]

is this related to the abn problems?
seems I cannot pool mine without this happening after only a few minutes:

Code:

ContextualCheckBlockHeader::FAILED incorrect proof of work at 132806, block.nbits 469802878.000000, next work 459223285.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132806, block.nbits 469802878.000000, next work 459223285.000000 (code 16)

I dont see a miner by the name of Nipar, please share miner name.

nickname=nichaols1
miner names are  np-01F and np-L2-F

I also downloaded the windows version with the updated getabnweight version 2.7 and it still happens
thanks.

I made a change to the pool to attempt to reveal the problem, did it just resolve (try to 'setgenerate true N') on one of the nodes?

Waiting for the leader board to update and show only 1 miner

No, I mean to see if the problem miner now has a valid ABN?

"poolinfo5": "Internal ABN: Invalid 1563578281; ",
  "abninfo": "Mining with funded Valid ABN 475241571a003cb33dc9c3b71304aea27e6c6d2d1cf221178ef8a39a31ba2bc1; Mining with funded Valid ABN 475241571a003cb33dc9c3b71304aea27e6c6d2d1cf221178ef8a39a31ba2bc1; " and still produces that fail error

I think you are fixed;  it takes 3-5 mins for all errors to clear.

But the root of the issue was you couldn't get a valid ABN, now you have one.

Also, now if you drill into the leaderboard, you can see the health columns went to 100% now.

So far so good, setgenerate false then true on both, errors cleared. watched the debug log for a bit.

and now it's doing it again:

2019-07-19 23:34:41 {PNB}: ACC  BibleMiner -- started thread 0.000000
2019-07-19 23:35:26 BibleMiner -- started thread 1.000000
2019-07-19 23:35:26 BibleMiner -- started thread 2.000000
2019-07-19 23:35:27 BibleMiner -- started thread 3.000000
2019-07-19 23:35:27 BibleMiner -- started thread 4.000000
2019-07-19 23:35:27 BibleMiner -- started thread 5.000000
2019-07-19 23:35:27  ** Started 6.000000 BibleMiner threads. **
2019-07-19 23:36:11 UpdateTip: new best=297f95c8a0694d9390977b6899cd882825b9565a830d1e570eb717c5172625f1 height=132814 version=0x2000000c log2_work=59.51361825 tx=1098411 date='2019-07-19 23:36:10' progress=1.000000 cache=0.0MiB(0txo)
2019-07-19 23:36:11 {PNB}: ACC
ContextualCheckBlockHeader::FAILED incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000 (code 16)
2019-07-19 23:36:29
ContextualCheckBlockHeader::FAILED incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000 (code 16)
2019-07-19 23:36:29
ContextualCheckBlockHeader::FAILED incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000 (code 16)
2019-07-19 23:36:29
ContextualCheckBlockHeader::FAILED incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000 (code 16)
2019-07-19 23:36:29
ContextualCheckBlockHeader::FAILED incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000 (code 16)
2019-07-19 23:36:30
ContextualCheckBlockHeader::FAILED incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 132815, block.nbits 469800705.000000, next work 469794835.000000 (code 16)


this is the linux version of 1443 with getabnweight version 2.6
I am now also recieving a lot of stale blocks from the pool.


..

What is the timestamp range of stale blocks in the log, did it continue?  I believe this is normal behavior.

the stale blocks are not recorded in the debug log.
however there is this:

2019-07-20 00:14:23
ContextualCheckBlock::ABN ERROR!  Block 132819.000000 does not meet anti-bot-net-minimum required guidelines: ReqABNHeight 128597.000000, BlockWeight 0.000000, RequiredWeight 125000.000000UpdateTip: new best=61a0212f43f1849d2f5556be625612edd8ed65d00c2271cd42bd5a30b0cf6894 height=132819 version=0x2000000c log2_work=59.51363320 tx=1098431 date='2019-07-20 00:14:17' progress=1.000000 cache=0.0MiB(0txo)
2019-07-20 00:14:23 {PNB}: ACC


...

We get a little bit of spam per block change in this version, just let it go for tonight and see if you fail to get an ABN for more than 5 mins.

In the next version, Ill make it do an extra test each time it gets an ABN and keep it out of the log, that should help keep the log clean.

[togoshigekata]

===================================================================================
=== GET PAID BBP COINS FROM MONTHLY BUDGET FOR YOUR WORK!

Anyone can get paid BBP for helping do work for BiblePay!
http://wiki.biblepay.org/UnderstandingGovernance

From GUI Wallet, in top menu click Proposals >> Proposals Add
NOTE: Only costs 2500 BBP to submit a proposal requesting funding for your work

Here is an incomplete ownership list of different resources:
https://www.reddit.com/r/BiblePay/comments/9utdsh/biblepay_ownership_list/

===================================================================================
=== OPEN TODO LIST:

- Update and migrate Reddit Mining guides to website/wiki
https://www.reddit.com/r/BiblePay/comments/6umlqq/how_to_mine_biblepay_on_windows/
https://www.reddit.com/r/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/
https://www.reddit.com/r/BiblePay/comments/7qnbp4/bbp_miner_on_pi/

- Update and migrate Update/Clean wallet guide to website/wiki
https://www.reddit.com/r/BiblePay/comments/7nmvm8/how_to_update_clean_wallets/
(erasechain?)

- Update Bitcointalk ANN
Current: https://bitcointalk.org/index.php?topic=2388064
My Latest Attempt: https://bitcointalk.org/index.php?topic=5067231

- Update ANNs for all forums
https://www.reddit.com/r/BiblePay/comments/7qmt6m/bitcointalk_main_post_language_translations/

- Update Wiki main page
---- Create Table of Contents
http://wiki.biblepay.org/Main_Page

- Update White Paper
https://pool.biblepay.org/Docs/BiblePay_White_Paper.pdf

- Write and Publish Step by Step Buying Bitcoin and Buying BiblePay guide
https://bitcointalk.org/index.php?topic=2388064.msg51062536#msg51062536

- Create Youtube Videos
--- How to Mine
--- How to Buy Coins
--- How to Create Proposals, How to View, How Budget System Works
--- How to Setup Masternode (How to Vote)

- Translate to All Languages
--- Bitcointalk ANN - https://www.reddit.com/r/BiblePay/comments/7qmt6m/bitcointalk_main_post_language_translations/
--- Mining Guides
--- Website - http://biblepay.org/
https://www.reddit.com/r/BiblePay/comments/7dyabk/help_translate_website_documentation_to_other/
--- White Paper
--- Wallet?
--- Bible?

Language Plugins for Wordpress:

- Polylang: https://wordpress.org/plugins/polylang/
- qTranslate X: https://wordpress.org/plugins/qtranslate-x/
- Polylang Pro: https://polylang.pro/downloads/polylang-pro/
- WordPress Multilingual Plugin (WPML): https://wpml.org/

- Create Twitter Account and Follow BiblePay, Like and Retweet Tweets
https://twitter.com/i/flow/signup?lang=en

- Create or Update Bitcointalk Forum Signature
https://www.reddit.com/r/BiblePay/comments/7s1qsy/bitcointalk_forum_signature_guide/

- Help Test in Testnet v0.14 Dash Features
https://forum.biblepay.org/index.php?topic=391.0

===================================================================================
=== MORE TODO:

- Advertising and Journalist Research (Multiple Sheets)
https://docs.google.com/spreadsheets/d/1grgb5Y74XMqShKDp051h1bSZVbHzRLna1bYzoTh6MAY/edit#gid=0
--- Create Banner Ad Graphics
--- Write Articles/Stories

Christcoin is a dead coin now, but look what places it got articles:
https://baptistnews.com/article/market-christian-cryptocurrency-christ-coin-aims-find/#.XNs1E45KiUk
https://www.worldreligionnews.com/religion-news/first-cryptocurrency-god-christ-coin
https://religionnews.com/2017/10/04/christ-coin-launches-as-first-faith-based-cryptocurrency/
https://www.christiantoday.com/article/christ-coin-new-christian-digital-currency-launches-with-rewards-for-the-faithful/115333.htm

- Google Ads - https://forum.biblepay.org/index.php?topic=204.0
- Facebook Ads
- Reddit Ads - https://forum.biblepay.org/index.php?topic=82.0
- Twitter Ads (Banned)

- Monthly Updates
- Weekly Updates
- Email Alerts for Mandatory Upgrades and Monthly News
- Monthly Proposal Summaries

Should we explain our History? and how should we explain it?
https://www.reddit.com/r/BiblePay/comments/ba81wh/current_block_reward_breakdown_mining_guides_and/
https://forum.biblepay.org/index.php?topic=323.0
https://forum.biblepay.org/index.php?topic=380.0
https://wiki.biblepay.org/Nutrition_Information

- How do we reach the people that would be most interested in BiblePay?
- How do people find BiblePay?
- What do they see when they find us?
- Why should someone invest in BiblePay? (Why does someone invest in Bitcoin?)
- How is BiblePay different and better than Bitcoin? What is unique?
- How easy is the path to invest?
- How do they stay in the loop / up to date?

1. Simple Fun Youtube video on How to install BiblePay wallet, How to Buy Bitcoin, How to Buy BiblePay coins, and then How to Backup wallet and keep up to date on the project, Anyone here got youtube/video creation skills? (Older mining video that was good: https://www.youtube.com/watch?v=K1yKx8KsH60) [Most people are visual learners]

2. Higher google search ranking for religion keywords matched with crypto keywords (more articles, google adwords, etc), examples of religious keywords: christian denominations: https://en.wikipedia.org/wiki/List_of_Christian_denominations_by_number_of_members, Anyone interested in running a Google Adwords campaign? Anyone interested in writing articles hitting upon keywords in title and in article?

3. I think we are missing out on Facebook, lots of older people on Facebook, older people probably dont use Reddit, Twitter, Discord, etc (I believe our Google Analytics data showed average age of users clicking on BiblePay.org was around age 35), we should be posting regularly on there, anyone interested to make periodic posts that are super user friendly / not too technical?

We need help creating youtube videos
We need help creating graphics
We need help writing articles/stories
We need help communicating on Facebook
We need help running an email newsletter
We need help advertising our monthly budget proposals

- Coin Comparisons
https://wiki.biblepay.org/Nutrition_Information
https://discontinuo.us/biblepay-unofficial-wiki/news/1904/bbp-vs-doge

- Airdrop
https://forum.biblepay.org/index.php?topic=120.0
https://www.biblepay.org/airdrop/
https://airdropalert.com/biblepay-airdrop

- Random Faucet
https://forum.biblepay.org/index.php?topic=80.0
https://www.reddit.com/r/BiblePay/comments/7m6t8s/build_2nd_faucet/

- Website SEO (Yoast plugin)

- International Crypto Forums
--- 8btc.com (Chinese)
--- MiningClub.info (Russian)

- Slide Deck
http://smallbusiness.chron.com/deck-marketing-64930.html
"Slide decks are full of infographics and data optimized for "at-a-glance" viewing"

- Paper Wallet Giveaway
How to generate 100+ paper wallets with $1-5 loaded on each

- April of BLOOM has PR experience
https://forum.biblepay.org/index.php?topic=72.0

- Banner Ads
http://fozy.altervista.org/latest-banners.html
https://pasteboard.co/HS9J9W1.png
https://pasteboard.co/HS9Jrz0.png

- Interesting Data
https://www.alexa.com/siteinfo/biblepay.org
https://coincheckup.com/coins/biblepay/analysis

- Cathio
Contact organization and writers who wrote articles about them
(I think we are missing out on the keyword catholic, we should write page/article
about how we are open to everyone including all Christian denominations)

====================================================================================

===================================================================================
=== INFO:

- What information needs to be added to our website/ann/whitepaper/etc?

-- IPFS
https://www.reddit.com/r/BiblePay/comments/9b6tex/testnet_testing_ipfs_decentralized_file_system/
https://www.reddit.com/r/BiblePay/comments/9h1578/rob_biblepay_progress/
https://medium.com/biblepay-news/biblepay-october-2018-update-2eba069fd2a2
https://www.reddit.com/r/BiblePay/comments/9st66d/november_announcement/

-- Quantitative Tightening
https://forum.biblepay.org/index.php?topic=397.0

-- Dash Evolution
https://www.reddit.com/r/BiblePay/comments/bifvpk/biblepay_evolution_what_is_it/

-- Generic Smart Contracts (GSCs)
https://wiki.biblepay.org/Generic_Smart_Contracts

-- Proof of Giving (POG)
https://wiki.biblepay.org/Generic_Smart_Contracts

-- AntiBotNet (ABN)
https://wiki.biblepay.org/Generic_Smart_Contracts

-- Healing Campaign
https://wiki.biblepay.org/BiblePay_Healing_Campaign

-- Real Life Utility
https://bitcointalk.org/index.php?topic=2388064.msg51300144#msg51300144

-- Bug Bountys
https://forum.biblepay.org/index.php?topic=408.msg6046#msg6046

-- Proof of Orphan Mining (POOM)
https://wiki.biblepay.org/POOM

-- Christian Spaces

-- Chain Locks

[eternalenvoy]

I would say http://explorer.biblepay.org:3001 is stuck in block 132234 (we are now like 436 blocks ahead that)

It's not forked because blockhashes match.

Official Explorer seem have problem since the block already @132880 now.
Also found it seem have a fork problem?Even I deleted all files and reindex, few days later , some wallet show different blockhash(config are same, maybe some nodes are moving on the wrong road, and some of my machines are coincidentally connected to the node which is on wrong direction.).

 getblockhash 132863

(chainz.cryptoid.info is on this way)
f8ef624e2e81b666f48c6ecef6a18d5ec789c323b71f10d6b31911efe7db8457

186e46fb047626477e400f644497b85e7c202a7512301595c9269c774de5cff3

[bible_pay]

I would say http://explorer.biblepay.org:3001 is stuck in block 132234 (we are now like 436 blocks ahead that)

It's not forked because blockhashes match.

Official Explorer seem have problem since the block already @132880 now.
Also found it seem have a fork problem?Even I deleted all files and reindex, few days later , some wallet show different blockhash(config are same, maybe some nodes are moving on the wrong road, and some of my machines are coincidentally connected to the node which is on wrong direction.).

 getblockhash 132863

(chainz.cryptoid.info is on this way)
f8ef624e2e81b666f48c6ecef6a18d5ec789c323b71f10d6b31911efe7db8457

186e46fb047626477e400f644497b85e7c202a7512301595c9269c774de5cff3

I just ran my global sanc report and 100% of the nodes are in agreement with Chainz and my local node and the pool:

getblockhash 132922

03fe0f4fbd2ab5848404eb4dfddc543a1f759711201d4841af0169e2d4467e31

In this case it looks like explorer.biblepay.org is wrong - please resync the chain with the -erasechain=1.
Ive seen this happen after a reindex (reindex is not good for Biblepay, we will need to address this right now for the next version.  Im adding to my punchlist now).

If anyone ever goes out of sync, please start with -erasechain=1 and dont do the reindex suggestion that other communities use.  (It does not clean up governance at all and cant handle compact blocks or non fin tx or prayers or SAN data leaving your node in a corrupt state).

EDIT:  explorer.biblepay.org is not forked - its stuck on a block 500 blocks back (look at its hash)

I wonder if we should retire this explorer - if its going to be unreliable.  Togo, can you reset it?

[togoshigekata]

https://chainz.cryptoid.info/bbp/
http://explorer.biblepay.org/

Updated explorer to latest version, performed an erasechain, its synced back up now

I think its been pretty reliable, and I think its good to have a backup explorer (from our history)
Id be totally fine with the url being set to the chainz one though
and I will gladly pass on the job of running the 2nd explorer to anyone interested!
(or if there is some other service we could use)

Iquidus explorer is slow, and has higher costs
Chainz explorer is fast, and has more features

Note: Theres a guy working on multithreading (clustering) Iquidus if anyone is interested to help him
https://github.com/iquidus/explorer/pull/257

[Borgholio]

Two of my machines that I started with -erasechain=1 yesterday have again come out of sync.  I'm doing erasechain again but I'm wondering if this is caused by explorer.biblepay.org being stuck?

[MIP]

Two of my machines that I started with -erasechain=1 yesterday have again come out of sync.  I'm doing erasechain again but I'm wondering if this is caused by explorer.biblepay.org being stuck?

I don't think there is a relation. I have all my machines synced without problems

@Togo thanks for the effort. I think that it's again stuck like 100 block behind again.

Probably Iquidus is not the most efficient setup for long chains, I agree with you.

[bible_pay]

Two of my machines that I started with -erasechain=1 yesterday have again come out of sync.  I'm doing erasechain again but I'm wondering if this is caused by explorer.biblepay.org being stuck?

Let's try to find the root cause.  Do you happen to have the log of one of the machines before it went out of sync?

B) Is this machine running with litemode=1? 

We need to see if the machine is having trouble getting gov data.
Do you have tons of banned peers in the peers list?

[bible_pay]

https://chainz.cryptoid.info/bbp/
http://explorer.biblepay.org/

Updated explorer to latest version, performed an erasechain, its synced back up now

I think its been pretty reliable, and I think its good to have a backup explorer (from our history)
Id be totally fine with the url being set to the chainz one though
and I will gladly pass on the job of running the 2nd explorer to anyone interested!
(or if there is some other service we could use)

Iquidus explorer is slow, and has higher costs
Chainz explorer is fast, and has more features

Note: Theres a guy working on multithreading (clustering) Iquidus if anyone is interested to help him
https://github.com/iquidus/explorer/pull/257

This is more related to some prior projects - not iquidis, but its worth a try, could you try this in the config:
rpcthreads=500
litemode=1

And resync? 
I was under the impression with Evo we were communicating much faster with Iquidis (I remember you said there is a big difference), but apparently iquidis gets hung occasionally.

So also could you clarify if the node itself is stuck 200 blocks behind, or is it iquidis that ceases to sync?  (If its not the node, there is no need to resync the entire chain, if its iquidis we would just resync the iquidis database.  But the rpc settings might help if its too dumb to recover).  Maybe the daemon is dying, maybe research how to persistenly keep the daemon running also.

Btw, I sent you a PM and 2 emails but have not received a reply.

[bible_pay]

Two of my machines that I started with -erasechain=1 yesterday have again come out of sync.  I'm doing erasechain again but I'm wondering if this is caused by explorer.biblepay.org being stuck?

I don't think there is a relation. I have all my machines synced without problems

@Togo thanks for the effort. I think that it's again stuck like 100 block behind again.

Probably Iquidus is not the most efficient setup for long chains, I agree with you.

Good point.  He could possibly investigate other explorer branches - but so far I see Dash-Green is also running iquidis.  MIP maybe you can find out what explorer Dash uses when you have a free minute.

[bible_pay]

** DETERMINISTIC SANCS / GIN / PROD **


I promised to mention the status of Prod/dip3 and Deterministic sancs upgrade.

So our prod chain has voted in dip3 successfully, and we will soon be able to continue upgrading to deterministic sancs in prod.

But I would like to make one small change to the schedule.

Since it is so late into July, and our superblock is near, lets postpone the deterministic sancs upgrade until August (after our July superblock pays out).

I will modify the schedule now.

https://wiki.biblepay.org/Evolution_Upgrade

[togoshigekata]

https://chainz.cryptoid.info/bbp/
http://explorer.biblepay.org/

Updated explorer to latest version, performed an erasechain, its synced back up now

I think its been pretty reliable, and I think its good to have a backup explorer (from our history)
Id be totally fine with the url being set to the chainz one though
and I will gladly pass on the job of running the 2nd explorer to anyone interested!
(or if there is some other service we could use)

Iquidus explorer is slow, and has higher costs
Chainz explorer is fast, and has more features

Note: Theres a guy working on multithreading (clustering) Iquidus if anyone is interested to help him
https://github.com/iquidus/explorer/pull/257

This is more related to some prior projects - not iquidis, but its worth a try, could you try this in the config:
rpcthreads=500
litemode=1

And resync?  
I was under the impression with Evo we were communicating much faster with Iquidis (I remember you said there is a big difference), but apparently iquidis gets hung occasionally.

So also could you clarify if the node itself is stuck 200 blocks behind, or is it iquidis that ceases to sync?  (If its not the node, there is no need to resync the entire chain, if its iquidis we would just resync the iquidis database.  But the rpc settings might help if its too dumb to recover).  Maybe the daemon is dying, maybe research how to persistenly keep the daemon running also.

The daemon is running fine, its fully synced, checked blockhashes
(Theres a crontab firing every 5 minutes to make sure its running and restart it if it isnt)

I checked mongodb, log file was 5.3GB, not sure if that is slowing things down, deleted it
I edited the mongod.conf file to try to limit the logging [set quiet to enabled]
(easy worst case I can add a crontab to just delete the log file every day)

Running everything again, everything is going, but the website is not updating with latest blocks, weird,
but if you type in a block number it will show/load it

I started looking into the indexing process more, and it fires off and then disappears quick,
I sent the output to a file, theres an error in Iquidus

Code:

/home/explorer/lib/explorer.js:310
      if (vout[0].scriptPubKey.type == 'nonstandard') {
                 ^
 
TypeError: Cannot read property 'scriptPubKey' of undefined
    at /home/explorer/lib/explorer.js:310:18
    at Object.loop.next (/home/explorer/lib/explorer.js:194:24)
    at Object.module.exports.syncLoop (/home/explorer/lib/explorer.js:205:10)
    at Object.module.exports.prepare_vout (/home/explorer/lib/explorer.js:284:20)
    at /home/explorer/lib/database.js:141:17
    at /home/explorer/lib/explorer.js:392:14
    at Object.loop.next (/home/explorer/lib/explorer.js:194:24)
    at Object.module.exports.syncLoop (/home/explorer/lib/explorer.js:205:10)
    at Object.module.exports.prepare_vin (/home/explorer/lib/explorer.js:369:20)
    at /home/explorer/lib/database.js:140:15
    at Request._callback (/home/explorer/lib/explorer.js:107:14)
    at Request.self.callback (/home/explorer/node_modules/request/request.js:187:22)
    at emitTwo (events.js:87:13)
    at Request.emit (events.js:172:7)
    at Request.<anonymous> (/home/explorer/node_modules/request/request.js:1044:10)
    at emitOne (events.js:77:13)

Looks like its happening in the 3rd parameter, an anonymous function, getting passed into syncLoop()

prepare_vout():
https://github.com/iquidus/explorer/blob/master/lib/explorer.js#L310

syncLoop():
https://github.com/iquidus/explorer/blob/c8ac131aed4f065b4f327ec379eaef2a006e5f50/lib/explorer.js#L169

Looks like this guy ran into similar issue
https://github.com/iquidus/explorer/issues/60
and posted this solution: https://github.com/cryptorex/bitcoinz-explorer/commit/267a0dfd8015bc90488b2b53ae9c49be2da83bff
Ill try adding it and report back

===

Iquidus Block Explorer Guide
https://www.reddit.com/r/BiblePay/comments/7elm7r/iquidus_block_explorer_guide/

===

Options:
1. Try to pinpoint the bug
2. Reset the mongo database to last backup and sync from there
3. Reset the mongo database entirely and sync from the beginning
4. Retire the explorer
5. Change URL to point to Chainz
6. Find and setup 2nd explorer service

[bible_pay]

https://chainz.cryptoid.info/bbp/
http://explorer.biblepay.org/

Updated explorer to latest version, performed an erasechain, its synced back up now

I think its been pretty reliable, and I think its good to have a backup explorer (from our history)
Id be totally fine with the url being set to the chainz one though
and I will gladly pass on the job of running the 2nd explorer to anyone interested!
(or if there is some other service we could use)

Iquidus explorer is slow, and has higher costs
Chainz explorer is fast, and has more features

Note: Theres a guy working on multithreading (clustering) Iquidus if anyone is interested to help him
https://github.com/iquidus/explorer/pull/257

This is more related to some prior projects - not iquidis, but its worth a try, could you try this in the config:
rpcthreads=500
litemode=1

And resync?  
I was under the impression with Evo we were communicating much faster with Iquidis (I remember you said there is a big difference), but apparently iquidis gets hung occasionally.

So also could you clarify if the node itself is stuck 200 blocks behind, or is it iquidis that ceases to sync?  (If its not the node, there is no need to resync the entire chain, if its iquidis we would just resync the iquidis database.  But the rpc settings might help if its too dumb to recover).  Maybe the daemon is dying, maybe research how to persistenly keep the daemon running also.

The daemon is running fine, its fully synced, checked blockhashes
(Theres a crontab firing every 5 minutes to make sure its running and restart it if it isnt)

I checked mongodb, log file was 5.3GB, not sure if that is slowing things down, deleted it
I edited the mongod.conf file to try to limit the logging [set quiet to enabled]
(easy worst case I can add a crontab to just delete the log file every day)

Running everything again, everything is going, but the website is not updating with latest blocks, weird,
but if you type in a block number it will show/load it

I started looking into the indexing process more, and it fires off and then disappears quick,
I sent the output to a file, theres an error in Iquidus

Code:

/home/explorer/lib/explorer.js:310
      if (vout[0].scriptPubKey.type == 'nonstandard') {
                 ^
 
TypeError: Cannot read property 'scriptPubKey' of undefined
    at /home/explorer/lib/explorer.js:310:18
    at Object.loop.next (/home/explorer/lib/explorer.js:194:24)
    at Object.module.exports.syncLoop (/home/explorer/lib/explorer.js:205:10)
    at Object.module.exports.prepare_vout (/home/explorer/lib/explorer.js:284:20)
    at /home/explorer/lib/database.js:141:17
    at /home/explorer/lib/explorer.js:392:14
    at Object.loop.next (/home/explorer/lib/explorer.js:194:24)
    at Object.module.exports.syncLoop (/home/explorer/lib/explorer.js:205:10)
    at Object.module.exports.prepare_vin (/home/explorer/lib/explorer.js:369:20)
    at /home/explorer/lib/database.js:140:15
    at Request._callback (/home/explorer/lib/explorer.js:107:14)
    at Request.self.callback (/home/explorer/node_modules/request/request.js:187:22)
    at emitTwo (events.js:87:13)
    at Request.emit (events.js:172:7)
    at Request.<anonymous> (/home/explorer/node_modules/request/request.js:1044:10)
    at emitOne (events.js:77:13)

Looks like its happening in the 3rd parameter, an anonymous function, getting passed into syncLoop()

prepare_vout():
https://github.com/iquidus/explorer/blob/master/lib/explorer.js#L310

syncLoop():
https://github.com/iquidus/explorer/blob/c8ac131aed4f065b4f327ec379eaef2a006e5f50/lib/explorer.js#L169

Looks like this guy ran into similar issue
https://github.com/iquidus/explorer/issues/60
and posted this solution: https://github.com/cryptorex/bitcoinz-explorer/commit/267a0dfd8015bc90488b2b53ae9c49be2da83bff
Ill try adding it and report back

===

Iquidus Block Explorer Guide
https://www.reddit.com/r/BiblePay/comments/7elm7r/iquidus_block_explorer_guide/

===

Options:
1. Try to pinpoint the bug
2. Reset the mongo database to last backup and sync from there
3. Reset the mongo database entirely and sync from the beginning
4. Retire the explorer
5. Change URL to point to Chainz
6. Find and setup 2nd explorer service

1)  Can you try applying this .js patch to the code right above the .type == 'nonstandard' in explorer.js and burn it in?
https://github.com/DeckerSU/explorer/commit/ac74e41c6162871fcaa6973d34f09f1cf3e5a1ce
If it works we can either find zcashs iquidis branch, and use it, or patch it based on a config setting in Iquidis' settings and push it to their github.

2) Are you going to address my comment about the PMs and emails?

[bible_pay]

If anyone is interested in Ken Peters "I saw the Tribulation" (and personally, I think it is very valuable and prophetic), I found this transcript of it:

https://z3news.com/w/ken-peters-tribulation/

Keep in mind he saw this in 1980 which is even more fascinating.

[Borgholio]

Two of my machines that I started with -erasechain=1 yesterday have again come out of sync.  I'm doing erasechain again but I'm wondering if this is caused by explorer.biblepay.org being stuck?

Let's try to find the root cause.  Do you happen to have the log of one of the machines before it went out of sync?

B) Is this machine running with litemode=1? 

We need to see if the machine is having trouble getting gov data.
Do you have tons of banned peers in the peers list?

They're not running in litemode, I'll try that if it happens again.  I'll also get a copy of the logs and check the banned peers too and let you know.  Thanks!

[bible_pay]

** Today's Goal **

- We are currently running 1.4.4.3. 
- We successfully support funded and non funded mining.  I think the ABN endeavor is turning out to be a success, as we are attracting new users, and this environment is satisfying both newbies who do not want to hold bbp and satisfying old-timers who want to provide the ABNs.
- The pool is still running in protocol v1.0.
- Some log spam exists related to ABN/funded mining activing, checkblock errors due to stale blocks from the pool, and some nodes seem to get banned occasionally.

Proposed Solution:
- Release pool mining protocol version 2.0.  This allows funded or non-funded mining in the pool without limitations, and provides more accurate health info.
- Remove log spam.
- Ensure blocks from the pool are not causing log spam issues.  Address any pool checkblockvaliditylite errors.  Ensure miners are not being d-dossed for bad block nBits or blockheaders.

I will notify when the new version is ready.  This is a leisure upgrade.

** Near Term Future **

- Update the roadmap goals for Q3.  Share the BiblePay goals (as related to Christian Spaces/HTML5) with the forum. 
- Make the users aware of a new project we will implement towards the end of the year and how they can help with this project.