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

[bible_pay]

I found a tweet where we got mentioned by a PhD Computer Scientist at an ACM conference in London
https://twitter.com/Maryammjd/status/1193931668136103937

SSR'19: The 5th Conference on Security Standardisation Research
https://dl.acm.org/citation.cfm?id=3353551

She has us on the projector at the conference!?  Thats very cool.

I'm glad to see what we're doing is not in vain.

God has a master plan....

[bible_pay]

Kairos 2019 Christmas Party

Andy sent these pics and videos over (of the Christmas Party):

https://pool.biblepay.org/SAN/Mission/Kairos/Kairos1/20191218_151157.mp4
https://pool.biblepay.org/SAN/Mission/Kairos/Kairos1/20191218_152409.jpg
https://pool.biblepay.org/SAN/Mission/Kairos/Kairos1/20191218_153433.jpg

[bible_pay]

BiblePay - MainNet
1.4.8.4 - Mandatory Christmas 2019 Upgrade @ 166075


- Merge in all Dash Prod 0.14 branch code and fixes up to Nov 2019

- Merge in PODC 2.0 and DWS and ExternalPurse and DSQL and Decentralized
Web surfing and Kairos Childrens Fund (POOM) and ChainLocks and
Deterministic Sancs and IX autolocks and IX fixes

- Merge in improved POBH internal solo miner (brings solo mining to 90%+
compared to external miner)

- Go live height is block 166075 (approx 12/26/2019)

Reddit Summary Post:
https://www.reddit.com/r/BiblePay/comments/echya3/biblepay_v1484_mandatory_christmas_2019_upgrade/

Congrats on the update Rob and MIP!
And thank you oncoapop, sun, cap, orbis, tailsman and anyone else who helped!

Nice!  This explains a lot to the user.

[bible_pay]

A user in discord asked what makes BiblePay unique,
I did my best to try to answer him, and that led me to wanting to write an article about it

This is my draft for the questions, What is BiblePay? and What makes BiblePay unique?
https://pastebin.com/LM2DgK6H

Any and all feedback welcome!

=

The goal is for someone just sort of browsing us, without having to dig in too much, figure our our selling points

Rob your Nutritional Information wiki is a fantastic resource for this, it really does already answer the uniqueness question, in amazing detail!

https://wiki.biblepay.org/Nutrition_Information

Thanks, I also noticed those matrices were valuable in conveying complicated gospel topics, especially where they are debatable.
I made one recently for the Rapture, which I haven't posted yet:

https://wiki.biblepay.org/Rapture_Study

Notice how much clarity you can add when you balance the viewpoint either way. 


I will circle back and edit the Nutritional Guide asap with our new features, but first I promised to release information on:  BiblePay dimensions, todo list, use-cases and short-term goals (BestBuy and Direct Mail and greeting cards, direct mail letters from the rpc, etc).

[bible_pay]

** BIBLEPAY DIMENSIONS **

This is one area I feel we will need to spearhead a new project to dedicate ourselves to finding the 'solid use case' for BiblePay, to achieve a 100% score on the first dimension:

https://wiki.biblepay.org/Dimensions


I'm now in the process of creating a new Use cases document and an online Todo list.  The Todo list simply shows items dynamically that IT is working on - things that are happening that didn't fit the github list.  

The Use Cases list will attempt to show all of the potential paths, but of course some will be blocked due to impossible challenges, resource availability, and partner failures.  But I am confident that we will zero in on some excellent ones that will not only be possible but will be become a reality for BiblePay.  

[bible_pay]

is the chain healthy? some saying they got on a fork.

Yeah, diff is still 177,000.

I don't see any signs of it.

[bible_pay]

** The integrity of Biblepay has always been in good standing **


We have receive 2,742 pages of inbound letters, written by our sponsored children to BIBLEPAY.

Obviously, anyone who has ever accused us of sponsoring false children is a false accuser.

In the spirit of providing transparency I will migrate all these letters over to BMS next so we can quickly leaf through them.  And of course, I don't want us to lose these precious letters that took time for each child to write.

