BiblePay DAO
This page explains the organizational structure of the BiblePay Decentralized Autonomous Organization.
BiblePay is a decentralized organization composed of multiple layers.
The community itself owns Biblepay as a whole, but the governance committee is the voice for the community that makes steering decisions. The Governance Committee is composed of our 200+ sanctuaries, who may vote on issues. Although it is a right for a sanctuary to vote on an issue, the code that runs in the sanctuary is an asset owned by the Biblepay DAO. Therefore our sanctuaries do not have the right to run modified versions of biblepay, and must run the most recent version. These running sanctuaries are considered Biblepay Assets, and must provide service to the best of their ability, otherwise the Sanctuary will not be paid. One example of code that Biblepay as a DAO has the right to deploy to Sanctuaries is our Cancer Mining Magnitude Assessment process. The Sanctuary is obligated to download, assimilate, compile and vote on the data, and must execute the code because our DAO considers the Sanctuary an asset of the DAO. In contrast, a normal user will not be obligated to run Sanctuary Service Modules.
The BiblePay Foundation
The BiblePay Foundation is a non-profit Texas Corporation that takes care of vendor relationships, vendor payments, orphan fundraisers, cryptocurrency exchanges, taxes and legal decisions.
The Foundation will initially be created with 6 board members invited by the Founder of BiblePay. It will then become autonomous, since its bylaws will have processes that ensure continuity, such as the ability for the foundation to vote in replacement boardmembers and remove non-performing boardmembers.
The board will initially consist of:
- President - Rob Andrews (Founder)
- Secretary - Togo Shigekata
- VP of Operations - Luke Znffal
- Treasurer and Finance Director - Jaap
- Director of Strategy - Chad Rogers
- VP of Development - Javier Mip
The BiblePay source code is opensource and public and owned by the community members equally (IE every holder of BBP currency).
The intellectual property concepts that are in development but not yet in production are owned by the Biblepay Foundation, until deployed.
The github repository will go through several phases of ownership during the lifetime of Biblepay. Initially, while Biblepay is small (defined below) and co-developers are new (defined below), Rob Andrews (founder) will be the sole person to hold github Release permissions (for security reasons explained below). This is considered phase 1.
During Phase 2, Three co-developers will be given Spork Signing keys and Release Keys. This means it will take two out of three developers to sign a spork or create a release. Also, the Treasurer or the VP of Operations will be given access to an emergency key for continuity in case a supermajority of the lead developers dissapear.
During Phase 3, Five co-developers will be given Spork Signing keys and Release Keys. A supermajority signed spork or release will be required.
Definition of Phases:
| Phase | Market Cap | Number of Cross-Trained Developers |
|---|---|---|
| Phase 1 | 0-20,000,000 | 2 or less developers are Cross-Trained |
| Phase 2 | 20,000,001-50,000,000 | 3 or more developers are cross-trained |
| Phase 3 | 50,000,000+ | 5 or more developers are cross-trained |
This chart explains that Rob will be the single github release manager in Phase 1 until two things occur: Our market cap exceeds 20Mil and Rob cross trains a minimum of two trustworthy co-devs vital release information and explains how to sign the spork keys and perform releases. At this point, continuity will be achieved in that if all devs dissapear, the foundation will have a backup key. Also, if only one dev dissapears the other two devs will step in and provide releases.
When our market cap exceeds 50Mil, we will beef up cross-training and spork signing to be more resilient as Phase 3 shows.
The reason we will transition through phases is: There are several risks involved when transitioning to a cross-trained environment that could be used maliciously while the coin is small. It is clear that Rob must have the best intentions since he has a lot of development hours and integrity at stake, so the assumption is while marketcap is between 0-20 MIL, the safest path to preserve the coins life is to trust Rob with sporks and deploys until the size of the marketcap exceeds what is considered a small operation and above the scope of a single dev. From Rob's perspective, the initial risks include: theft of the repository, virus protection, configuration management protection, rebranding risks, repurposing risks and malicious intent or ill will towards the end user. Rob is trying to prevent any of this from occurring in biblepay until the market cap exceeds what is comfortable for continuity. However after 20MIL, it is a common view that the DAO has grown large enough that it has outgrown Robs initial safety layer, and must be allowed to be free. At this point, the keys will be shared as outlined above to ensure continuity.
