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

[sunk818]

Fixed in the next version; we now respect the non-biblepay-team-percentage spork, and will not show the warning.

So can I disregard this warning and stay with non biblepay team ?
Or need to wait for the fix?

Yes. grcpool1,2,3 have been receiving BBP as far as I know for a few weeks now.

[bible_pay]

Fixed in the next version; we now respect the non-biblepay-team-percentage spork, and will not show the warning.

So can I disregard this warning and stay with non biblepay team ?
Or need to wait for the fix?

Yes, please disregard the warning.  We should also have a report in the pool also to show all members not in team biblepay :
Reports | Superblock View | Superblock View Non Biblepay

[bible_pay]

How can we see the reconciliation page which shows the charitable income and expenses?

http://accountability.biblepay.org/

On left side, Accountability will show you Expenses and Revenue submenu. Also note that the date sorting is opposite. One is ascending and the other is descending by date. A little confusing, but its all there.

Also, please try Business Objects | Expense | List from the core wallet.

And also, Revenue List.

Also- exec theymos.

[coinsinspect]

I thought the team limit removed, I changed team and I am getting this:
Warning": "CPID xxxxxx not in team Biblepay. This CPID is not receiving rewards for cancer research.

This is a client display bug,   (error is hardcoded into the client).   Check PODC Status page for more current info

Edit:  What is the command you're running and getting this error from?

getboincinfo on Linux

wallet version: 1.1.5.9

EDIT: same for 1.1.6.1 on Linux, I don't have GUI.

Fixed in the next version; we now respect the non-biblepay-team-percentage spork, and will not show the warning.

my masternode connected to same wallet is in this mode since team change: WATCHDOG_EXPIRED

masternode debug.log shows this for every watchman call (once per minute) :
2018-12-15 14:40:27 ERROR: ContextualCheckBlock: CPID Signature empty.

[thesnat21]

I thought the team limit removed, I changed team and I am getting this:
Warning": "CPID xxxxxx not in team Biblepay. This CPID is not receiving rewards for cancer research.

This is a client display bug,   (error is hardcoded into the client).   Check PODC Status page for more current info

Edit:  What is the command you're running and getting this error from?

getboincinfo on Linux

wallet version: 1.1.5.9

EDIT: same for 1.1.6.1 on Linux, I don't have GUI.

Fixed in the next version; we now respect the non-biblepay-team-percentage spork, and will not show the warning.

my masternode connected to same wallet is in this mode since team change: WATCHDOG_EXPIRED

masternode debug.log shows this for every watchman call (once per minute) :
2018-12-15 14:40:27 ERROR: ContextualCheckBlock: CPID Signature empty.

Strange what version of the client is your MN running?

[coinsinspect]

I thought the team limit removed, I changed team and I am getting this:
Warning": "CPID xxxxxx not in team Biblepay. This CPID is not receiving rewards for cancer research.

This is a client display bug,   (error is hardcoded into the client).   Check PODC Status page for more current info

Edit:  What is the command you're running and getting this error from?

getboincinfo on Linux

wallet version: 1.1.5.9

EDIT: same for 1.1.6.1 on Linux, I don't have GUI.

Fixed in the next version; we now respect the non-biblepay-team-percentage spork, and will not show the warning.

my masternode connected to same wallet is in this mode since team change: WATCHDOG_EXPIRED

masternode debug.log shows this for every watchman call (once per minute) :
2018-12-15 14:40:27 ERROR: ContextualCheckBlock: CPID Signature empty.

Strange what version of the client is your MN running?

masternode and windows controller wallet are both 1.1.6.1
controller wallet is also connected to boinc

[bible_pay]

I thought the team limit removed, I changed team and I am getting this:
Warning": "CPID xxxxxx not in team Biblepay. This CPID is not receiving rewards for cancer research.

This is a client display bug,   (error is hardcoded into the client).   Check PODC Status page for more current info

Edit:  What is the command you're running and getting this error from?

getboincinfo on Linux

wallet version: 1.1.5.9

EDIT: same for 1.1.6.1 on Linux, I don't have GUI.

Fixed in the next version; we now respect the non-biblepay-team-percentage spork, and will not show the warning.

my masternode connected to same wallet is in this mode since team change: WATCHDOG_EXPIRED

masternode debug.log shows this for every watchman call (once per minute) :
2018-12-15 14:40:27 ERROR: ContextualCheckBlock: CPID Signature empty.

Strange what version of the client is your MN running?

masternode and windows controller wallet are both 1.1.6.1
controller wallet is also connected to boinc

Its probably just a coincidence, Ive had that issue occasionally but it always resolves itself after a couple hours.  However to see for sure if your watchman on the wall is running properly:

cd ~/.biblepaycore/watchman
./venv/bin/python bin/watchman.py


See if that command returns an empty string.  If so watchman is set up correctly.  (If your installation is in a different place type : crontab -e      then copy the command out of the crontab and run that instead).


If not that is the problem, then paste the error.

[coinsinspect]

I thought the team limit removed, I changed team and I am getting this:
Warning": "CPID xxxxxx not in team Biblepay. This CPID is not receiving rewards for cancer research.

This is a client display bug,   (error is hardcoded into the client).   Check PODC Status page for more current info

Edit:  What is the command you're running and getting this error from?

getboincinfo on Linux

wallet version: 1.1.5.9

EDIT: same for 1.1.6.1 on Linux, I don't have GUI.