Another way to 'provably' complete the equation that we sponsored a child for N duration is to tie the inbound letter to the hex-id code and randomly check for a childs inbound letter in the future.

[bible_pay]

I mentioned the other day that we would be adding the orphan list and orphan collage to dsql (the post is missing on bitcointalk).

We have added the orphan list and orphan collage to DSQL.
We also added SEO to DSQL.

Therefore google can now spider DSQL.

Once we see this in the google cache, then we can test to see if our traffic increases.

[bible_pay]

is the chain healthy? some saying they got on a fork.

Yeah, diff is still 177,000.

I don't see any signs of it.

did you upgrade all your nodes to latest?
what about those that did not?

Looking at the Mandatory upgrade post, the cutover height is not until 166075.

[bible_pay]

** The integrity of Biblepay has always been in good standing **


We have receive 2,742 pages of inbound letters, written by our sponsored children to BIBLEPAY.

Obviously, anyone who has ever accused us of sponsoring false children is a false accuser.

In the spirit of providing transparency I will migrate all these letters over to BMS next so we can quickly leaf through them.  And of course, I don't want us to lose these precious letters that took time for each child to write.

Another way to 'provably' complete the equation that we sponsored a child for N duration is to tie the inbound letter to the hex-id code and randomly check for a childs inbound letter in the future.

Ok, Childrens inbound letters have been migrated to:

https://web.biblepay.org

Orphans | Orphan Inbound Letters

As usual, you can also search by typing a phrase in the upper right search box.

[bible_pay]

** Solid Use-Case - Dash IX through BBP IX **

So, I stumbled across this site yesterday:  https://www.bitrefill.com/
They had high reviews from Dash, from people who were buying digital gift cards (these are sent directly to your e-mail box, and then you can buy whatever you want once you have that).

So, the idea here is the Dash, with its millions of $ of integration already completed, already has a massive amount of support in almost every area, buying gift cards, physical products, delivering physical products etc.  

In light of that, our most straightforward and useful feature would be a method to instantly send a DASH instantsend transaction to a recipient from the BBP wallet (using BBP funds via instantsend).

It would work like this.  Take bitrefill for example, they sell an amazon $20 gift card that is delivered in 1 minute to your email address.  You browse, and buy it and select "Dash" as the payment method.  A screen appears asking to send DASH to the DASH receive address.  At this point you have 15 mins to get into dash and send the funds.  Once you send the funds, the e-delivery occurs within 1 minute to your inbox.

So what we want to do, is provide an rpc command, something like "dashpay receiveaddress amount".  What we will do is send the amount in DASH to the DASH receive address, via instant send.   (The command will return a DASH transactionID.  Then you can track the transactionid (If necessary) via the Dash BX).    Theoretically, this would allow any BBP user to make an instant purchase and then we would be instantly as useful as dash.  Of crouse, we will need to put an initial limit on this for safety (IE $25 per transaction).  I believe this is theoretically possible, using instantsend, by requiring a lock on the transaction from a masternode.  (IE we can safely relay the funds out to the recipient, and not worry about a double spend, as long as our advanced checks pass - etc).

Ill look into this feature next.  This sounds like it would theoretically plug most of the hole in BBP's dimension doc.  We can consider Dash our big brother.  

[sunk818]

is the chain healthy? some saying they got on a fork.

Yeah, diff is still 177,000.

I don't see any signs of it.

did you upgrade all your nodes to latest?
what about those that did not?

Looking at the Mandatory upgrade post, the cutover height is not until 166075.

I've been away and still running 1484. I saw that my wallet had a lot of mined blocks and these warnings saying blocks have unexpected version, bad lexical cast, and block heights that do not match explorer.biblepay.org nor chainz. I'm about 15 blocks behind.

I had 20 blocks that were found on the wrong chain: http://sunpool.whitewalr.us/tbs

The difficulty has been under 100k recently as far I can tell.

Apparently, there's been a spike of orphans lately too.




