*** HUGE CHANGES IN BIBLEPAY TO IMPROVE OUR COMMUNITY AND HELP OUR CREDIBILITY AND CREATE STRENGTH ***



So this all started when one of our fast participants, Andy from LA offered to help with a few things.  Things that resonated with me because we both pray for BiblePay and receive confirmations about issues.  

I admit not all of my ideas are going to stick forever - as some are rooted in prior IT experience and not in God's will.  So when I hear that God wants to change something about BiblePay, I listen.

There were 3 areas that Andy brought to my attention that resonated:  Ease-of-use for investors and users, Key-man risk (dev+governmental), Sanctuary simplicity.  You are already seeing some of the changes (with these providers for masternodes like GIN we reached out to in response to the Sanc issue).  

For the Ease-of-use part, our complaint was that when an investor arrives on our landing page- they are way too confused.  And the page is dark and not full of love.  In light of that, Jaap is working on our landing page changes:  Show key information to potential investors (Quickly download the wallet, how to trade biblepay, what we do, boilerplate) and he is also adding a brighter background theme and images of children.   He is also making it easier for new users to understand how to get started in relation to the next wallet version (which will have a couple more GUI buttons to get started with one click).

Key Man Risk:  This started with a conversation from one of Andys clients, wanting to get into BiblePay as a whale, but he was afraid that I was the single point of failure.  After showing him the DAO page, many, many changes were put into play.  One being that we are working on an internal plan to remove key-man risk in Phase 1 (that is at the end of this month).  More info will be given on this today.  This will eliminate key-man risk.

Sanctuary Simplicity:  The whale would not join unless they find a way for a one-click masternode.  In this case, MIP is now creating a script for one-click sanctuaries.  We also reached out to GIN who came through for us for decentralized sancs.

This exercise brought up many sub-exercises and new projects for us, which I think in the long run make us stronger and more credible.

The key-man exercise brought up some of the weak points that exist in having a BiblePay foundation.

The problems with the BiblePay foundation are that we were becoming centralized, and "ruled" by only 6 individuals, with governmental systemic risk.  This gave the rest of the community the feeling that their masternode investment voting rights were not being used appropriately by biblepay, the biblepay directors were "better" than everyone else (IE could make legal decisions and trample on the rights of the community).  Arguably, one of the most important issues raised was the governmental risk involved with a centralized foundation.  This was the risk of being a lightning rod for a government to shut down biblepay or force biblepay to add wallet rules that remove anonymity.

In light of all these points, and with the desire to decentralize I feel we should dissolve the biblepay foundation.

The primary reason we started the foundation was to enable conversion of biblepay to Fiat for Compassion.com payments.  However, I feel we have other options for this now.  All of our other vendors, Kairos, Cameroon One, BLOOM accept BiblePay or Bitcoin.  I've reached out to compassion over the weekend to ask if they will set up a dedicated receiving address and accept our payments in Bitcoin.  If not, I will provide a homework assignment for the community to find a way to set up a program where we can convert biblepay to fiat for slices of payments to compassion.  Another option is to phase out compassion and ramp up sponsoring with orgs who do accept BTC (although Im not recommending this as compassion is $38 per month per child).


As far as Newbie Experience:  As you know we recently saw the no-team requirement poll pass, and the reward level to non-biblepay teams set to 100%.  In the next version of biblepay, we are trying to make it so a brand new user can mine with very little resistance.  This means downloading the wallet, buying the UTXO amount on the exchange, downloading boinc, and clicking "Add me to Rosetta", and then click "Associate".  The next version will also show how many tasks are running on the GUI - giving the user the understanding that the wallet is working (without going through RPC commands).