Fixed in the next version; we now respect the non-biblepay-team-percentage spork, and will not show the warning.

my masternode connected to same wallet is in this mode since team change: WATCHDOG_EXPIRED

masternode debug.log shows this for every watchman call (once per minute) :
2018-12-15 14:40:27 ERROR: ContextualCheckBlock: CPID Signature empty.

Strange what version of the client is your MN running?

masternode and windows controller wallet are both 1.1.6.1
controller wallet is also connected to boinc

Its probably just a coincidence, Ive had that issue occasionally but it always resolves itself after a couple hours.  However to see for sure if your watchman on the wall is running properly:

cd ~/.biblepaycore/watchman
./venv/bin/python bin/watchman.py


See if that command returns an empty string.  If so watchman is set up correctly.  (If your installation is in a different place type : crontab -e      then copy the command out of the crontab and run that instead).


If not that is the problem, then paste the error.

it seems to be resolved.
many thanks for your quick support.

[bible_pay]

OP Post has been updated to the nicer version.

Please give credit to Togo and Yeshua for giving us the infrastructure.

[SVK Noko]

One short question. When will the new POG concept start running?

Thanks.

[slovakia]

OP Post  
omg what is it?

SVK Noko i hope never,when nobody knows answer for my questions

[capulo]

please dont make some upgrades over xmas like last year it was neverending compiling and deploying marathon

[SVK Noko]

please dont make some upgrades over xmas like last year it was neverending compiling and deploying marathon

In worst case just switch over CPU power to another coin and keep MN running only :-) thats my emergency plan.

[thesnat21]

I don't see this being ready that quickly, i'm not sure if there is a specific timeline.

[bible_pay]

I don't see this being ready that quickly, i'm not sure if there is a specific timeline.

Rough Timeline:

1.  Test POG in the testnet thread for 25 more days.  Ensure all bugs are addressed, if not continue longer.
2.  Enter a Production Sanctuary Proposal to propose that we promote POG to PROD with the following characteristics:
     Expand POBH to be POG/POBH, using POBH (heat miner) rewards to pay the POG budget (IE 450~ bbp per block).
3.  Around end of January 2019, if the Sanc Proposal passes, decide on the mandatory upgrade date.  Note that doing this requires CoinExchange to approve the date.
  If they do not we would need to wait until March 30, 2019 to do this step.
4.  Run this new POG algorithm in Prod for 90 days.  Record our user baseline and POG difficulty and monitor user metrics very closely.
5.  Evaluate the results to determine if POG should be considered in a bigger scope for easy adoption.

In summary:  It would be between Feb 1 2019 - March 30 2019.

NOTE: We can use more help in the testnet thread - we are finding and solving all the bugs, but I would like to see the difficulty higher in testnet and also have more hot sancs in testnet.

[slovakia]

Rob any info about stratis?

[togoshigekata]

any info about stratis?

October Update
https://wiki.biblepay.org/October_Update
"deprioritization of Stratis. This is primarily because Rob believes that Stratis is still in a volatile state, and those devs are working hard to bring it up to the level of Bitcoin"

November Update
https://forum.biblepay.org/index.php?topic=292.0
"One major change to our roadmap is our official position on Stratis. Although we still stand behind stratis and their core mission, and wish to remain informed and align ourselves with the potential value in the stratis codebase, many factors influence using stratis-c# as the primary production platform. The considerations being evaluated include: The latest bitcoin security commits, segwit, BLS and BLS secret-sharing, Dash's evolution commits, the lightning network, on chain storage, etc. In general, I want to first give kudos to the main devs of stratis. They are doing something almost impossible in order to get stratis to be compatible with the latest bitcoin version. Where we have to make our decision however, is weighing the benefits of the most cutting edge - to be released features in bitcoin and dash. Biblepay has discovered that it needs certain boilerplate abilities, and, pending IPFS integration, maps to IPFS, Segwit and potentially some of the latest Dash features (for reasons explained later).

Additionally, there are over 100 features that have been added to bitcoin and dash-QT, that the existing features users have become very accustomed to (for example coin control), the HD wallets supporting features, etc. In light of this, I will be recommending that we adjust our roadmap to move stratis to 'R&D (research and development)' for future consideration and integration, but we move the Dash rebase to our more short term priorities. The goal is for us to do the due diligence on rebasing biblepay to have the latest dash features, so that we can leverage some of the latest features to store our IPFS relationship in a more resilient manner (IE our business objects). In summary, this means pushing Stratis out to 2022 and considering it an R&D project, and moving Dash Rebase to June 2019. Also relying on Dash's release as our PR event to be released with any other large BBP feature that is worthy of a giant PR event."

[bible_pay]

One of our community members, Frances has written a summary about investing in Crypto called "Absolute Beginners Guide to CryptoCurrency Investing – Frances Doxtator".

Maybe new users will find this useful:

I have added it to our Guides section under Investing on our web site here:

http://www.biblepay.org/userguides/

[secoccular]

One of our community members, Frances has written a summary about investing in Crypto called "Absolute Beginners Guide to CryptoCurrency Investing – Frances Doxtator".

Maybe new users will find this useful:

I have added it to our Guides section under Investing on our web site here:

http://www.biblepay.org/userguides/

Nice work. It's difficult to write about the subject, as quickly as things change. For instance, this sentence from the article: "Note that crypto is now in a huge bull market".

[slovakia]

POG works full automaticly in testnet mode: FINALLY ... it will be easy way for newbies

Robert: good job