2019-12-22 20:20:28 {PNB}: ACC  UpdateTip: new best=255568dadbe9913d94e18fa4378adc773d35643a4fbd7166877339cc02c04925 height=165102 version=0x20000000 log2_work=60.05644645 tx=1186215 date='2019-12-22 20:08:47' progress=0.999994 cache=0.0MiB(0txo) warning='4 of last 100 blocks have unexpected version'
2019-12-22 20:20:29 {PNB}: ACC  caught cdbl bad lexical cast 1 from </html> with 0.000000UpdateTip: new best=ce781a158c37e79d86340d70923030bedda334b57ffa80c7b1d55e51549d02ed height=165103 version=0x20000000 log2_work=60.05644873 tx=1186217 date='2019-12-22 20:22:47' progress=0.999999 cache=0.0MiB(0txo) warning='3 of last 100 blocks have unexpected version'
2019-12-22 20:23:48 {PNB}: ACC  caught cdbl bad lexical cast 1 from </html> with 0.000000Misbehaving: 45.76.120.35:40000 peer=17 (0 -> 1)
2019-12-22 20:19:12 ERROR: ConnectBlock(): ProcessSpecialTxsInBlock for block 81e8883fdb4c065ff6c6de64e169fa0730e8b15d3e3c7dc2988939cdbeab82bd failed with bad-qc-invalid-null (code 16)

[bible_pay]

** Solid Use-Case - Dash IX through BBP IX **

That's a great idea. Atomic swap in-wallet would be awesome. Who until then trades the BBP for DASH? A bot on SX? Would a smart contract on the BBP and DASH network be able to automate trading somehow between their respective wallets?

There's a great angle for Africa as well. Many are using Amazon gift cards as a way to get BTC as it is more stable than their native fiat:
https://bitcoinmagazine.com/articles/bitcoin-and-gift-cards-are-powering-a-million-dollar-remittance-market-in-africa

Yeah, it seems like one of the exciting ones.  It sort of Trumps some of the things Ive been working on (trying to integrate with the best buy API).

Give me a little time to try to explain the IX to IX conversion.  I'm going to work on this next.

Also, I've got to share the idea about becoming a decentralized online church.

[bible_pay]

is the chain healthy? some saying they got on a fork.

Yeah, diff is still 177,000.

I don't see any signs of it.

did you upgrade all your nodes to latest?
what about those that did not?

Looking at the Mandatory upgrade post, the cutover height is not until 166075.

I've been away and still running 1484. I saw that my wallet had a lot of mined blocks and these warnings saying blocks have unexpected version, bad lexical cast, and block heights that do not match explorer.biblepay.org nor chainz. I'm about 15 blocks behind.

I had 20 blocks that were found on the wrong chain: http://sunpool.whitewalr.us/tbs

The difficulty has been under 100k recently as far I can tell.

Apparently, there's been a spike of orphans lately too.




2019-12-22 20:20:28 {PNB}: ACC  UpdateTip: new best=255568dadbe9913d94e18fa4378adc773d35643a4fbd7166877339cc02c04925 height=165102 version=0x20000000 log2_work=60.05644645 tx=1186215 date='2019-12-22 20:08:47' progress=0.999994 cache=0.0MiB(0txo) warning='4 of last 100 blocks have unexpected version'
2019-12-22 20:20:29 {PNB}: ACC  caught cdbl bad lexical cast 1 from </html> with 0.000000UpdateTip: new best=ce781a158c37e79d86340d70923030bedda334b57ffa80c7b1d55e51549d02ed height=165103 version=0x20000000 log2_work=60.05644873 tx=1186217 date='2019-12-22 20:22:47' progress=0.999999 cache=0.0MiB(0txo) warning='3 of last 100 blocks have unexpected version'
2019-12-22 20:23:48 {PNB}: ACC  caught cdbl bad lexical cast 1 from </html> with 0.000000Misbehaving: 45.76.120.35:40000 peer=17 (0 -> 1)
2019-12-22 20:19:12 ERROR: ConnectBlock(): ProcessSpecialTxsInBlock for block 81e8883fdb4c065ff6c6de64e169fa0730e8b15d3e3c7dc2988939cdbeab82bd failed with bad-qc-invalid-null (code 16)

Can you please try upgrading next?  Ive already upgraded my sancs and home node, and the exchanges have upgraded, so at this point it would be counterproductive for me to downgrade just to see if they are on a fork.  We can ask others, if anyone else is running the old version if they are going on a fork?

Whats very possible is that once 51% of the sancs moved to the new version (70750), it probably became the defacto.  You can see if your 'exec health' disagrees on the old version with the new version, but I just recommend upgrading now.

Btw, I plan on enabling Kairos later today, so please watch so we can start sponsoring after that.  As I feel we will have a lot to do starting tomorrow to roll out WCG.  I plan on enabling WCG tomorrow.

[jaapgvk]

is the chain healthy? some saying they got on a fork.

Yeah, diff is still 177,000.

I don't see any signs of it.

did you upgrade all your nodes to latest?
what about those that did not?

Looking at the Mandatory upgrade post, the cutover height is not until 166075.

I've been away and still running 1484. I saw that my wallet had a lot of mined blocks and these warnings saying blocks have unexpected version, bad lexical cast, and block heights that do not match explorer.biblepay.org nor chainz. I'm about 15 blocks behind.

I had 20 blocks that were found on the wrong chain: http://sunpool.whitewalr.us/tbs

The difficulty has been under 100k recently as far I can tell.

Apparently, there's been a spike of orphans lately too.




2019-12-22 20:20:28 {PNB}: ACC  UpdateTip: new best=255568dadbe9913d94e18fa4378adc773d35643a4fbd7166877339cc02c04925 height=165102 version=0x20000000 log2_work=60.05644645 tx=1186215 date='2019-12-22 20:08:47' progress=0.999994 cache=0.0MiB(0txo) warning='4 of last 100 blocks have unexpected version'
2019-12-22 20:20:29 {PNB}: ACC  caught cdbl bad lexical cast 1 from </html> with 0.000000UpdateTip: new best=ce781a158c37e79d86340d70923030bedda334b57ffa80c7b1d55e51549d02ed height=165103 version=0x20000000 log2_work=60.05644873 tx=1186217 date='2019-12-22 20:22:47' progress=0.999999 cache=0.0MiB(0txo) warning='3 of last 100 blocks have unexpected version'
2019-12-22 20:23:48 {PNB}: ACC  caught cdbl bad lexical cast 1 from </html> with 0.000000Misbehaving: 45.76.120.35:40000 peer=17 (0 -> 1)
2019-12-22 20:19:12 ERROR: ConnectBlock(): ProcessSpecialTxsInBlock for block 81e8883fdb4c065ff6c6de64e169fa0730e8b15d3e3c7dc2988939cdbeab82bd failed with bad-qc-invalid-null (code 16)

Can you please try upgrading next?  Ive already upgraded my sancs and home node, and the exchanges have upgraded, so at this point it would be counterproductive for me to downgrade just to see if they are on a fork.  We can ask others, if anyone else is running the old version if they are going on a fork?

Whats very possible is that once 51% of the sancs moved to the new version (70750), it probably became the defacto.  You can see if your 'exec health' disagrees on the old version with the new version, but I just recommend upgrading now.

Btw, I plan on enabling Kairos later today, so please watch so we can start sponsoring after that.  As I feel we will have a lot to do starting tomorrow to roll out WCG.  I plan on enabling WCG tomorrow.

I didn't upgrade my sanctuaries yet, and it seems that they are on a lower blockheight than my upgraded wallets. Will upgrade now.

[sunk818]

Can you please try upgrading next?  Ive already upgraded my sancs and home node, and the exchanges have upgraded, so at this point it would be counterproductive for me to downgrade just to see if they are on a fork.  We can ask others, if anyone else is running the old version if they are going on a fork?
...
Btw, I plan on enabling Kairos later today, so please watch so we can start sponsoring after that.  As I feel we will have a lot to do starting tomorrow to roll out WCG.  I plan on enabling WCG tomorrow.

Upgrade works fine. The expectation from the previous communication about 1.4.8.4 was that 1.4.5.3 should work until the mandatory cutover block height. This doesn't seem to the case. Its not a big deal because the cutover height will arrive shortly, but it'd be nice to help wallet users plan better.

Great news on WCG and Kairos. Let me know when Kairos is enabled. I'll be out of town, but will try to configure ASAP.

Merry Christmas to you and everyone else reading this post.

[bible_pay]

Can you please try upgrading next?  Ive already upgraded my sancs and home node, and the exchanges have upgraded, so at this point it would be counterproductive for me to downgrade just to see if they are on a fork.  We can ask others, if anyone else is running the old version if they are going on a fork?
...
Btw, I plan on enabling Kairos later today, so please watch so we can start sponsoring after that.  As I feel we will have a lot to do starting tomorrow to roll out WCG.  I plan on enabling WCG tomorrow.

Upgrade works fine. The expectation from the previous communication about 1.4.8.4 was that 1.4.5.3 should work until the mandatory cutover block height. This doesn't seem to the case. Its not a big deal because the cutover height will arrive shortly, but it'd be nice to help wallet users plan better.

Great news on WCG and Kairos. Let me know when Kairos is enabled. I'll be out of town, but will try to configure ASAP.

Merry Christmas to you and everyone else reading this post.

Correct, the code was supposed to be compatible until the cutover height; there is no flaw in the code.
In addition it was written so to remain compatible even with the upgraded sancs.

However there is a DASH rule, where once 60% upgrade to the new governance protoversion, the old governance protoversion is no longer respected.

So, I believe this is a unique case, because we had a mandatory for the gov-protoversion to increase at the same time the wallet version increased.

If this ever comes up again, we will say:  "By the height" or "when 60% of the sancs upgrade" whichever comes sooner- and we will have to monitor the progress.

[togoshigekata]

BiblePay Q4 article posted in Masternode Buzz News!
https://twitter.com/Masternode_Buzz/status/1209077651291459584

Please click like and comment about BiblePay!

DailyBuzz Monday 23 December 2019
https://masternode.buzz/dailybuzz-monday-23-december-2019/

Follow Masternode Buzz:
https://twitter.com/masternode_buzz
https://t.me/MasternodeBuzz
https://discordapp.com/invite/KRkUPJM

Note: Masternode Buzz is Masternode Online

=

Statistics of Newsletter I sent 2 days ago:



https://www.thenewsletterplugin.com/documentation/statistics

"The statistics module tracks two main events: the opening of an email and the clicks on links of an email."

[togoshigekata]

A user in discord asked what makes BiblePay unique,
I did my best to try to answer him, and that led me to wanting to write an article about it

This is my draft for the questions, What is BiblePay? and What makes BiblePay unique?
https://pastebin.com/LM2DgK6H

Any and all feedback welcome!

=

The goal is for someone just sort of browsing us, without having to dig in too much, figure our our selling points

Rob your Nutritional Information wiki is a fantastic resource for this, it really does already answer the uniqueness question, in amazing detail!

https://wiki.biblepay.org/Nutrition_Information

My attempt at grouping things up:

What makes BiblePay unique?

Dash

- Masternodes
--- 2nd Tier network of nodes
--- Instantly send coins
--- Privately send coins
--- Superblocks, Proposal System, Voting
--- Get daily rewards for locking up coins and running one
- Difficulty adjusting every block for mining, also changes rewards

BiblePay

- Charity
--- 10% of all mined coins donated to Charity every month
--- Over $200,000 donated across 4 charities, supporting hundreds of orphans
--- All Revenue and Expenses public: http://accountability.biblepay.org/
--- All Sponsored Orphans public
--- Rewards for writing letters to our orphans
--- Decentralized charity, sponsor orphans directly and get rewarded coins

- CPU Only Mining
--- Anyone can mine coins! Decentralizes mining

- Science Research
--- Rewards for contributing to real science, cancer and disease research
--- Team BiblePay has donated over 30,000 years of CPU time to research

- Two Blockchain/C++ Developers
--- https://www.biblepay.org/cryptoguru/#team
--- Rob is former Founder of Gridcoin (GRC) cryptocurrency

- Fair Launch
--- No Premine, No Instamine
--- Linux and Window miners available
--- Announced on Bitcointalk forum

- No Founder Reward
- Max Supply
--- Larger numbers easier to use
- Emission Schedule
--- Deflationary

- Monthly Budget System
--- Self Funding
--- In-Wallet Proposals

- Merging Dash Code Changes
--- Constant new features and improvements from a larger tech team
--- Chainlocks, now almost impossible to 51% attack BiblePay

- Spreading Christianity
--- Earn coins through Healing Campaign, writing diary entries
--- Earn coins Listening and watching Christian content
--- In-wallet Prayer system
--- In-wallet Bible reader
--- Christian Spaces, hosting christian content so it cant be deleted

- Mobile Phone Wallet

- Generic Smart Contracts
--- Allows new features without disrupting quality of service

- Certificate of Deposit
--- Potentially gain interest on your coins

- Bug Bounty Program

=

Nutrition Information:
https://wiki.biblepay.org/Nutrition_Information

Dimensions
https://wiki.biblepay.org/Dimensions

=

Ranked #30 most replied to thread on Bitcointalk Forum Announcement section:
https://bitcointalk.org/index.php?board=159.0;sort=replies;desc

Ranked #106 cryptocurrency by code commits
https://www.cryptomiso.com/#BBP

Ranked #188 team for contributions to science research
https://www.boincstats.com/stats/-1/team/detail/831912762/overview

=

If anyone wants to write an article on this, please do!
I just plan to write one on my own personal medium account,
Im still not sure which format to use to represent the information and how deep to go
Any and all feedback welcome!

[togoshigekata]

We need help with documentation,
we need fully accurate, up to date, step by step guides:

=

Proof of Work (POW):
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://whitewalr.us/2019/biblepay-nomp-pool-mining.html
https://whitewalr.us/2019/solo-mine-biblepay.html
https://www.biblepay.org/mining/

(Can the regular wallet mine on the NOMP pools? or is external miner still needed?)
EDIT: Answer: Core wallet can only solo mine (there are future plans to add a stratum connector)

=

Proof of Orphan (POOM):
https://wiki.biblepay.org/POOM
https://wiki.biblepay.org/Paying_For_a_POOM_Sponsored_Child
https://whitewalr.us/2019/biblepay-cameroonone-partnership.html
https://whitewalr.us/2019/cameroonone-poom-charity-donation.html

=

Healing Campaign:
https://wiki.biblepay.org/BiblePay_Healing_Campaign
https://whitewalr.us/2019/biblepay-gsc-healing.html

=

Dynamic Whale Staking (DWS):
https://forum.biblepay.org/index.php?topic=468.0

=

Proof of Distributed Computing (PODC):
https://wiki.biblepay.org/PODC
https://whitewalr.us/2019/boinc-wcg-join-change-team.html
Old: https://wiki.biblepay.org/Distributed_Computing_2
http://wiki.biblepay.org/Distributed_Computing_Start_Guide
http://wiki.biblepay.org/BOINC_Researcher_Setup
https://wiki.biblepay.org/Getting_Started_With_PODC

=

Anything missing?

=

We also need:

- How to Buy BiblePay coins
https://bitcointalk.org/index.php?topic=2388064.msg51062536#msg51062536

- How to Create Proposals
http://wiki.biblepay.org/Create_Sanctuary_2#SUBMIT_PROPOSAL

- How to Create Masternode

I this guide still accurate?
http://wiki.biblepay.org/Create_Sanctuary_2

I think we need to add the upgrading to deterministic?
https://www.reddit.com/r/BiblePay/comments/clyxyc/upgrading_masternodes_sanctuaries_to/

- How to Buy a Subway Gift Card?
https://bitcointalk.org/index.php?topic=2388064.msg51300144#msg51300144

=

In addition to Text tutorials,
we need screenshots,
we also need Video (visual) tutorials