https://wiki.biblepay.org/api.php?action=feedcontributions&user=Sunk818&feedformat=atomBiblePay Wiki - User contributions [en]2024-03-28T22:18:08ZUser contributionsMediaWiki 1.31.12https://wiki.biblepay.org/index.php?title=Quick_Start&diff=6279Quick Start2019-07-12T00:22:00Z<p>Sunk818: formatting, spelling, consistency</p>
<hr />
<div><br />
==About BiblePay==<br />
<br />
<br />
Launched in July 2017 with no premine and ICO, BiblePay describes itself as a decentralized autonomous cryptocurrency that gives 10% to orphan-charity (with Sanctuary governance). The project is passionate about spreading the gospel of Jesus, having the entire KJV bible compiled in its hashing algorithm (POBH). BiblePay (BBP) is deflationary, decreasing its emissions by 19.5% per year.<br />
<br />
<br />
The project views itself as a utility that provides an alternative method for giving to charity. With Generic Smart Contracts, the project seeks to become the go-to wallet for Christians. In the future, the team intends to lease file space on its Sanctuaries and release corporate integration features, such as c# access to the blockchain. The BiblePay platform is a derivative of Dash-Evolution. Located in Dallas, TX, the team seeks to help orphans globally. The roadmap can be viewed at: https://wiki.biblepay.org/Roadmap<br />
<br />
<br />
<br />
==How to Mine or Earn BiblePay==<br />
<br />
<br />
<ul>We have three different methods available to earn BBP:<br><br />
<li>Running a Sanctuary (25%)<br />
<li>Heat mining (25%)<br />
<li>GSC campaigns (40%)<br />
</ul><br />
<br />
<br />
'''Running a Sanctuary'''<br />
<br />
In this endeavor, you provide (IE lock up) 4,500,001 BiblePay in the block chain (this is the amount of collateral you must store in the collateral transaction for your sanctuary). <br />
<br />
While you provide sanctuary services to the network, your (receiving address) will receive one reward per payment cycle (approx. 25% of our blockchain rewards).<br />
<br />
Do it yourself guide:<br />
https://wiki.biblepay.org/Create_Sanctuary_2<br />
<br />
Or, to create a turnkey sanctuary through GIN:<br />
https://p.ginplatform.io/#!/<br />
<br />
<br />
<br />
'''Heat Mining'''<br />
<br />
<br />
To heat mine (our form of POW (proof-of-work) is called POBH (proof-of-bible-hash)), you only need to have your home PC running the full biblepay-qt client.<br />
Approx. 25% of our blockchain rewards are paid to heat miners.<br />
<br />
<br />
We have two types of heat mining: ABN and non ABN.<br />
<br />
ABN mining requires an investment (of 125,000 coin*age). (This is approximately 125,000 bbp aged for one day).<br />
<br />
In this scenario, the miner puts up a stake, in an ABN transaction, that is required in order to mine.<br />
This miner will make more rewards, than a non-abn miner (they will receive the entire POW reward if solo mining, while a non-abn miner will only receive 80% of the reward and is forced to pool mine).<br />
<br />
<br />
'''How to Set Up Solo Mining'''<br />
<br />
To solo mine with an ABN, ensure you have enough ABN weight with this command: 'exec getabnweight 125000'. If you have more than 125,000 you are eligible to solo mine (or pool mine) with an ABN.<br />
<br />
Create your biblepay.conf file:<br />
<br />
<pre><br />
gen=1<br />
genproclimit=number_of_cores<br />
(Choose a number to replace number_of_cores that is the desired amount of CPU utilization. For example if you have 4 cores, start with 4 and raise it until your CPU utilization is at the desired level).<br />
</pre><br />
<br />
<br />
'''Setup for Pool Mining:'''<br />
<br />
<br />
Create a biblepay.conf file:<br />
<br />
<pre><br />
pool=https://pool.biblepay.org<br />
workerid=your_worker_name (replace with your pool.biblepay.org worker name)<br />
gen=1<br />
genproclimit=number_of_cores<br />
</pre><br />
<br />
Create an account on https://pool.biblepay.org<br />
<br />
Create a worker on pool.biblepay.org (navigate to Workers | Add) - When creating the worker, choose "Non-Funded ABN" (the default), meaning you provide the ABN.<br />
<br />
<br />
<br />
'''Turnkey heat mining (mining without sufficient ABN weight):'''<br />
<br />
<br />
If you don't have enough BBP to mine with an ABN yet, no worries, you can still get started immediately and pool mine, and receive an 80% reward rate. (The extra 20% is split among the remaining pool participants with ABNs).<br />
<br />
<br />
Follow the Pool Mining instructions above to create a pool account, create the same biblepay.conf file, except when creating your worker in the pool - choose "Funded ABN". The pool worker type designates the payment mechanism. When you start your miner, you will see a specific message (mining with funded ABN).<br />
<br />
<br />
'''GSC Campaigns: (40% of our emissions)'''<br />
<br />
We currently have POG and Healing campaigns. These campaigns are similar to homogenized proof-of-stake + proof-of-donation (to our foundation).<br />
<br />
You will receive rewards based on your free balance in coin*age, mulitplied by a factor corresponding to how much you donated to the orphan foundation.<br />
<br />
<br />
'''POG (Proof-of-Giving):'''<br />
<br />
The POG campaign (proof-of-giving) rewards you for: GSC transmissions containing your internal coin age, plus giving a donation to the foundation.<br />
As an example, if you have a 100,000 BBP balance, with 1 day of coin age, since you have 100K coin*age, you would receive a reward of approximately 1% per day (as of July 11th) with a small tithe amount (of 2.50). Depending on the competition level and the tithe amount, your reward will vary.<br />
<br />
<ul>Steps to join the POG campaign and receive POG rewards:<br />
<li>Create a CPK (Christian-public keypair). Type 'exec cpk your_nickname' into the RPC.<br />
<li>Type exec join pog<br />
<li>The default giving amount is 2.50 bbp per day (to the foundation). If you would like to change this, change the key:<br />
<pre><br />
pog_foundationdonationamount=nnnn (replace nnnn with the amount you want to tithe per 12 hours).<br />
</pre><br />
<br />
To find the project reward for POG, type<br />
<pre> 'exec roi'</pre><br />
</ul><br />
<br />
More information on POG and GSC can be found here:<br />
https://wiki.biblepay.org/Getting_Started_with_Evolution<br />
<br />
<br />
'''Healing'''<br />
<br />
<br />
The Healing campaign rewards you for creating diary entries (such as when you pray for another person, or when you participate in outdoor street healing, or spiritual warfare). To create a diary entry, go to the Send page, click the Diary checkbox, and type the entry in the Diary textbox and click Send. You must join the Healing campaign with the command 'exec join healing' first.<br />
<br />
<br />
<br />
==BiblePay long term outlook==<br />
<br />
<br />
<ul><b>Why be bullish for BBP:</b><br />
<li>There are over 2.2Billion Christians on the planet<br />
<li>We have deflationary emissions, of 19.5% per year<br />
<li>We are derived from Dash, a stable and respected codebase, with governance and sanctuaries<br />
<li>We give 10% of our blockchain emissions directly to sponsor orphans through 75%+ efficient charities such as Compassion and Cameroon One<br />
<li>When you hold BBP as an asset, you are helping over 100 orphans per month be fed, clothed and educated<br />
<li>We are one of the few who will offer c# integration within one year<br />
<li>We have a solid use case being released at the end of 2019: decentralized leased Christian file storage, Voting on Christian objects, and Viewing <br />
Christian objects<br />
<li>Over 40 unique features that make us worthy of the top 100:<br />
https://wiki.biblepay.org/Nutrition_Information<br />
</ul><br />
<br />
<br />
<br />
<br />
'''What Good has BiblePay done for the world? '''<br />
<br />
<ul><br />
<li>BiblePay currently sponsors 105 orphans monthly through Compassion, Cameroon One, SXS Uganda, HOFC Kenya, and Kairos Childrens Fund<br />
<li>BiblePay not only pays for Christian Education and meals, but at SXS and HOFC Kenya, we also pay for boarding and regular education. <br />
<li>We are currently helping over 10 children where both parents had AIDS and abandoned the child (speak to pastor Joshua in Kenya).<br />
<li>See http://accountability.biblepay.org for a detailed list of how much help we have provided globally.<br />
<li>BiblePay has spent over $201,000 in expenses for Orphans in the last two years.<br />
<li>BiblePay has liquidated over $200,000 in blockchain tithes to help orphans.<br />
<li>BiblePay has donated to Hope For Widows.<br />
<li>See BiblePay's orphan collage as of August 2018: http://pool.biblepay.org/docs/SponsorshipsAugust2018.pdf<br />
<li>For investors who seek cryptocurrency exposure, we are a feel-good deflationary cryptocurrency, spending 10% of our emissions on orphan-charity<br />
</ul></div>Sunk818https://wiki.biblepay.org/index.php?title=Quick_Start&diff=6278Quick Start2019-07-12T00:20:12Z<p>Sunk818: formatting, spelling, consistency</p>
<hr />
<div>==About BiblePay==<br />
Launched in July 2017 with no premine and ICO, BiblePay describes itself as a decentralized autonomous cryptocurrency that gives 10% to orphan-charity (with Sanctuary governance). The project is passionate about spreading the gospel of Jesus, having the entire KJV Bible compiled in its hashing algorithm (Proof of Bible Hash - PoBH). BiblePay (BBP) is deflationary, decreasing its emissions by 19.5% per year.<br />
<br />
<br />
The project views itself as a utility that provides an alternative method for giving to charity. With Generic Smart Contracts (GSC), the project seeks to become the go-to wallet for Christians. In the future, the team intends to lease file space on its Sanctuaries and release corporate integration features, such as c# access to the blockchain. The BiblePay platform is a derivative of Dash-Evolution. Located in Dallas, TX, the team seeks to help orphans globally. The roadmap can be viewed at: [https://wiki.biblepay.org/Roadmap https://wiki.biblepay.org/Roadmap]<br />
<br />
<br />
==How to Mine or Earn BiblePay==<br />
We have three different methods available to earn BBP:<br /><br />
* Running a Sanctuary (25%)<br />
* Heat mining (25%)<br />
* GSC campaigns (40%)<br />
<br />
'''Running a Sanctuary'''<br />
<br />
In this endeavor, you provide (IE lock up) 4,500,001 BiblePay in the block chain (this is the amount of collateral you must store in the collateral transaction for your sanctuary). <br />
<br />
While you provide sanctuary services to the network, your (receiving address) will receive one reward per payment cycle (approx. 25% of our blockchain rewards).<br />
<br />
Do it yourself guide: [https://wiki.biblepay.org/Create Sanctuary_2 https://wiki.biblepay.org/Create Sanctuary_2]<br />
<br />
Or, to create a turnkey sanctuary through GIN: [https://p.ginplatform.io/#!/ https://p.ginplatform.io/#!/]<br />
<br />
<br />
'''Heat Mining'''<br />
<br />
<br />
To heat mine (our form of PoW (Proof-of-Work) is called PoBH (Proof-of-Bible-Hash)), you only need to have your home PC running the full biblepay-qt client.<br />
<br />
Approx. 25% of our blockchain rewards are paid to heat miners.<br />
<br />
<br />
We have two types of heat mining: ABN (AntiBotNet) and non ABN.<br />
<br />
ABN mining requires an investment (of 125,000 coin*age). (This is approximately 125,000 BBP aged for one day).<br />
<br />
In this scenario, the miner puts up a stake, in an ABN transaction, that is required in order to mine.<br />
<br />
<br />
This miner will make more rewards, than a non-ABN miner (they will receive the entire POW reward if solo mining, while a non-ABN miner will only receive 80% of the reward and is forced to pool mine).<br />
<br />
<br />
'''How to Set Up Solo Mining'''<br />
<br />
<br />
<br />
<br />
To solo mine with an ABN, ensure you have enough ABN weight with this command: 'exec getabnweight 125000'. If you have more than 125,000 BBP you are eligible to solo mine (or pool mine) with an ABN.<br />
<br />
Create your biblepay.conf file:<br />
<br />
<br />
<nowiki><pre>gen=1<br data-attributes="class=%22mw_emptyline%22"><br />genproclimit=number_of_cores (Choose a number to replace number_of_cores that is the desired amount of CPU utilization. For example if you have 4 cores, start with 4 and raise it until your CPU utilization is at the desired level).</pre></nowiki><br />
<br />
'''Setup for Pool Mining:'''<br />
<br />
<br />
Create a biblepay.conf file:<br />
<br />
<nowiki><pre>pool=https://pool.biblepay.org<br data-attributes="class=%22mw_emptyline%22"><br />workerid=your_worker_name (replace with your pool.biblepay.org worker name)<br data-attributes="class=%22mw_emptyline%22"><br />gen=1<br data-attributes="class=%22mw_emptyline%22"><br />genproclimit=number_of_cores<br data-attributes="class=%22mw_emptyline%22"></pre>Create an account on https://pool.biblepay.org<br />
</nowiki><br />
<br />
Create a worker on pool.biblepay.org (navigate to Workers | Add) - When creating the worker, choose "Non-Funded ABN" (the default), meaning you provide the ABN.<br />
<br />
<br />
<br />
'''Turnkey heat mining (mining without sufficient ABN weight):'''<br />
<br />
<br />
If you don't have enough BBP to mine with an ABN yet, no worries, you can still get started immediately and pool mine, and receive an 80% reward rate. (The extra 20% is split among the remaining pool participants with ABNs).<br />
<br />
<br />
Follow the Pool Mining instructions above to create a pool account, create the same biblepay.conf file, except when creating your worker in the pool - choose "Funded ABN". The pool worker type designates the payment mechanism. When you start your miner, you will see a specific message (mining with funded ABN).<br />
<br />
<br />
'''GSC Campaigns: (40% of our emissions):'''<br />
<br />
<br />
<br />
<br />
We currently have POG and Healing campaigns. These campaigns are similar to homogenized proof-of-stake + proof-of-donation (to our foundation).<br />
<br />
You will receive rewards based on your free balance in coin*age, mulitplied by a factor corresponding to how much you donated to the orphan foundation.<br />
<br />
<br />
'''POG (Proof-of-Giving):'''<br />
<br />
The POG campaign (proof-of-giving) rewards you for: GSC transmissions containing your internal coin age, plus giving a donation to the foundation.<br />
As an example, if you have a 100,000 BBP balance, with 1 day of coin age, since you have 100K coin*age, you would receive a reward of approximately 1% per day (as of July 11th) with a small tithe amount (of 2.50). Depending on the competition level and the tithe amount, your reward will vary.<br />
<br />
Steps to join the POG campaign and receive POG rewards:<br />
* Create a CPK (Christian-public keypair). Type 'exec cpk your_nickname' into the RPC.<br />
* Type exec join pog<br />
* The default giving amount is 2.50 bbp per day (to the foundation). If you would like to change this, change the key:<br />
<br />
<pre>pog_foundationdonationamount=nnnn (replace nnnn with the amount you want to tithe per 12 hours).<br /></pre><br />
<br />
To find the project reward for POG, type<br />
<pre> 'exec roi'</pre><br />
<br />
More information on POG and GSC can be found here:[https://wiki.biblepay.org/Getting Started_with_Evolution https://wiki.biblepay.org/Getting Started_with_Evolution]<br />
<br />
<br />
<br />
<br />
<br />
'''Healing'''<br />
<br />
<br />
The Healing campaign rewards you for creating diary entries (such as when you pray for another person, or when you participate in outdoor street healing, or spiritual warfare). To create a diary entry, go to the Send page, click the Diary checkbox, and type the entry in the Diary textbox and click Send. You must join the Healing campaign with the command 'exec join healing' first.<br />
<br />
<br />
<br />
<br />
==BiblePay long term outlook==<br />
'''Why be bullish for BBP:'''<br />
* There are over 2.2Billion Christians on the planet<br />
* We have deflationary emissions, of 19.5% per year<br />
* We are derived from Dash, a stable and respected codebase, with governance and sanctuaries<br />
* We give 10% of our blockchain emissions directly to sponsor orphans through 75%+ efficient charities such as Compassion and Cameroon One<br />
* When you hold BBP as an asset, you are helping over 100 orphans per month be fed, clothed and educated<br />
* We are one of the few who will offer c# integration within one year<br />
* We have a solid use case being released at the end of 2019: decentralized leased Christian file storage, Voting on Christian objects, and Viewing Christian objects<br />
* Over 40 unique features that make us worthy of the top 100: [https://wiki.biblepay.org/Nutrition Information https://wiki.biblepay.org/Nutrition Information]<br />
<br />
'''What Good has BiblePay done for the world? '''<br />
<br />
* BiblePay currently sponsors 105 orphans monthly through Compassion, Cameroon One, SXS Uganda, HOFC Kenya, and Kairos Childrens Fund<br />
* BiblePay not only pays for Christian Education and meals, but at SXS and HOFC Kenya, we also pay for boarding and regular education. <br />
* We are currently helping over 10 children where both parents had AIDS and abandoned the child (speak to pastor Joshua in Kenya).<br />
* See http://accountability.biblepay.org for a detailed list of how much help we have provided globally.<br />
* BiblePay has spent over $201,000 in expenses for Orphans in the last two years.<br />
* BiblePay has liquidated over $200,000 in blockchain tithes to help orphans.<br />
* BiblePay has donated to Hope For Widows.<br />
* See BiblePay's orphan collage as of August 2018: [http://pool.biblepay.org/docs/SponsorshipsAugust2018.pdf http://pool.biblepay.org/docs/SponsorshipsAugust2018.pdf]<br />
* For investors who seek cryptocurrency exposure, we are a feel-good deflationary cryptocurrency, spending 10% of our emissions on orphan-charity</div>Sunk818https://wiki.biblepay.org/index.php?title=Quick_Start&diff=6277Quick Start2019-07-12T00:16:46Z<p>Sunk818: formatting</p>
<hr />
<div>==About BiblePay==<br />
Launched in July 2017 with no premine and ICO, BiblePay describes itself as a decentralized autonomous cryptocurrency that gives 10% to orphan-charity (with Sanctuary governance). The project is passionate about spreading the gospel of Jesus, having the entire KJV Bible compiled in its hashing algorithm (Proof of Bible Hash - PoBH). BiblePay (BBP) is deflationary, decreasing its emissions by 19.5% per year.<br />
<br />
<br />
The project views itself as a utility that provides an alternative method for giving to charity. With Generic Smart Contracts (GSC), the project seeks to become the go-to wallet for Christians. In the future, the team intends to lease file space on its Sanctuaries and release corporate integration features, such as c# access to the blockchain. The BiblePay platform is a derivative of Dash-Evolution. Located in Dallas, TX, the team seeks to help orphans globally. The roadmap can be viewed at: [https://wiki.biblepay.org/Roadmap https://wiki.biblepay.org/Roadmap]<br />
<br />
<br />
==How to Mine or Earn BiblePay==<br />
We have three different methods available to earn BBP:<br /><br />
* Running a Sanctuary (25%)<br />
* Heat mining (25%)<br />
* GSC campaigns (40%)<br />
<br />
'''Running a Sanctuary'''<br />
<br />
In this endeavor, you provide (IE lock up) 4,500,001 BiblePay in the block chain (this is the amount of collateral you must store in the collateral transaction for your sanctuary). <br />
<br />
While you provide sanctuary services to the network, your (receiving address) will receive one reward per payment cycle (approx. 25% of our blockchain rewards).<br />
<br />
Do it yourself guide: [https://wiki.biblepay.org/Create Sanctuary_2 https://wiki.biblepay.org/Create Sanctuary_2]<br />
<br />
Or, to create a turnkey sanctuary through GIN: [https://p.ginplatform.io/#!/ https://p.ginplatform.io/#!/]<br />
<br />
<br />
'''Heat Mining'''<br />
<br />
<br />
To heat mine (our form of PoW (Proof-of-Work) is called PoBH (Proof-of-Bible-Hash)), you only need to have your home PC running the full biblepay-qt client.<br />
<br />
Approx. 25% of our blockchain rewards are paid to heat miners.<br />
<br />
<br />
We have two types of heat mining: ABN (AntiBotNet) and non ABN.<br />
<br />
ABN mining requires an investment (of 125,000 coin*age). (This is approximately 125,000 BBP aged for one day).<br />
<br />
In this scenario, the miner puts up a stake, in an ABN transaction, that is required in order to mine.<br />
<br />
<br />
This miner will make more rewards, than a non-ABN miner (they will receive the entire POW reward if solo mining, while a non-ABN miner will only receive 80% of the reward and is forced to pool mine).<br />
<br />
<br />
'''How to Set Up Solo Mining'''<br />
<br />
<br />
<br />
<br />
To solo mine with an ABN, ensure you have enough ABN weight with this command: 'exec getabnweight 125000'. If you have more than 125,000 BBP you are eligible to solo mine (or pool mine) with an ABN.<br />
<br />
Create your biblepay.conf file:<br />
<br />
<br />
<br />
<br />
<br />
<br />
<pre>gen=1<br data-attributes="class=%22mw_emptyline%22"><br />genproclimit=number_of_cores (Choose a number to replace number_of_cores that is the desired amount of CPU utilization. For example if you have 4 cores, start with 4 and raise it until your CPU utilization is at the desired level).</pre>'''Setup for Pool Mining:'''<br />
<br />
<br />
Create a biblepay.conf file:<br />
<br />
<br />
<br />
<br />
<br />
<pre>pool=https://pool.biblepay.org<br data-attributes="class=%22mw_emptyline%22"><br />workerid=your_worker_name (replace with your pool.biblepay.org worker name)<br data-attributes="class=%22mw_emptyline%22"><br />gen=1<br data-attributes="class=%22mw_emptyline%22"><br />genproclimit=number_of_cores<br data-attributes="class=%22mw_emptyline%22"></pre>Create an account on https://pool.biblepay.org<br />
<br />
Create a worker on pool.biblepay.org (navigate to Workers | Add) - When creating the worker, choose "Non-Funded ABN" (the default), meaning you provide the ABN.<br />
<br />
<br />
<br />
'''Turnkey heat mining (mining without sufficient ABN weight):'''<br />
<br />
<br />
If you don't have enough BBP to mine with an ABN yet, no worries, you can still get started immediately and pool mine, and receive an 80% reward rate. (The extra 20% is split among the remaining pool participants with ABNs).<br />
<br />
<br />
Follow the Pool Mining instructions above to create a pool account, create the same biblepay.conf file, except when creating your worker in the pool - choose "Funded ABN". The pool worker type designates the payment mechanism. When you start your miner, you will see a specific message (mining with funded ABN).<br />
<br />
<br />
'''GSC Campaigns: (40% of our emissions):'''<br />
<br />
<br />
<br />
<br />
We currently have POG and Healing campaigns. These campaigns are similar to homogenized proof-of-stake + proof-of-donation (to our foundation).<br />
<br />
You will receive rewards based on your free balance in coin*age, mulitplied by a factor corresponding to how much you donated to the orphan foundation.<br />
<br />
<br />
'''POG (Proof-of-Giving):'''<br />
<br />
The POG campaign (proof-of-giving) rewards you for: GSC transmissions containing your internal coin age, plus giving a donation to the foundation.<br />
As an example, if you have a 100,000 BBP balance, with 1 day of coin age, since you have 100K coin*age, you would receive a reward of approximately 1% per day (as of July 11th) with a small tithe amount (of 2.50). Depending on the competition level and the tithe amount, your reward will vary.<br />
<br />
Steps to join the POG campaign and receive POG rewards:<br />
* Create a CPK (Christian-public keypair). Type 'exec cpk your_nickname' into the RPC.<br />
* Type exec join pog<br />
* The default giving amount is 2.50 bbp per day (to the foundation). If you would like to change this, change the key:<br />
<br />
<br />
<br />
<br />
<pre>pog_foundationdonationamount=nnnn (replace nnnn with the amount you want to tithe per 12 hours).<br /></pre><br />
<br />
To find the project reward for POG, type<br />
<pre> 'exec roi'</pre><br />
<br />
More information on POG and GSC can be found here:[https://wiki.biblepay.org/Getting Started_with_Evolution https://wiki.biblepay.org/Getting Started_with_Evolution]<br />
<br />
<br />
<br />
<br />
<br />
'''Healing'''<br />
<br />
<br />
The Healing campaign rewards you for creating diary entries (such as when you pray for another person, or when you participate in outdoor street healing, or spiritual warfare). To create a diary entry, go to the Send page, click the Diary checkbox, and type the entry in the Diary textbox and click Send. You must join the Healing campaign with the command 'exec join healing' first.<br />
<br />
<br />
<br />
<br />
==BiblePay long term outlook==<br />
'''Why be bullish for BBP:'''<br />
* There are over 2.2Billion Christians on the planet<br />
* We have deflationary emissions, of 19.5% per year<br />
* We are derived from Dash, a stable and respected codebase, with governance and sanctuaries<br />
* We give 10% of our blockchain emissions directly to sponsor orphans through 75%+ efficient charities such as Compassion and Cameroon One<br />
* When you hold BBP as an asset, you are helping over 100 orphans per month be fed, clothed and educated<br />
* We are one of the few who will offer c# integration within one year<br />
* We have a solid use case being released at the end of 2019: decentralized leased Christian file storage, Voting on Christian objects, and Viewing Christian objects<br />
* Over 40 unique features that make us worthy of the top 100: [https://wiki.biblepay.org/Nutrition Information https://wiki.biblepay.org/Nutrition Information]<br />
<br />
'''What Good has BiblePay done for the world? '''<br />
<br />
* BiblePay currently sponsors 105 orphans monthly through Compassion, Cameroon One, SXS Uganda, HOFC Kenya, and Kairos Childrens Fund<br />
* BiblePay not only pays for Christian Education and meals, but at SXS and HOFC Kenya, we also pay for boarding and regular education. <br />
* We are currently helping over 10 children where both parents had AIDS and abandoned the child (speak to pastor Joshua in Kenya).<br />
* See http://accountability.biblepay.org for a detailed list of how much help we have provided globally.<br />
* BiblePay has spent over $201,000 in expenses for Orphans in the last two years.<br />
* BiblePay has liquidated over $200,000 in blockchain tithes to help orphans.<br />
* BiblePay has donated to Hope For Widows.<br />
* See BiblePay's orphan collage as of August 2018: [http://pool.biblepay.org/docs/SponsorshipsAugust2018.pdf http://pool.biblepay.org/docs/SponsorshipsAugust2018.pdf]<br />
* For investors who seek cryptocurrency exposure, we are a feel-good deflationary cryptocurrency, spending 10% of our emissions on orphan-charity</div>Sunk818https://wiki.biblepay.org/index.php?title=Quick_Start&diff=6276Quick Start2019-07-12T00:14:35Z<p>Sunk818: formatting, spelling, consistency</p>
<hr />
<div>==About BiblePay==<br />
Launched in July 2017 with no premine and ICO, BiblePay describes itself as a decentralized autonomous cryptocurrency that gives 10% to orphan-charity (with Sanctuary governance). The project is passionate about spreading the gospel of Jesus, having the entire KJV Bible compiled in its hashing algorithm (Proof of Bible Hash - PoBH). BiblePay (BBP) is deflationary, decreasing its emissions by 19.5% per year.<br />
<br />
<br />
The project views itself as a utility that provides an alternative method for giving to charity. With Generic Smart Contracts (GSC), the project seeks to become the go-to wallet for Christians. In the future, the team intends to lease file space on its Sanctuaries and release corporate integration features, such as c# access to the blockchain. The BiblePay platform is a derivative of Dash-Evolution. Located in Dallas, TX, the team seeks to help orphans globally. The roadmap can be viewed at: [https://wiki.biblepay.org/Roadmap https://wiki.biblepay.org/Roadmap]<br />
<br />
<br />
==How to Mine or Earn BiblePay==<br />
We have three different methods available to earn BBP:<br /><br />
* Running a Sanctuary (25%)<br />
* Heat mining (25%)<br />
* GSC campaigns (40%)<br />
<br />
'''Running a Sanctuary'''<br />
<br />
In this endeavor, you provide (IE lock up) 4,500,001 BiblePay in the block chain (this is the amount of collateral you must store in the collateral transaction for your sanctuary). <br />
<br />
While you provide sanctuary services to the network, your (receiving address) will receive one reward per payment cycle (approx. 25% of our blockchain rewards).<br />
<br />
Do it yourself guide: [https://wiki.biblepay.org/Create Sanctuary_2 https://wiki.biblepay.org/Create Sanctuary_2]<br />
<br />
Or, to create a turnkey sanctuary through GIN: [https://p.ginplatform.io/#!/ https://p.ginplatform.io/#!/]<br />
<br />
<br />
'''Heat Mining'''<br />
<br />
<br />
To heat mine (our form of PoW (Proof-of-Work) is called PoBH (Proof-of-Bible-Hash)), you only need to have your home PC running the full biblepay-qt client.<br />
<br />
Approx. 25% of our blockchain rewards are paid to heat miners.<br />
<br />
<br />
We have two types of heat mining: ABN (AntiBotNet) and non ABN.<br />
<br />
ABN mining requires an investment (of 125,000 coin*age). (This is approximately 125,000 BBP aged for one day).<br />
<br />
In this scenario, the miner puts up a stake, in an ABN transaction, that is required in order to mine.<br />
<br />
<br />
This miner will make more rewards, than a non-ABN miner (they will receive the entire POW reward if solo mining, while a non-ABN miner will only receive 80% of the reward and is forced to pool mine).<br />
<br />
<br />
'''How to Set Up Solo Mining'''<br />
<br />
<br />
<br />
<br />
To solo mine with an ABN, ensure you have enough ABN weight with this command: 'exec getabnweight 125000'. If you have more than 125,000 BBP you are eligible to solo mine (or pool mine) with an ABN.<br />
<br />
Create your biblepay.conf file:<br />
<br />
<br />
<br />
<br />
<pre>gen=1<br />genproclimit=number_of_cores (Choose a number to replace number_of_cores that is the desired amount of CPU utilization. For example if you have 4 cores, start with 4 and raise it until your CPU utilization is at the desired level).</pre>'''Setup for Pool Mining:'''<br />
<br />
<br />
Create a biblepay.conf file:<br />
<br />
<br />
<br />
<pre>pool=https://pool.biblepay.org<br />workerid=your_worker_name (replace with your pool.biblepay.org worker name)<br />gen=1<br />genproclimit=number_of_cores</pre>Create an account on https://pool.biblepay.org<br />
<br />
Create a worker on pool.biblepay.org (navigate to Workers | Add) - When creating the worker, choose "Non-Funded ABN" (the default), meaning you provide the ABN.<br />
<br />
<br />
<br />
'''Turnkey heat mining (mining without sufficient ABN weight):'''<br />
<br />
<br />
If you don't have enough BBP to mine with an ABN yet, no worries, you can still get started immediately and pool mine, and receive an 80% reward rate. (The extra 20% is split among the remaining pool participants with ABNs).<br />
<br />
<br />
Follow the Pool Mining instructions above to create a pool account, create the same biblepay.conf file, except when creating your worker in the pool - choose "Funded ABN". The pool worker type designates the payment mechanism. When you start your miner, you will see a specific message (mining with funded ABN).<br />
<br />
<br />
'''GSC Campaigns: (40% of our emissions):'''<br />
<br />
<br />
<br />
<br />
We currently have POG and Healing campaigns. These campaigns are similar to homogenized proof-of-stake + proof-of-donation (to our foundation).<br />
<br />
You will receive rewards based on your free balance in coin*age, mulitplied by a factor corresponding to how much you donated to the orphan foundation.<br />
<br />
<br />
'''POG (Proof-of-Giving):'''<br />
<br />
The POG campaign (proof-of-giving) rewards you for: GSC transmissions containing your internal coin age, plus giving a donation to the foundation.<br />
As an example, if you have a 100,000 BBP balance, with 1 day of coin age, since you have 100K coin*age, you would receive a reward of approximately 1% per day (as of July 11th) with a small tithe amount (of 2.50). Depending on the competition level and the tithe amount, your reward will vary.<br />
<br />
Steps to join the POG campaign and receive POG rewards:<br />
* Create a CPK (Christian-public keypair). Type 'exec cpk your_nickname' into the RPC.<br />
* Type exec join pog<br />
* The default giving amount is 2.50 bbp per day (to the foundation). If you would like to change this, change the key:<br />
<br />
<br />
<pre>pog_foundationdonationamount=nnnn (replace nnnn with the amount you want to tithe per 12 hours).<br /></pre><br />
<br />
To find the project reward for POG, type<br />
<pre> 'exec roi'</pre><br />
<br />
More information on POG and GSC can be found here:[https://wiki.biblepay.org/Getting Started_with_Evolution https://wiki.biblepay.org/Getting Started_with_Evolution]<br />
<br />
<br />
<br />
<br />
<br />
'''Healing'''<br />
<br />
<br />
The Healing campaign rewards you for creating diary entries (such as when you pray for another person, or when you participate in outdoor street healing, or spiritual warfare). To create a diary entry, go to the Send page, click the Diary checkbox, and type the entry in the Diary textbox and click Send. You must join the Healing campaign with the command 'exec join healing' first.<br />
<br />
<br />
<br />
<br />
==BiblePay long term outlook==<br />
'''Why be bullish for BBP:'''<br />
* There are over 2.2Billion Christians on the planet<br />
* We have deflationary emissions, of 19.5% per year<br />
* We are derived from Dash, a stable and respected codebase, with governance and sanctuaries<br />
* We give 10% of our blockchain emissions directly to sponsor orphans through 75%+ efficient charities such as Compassion and Cameroon One<br />
* When you hold BBP as an asset, you are helping over 100 orphans per month be fed, clothed and educated<br />
* We are one of the few who will offer c# integration within one year<br />
* We have a solid use case being released at the end of 2019: decentralized leased Christian file storage, Voting on Christian objects, and Viewing Christian objects<br />
* Over 40 unique features that make us worthy of the top 100: [https://wiki.biblepay.org/Nutrition Information https://wiki.biblepay.org/Nutrition Information]<br />
<br />
'''What Good has BiblePay done for the world? '''<br />
<br />
* BiblePay currently sponsors 105 orphans monthly through Compassion, Cameroon One, SXS Uganda, HOFC Kenya, and Kairos Childrens Fund<br />
* BiblePay not only pays for Christian Education and meals, but at SXS and HOFC Kenya, we also pay for boarding and regular education. <br />
* We are currently helping over 10 children where both parents had AIDS and abandoned the child (speak to pastor Joshua in Kenya).<br />
* See http://accountability.biblepay.org for a detailed list of how much help we have provided globally.<br />
* BiblePay has spent over $201,000 in expenses for Orphans in the last two years.<br />
* BiblePay has liquidated over $200,000 in blockchain tithes to help orphans.<br />
* BiblePay has donated to Hope For Widows.<br />
* See BiblePay's orphan collage as of August 2018: [http://pool.biblepay.org/docs/SponsorshipsAugust2018.pdf http://pool.biblepay.org/docs/SponsorshipsAugust2018.pdf]<br />
* For investors who seek cryptocurrency exposure, we are a feel-good deflationary cryptocurrency, spending 10% of our emissions on orphan-charity</div>Sunk818https://wiki.biblepay.org/index.php?title=Generic_Smart_Contracts&diff=6256Generic Smart Contracts2019-06-12T17:39:26Z<p>Sunk818: </p>
<hr />
<div><br />
'''BIBLEPAY EVOLUTION - GENERIC SMART CONTRACTS'''<br />
<br />
Generic Smart Contracts (GSC's) allow BiblePay to accomplish its goals without disrupting quality of service for our users. These contracts provide a modular abstract interface for user rewards, and exciting capabilities that are not possible in hard consensus systems. <br />
<br><br />
<br />
Some of the features our GSC's include: payments based on campaigns, corporate turnkey integration, c#/stratis integration, Restful API oracles, web tipping, decentralized voting on Christian objects, Christian economy features, and more.<br />
<br><br />
<br />
<br><br />
<br />
<br />
'''Generic Smart Contract Format'''<br />
<br />
The GSC is split into a client server architecture. The client side user joins campaigns with a CPK (Christian Public Keypair) and competes in these campaigns for points. The server side (our Sanctuaries) assess user points and tracks user progress. Once per day, the points are converted and paid in a Generic Smart Contract. The GSC is voted on by the Sanctuaries automatically at a certain chain height.<br />
<br><br />
<br />
The GSC is paid once per day as a superblock from BiblePay core, and is split among campaigns by points rewarded per campaign per user. <br />
<br><br />
<br />
Sanctuaries assess the points per campaign per user, and allocate the total daily reward amount by points to participants. <br />
<br />
<br><br />
<br><br />
<br />
'''CAMPAIGNS'''<br />
<br />
<br />
BiblePay will support an unlimited amount of campaigns over the long term. Each campaign will have a name, a distinct purpose, and a set of rules and formulas that adhere to the GSC-Server-Abstraction-Layer.<br />
<br />
<br><br />
<br />
A user joins a campaign by typing a command (see RPC commands). The user must have a Christian Public Keypair to join a campaign (see RPC commands). <br />
<br><br />
<br />
<br />
'''Sanctuary Side'''<br />
<br />
<br />
The sanctuaries will assess the points for each user, by looping through all live campaigns, and assessing the amount of points that should be assigned to each user and assigning Points. <br />
<br><br />
NOTE: If multiple transactions were sent by a user in one day, the user points will be summed.<br />
<br />
<br><br />
<br />
If the user has a 1 million balance in stake, the interest component will be 27 points, while the POG campaign reward=1000 points, equaling 1027 points for the day (see detailed example for more information).<br />
<br><br />
<br />
Once the points are assessed at a daily quorum height, the sanctuaries will auto-vote on these points.<br />
<br><br />
<br />
The daily generic smart contract will automatically convert points to BBP rewards in the superblock generator module.<br />
<br><br />
<br><br />
'''Christian Economy Integration'''<br />
<br />
<br><br />
The GSC system enables biblepay to create an exciting new campaign type for Christian economies in the future: HTML5 voting and HTML5 tipping. <br />
<br><br />
In voting, it will be possible for a user to navigate to a list of Christian objects (say for instance, Orphan outgoing letters), and vote on these letters with their CPK. <br />
<br><br />
The sanctuary will pick up votes for the "Orphan Letters" campaign automatically, allowing points to be rewarded in that campaign for voting activity from the 'Orphan' campaign budget.<br />
<br><br />
The same can be done with any list of Christian objects, for example, a list of "Rapture video objects". As users vote on these items, the HTML5 vote will be picked up and converted to points according to the rules of the campaign.<br />
<br />
<br><br />
<br />
'''Christian Public Keypair Reputation Score'''<br />
<br />
<br />
Since an individual user will create a CPK to participate, it will be possible for the user to accumulate a reputation score, based on behavior. This will open up exciting possibilities for our network for future campaigns that reward points based on behavior. One example of negative behavior is if someone consistently votes down high quality content. If the users reputation score decreases, this user may be rewarded less share percentage in some campaigns (because activity is of low caliber). <br />
<br><br />
<br />
<br />
As voting activity is assessed, the CPK will accumulate a reputation score change. Over time, it will be preferable for the user to keep the existing CPK (due to the positive reputation score) rather than create multiple keys or recreate the keypair. The reputation score may then be used to influence payout percentages in some activities, after it is established that reputation scores are accurate.<br />
<br><br />
<br><br />
<br><br />
<br />
'''Corporate GSC Integration'''<br />
<br><br />
<br />
A very exciting feature BiblePay will offer in our GSC system is corporate integration. This is a value add for corporations who do not want to spend hours learning blockchain programming to make cryptocurrency payments automatically. <br />
<br><br />
This feature allows a corporate developer to configure a recurring or one-time payment to be made easily through the blockchain to a vendor by emitting a coinbase payment in our GSC.<br />
<br><br />
<br><br />
<br />
'''Evolution Anti-BotNet Features, 51% attack prevention with ChainLocks'''<br />
<br><br />
<br />
In Evolution, we have built in a brand new feature called ABN (anti-botnet). The original use-case for ABN stems from our mission to prevent ASIC/GPU ports, run BiblePay on commodity PCs, and create a fair mining environment without groups of monopolies forming (IE Asic monopolies) who take a large percentage of mining rewards. Even with CPU mining, we have seen some rich actors, who own 300 servers, point all the hash power at BiblePay and take an unduly large percentage of daily rewards. On one hand, we agree, they have every right to. But on the other hand, we really would like to appeal to distinct head count so as to expose more people to the Gospel. In light of this we have released ABN, which requires a certain amount of coin*age to be present in each mined block in order to mine BiblePay. What this does is quickly uses up coin*age when an attack occurs (to give an example, if you are BotNet with 50 PCs, and your wallet balance is 50,000, after solving a few blocks with high hash power your wallet will run out of coin*age and you will not be able to mine more BiblePay until coin*age increases).<br />
<br><br />
<br />
The feature works like this. Our network requires an average calculated and pre-assessed static amount (posted in getmininginfo) of required coin*age and stores this in the chain. Each miner checks this number, and will search the wallet (this is all automatic) for coins totaling the requirement and place these coins in an ABN Stake transaction - and then begin mining. We do allow mining for All participants if a block is over 60 minutes old (this is so that our chain never stops if every single participant runs out of coin age).<br />
<br><br />
In this way, every block mined in Evolution is sure to be solved by a normal participant and not a bot-net over time.<br />
<br><br />
In addition to all of this, we have inherited Dash's 51% attack prevention system (ChainLocks). We have this feature fully merged in and ready to be released. This is an amazing addition to BiblePay, as it removes 51% attack risk by almost 100%. This is accomplished by asking our Sanctuaries to keep track of each solved block and not allow deep reorganizations once ChainLocks are live.<br />
<br />
<br><br />
<br><br />
<br />
'''Deployment Timeline and Roadmap changes'''<br />
<br><br />
<br />
<br />
For BiblePay Evolution, we will start by releasing One campaign: Proof-of-Giving. This will prove the entire GSC concept in testnet from end-to-end, with a daily smart contract being emitted, CPK users being registered and participating in the first campaign, the Sanctuaries assessing the points, Sanctuaries voting, and payments being made.<br />
<br><br />
<br />
After the release of Evolution, our IT team will continue to develop the Corporate integration, additional new campaigns, and HTML5 integration.<br />
<br><br />
<br><br />
<br />
<br />
''' BiblePay Architecture Changes for Reliability, Mass Development and Mass Adoption '''<br />
<br><br />
<br><br />
<br />
In order to maintain a reliable environment in production, we have decided to change our current architecture. We are changing procedures to prevent or minimize production deployments that: <br />
Change consensus, or Add client-side features. Both of these things may be valuable in the long term (for example a new campaign allowing web tipping, or a gospel feature for Spiritual Warfare), but, not at the expense of the Quality of Service for those using BBP in prod, or for Exchanges or Sanctuaries. <br />
<br />
<br><br />
In light of this, we have designed a new architecture where we will demarcate and abstract the core client from the Sanctuary in a way where BiblePay-IT may deploy consensus changes on the Sanctuary side only. This will be accomplished by creating a client side abstraction interface the core client will adhere to.<br />
<br />
<br><br />
Our goal is that when we release Evolution, the client side contract will no longer change, and therefore updates to the sanctuary will not require upgrades for the users or exchanges.<br />
<br><br />
We will accomplish this by deploying incremental updates to the sanctuaries that allow the consensus mechanism to be updated on the server side only. This means that when a new campaign is released (let us say for example, web tipping), the Sanctuaries will need to upgrade, but not the users, and the exchanges and network will not endure a hard fork. After the Sancs upgrade, web tipping will be announced and users may "join web tip campaign" and automatically receive rewards via the daily GSC.<br />
<br><br />
<br />
Another large change that is occurring is our move toward an additional HTML5 GUI for new UI pages. We believes we will attract HTML5 web developers that will give us the bandwidth to build out pages such as Orphan writing, Orphan voting, Lists of Christian Objects, Embedded Christian Videos, etc. This also accomplishes our goal of not upgrading the core client during new GUI changes as these pages adhere to the new model.<br />
<br><br />
Part of this change will mean that when a user navigates to a Christian Space resource, we will honor their CPK (Christian public keypair) as authentication, and this will allow the user to vote on the resource or view it , as the resource will know their voting ability and reputation score. This will allow the user to navigate into BiblePay's additional UI pages.<br />
<br><br />
<br />
These exciting features are being added to BiblePay to make your user experience smoother and provide a high quality production Environment.<br />
<br />
<br><br />
<br />
<br />
<br />
'''Modularity and Extensibility'''<br />
<br />
<br><br />
To help remove IT development bottlenecks in the UI area, our dev team is making BiblePay-Evolution HTML work in a way where non-C++ devs (web devs) may participate in development and deploy GUI changes. <br />
<br><br />
To give an example of how this will work, we have a background project with Kestrel and Sanctuaries, so that BiblePay will emit HTML5 markup from sanctuaries. This will allow webdevs to participate in: Creating Christian Spaces, building out BiblePay, and modifying BiblePay UI in a modular and extensible way, without knowing how to be a blockchain programmer. <br />
<br><br />
To the end user this means we will have tens to hundreds of new pages in the wallet in Christian Spaces in the future, allowing us to vote on these objects with our CPK and therefore our reputation scores will change, and we hope the experience will be edifying for everyone, giving BiblePay a truly valuable purpose.<br />
<br><br />
<br />
<br />
<br />
'''RoadMap Modifications'''<br />
<br />
<br><br />
<br />
March 2019: Release Evolution to Testnet. Test normal core wallet functions: Sanctuary creation, sanctuary operation, receive/send money, proposals, etc.<br />
<br><br />
<br />
Mid April 2019: Test GSCs in TestNet, ensure payments work, campaigns emit points, campaigns can be joined and unjoined, and CPKs work. Ensure the first campaign (POG) works properly.<br />
<br><br />
<br />
May 2019: Finish testing Evo, release Evo to Prod. Go Live with Evo and GSC (Generic Smart Contracts) - and One Campaign in Prod! (POG).<br />
<br><br />
<br />
July 2019: Finish modifications to server side GSC's, alter any business logic. Add additional Campaign if necessary. <br />
<br><br />
<br />
September 2019: Release Christian spaces (Allow voting on Christian objects, allow navigation of decentralized UI by CPKs). <br />
<br><br />
<br />
September 10th, 2019: Make a very important announcement regarding the future of BiblePay (IE the announcement that was promised this year) - regarding a feature that cannot be disclosed until September due to the sensitive nature of the subject. What we can say, is this item gives BiblePay the ability to be a 'serious contender' in the space.<br />
<br><br />
<br />
Dec 2019: Release Corporate Integration features. This allows 3rd party sites like (Steve Cioccolanti to integrate with BiblePay), c# Payments, Reports from Stratis, and also allows us to create DOCS (decentralized orphan contracts).<br />
<br><br />
<br />
<br />
<br />
<br />
'''Our first Campaign - POG (Proof-of-Giving)'''<br />
<br />
<br><br />
<br />
Notes about Campaigns: A user cannot join any campaigns unless they have a CPK (A Christian-public-keypair). You only need one CPK for life. The CPK is stored in your wallet.dat so when you move to a new machine you will still have your CPK. If you want to join multiple projects, you should create ONE CPK, then join each project with the join command. You will receive an error if you do not have a CPK and attempt to join a project. (If you try to create multiple CPKs you will receive an error).<br />
<br><br />
<br />
Attributes of Campaign 1 (POG):<br />
<br><br />
<br />
Assessment Includes:<br />
All users with a CPK who have joined campaign "POG"<br />
<br />
Requirements:<br />
A contribution sent to the Orphan Foundation during the last 24 hour period<br />
<br />
Assessment:<br />
Sum of( (Coin_Amount * 1) * (Coin_Age_Days * 1) * (CubedRoot(Tithe_To_Foundation)))<br />
<br><br />
Meaning:<br />
For each donation to the foundation by a participant, we will reward the participant with the most portion of the reward based on Coin_Age, but to a much lesser extent, the donation amount.<br />
<br><br />
<br />
Example (One Tithe with 7 days coin age, 1,000 donation):<br />
Coin Value : 25000, Coin Age: 7 days, Donation Amount: 1,000 bbp. Points Accrued = 25000 * 7 * CubedRoot(1000^(1/3)=10) = 1,750,000 points<br />
<br />
Example 2 (One Tithe with 3.4 days coin age, 24,000 donation):<br />
Coin Value: 25000, Coin Age: 3.4 days, Donation Amount: 24,000 bbp. Points Accrued = 25000 * 3.4 * CubedRoot(24000^(1/3)=28.84) = 2,451,400 points<br />
<br><br />
More than one Tithe per day results in points being summed to the CPK-Participant.<br />
<br><br />
Since One campaign exists, the entire GSC budget is allocated to one campaign, however in the future GSC budgets are split among campaigns.<br />
<br><br />
The campaign points are summed and converted into Total Prominence per participant, so that a CPK may see their assessed total Prominence per user Or points per Campaign.<br />
<br><br />
The Budget is divided by Prominence and converted to payment amounts in the GSC.<br />
<br><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
'''ADDENDUM'''<br />
<br />
'''Campaign Examples and Payment Example'''<br />
<br />
<br><br />
Let us assume we have 2 campaigns in BiblePay: BiblePay POG and BiblePay Interest as live campaigns. <br />
<br><br />
<br />
The BiblePay interest campaign pays 1% annual interest for a users proven UTXO balance.<br />
<br><br />
The BiblePay POG campaign pays a reward of (Coin*Age*CubedRoot(Tithe_To_Foundation_Amount)) for a daily foundation tithe.<br />
<br><br />
(Campaign parameters are malleable and votable by sanctuary proposals - and parameters updateable by spork).<br />
<br><br />
<br />
If User A belongs to both Campaign A, B, User A's miner will automatically iterate through each campaign and create a GSC-Transmission for each campaign, once per day, using the configurable percentage per campaign of balance available for GSCs, in one transaction per campaign (this prevents network spam). The GSC-client will automatically loop through campaigns joined by the user and try to participate in them.<br />
<br />
<br><br />
<br><br />
'''RPC COMMANDS'''<br />
<br />
<br />
<br><br />
<br />
How do I create a CPK (Christian-public-keypair)?<br />
exec cpk nickname<br />
<br />
<br />
<br><br />
<br />
How do I join Project #1 - POG?<br />
<br />
exec join pog<br />
<br />
How do I join Project #2 - Healing?<br />
<br />
exec join healing<br />
<br />
<br><br />
How do I know if my node contributed to POG?<br />
<br />
Look for a transaction on the transaction list labeled "GSC transmission"<br />
<br />
<br><br />
<br />
How do I change the default quantity of coins my node accesses for a GSC transmission?<br />
<br />
The node uses half of your coins by default, once every 24 hours (1 hour in testnet). To change this, change the key:<br />
pog_coinagepercentage=0.80<br />
This will make your node use 80% of your coins.<br />
<br />
<br />
How do I change the default foundation donation amount per day?<br />
<br />
The node tithes 2.5 BBP once every 12 hours by default. To change this, change the key:<br />
pog_foundationdonation=1000<br />
This will make your node send 1000 BBP per GSC transmission.<br />
<br />
[[Category:Concepts]]<br />
[[Category:Evolution]]</div>Sunk818https://wiki.biblepay.org/index.php?title=Generic_Smart_Contracts&diff=6255Generic Smart Contracts2019-06-12T17:38:20Z<p>Sunk818: changed tithe amount and frequency</p>
<hr />
<div><br />
'''BIBLEPAY EVOLUTION - GENERIC SMART CONTRACTS'''<br />
<br />
Generic Smart Contracts (GSC's) allow BiblePay to accomplish its goals without disrupting quality of service for our users. These contracts provide a modular abstract interface for user rewards, and exciting capabilities that are not possible in hard consensus systems. <br />
<br><br />
<br />
Some of the features our GSC's include: payments based on campaigns, corporate turnkey integration, c#/stratis integration, Restful API oracles, web tipping, decentralized voting on Christian objects, Christian economy features, and more.<br />
<br><br />
<br />
<br><br />
<br />
<br />
'''Generic Smart Contract Format'''<br />
<br />
The GSC is split into a client server architecture. The client side user joins campaigns with a CPK (Christian Public Keypair) and competes in these campaigns for points. The server side (our Sanctuaries) assess user points and tracks user progress. Once per day, the points are converted and paid in a Generic Smart Contract. The GSC is voted on by the Sanctuaries automatically at a certain chain height.<br />
<br><br />
<br />
The GSC is paid once per day as a superblock from BiblePay core, and is split among campaigns by points rewarded per campaign per user. <br />
<br><br />
<br />
Sanctuaries assess the points per campaign per user, and allocate the total daily reward amount by points to participants. <br />
<br />
<br><br />
<br><br />
<br />
'''CAMPAIGNS'''<br />
<br />
<br />
BiblePay will support an unlimited amount of campaigns over the long term. Each campaign will have a name, a distinct purpose, and a set of rules and formulas that adhere to the GSC-Server-Abstraction-Layer.<br />
<br />
<br><br />
<br />
A user joins a campaign by typing a command (see RPC commands). The user must have a Christian Public Keypair to join a campaign (see RPC commands). <br />
<br><br />
<br />
<br />
'''Sanctuary Side'''<br />
<br />
<br />
The sanctuaries will assess the points for each user, by looping through all live campaigns, and assessing the amount of points that should be assigned to each user and assigning Points. <br />
<br><br />
NOTE: If multiple transactions were sent by a user in one day, the user points will be summed.<br />
<br />
<br><br />
<br />
If the user has a 1 million balance in stake, the interest component will be 27 points, while the POG campaign reward=1000 points, equaling 1027 points for the day (see detailed example for more information).<br />
<br><br />
<br />
Once the points are assessed at a daily quorum height, the sanctuaries will auto-vote on these points.<br />
<br><br />
<br />
The daily generic smart contract will automatically convert points to BBP rewards in the superblock generator module.<br />
<br><br />
<br><br />
'''Christian Economy Integration'''<br />
<br />
<br><br />
The GSC system enables biblepay to create an exciting new campaign type for Christian economies in the future: HTML5 voting and HTML5 tipping. <br />
<br><br />
In voting, it will be possible for a user to navigate to a list of Christian objects (say for instance, Orphan outgoing letters), and vote on these letters with their CPK. <br />
<br><br />
The sanctuary will pick up votes for the "Orphan Letters" campaign automatically, allowing points to be rewarded in that campaign for voting activity from the 'Orphan' campaign budget.<br />
<br><br />
The same can be done with any list of Christian objects, for example, a list of "Rapture video objects". As users vote on these items, the HTML5 vote will be picked up and converted to points according to the rules of the campaign.<br />
<br />
<br><br />
<br />
'''Christian Public Keypair Reputation Score'''<br />
<br />
<br />
Since an individual user will create a CPK to participate, it will be possible for the user to accumulate a reputation score, based on behavior. This will open up exciting possibilities for our network for future campaigns that reward points based on behavior. One example of negative behavior is if someone consistently votes down high quality content. If the users reputation score decreases, this user may be rewarded less share percentage in some campaigns (because activity is of low caliber). <br />
<br><br />
<br />
<br />
As voting activity is assessed, the CPK will accumulate a reputation score change. Over time, it will be preferable for the user to keep the existing CPK (due to the positive reputation score) rather than create multiple keys or recreate the keypair. The reputation score may then be used to influence payout percentages in some activities, after it is established that reputation scores are accurate.<br />
<br><br />
<br><br />
<br><br />
<br />
'''Corporate GSC Integration'''<br />
<br><br />
<br />
A very exciting feature BiblePay will offer in our GSC system is corporate integration. This is a value add for corporations who do not want to spend hours learning blockchain programming to make cryptocurrency payments automatically. <br />
<br><br />
This feature allows a corporate developer to configure a recurring or one-time payment to be made easily through the blockchain to a vendor by emitting a coinbase payment in our GSC.<br />
<br><br />
<br><br />
<br />
'''Evolution Anti-BotNet Features, 51% attack prevention with ChainLocks'''<br />
<br><br />
<br />
In Evolution, we have built in a brand new feature called ABN (anti-botnet). The original use-case for ABN stems from our mission to prevent ASIC/GPU ports, run BiblePay on commodity PCs, and create a fair mining environment without groups of monopolies forming (IE Asic monopolies) who take a large percentage of mining rewards. Even with CPU mining, we have seen some rich actors, who own 300 servers, point all the hash power at BiblePay and take an unduly large percentage of daily rewards. On one hand, we agree, they have every right to. But on the other hand, we really would like to appeal to distinct head count so as to expose more people to the Gospel. In light of this we have released ABN, which requires a certain amount of coin*age to be present in each mined block in order to mine BiblePay. What this does is quickly uses up coin*age when an attack occurs (to give an example, if you are BotNet with 50 PCs, and your wallet balance is 50,000, after solving a few blocks with high hash power your wallet will run out of coin*age and you will not be able to mine more BiblePay until coin*age increases).<br />
<br><br />
<br />
The feature works like this. Our network requires an average calculated and pre-assessed static amount (posted in getmininginfo) of required coin*age and stores this in the chain. Each miner checks this number, and will search the wallet (this is all automatic) for coins totaling the requirement and place these coins in an ABN Stake transaction - and then begin mining. We do allow mining for All participants if a block is over 60 minutes old (this is so that our chain never stops if every single participant runs out of coin age).<br />
<br><br />
In this way, every block mined in Evolution is sure to be solved by a normal participant and not a bot-net over time.<br />
<br><br />
In addition to all of this, we have inherited Dash's 51% attack prevention system (ChainLocks). We have this feature fully merged in and ready to be released. This is an amazing addition to BiblePay, as it removes 51% attack risk by almost 100%. This is accomplished by asking our Sanctuaries to keep track of each solved block and not allow deep reorganizations once ChainLocks are live.<br />
<br />
<br><br />
<br><br />
<br />
'''Deployment Timeline and Roadmap changes'''<br />
<br><br />
<br />
<br />
For BiblePay Evolution, we will start by releasing One campaign: Proof-of-Giving. This will prove the entire GSC concept in testnet from end-to-end, with a daily smart contract being emitted, CPK users being registered and participating in the first campaign, the Sanctuaries assessing the points, Sanctuaries voting, and payments being made.<br />
<br><br />
<br />
After the release of Evolution, our IT team will continue to develop the Corporate integration, additional new campaigns, and HTML5 integration.<br />
<br><br />
<br><br />
<br />
<br />
''' BiblePay Architecture Changes for Reliability, Mass Development and Mass Adoption '''<br />
<br><br />
<br><br />
<br />
In order to maintain a reliable environment in production, we have decided to change our current architecture. We are changing procedures to prevent or minimize production deployments that: <br />
Change consensus, or Add client-side features. Both of these things may be valuable in the long term (for example a new campaign allowing web tipping, or a gospel feature for Spiritual Warfare), but, not at the expense of the Quality of Service for those using BBP in prod, or for Exchanges or Sanctuaries. <br />
<br />
<br><br />
In light of this, we have designed a new architecture where we will demarcate and abstract the core client from the Sanctuary in a way where BiblePay-IT may deploy consensus changes on the Sanctuary side only. This will be accomplished by creating a client side abstraction interface the core client will adhere to.<br />
<br />
<br><br />
Our goal is that when we release Evolution, the client side contract will no longer change, and therefore updates to the sanctuary will not require upgrades for the users or exchanges.<br />
<br><br />
We will accomplish this by deploying incremental updates to the sanctuaries that allow the consensus mechanism to be updated on the server side only. This means that when a new campaign is released (let us say for example, web tipping), the Sanctuaries will need to upgrade, but not the users, and the exchanges and network will not endure a hard fork. After the Sancs upgrade, web tipping will be announced and users may "join web tip campaign" and automatically receive rewards via the daily GSC.<br />
<br><br />
<br />
Another large change that is occurring is our move toward an additional HTML5 GUI for new UI pages. We believes we will attract HTML5 web developers that will give us the bandwidth to build out pages such as Orphan writing, Orphan voting, Lists of Christian Objects, Embedded Christian Videos, etc. This also accomplishes our goal of not upgrading the core client during new GUI changes as these pages adhere to the new model.<br />
<br><br />
Part of this change will mean that when a user navigates to a Christian Space resource, we will honor their CPK (Christian public keypair) as authentication, and this will allow the user to vote on the resource or view it , as the resource will know their voting ability and reputation score. This will allow the user to navigate into BiblePay's additional UI pages.<br />
<br><br />
<br />
These exciting features are being added to BiblePay to make your user experience smoother and provide a high quality production Environment.<br />
<br />
<br><br />
<br />
<br />
<br />
'''Modularity and Extensibility'''<br />
<br />
<br><br />
To help remove IT development bottlenecks in the UI area, our dev team is making BiblePay-Evolution HTML work in a way where non-C++ devs (web devs) may participate in development and deploy GUI changes. <br />
<br><br />
To give an example of how this will work, we have a background project with Kestrel and Sanctuaries, so that BiblePay will emit HTML5 markup from sanctuaries. This will allow webdevs to participate in: Creating Christian Spaces, building out BiblePay, and modifying BiblePay UI in a modular and extensible way, without knowing how to be a blockchain programmer. <br />
<br><br />
To the end user this means we will have tens to hundreds of new pages in the wallet in Christian Spaces in the future, allowing us to vote on these objects with our CPK and therefore our reputation scores will change, and we hope the experience will be edifying for everyone, giving BiblePay a truly valuable purpose.<br />
<br><br />
<br />
<br />
<br />
'''RoadMap Modifications'''<br />
<br />
<br><br />
<br />
March 2019: Release Evolution to Testnet. Test normal core wallet functions: Sanctuary creation, sanctuary operation, receive/send money, proposals, etc.<br />
<br><br />
<br />
Mid April 2019: Test GSCs in TestNet, ensure payments work, campaigns emit points, campaigns can be joined and unjoined, and CPKs work. Ensure the first campaign (POG) works properly.<br />
<br><br />
<br />
May 2019: Finish testing Evo, release Evo to Prod. Go Live with Evo and GSC (Generic Smart Contracts) - and One Campaign in Prod! (POG).<br />
<br><br />
<br />
July 2019: Finish modifications to server side GSC's, alter any business logic. Add additional Campaign if necessary. <br />
<br><br />
<br />
September 2019: Release Christian spaces (Allow voting on Christian objects, allow navigation of decentralized UI by CPKs). <br />
<br><br />
<br />
September 10th, 2019: Make a very important announcement regarding the future of BiblePay (IE the announcement that was promised this year) - regarding a feature that cannot be disclosed until September due to the sensitive nature of the subject. What we can say, is this item gives BiblePay the ability to be a 'serious contender' in the space.<br />
<br><br />
<br />
Dec 2019: Release Corporate Integration features. This allows 3rd party sites like (Steve Cioccolanti to integrate with BiblePay), c# Payments, Reports from Stratis, and also allows us to create DOCS (decentralized orphan contracts).<br />
<br><br />
<br />
<br />
<br />
<br />
'''Our first Campaign - POG (Proof-of-Giving)'''<br />
<br />
<br><br />
<br />
Notes about Campaigns: A user cannot join any campaigns unless they have a CPK (A Christian-public-keypair). You only need one CPK for life. The CPK is stored in your wallet.dat so when you move to a new machine you will still have your CPK. If you want to join multiple projects, you should create ONE CPK, then join each project with the join command. You will receive an error if you do not have a CPK and attempt to join a project. (If you try to create multiple CPKs you will receive an error).<br />
<br><br />
<br />
Attributes of Campaign 1 (POG):<br />
<br><br />
<br />
Assessment Includes:<br />
All users with a CPK who have joined campaign "POG"<br />
<br />
Requirements:<br />
A contribution sent to the Orphan Foundation during the last 24 hour period<br />
<br />
Assessment:<br />
Sum of( (Coin_Amount * 1) * (Coin_Age_Days * 1) * (CubedRoot(Tithe_To_Foundation)))<br />
<br><br />
Meaning:<br />
For each donation to the foundation by a participant, we will reward the participant with the most portion of the reward based on Coin_Age, but to a much lesser extent, the donation amount.<br />
<br><br />
<br />
Example (One Tithe with 7 days coin age, 1,000 donation):<br />
Coin Value : 25000, Coin Age: 7 days, Donation Amount: 1,000 bbp. Points Accrued = 25000 * 7 * CubedRoot(1000^(1/3)=10) = 1,750,000 points<br />
<br />
Example 2 (One Tithe with 3.4 days coin age, 24,000 donation):<br />
Coin Value: 25000, Coin Age: 3.4 days, Donation Amount: 24,000 bbp. Points Accrued = 25000 * 3.4 * CubedRoot(24000^(1/3)=28.84) = 2,451,400 points<br />
<br><br />
More than one Tithe per day results in points being summed to the CPK-Participant.<br />
<br><br />
Since One campaign exists, the entire GSC budget is allocated to one campaign, however in the future GSC budgets are split among campaigns.<br />
<br><br />
The campaign points are summed and converted into Total Prominence per participant, so that a CPK may see their assessed total Prominence per user Or points per Campaign.<br />
<br><br />
The Budget is divided by Prominence and converted to payment amounts in the GSC.<br />
<br><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
'''ADDENDUM'''<br />
<br />
'''Campaign Examples and Payment Example'''<br />
<br />
<br><br />
Let us assume we have 2 campaigns in BiblePay: BiblePay POG and BiblePay Interest as live campaigns. <br />
<br><br />
<br />
The BiblePay interest campaign pays 1% annual interest for a users proven UTXO balance.<br />
<br><br />
The BiblePay POG campaign pays a reward of (Coin*Age*CubedRoot(Tithe_To_Foundation_Amount)) for a daily foundation tithe.<br />
<br><br />
(Campaign parameters are malleable and votable by sanctuary proposals - and parameters updateable by spork).<br />
<br><br />
<br />
If User A belongs to both Campaign A, B, User A's miner will automatically iterate through each campaign and create a GSC-Transmission for each campaign, once per day, using the configurable percentage per campaign of balance available for GSCs, in one transaction per campaign (this prevents network spam). The GSC-client will automatically loop through campaigns joined by the user and try to participate in them.<br />
<br />
<br><br />
<br><br />
'''RPC COMMANDS'''<br />
<br />
<br />
<br><br />
<br />
How do I create a CPK (Christian-public-keypair)?<br />
exec cpk nickname<br />
<br />
<br />
<br><br />
<br />
How do I join Project #1 - POG?<br />
<br />
exec join pog<br />
<br />
How do I join Project #2 - Healing?<br />
<br />
exec join healing<br />
<br />
<br><br />
How do I know if my node contributed to POG?<br />
<br />
Look for a transaction on the transaction list labeled "GSC transmission"<br />
<br />
<br><br />
<br />
How do I change the default quantity of coins my node accesses for a GSC transmission?<br />
<br />
The node uses half of your coins by default, once every 24 hours (1 hour in testnet). To change this, change the key:<br />
pog_coinagepercentage=.80<br />
This will make your node use 80% of your coins.<br />
<br />
<br />
How do I change the default foundation donation amount per day?<br />
<br />
The node tithes 2.5 BBP every 12 hours by default. To change this, change the key:<br />
pog_foundationdonation=1000<br />
This will make your node send 1000 BBP per GSC transmission.<br />
<br />
[[Category:Concepts]]<br />
[[Category:Evolution]]</div>Sunk818https://wiki.biblepay.org/index.php?title=Generic_Smart_Contracts&diff=6254Generic Smart Contracts2019-06-12T17:36:06Z<p>Sunk818: added how to join project #2 healing</p>
<hr />
<div><br />
'''BIBLEPAY EVOLUTION - GENERIC SMART CONTRACTS'''<br />
<br />
Generic Smart Contracts (GSC's) allow BiblePay to accomplish its goals without disrupting quality of service for our users. These contracts provide a modular abstract interface for user rewards, and exciting capabilities that are not possible in hard consensus systems. <br />
<br><br />
<br />
Some of the features our GSC's include: payments based on campaigns, corporate turnkey integration, c#/stratis integration, Restful API oracles, web tipping, decentralized voting on Christian objects, Christian economy features, and more.<br />
<br><br />
<br />
<br><br />
<br />
<br />
'''Generic Smart Contract Format'''<br />
<br />
The GSC is split into a client server architecture. The client side user joins campaigns with a CPK (Christian Public Keypair) and competes in these campaigns for points. The server side (our Sanctuaries) assess user points and tracks user progress. Once per day, the points are converted and paid in a Generic Smart Contract. The GSC is voted on by the Sanctuaries automatically at a certain chain height.<br />
<br><br />
<br />
The GSC is paid once per day as a superblock from BiblePay core, and is split among campaigns by points rewarded per campaign per user. <br />
<br><br />
<br />
Sanctuaries assess the points per campaign per user, and allocate the total daily reward amount by points to participants. <br />
<br />
<br><br />
<br><br />
<br />
'''CAMPAIGNS'''<br />
<br />
<br />
BiblePay will support an unlimited amount of campaigns over the long term. Each campaign will have a name, a distinct purpose, and a set of rules and formulas that adhere to the GSC-Server-Abstraction-Layer.<br />
<br />
<br><br />
<br />
A user joins a campaign by typing a command (see RPC commands). The user must have a Christian Public Keypair to join a campaign (see RPC commands). <br />
<br><br />
<br />
<br />
'''Sanctuary Side'''<br />
<br />
<br />
The sanctuaries will assess the points for each user, by looping through all live campaigns, and assessing the amount of points that should be assigned to each user and assigning Points. <br />
<br><br />
NOTE: If multiple transactions were sent by a user in one day, the user points will be summed.<br />
<br />
<br><br />
<br />
If the user has a 1 million balance in stake, the interest component will be 27 points, while the POG campaign reward=1000 points, equaling 1027 points for the day (see detailed example for more information).<br />
<br><br />
<br />
Once the points are assessed at a daily quorum height, the sanctuaries will auto-vote on these points.<br />
<br><br />
<br />
The daily generic smart contract will automatically convert points to BBP rewards in the superblock generator module.<br />
<br><br />
<br><br />
'''Christian Economy Integration'''<br />
<br />
<br><br />
The GSC system enables biblepay to create an exciting new campaign type for Christian economies in the future: HTML5 voting and HTML5 tipping. <br />
<br><br />
In voting, it will be possible for a user to navigate to a list of Christian objects (say for instance, Orphan outgoing letters), and vote on these letters with their CPK. <br />
<br><br />
The sanctuary will pick up votes for the "Orphan Letters" campaign automatically, allowing points to be rewarded in that campaign for voting activity from the 'Orphan' campaign budget.<br />
<br><br />
The same can be done with any list of Christian objects, for example, a list of "Rapture video objects". As users vote on these items, the HTML5 vote will be picked up and converted to points according to the rules of the campaign.<br />
<br />
<br><br />
<br />
'''Christian Public Keypair Reputation Score'''<br />
<br />
<br />
Since an individual user will create a CPK to participate, it will be possible for the user to accumulate a reputation score, based on behavior. This will open up exciting possibilities for our network for future campaigns that reward points based on behavior. One example of negative behavior is if someone consistently votes down high quality content. If the users reputation score decreases, this user may be rewarded less share percentage in some campaigns (because activity is of low caliber). <br />
<br><br />
<br />
<br />
As voting activity is assessed, the CPK will accumulate a reputation score change. Over time, it will be preferable for the user to keep the existing CPK (due to the positive reputation score) rather than create multiple keys or recreate the keypair. The reputation score may then be used to influence payout percentages in some activities, after it is established that reputation scores are accurate.<br />
<br><br />
<br><br />
<br><br />
<br />
'''Corporate GSC Integration'''<br />
<br><br />
<br />
A very exciting feature BiblePay will offer in our GSC system is corporate integration. This is a value add for corporations who do not want to spend hours learning blockchain programming to make cryptocurrency payments automatically. <br />
<br><br />
This feature allows a corporate developer to configure a recurring or one-time payment to be made easily through the blockchain to a vendor by emitting a coinbase payment in our GSC.<br />
<br><br />
<br><br />
<br />
'''Evolution Anti-BotNet Features, 51% attack prevention with ChainLocks'''<br />
<br><br />
<br />
In Evolution, we have built in a brand new feature called ABN (anti-botnet). The original use-case for ABN stems from our mission to prevent ASIC/GPU ports, run BiblePay on commodity PCs, and create a fair mining environment without groups of monopolies forming (IE Asic monopolies) who take a large percentage of mining rewards. Even with CPU mining, we have seen some rich actors, who own 300 servers, point all the hash power at BiblePay and take an unduly large percentage of daily rewards. On one hand, we agree, they have every right to. But on the other hand, we really would like to appeal to distinct head count so as to expose more people to the Gospel. In light of this we have released ABN, which requires a certain amount of coin*age to be present in each mined block in order to mine BiblePay. What this does is quickly uses up coin*age when an attack occurs (to give an example, if you are BotNet with 50 PCs, and your wallet balance is 50,000, after solving a few blocks with high hash power your wallet will run out of coin*age and you will not be able to mine more BiblePay until coin*age increases).<br />
<br><br />
<br />
The feature works like this. Our network requires an average calculated and pre-assessed static amount (posted in getmininginfo) of required coin*age and stores this in the chain. Each miner checks this number, and will search the wallet (this is all automatic) for coins totaling the requirement and place these coins in an ABN Stake transaction - and then begin mining. We do allow mining for All participants if a block is over 60 minutes old (this is so that our chain never stops if every single participant runs out of coin age).<br />
<br><br />
In this way, every block mined in Evolution is sure to be solved by a normal participant and not a bot-net over time.<br />
<br><br />
In addition to all of this, we have inherited Dash's 51% attack prevention system (ChainLocks). We have this feature fully merged in and ready to be released. This is an amazing addition to BiblePay, as it removes 51% attack risk by almost 100%. This is accomplished by asking our Sanctuaries to keep track of each solved block and not allow deep reorganizations once ChainLocks are live.<br />
<br />
<br><br />
<br><br />
<br />
'''Deployment Timeline and Roadmap changes'''<br />
<br><br />
<br />
<br />
For BiblePay Evolution, we will start by releasing One campaign: Proof-of-Giving. This will prove the entire GSC concept in testnet from end-to-end, with a daily smart contract being emitted, CPK users being registered and participating in the first campaign, the Sanctuaries assessing the points, Sanctuaries voting, and payments being made.<br />
<br><br />
<br />
After the release of Evolution, our IT team will continue to develop the Corporate integration, additional new campaigns, and HTML5 integration.<br />
<br><br />
<br><br />
<br />
<br />
''' BiblePay Architecture Changes for Reliability, Mass Development and Mass Adoption '''<br />
<br><br />
<br><br />
<br />
In order to maintain a reliable environment in production, we have decided to change our current architecture. We are changing procedures to prevent or minimize production deployments that: <br />
Change consensus, or Add client-side features. Both of these things may be valuable in the long term (for example a new campaign allowing web tipping, or a gospel feature for Spiritual Warfare), but, not at the expense of the Quality of Service for those using BBP in prod, or for Exchanges or Sanctuaries. <br />
<br />
<br><br />
In light of this, we have designed a new architecture where we will demarcate and abstract the core client from the Sanctuary in a way where BiblePay-IT may deploy consensus changes on the Sanctuary side only. This will be accomplished by creating a client side abstraction interface the core client will adhere to.<br />
<br />
<br><br />
Our goal is that when we release Evolution, the client side contract will no longer change, and therefore updates to the sanctuary will not require upgrades for the users or exchanges.<br />
<br><br />
We will accomplish this by deploying incremental updates to the sanctuaries that allow the consensus mechanism to be updated on the server side only. This means that when a new campaign is released (let us say for example, web tipping), the Sanctuaries will need to upgrade, but not the users, and the exchanges and network will not endure a hard fork. After the Sancs upgrade, web tipping will be announced and users may "join web tip campaign" and automatically receive rewards via the daily GSC.<br />
<br><br />
<br />
Another large change that is occurring is our move toward an additional HTML5 GUI for new UI pages. We believes we will attract HTML5 web developers that will give us the bandwidth to build out pages such as Orphan writing, Orphan voting, Lists of Christian Objects, Embedded Christian Videos, etc. This also accomplishes our goal of not upgrading the core client during new GUI changes as these pages adhere to the new model.<br />
<br><br />
Part of this change will mean that when a user navigates to a Christian Space resource, we will honor their CPK (Christian public keypair) as authentication, and this will allow the user to vote on the resource or view it , as the resource will know their voting ability and reputation score. This will allow the user to navigate into BiblePay's additional UI pages.<br />
<br><br />
<br />
These exciting features are being added to BiblePay to make your user experience smoother and provide a high quality production Environment.<br />
<br />
<br><br />
<br />
<br />
<br />
'''Modularity and Extensibility'''<br />
<br />
<br><br />
To help remove IT development bottlenecks in the UI area, our dev team is making BiblePay-Evolution HTML work in a way where non-C++ devs (web devs) may participate in development and deploy GUI changes. <br />
<br><br />
To give an example of how this will work, we have a background project with Kestrel and Sanctuaries, so that BiblePay will emit HTML5 markup from sanctuaries. This will allow webdevs to participate in: Creating Christian Spaces, building out BiblePay, and modifying BiblePay UI in a modular and extensible way, without knowing how to be a blockchain programmer. <br />
<br><br />
To the end user this means we will have tens to hundreds of new pages in the wallet in Christian Spaces in the future, allowing us to vote on these objects with our CPK and therefore our reputation scores will change, and we hope the experience will be edifying for everyone, giving BiblePay a truly valuable purpose.<br />
<br><br />
<br />
<br />
<br />
'''RoadMap Modifications'''<br />
<br />
<br><br />
<br />
March 2019: Release Evolution to Testnet. Test normal core wallet functions: Sanctuary creation, sanctuary operation, receive/send money, proposals, etc.<br />
<br><br />
<br />
Mid April 2019: Test GSCs in TestNet, ensure payments work, campaigns emit points, campaigns can be joined and unjoined, and CPKs work. Ensure the first campaign (POG) works properly.<br />
<br><br />
<br />
May 2019: Finish testing Evo, release Evo to Prod. Go Live with Evo and GSC (Generic Smart Contracts) - and One Campaign in Prod! (POG).<br />
<br><br />
<br />
July 2019: Finish modifications to server side GSC's, alter any business logic. Add additional Campaign if necessary. <br />
<br><br />
<br />
September 2019: Release Christian spaces (Allow voting on Christian objects, allow navigation of decentralized UI by CPKs). <br />
<br><br />
<br />
September 10th, 2019: Make a very important announcement regarding the future of BiblePay (IE the announcement that was promised this year) - regarding a feature that cannot be disclosed until September due to the sensitive nature of the subject. What we can say, is this item gives BiblePay the ability to be a 'serious contender' in the space.<br />
<br><br />
<br />
Dec 2019: Release Corporate Integration features. This allows 3rd party sites like (Steve Cioccolanti to integrate with BiblePay), c# Payments, Reports from Stratis, and also allows us to create DOCS (decentralized orphan contracts).<br />
<br><br />
<br />
<br />
<br />
<br />
'''Our first Campaign - POG (Proof-of-Giving)'''<br />
<br />
<br><br />
<br />
Notes about Campaigns: A user cannot join any campaigns unless they have a CPK (A Christian-public-keypair). You only need one CPK for life. The CPK is stored in your wallet.dat so when you move to a new machine you will still have your CPK. If you want to join multiple projects, you should create ONE CPK, then join each project with the join command. You will receive an error if you do not have a CPK and attempt to join a project. (If you try to create multiple CPKs you will receive an error).<br />
<br><br />
<br />
Attributes of Campaign 1 (POG):<br />
<br><br />
<br />
Assessment Includes:<br />
All users with a CPK who have joined campaign "POG"<br />
<br />
Requirements:<br />
A contribution sent to the Orphan Foundation during the last 24 hour period<br />
<br />
Assessment:<br />
Sum of( (Coin_Amount * 1) * (Coin_Age_Days * 1) * (CubedRoot(Tithe_To_Foundation)))<br />
<br><br />
Meaning:<br />
For each donation to the foundation by a participant, we will reward the participant with the most portion of the reward based on Coin_Age, but to a much lesser extent, the donation amount.<br />
<br><br />
<br />
Example (One Tithe with 7 days coin age, 1,000 donation):<br />
Coin Value : 25000, Coin Age: 7 days, Donation Amount: 1,000 bbp. Points Accrued = 25000 * 7 * CubedRoot(1000^(1/3)=10) = 1,750,000 points<br />
<br />
Example 2 (One Tithe with 3.4 days coin age, 24,000 donation):<br />
Coin Value: 25000, Coin Age: 3.4 days, Donation Amount: 24,000 bbp. Points Accrued = 25000 * 3.4 * CubedRoot(24000^(1/3)=28.84) = 2,451,400 points<br />
<br><br />
More than one Tithe per day results in points being summed to the CPK-Participant.<br />
<br><br />
Since One campaign exists, the entire GSC budget is allocated to one campaign, however in the future GSC budgets are split among campaigns.<br />
<br><br />
The campaign points are summed and converted into Total Prominence per participant, so that a CPK may see their assessed total Prominence per user Or points per Campaign.<br />
<br><br />
The Budget is divided by Prominence and converted to payment amounts in the GSC.<br />
<br><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
'''ADDENDUM'''<br />
<br />
'''Campaign Examples and Payment Example'''<br />
<br />
<br><br />
Let us assume we have 2 campaigns in BiblePay: BiblePay POG and BiblePay Interest as live campaigns. <br />
<br><br />
<br />
The BiblePay interest campaign pays 1% annual interest for a users proven UTXO balance.<br />
<br><br />
The BiblePay POG campaign pays a reward of (Coin*Age*CubedRoot(Tithe_To_Foundation_Amount)) for a daily foundation tithe.<br />
<br><br />
(Campaign parameters are malleable and votable by sanctuary proposals - and parameters updateable by spork).<br />
<br><br />
<br />
If User A belongs to both Campaign A, B, User A's miner will automatically iterate through each campaign and create a GSC-Transmission for each campaign, once per day, using the configurable percentage per campaign of balance available for GSCs, in one transaction per campaign (this prevents network spam). The GSC-client will automatically loop through campaigns joined by the user and try to participate in them.<br />
<br />
<br><br />
<br><br />
'''RPC COMMANDS'''<br />
<br />
<br />
<br><br />
<br />
How do I create a CPK (Christian-public-keypair)?<br />
exec cpk nickname<br />
<br />
<br />
<br><br />
<br />
How do I join Project #1 - POG?<br />
<br />
exec join pog<br />
<br />
How do I join Project #2 - Healing?<br />
<br />
exec join healing<br />
<br />
<br><br />
How do I know if my node contributed to POG?<br />
Look for a transaction on the transaction list labeled "GSC transmission"<br />
<br />
<br><br />
<br />
How do I change the default quantity of coins my node accesses for a GSC transmission?<br />
The node uses half of your coins by default, once every 24 hours (1 hour in testnet). To change this, change the key:<br />
pog_coinagepercentage=.80<br />
This will make your node use 80% of your coins.<br />
<br />
<br />
How do I change the default foundation donation amount per day?<br />
The node tithes 7 BBP per day by default. To change this, change the key:<br />
pog_foundationdonation=1000<br />
This will make your node send 1000 BBP per GSC transmission.<br />
<br />
[[Category:Concepts]]<br />
[[Category:Evolution]]</div>Sunk818https://wiki.biblepay.org/index.php?title=Generic_Smart_Contracts&diff=6166Generic Smart Contracts2019-03-25T15:23:14Z<p>Sunk818: </p>
<hr />
<div><br />
'''BIBLEPAY EVOLUTION - GENERIC SMART CONTRACTS'''<br />
<br />
Generic Smart Contracts (GSC's) allow BiblePay to accomplish its goals without disrupting quality of service for our users. These contracts provide a modular abstract interface for user rewards, and exciting capabilities that are not possible in hard consensus systems. <br />
<br><br />
<br />
Some of the features our GSC's include: payments based on campaigns, corporate turnkey integration, c#/stratis integration, Restful API oracles, web tipping, decentralized voting on Christian objects, Christian economy features, and more.<br />
<br><br />
<br />
<br><br />
<br />
<br />
'''Generic Smart Contract Format'''<br />
<br />
The GSC is split into a client server architecture. The client side user joins campaigns with a CPK (Christian Public Keypair) and competes in these campaigns for points. The server side (our Sanctuaries) assess user points and tracks user progress. Once per day, the points are converted and paid in a Generic Smart Contract. The GSC is voted on by the Sanctuaries automatically at a certain chain height.<br />
<br><br />
<br />
The GSC is paid once per day as a superblock from BiblePay core, and is split among campaigns by points rewarded per campaign per user. <br />
<br><br />
<br />
Sanctuaries assess the points per campaign per user, and allocate the total daily reward amount by points to participants. <br />
<br />
<br><br />
<br><br />
<br />
'''CAMPAIGNS'''<br />
<br />
<br />
BiblePay will support an unlimited amount of campaigns over the long term. Each campaign will have a name, a distinct purpose, and a set of rules and formulas that adhere to the GSC-Server-Abstraction-Layer.<br />
<br />
<br><br />
<br />
A user joins a campaign by typing a command (see RPC commands). The user must have a Christian Public Keypair to join a campaign (see RPC commands). <br />
<br><br />
<br />
<br />
'''Sanctuary Side'''<br />
<br />
<br />
The sanctuaries will assess the points for each user, by looping through all live campaigns, and assessing the amount of points that should be assigned to each user and assigning Points. <br />
<br><br />
NOTE: If multiple transactions were sent by a user in one day, the user points will be summed.<br />
<br />
<br><br />
<br />
If the user has a 1 million balance in stake, the interest component will be 27 points, while the POG campaign reward=1000 points, equaling 1027 points for the day (see detailed example for more information).<br />
<br><br />
<br />
Once the points are assessed at a daily quorum height, the sanctuaries will auto-vote on these points.<br />
<br><br />
<br />
The daily generic smart contract will automatically convert points to BBP rewards in the superblock generator module.<br />
<br><br />
<br><br />
'''Christian Economy Integration'''<br />
<br />
<br><br />
The GSC system enables biblepay to create an exciting new campaign type for Christian economies in the future: HTML5 voting and HTML5 tipping. <br />
<br><br />
In voting, it will be possible for a user to navigate to a list of Christian objects (say for instance, Orphan outgoing letters), and vote on these letters with their CPK. <br />
<br><br />
The sanctuary will pick up votes for the "Orphan Letters" campaign automatically, allowing points to be rewarded in that campaign for voting activity from the 'Orphan' campaign budget.<br />
<br><br />
The same can be done with any list of Christian objects, for example, a list of "Rapture video objects". As users vote on these items, the HTML5 vote will be picked up and converted to points according to the rules of the campaign.<br />
<br />
<br><br />
<br />
'''Christian Public Keypair Reputation Score'''<br />
<br />
<br />
Since an individual user will create a CPK to participate, it will be possible for the user to accumulate a reputation score, based on behavior. This will open up exciting possibilities for our network for future campaigns that reward points based on behavior. One example of negative behavior is if someone consistently votes down high quality content. If the users reputation score decreases, this user may be rewarded less share percentage in some campaigns (because activity is of low caliber). <br />
<br><br />
<br />
<br />
As voting activity is assessed, the CPK will accumulate a reputation score change. Over time, it will be preferable for the user to keep the existing CPK (due to the positive reputation score) rather than create multiple keys or recreate the keypair. The reputation score may then be used to influence payout percentages in some activities, after it is established that reputation scores are accurate.<br />
<br><br />
<br><br />
<br><br />
<br />
'''Corporate GSC Integration'''<br />
<br><br />
<br />
A very exciting feature BiblePay will offer in our GSC system is corporate integration. This is a value add for corporations who do not want to spend hours learning blockchain programming to make cryptocurrency payments automatically. <br />
<br><br />
This feature allows a corporate developer to configure a recurring or one-time payment to be made easily through the blockchain to a vendor by emitting a coinbase payment in our GSC.<br />
<br><br />
<br><br />
<br />
'''Evolution Anti-BotNet Features, 51% attack prevention with ChainLocks'''<br />
<br><br />
<br />
In Evolution, we have built in a brand new feature called ABN (anti-botnet). The original use-case for ABN stems from our mission to prevent ASIC/GPU ports, run BiblePay on commodity PCs, and create a fair mining environment without groups of monopolies forming (IE Asic monopolies) who take a large percentage of mining rewards. Even with CPU mining, we have seen some rich actors, who own 300 servers, point all the hash power at BiblePay and take an unduly large percentage of daily rewards. On one hand, we agree, they have every right to. But on the other hand, we really would like to appeal to distinct head count so as to expose more people to the Gospel. In light of this we have released ABN, which requires a certain amount of coin*age to be present in each mined block in order to mine BiblePay. What this does is quickly uses up coin*age when an attack occurs (to give an example, if you are BotNet with 50 PCs, and your wallet balance is 50,000, after solving a few blocks with high hash power your wallet will run out of coin*age and you will not be able to mine more BiblePay until coin*age increases).<br />
<br><br />
<br />
The feature works like this. Our network requires an average calculated and pre-assessed static amount (posted in getmininginfo) of required coin*age and stores this in the chain. Each miner checks this number, and will search the wallet (this is all automatic) for coins totaling the requirement and place these coins in an ABN Stake transaction - and then begin mining. We do allow mining for All participants if a block is over 60 minutes old (this is so that our chain never stops if every single participant runs out of coin age).<br />
<br><br />
In this way, every block mined in Evolution is sure to be solved by a normal participant and not a bot-net over time.<br />
<br><br />
In addition to all of this, we have inherited Dash's 51% attack prevention system (ChainLocks). We have this feature fully merged in and ready to be released. This is an amazing addition to BiblePay, as it removes 51% attack risk by almost 100%. This is accomplished by asking our Sanctuaries to keep track of each solved block and not allow deep reorganizations once ChainLocks are live.<br />
<br />
<br><br />
<br><br />
<br />
'''Deployment Timeline and Roadmap changes'''<br />
<br><br />
<br />
<br />
For BiblePay Evolution, we will start by releasing One campaign: Proof-of-Giving. This will prove the entire GSC concept in testnet from end-to-end, with a daily smart contract being emitted, CPK users being registered and participating in the first campaign, the Sanctuaries assessing the points, Sanctuaries voting, and payments being made.<br />
<br><br />
<br />
After the release of Evolution, our IT team will continue to develop the Corporate integration, additional new campaigns, and HTML5 integration.<br />
<br><br />
<br><br />
<br />
<br />
''' BiblePay Architecture Changes for Reliability, Mass Development and Mass Adoption '''<br />
<br><br />
<br><br />
<br />
In order to maintain a reliable environment in production, we have decided to change our current architecture. We are changing procedures to prevent or minimize production deployments that: <br />
Change consensus, or Add client-side features. Both of these things may be valuable in the long term (for example a new campaign allowing web tipping, or a gospel feature for Spiritual Warfare), but, not at the expense of the Quality of Service for those using BBP in prod, or for Exchanges or Sanctuaries. <br />
<br />
<br><br />
In light of this, we have designed a new architecture where we will demarcate and abstract the core client from the Sanctuary in a way where BiblePay-IT may deploy consensus changes on the Sanctuary side only. This will be accomplished by creating a client side abstraction interface the core client will adhere to.<br />
<br />
<br><br />
Our goal is that when we release Evolution, the client side contract will no longer change, and therefore updates to the sanctuary will not require upgrades for the users or exchanges.<br />
<br><br />
We will accomplish this by deploying incremental updates to the sanctuaries that allow the consensus mechanism to be updated on the server side only. This means that when a new campaign is released (let us say for example, web tipping), the Sanctuaries will need to upgrade, but not the users, and the exchanges and network will not endure a hard fork. After the Sancs upgrade, web tipping will be announced and users may "join web tip campaign" and automatically receive rewards via the daily GSC.<br />
<br><br />
<br />
Another large change that is occurring is our move toward an additional HTML5 GUI for new UI pages. We believes we will attract HTML5 web developers that will give us the bandwidth to build out pages such as Orphan writing, Orphan voting, Lists of Christian Objects, Embedded Christian Videos, etc. This also accomplishes our goal of not upgrading the core client during new GUI changes as these pages adhere to the new model.<br />
<br><br />
Part of this change will mean that when a user navigates to a Christian Space resource, we will honor their CPK (Christian public keypair) as authentication, and this will allow the user to vote on the resource or view it , as the resource will know their voting ability and reputation score. This will allow the user to navigate into BiblePay's additional UI pages.<br />
<br><br />
<br />
These exciting features are being added to BiblePay to make your user experience smoother and provide a high quality production Environment.<br />
<br />
<br><br />
<br />
<br />
<br />
'''Modularity and Extensibility'''<br />
<br />
<br><br />
To help remove IT development bottlenecks in the UI area, our dev team is making BiblePay-Evolution HTML work in a way where non-C++ devs (web devs) may participate in development and deploy GUI changes. <br />
<br><br />
To give an example of how this will work, we have a background project with Kestrel and Sanctuaries, so that BiblePay will emit HTML5 markup from sanctuaries. This will allow webdevs to participate in: Creating Christian Spaces, building out BiblePay, and modifying BiblePay UI in a modular and extensible way, without knowing how to be a blockchain programmer. <br />
<br><br />
To the end user this means we will have tens to hundreds of new pages in the wallet in Christian Spaces in the future, allowing us to vote on these objects with our CPK and therefore our reputation scores will change, and we hope the experience will be edifying for everyone, giving BiblePay a truly valuable purpose.<br />
<br><br />
<br />
<br />
<br />
'''RoadMap Modifications'''<br />
<br />
<br><br />
<br />
March 2019: Release Evolution to Testnet. Test normal core wallet functions: Sanctuary creation, sanctuary operation, receive/send money, proposals, etc.<br />
<br><br />
<br />
Mid April 2019: Test GSCs in TestNet, ensure payments work, campaigns emit points, campaigns can be joined and unjoined, and CPKs work. Ensure the first campaign (POG) works properly.<br />
<br><br />
<br />
May 2019: Finish testing Evo, release Evo to Prod. Go Live with Evo and GSC (Generic Smart Contracts) - and One Campaign in Prod! (POG).<br />
<br><br />
<br />
July 2019: Finish modifications to server side GSC's, alter any business logic. Add additional Campaign if necessary. <br />
<br><br />
<br />
September 2019: Release Christian spaces (Allow voting on Christian objects, allow navigation of decentralized UI by CPKs). <br />
<br><br />
<br />
September 10th, 2019: Make a very important announcement regarding the future of BiblePay (IE the announcement that was promised this year) - regarding a feature that cannot be disclosed until September due to the sensitive nature of the subject. What we can say, is this item gives BiblePay the ability to be a 'serious contender' in the space.<br />
<br><br />
<br />
Dec 2019: Release Corporate Integration features. This allows 3rd party sites like (Steve Cioccolanti to integrate with BiblePay), c# Payments, Reports from Stratis, and also allows us to create DOCS (decentralized orphan contracts).<br />
<br><br />
<br />
<br />
<br />
<br />
'''Our first Campaign - POG (Proof-of-Giving)'''<br />
<br />
<br><br />
<br />
Notes about Campaigns: A user cannot join any campaigns unless they have a CPK (A Christian-public-keypair). You only need one CPK for life. The CPK is stored in your wallet.dat so when you move to a new machine you will still have your CPK. If you want to join multiple projects, you should create ONE CPK, then join each project with the join command. You will receive an error if you do not have a CPK and attempt to join a project. (If you try to create multiple CPKs you will receive an error).<br />
<br><br />
<br />
Attributes of Campaign 1 (POG):<br />
<br><br />
<br />
Assessment Includes:<br />
All users with a CPK who have joined campaign "POG"<br />
<br />
Requirements:<br />
A contribution sent to the Orphan Foundation during the last 24 hour period<br />
<br />
Assessment:<br />
Sum of( (Coin_Amount * 1) * (Coin_Age_Days * 1) * (CubedRoot(Tithe_To_Foundation)))<br />
<br><br />
Meaning:<br />
For each donation to the foundation by a participant, we will reward the participant with the most portion of the reward based on Coin_Age, but to a much lesser extent, the donation amount.<br />
<br><br />
<br />
Example (One Tithe with 7 days coin age, 1,000 donation):<br />
Coin Value : 25000, Coin Age: 7 days, Donation Amount: 1,000 bbp. Points Accrued = 25000 * 7 * CubedRoot(1000^(1/3)=10) = 1,750,000 points<br />
<br />
Example 2 (One Tithe with 3.4 days coin age, 24,000 donation):<br />
Coin Value: 25000, Coin Age: 3.4 days, Donation Amount: 24,000 bbp. Points Accrued = 25000 * 3.4 * CubedRoot(24000^(1/3)=28.84) = 2,451,400 points<br />
<br><br />
More than one Tithe per day results in points being summed to the CPK-Participant.<br />
<br><br />
Since One campaign exists, the entire GSC budget is allocated to one campaign, however in the future GSC budgets are split among campaigns.<br />
<br><br />
The campaign points are summed and converted into Total Prominence per participant, so that a CPK may see their assessed total Prominence per user Or points per Campaign.<br />
<br><br />
The Budget is divided by Prominence and converted to payment amounts in the GSC.<br />
<br><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
'''ADDENDUM'''<br />
<br />
'''Campaign Examples and Payment Example'''<br />
<br />
<br><br />
Let us assume we have 2 campaigns in BiblePay: BiblePay POG and BiblePay Interest as live campaigns. <br />
<br><br />
<br />
The BiblePay interest campaign pays 1% annual interest for a users proven UTXO balance.<br />
<br><br />
The BiblePay POG campaign pays a reward of (Coin*Age*CubedRoot(Tithe_To_Foundation_Amount)) for a daily foundation tithe.<br />
<br><br />
(Campaign parameters are malleable and votable by sanctuary proposals - and parameters updateable by spork).<br />
<br><br />
<br />
If User A belongs to both Campaign A, B, User A's miner will automatically iterate through each campaign and create a GSC-Transmission for each campaign, once per day, using the configurable percentage per campaign of balance available for GSCs, in one transaction per campaign (this prevents network spam). The GSC-client will automatically loop through campaigns joined by the user and try to participate in them.<br />
<br />
<br><br />
<br><br />
'''RPC COMMANDS'''<br />
<br />
<br />
<br><br />
<br />
How do I create a CPK (Christian-public-keypair)?<br />
exec cpk nickname<br />
<br />
<br />
<br><br />
<br />
How do I join Project #1 - POG?<br />
<br />
exec join pog<br />
<br />
<br><br />
How do I know if my node contributed to POG?<br />
Look for a transaction on the transaction list labeled "GSC transmission"<br />
<br />
<br><br />
<br />
How do I change the default quantity of coins my node accesses for a GSC transmission?<br />
The node uses half of your coins by default, once every 24 hours (1 hour in testnet). To change this, change the key:<br />
pog_coinagepercentage=.80<br />
This will make your node use 80% of your coins.<br />
<br />
<br />
How do I change the default foundation donation amount per day?<br />
The node tithes 7 BBP per day by default. To change this, change the key:<br />
pog_foundationdonation=1000<br />
This will make your node send 1000 BBP per GSC transmission.<br />
<br />
[[Category:Concepts]]<br />
[[Category:Evolution]]</div>Sunk818https://wiki.biblepay.org/index.php?title=Generic_Smart_Contracts&diff=6165Generic Smart Contracts2019-03-25T15:22:33Z<p>Sunk818: added concepts category</p>
<hr />
<div><br />
'''BIBLEPAY EVOLUTION - GENERIC SMART CONTRACTS'''<br />
<br />
Generic Smart Contracts (GSC's) allow BiblePay to accomplish its goals without disrupting quality of service for our users. These contracts provide a modular abstract interface for user rewards, and exciting capabilities that are not possible in hard consensus systems. <br />
<br><br />
<br />
Some of the features our GSC's include: payments based on campaigns, corporate turnkey integration, c#/stratis integration, Restful API oracles, web tipping, decentralized voting on Christian objects, Christian economy features, and more.<br />
<br><br />
<br />
<br><br />
<br />
<br />
'''Generic Smart Contract Format'''<br />
<br />
The GSC is split into a client server architecture. The client side user joins campaigns with a CPK (Christian Public Keypair) and competes in these campaigns for points. The server side (our Sanctuaries) assess user points and tracks user progress. Once per day, the points are converted and paid in a Generic Smart Contract. The GSC is voted on by the Sanctuaries automatically at a certain chain height.<br />
<br><br />
<br />
The GSC is paid once per day as a superblock from BiblePay core, and is split among campaigns by points rewarded per campaign per user. <br />
<br><br />
<br />
Sanctuaries assess the points per campaign per user, and allocate the total daily reward amount by points to participants. <br />
<br />
<br><br />
<br><br />
<br />
'''CAMPAIGNS'''<br />
<br />
<br />
BiblePay will support an unlimited amount of campaigns over the long term. Each campaign will have a name, a distinct purpose, and a set of rules and formulas that adhere to the GSC-Server-Abstraction-Layer.<br />
<br />
<br><br />
<br />
A user joins a campaign by typing a command (see RPC commands). The user must have a Christian Public Keypair to join a campaign (see RPC commands). <br />
<br><br />
<br />
<br />
'''Sanctuary Side'''<br />
<br />
<br />
The sanctuaries will assess the points for each user, by looping through all live campaigns, and assessing the amount of points that should be assigned to each user and assigning Points. <br />
<br><br />
NOTE: If multiple transactions were sent by a user in one day, the user points will be summed.<br />
<br />
<br><br />
<br />
If the user has a 1 million balance in stake, the interest component will be 27 points, while the POG campaign reward=1000 points, equaling 1027 points for the day (see detailed example for more information).<br />
<br><br />
<br />
Once the points are assessed at a daily quorum height, the sanctuaries will auto-vote on these points.<br />
<br><br />
<br />
The daily generic smart contract will automatically convert points to BBP rewards in the superblock generator module.<br />
<br><br />
<br><br />
'''Christian Economy Integration'''<br />
<br />
<br><br />
The GSC system enables biblepay to create an exciting new campaign type for Christian economies in the future: HTML5 voting and HTML5 tipping. <br />
<br><br />
In voting, it will be possible for a user to navigate to a list of Christian objects (say for instance, Orphan outgoing letters), and vote on these letters with their CPK. <br />
<br><br />
The sanctuary will pick up votes for the "Orphan Letters" campaign automatically, allowing points to be rewarded in that campaign for voting activity from the 'Orphan' campaign budget.<br />
<br><br />
The same can be done with any list of Christian objects, for example, a list of "Rapture video objects". As users vote on these items, the HTML5 vote will be picked up and converted to points according to the rules of the campaign.<br />
<br />
<br><br />
<br />
'''Christian Public Keypair Reputation Score'''<br />
<br />
<br />
Since an individual user will create a CPK to participate, it will be possible for the user to accumulate a reputation score, based on behavior. This will open up exciting possibilities for our network for future campaigns that reward points based on behavior. One example of negative behavior is if someone consistently votes down high quality content. If the users reputation score decreases, this user may be rewarded less share percentage in some campaigns (because activity is of low caliber). <br />
<br><br />
<br />
<br />
As voting activity is assessed, the CPK will accumulate a reputation score change. Over time, it will be preferable for the user to keep the existing CPK (due to the positive reputation score) rather than create multiple keys or recreate the keypair. The reputation score may then be used to influence payout percentages in some activities, after it is established that reputation scores are accurate.<br />
<br><br />
<br><br />
<br><br />
<br />
'''Corporate GSC Integration'''<br />
<br><br />
<br />
A very exciting feature BiblePay will offer in our GSC system is corporate integration. This is a value add for corporations who do not want to spend hours learning blockchain programming to make cryptocurrency payments automatically. <br />
<br><br />
This feature allows a corporate developer to configure a recurring or one-time payment to be made easily through the blockchain to a vendor by emitting a coinbase payment in our GSC.<br />
<br><br />
<br><br />
<br />
'''Evolution Anti-BotNet Features, 51% attack prevention with ChainLocks'''<br />
<br><br />
<br />
In Evolution, we have built in a brand new feature called ABN (anti-botnet). The original use-case for ABN stems from our mission to prevent ASIC/GPU ports, run BiblePay on commodity PCs, and create a fair mining environment without groups of monopolies forming (IE Asic monopolies) who take a large percentage of mining rewards. Even with CPU mining, we have seen some rich actors, who own 300 servers, point all the hash power at BiblePay and take an unduly large percentage of daily rewards. On one hand, we agree, they have every right to. But on the other hand, we really would like to appeal to distinct head count so as to expose more people to the Gospel. In light of this we have released ABN, which requires a certain amount of coin*age to be present in each mined block in order to mine BiblePay. What this does is quickly uses up coin*age when an attack occurs (to give an example, if you are BotNet with 50 PCs, and your wallet balance is 50,000, after solving a few blocks with high hash power your wallet will run out of coin*age and you will not be able to mine more BiblePay until coin*age increases).<br />
<br><br />
<br />
The feature works like this. Our network requires an average calculated and pre-assessed static amount (posted in getmininginfo) of required coin*age and stores this in the chain. Each miner checks this number, and will search the wallet (this is all automatic) for coins totaling the requirement and place these coins in an ABN Stake transaction - and then begin mining. We do allow mining for All participants if a block is over 60 minutes old (this is so that our chain never stops if every single participant runs out of coin age).<br />
<br><br />
In this way, every block mined in Evolution is sure to be solved by a normal participant and not a bot-net over time.<br />
<br><br />
In addition to all of this, we have inherited Dash's 51% attack prevention system (ChainLocks). We have this feature fully merged in and ready to be released. This is an amazing addition to BiblePay, as it removes 51% attack risk by almost 100%. This is accomplished by asking our Sanctuaries to keep track of each solved block and not allow deep reorganizations once ChainLocks are live.<br />
<br />
<br><br />
<br><br />
<br />
'''Deployment Timeline and Roadmap changes'''<br />
<br><br />
<br />
<br />
For BiblePay Evolution, we will start by releasing One campaign: Proof-of-Giving. This will prove the entire GSC concept in testnet from end-to-end, with a daily smart contract being emitted, CPK users being registered and participating in the first campaign, the Sanctuaries assessing the points, Sanctuaries voting, and payments being made.<br />
<br><br />
<br />
After the release of Evolution, our IT team will continue to develop the Corporate integration, additional new campaigns, and HTML5 integration.<br />
<br><br />
<br><br />
<br />
<br />
''' BiblePay Architecture Changes for Reliability, Mass Development and Mass Adoption '''<br />
<br><br />
<br><br />
<br />
In order to maintain a reliable environment in production, we have decided to change our current architecture. We are changing procedures to prevent or minimize production deployments that: <br />
Change consensus, or Add client-side features. Both of these things may be valuable in the long term (for example a new campaign allowing web tipping, or a gospel feature for Spiritual Warfare), but, not at the expense of the Quality of Service for those using BBP in prod, or for Exchanges or Sanctuaries. <br />
<br />
<br><br />
In light of this, we have designed a new architecture where we will demarcate and abstract the core client from the Sanctuary in a way where BiblePay-IT may deploy consensus changes on the Sanctuary side only. This will be accomplished by creating a client side abstraction interface the core client will adhere to.<br />
<br />
<br><br />
Our goal is that when we release Evolution, the client side contract will no longer change, and therefore updates to the sanctuary will not require upgrades for the users or exchanges.<br />
<br><br />
We will accomplish this by deploying incremental updates to the sanctuaries that allow the consensus mechanism to be updated on the server side only. This means that when a new campaign is released (let us say for example, web tipping), the Sanctuaries will need to upgrade, but not the users, and the exchanges and network will not endure a hard fork. After the Sancs upgrade, web tipping will be announced and users may "join web tip campaign" and automatically receive rewards via the daily GSC.<br />
<br><br />
<br />
Another large change that is occurring is our move toward an additional HTML5 GUI for new UI pages. We believes we will attract HTML5 web developers that will give us the bandwidth to build out pages such as Orphan writing, Orphan voting, Lists of Christian Objects, Embedded Christian Videos, etc. This also accomplishes our goal of not upgrading the core client during new GUI changes as these pages adhere to the new model.<br />
<br><br />
Part of this change will mean that when a user navigates to a Christian Space resource, we will honor their CPK (Christian public keypair) as authentication, and this will allow the user to vote on the resource or view it , as the resource will know their voting ability and reputation score. This will allow the user to navigate into BiblePay's additional UI pages.<br />
<br><br />
<br />
These exciting features are being added to BiblePay to make your user experience smoother and provide a high quality production Environment.<br />
<br />
<br><br />
<br />
<br />
<br />
'''Modularity and Extensibility'''<br />
<br />
<br><br />
To help remove IT development bottlenecks in the UI area, our dev team is making BiblePay-Evolution HTML work in a way where non-C++ devs (web devs) may participate in development and deploy GUI changes. <br />
<br><br />
To give an example of how this will work, we have a background project with Kestrel and Sanctuaries, so that BiblePay will emit HTML5 markup from sanctuaries. This will allow webdevs to participate in: Creating Christian Spaces, building out BiblePay, and modifying BiblePay UI in a modular and extensible way, without knowing how to be a blockchain programmer. <br />
<br><br />
To the end user this means we will have tens to hundreds of new pages in the wallet in Christian Spaces in the future, allowing us to vote on these objects with our CPK and therefore our reputation scores will change, and we hope the experience will be edifying for everyone, giving BiblePay a truly valuable purpose.<br />
<br><br />
<br />
<br />
<br />
'''RoadMap Modifications'''<br />
<br />
<br><br />
<br />
March 2019: Release Evolution to Testnet. Test normal core wallet functions: Sanctuary creation, sanctuary operation, receive/send money, proposals, etc.<br />
<br><br />
<br />
Mid April 2019: Test GSCs in TestNet, ensure payments work, campaigns emit points, campaigns can be joined and unjoined, and CPKs work. Ensure the first campaign (POG) works properly.<br />
<br><br />
<br />
May 2019: Finish testing Evo, release Evo to Prod. Go Live with Evo and GSC (Generic Smart Contracts) - and One Campaign in Prod! (POG).<br />
<br><br />
<br />
July 2019: Finish modifications to server side GSC's, alter any business logic. Add additional Campaign if necessary. <br />
<br><br />
<br />
September 2019: Release Christian spaces (Allow voting on Christian objects, allow navigation of decentralized UI by CPKs). <br />
<br><br />
<br />
September 10th, 2019: Make a very important announcement regarding the future of BiblePay (IE the announcement that was promised this year) - regarding a feature that cannot be disclosed until September due to the sensitive nature of the subject. What we can say, is this item gives BiblePay the ability to be a 'serious contender' in the space.<br />
<br><br />
<br />
Dec 2019: Release Corporate Integration features. This allows 3rd party sites like (Steve Cioccolanti to integrate with BiblePay), c# Payments, Reports from Stratis, and also allows us to create DOCS (decentralized orphan contracts).<br />
<br><br />
<br />
<br />
<br />
<br />
'''Our first Campaign - POG (Proof-of-Giving)'''<br />
<br />
<br><br />
<br />
Notes about Campaigns: A user cannot join any campaigns unless they have a CPK (A Christian-public-keypair). You only need one CPK for life. The CPK is stored in your wallet.dat so when you move to a new machine you will still have your CPK. If you want to join multiple projects, you should create ONE CPK, then join each project with the join command. You will receive an error if you do not have a CPK and attempt to join a project. (If you try to create multiple CPKs you will receive an error).<br />
<br><br />
<br />
Attributes of Campaign 1 (POG):<br />
<br><br />
<br />
Assessment Includes:<br />
All users with a CPK who have joined campaign "POG"<br />
<br />
Requirements:<br />
A contribution sent to the Orphan Foundation during the last 24 hour period<br />
<br />
Assessment:<br />
Sum of( (Coin_Amount * 1) * (Coin_Age_Days * 1) * (CubedRoot(Tithe_To_Foundation)))<br />
<br><br />
Meaning:<br />
For each donation to the foundation by a participant, we will reward the participant with the most portion of the reward based on Coin_Age, but to a much lesser extent, the donation amount.<br />
<br><br />
<br />
Example (One Tithe with 7 days coin age, 1,000 donation):<br />
Coin Value : 25000, Coin Age: 7 days, Donation Amount: 1,000 bbp. Points Accrued = 25000 * 7 * CubedRoot(1000^(1/3)=10) = 1,750,000 points<br />
<br />
Example 2 (One Tithe with 3.4 days coin age, 24,000 donation):<br />
Coin Value: 25000, Coin Age: 3.4 days, Donation Amount: 24,000 bbp. Points Accrued = 25000 * 3.4 * CubedRoot(24000^(1/3)=28.84) = 2,451,400 points<br />
<br><br />
More than one Tithe per day results in points being summed to the CPK-Participant.<br />
<br><br />
Since One campaign exists, the entire GSC budget is allocated to one campaign, however in the future GSC budgets are split among campaigns.<br />
<br><br />
The campaign points are summed and converted into Total Prominence per participant, so that a CPK may see their assessed total Prominence per user Or points per Campaign.<br />
<br><br />
The Budget is divided by Prominence and converted to payment amounts in the GSC.<br />
<br><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
'''ADDENDUM'''<br />
<br />
'''Campaign Examples and Payment Example'''<br />
<br />
<br><br />
Let us assume we have 2 campaigns in BiblePay: BiblePay POG and BiblePay Interest as live campaigns. <br />
<br><br />
<br />
The BiblePay interest campaign pays 1% annual interest for a users proven UTXO balance.<br />
<br><br />
The BiblePay POG campaign pays a reward of (Coin*Age*CubedRoot(Tithe_To_Foundation_Amount)) for a daily foundation tithe.<br />
<br><br />
(Campaign parameters are malleable and votable by sanctuary proposals - and parameters updateable by spork).<br />
<br><br />
<br />
If User A belongs to both Campaign A, B, User A's miner will automatically iterate through each campaign and create a GSC-Transmission for each campaign, once per day, using the configurable percentage per campaign of balance available for GSCs, in one transaction per campaign (this prevents network spam). The GSC-client will automatically loop through campaigns joined by the user and try to participate in them.<br />
<br />
<br><br />
<br><br />
'''RPC COMMANDS'''<br />
<br />
<br />
<br><br />
<br />
How do I create a CPK (Christian-public-keypair)?<br />
exec cpk nickname<br />
<br />
<br />
<br><br />
<br />
How do I join Project #1 - POG?<br />
<br />
exec join pog<br />
<br />
<br><br />
How do I know if my node contributed to POG?<br />
Look for a transaction on the transaction list labeled "GSC transmission"<br />
<br />
<br><br />
<br />
How do I change the default quantity of coins my node accesses for a GSC transmission?<br />
The node uses half of your coins by default, once every 24 hours (1 hour in testnet). To change this, change the key:<br />
pog_coinagepercentage=.80<br />
This will make your node use 80% of your coins.<br />
<br />
<br />
How do I change the default foundation donation amount per day?<br />
The node tithes 7 BBP per day by default. To change this, change the key:<br />
pog_foundationdonation=1000<br />
This will make your node send 1000 BBP per GSC transmission.<br />
<br />
[[Category:Concepts]]</div>Sunk818https://wiki.biblepay.org/index.php?title=UnderstandingGovernance&diff=6148UnderstandingGovernance2019-03-06T05:19:42Z<p>Sunk818: /* Proposal websites */</p>
<hr />
<div>=Understanding BiblePay Governance=<br />
One of the greatest challenges of building a cryptocurrency platform is ensuring you create a decentralized system of governance to manage, fund, maintain and expand the project. This key element has been absent in every major currency to date, so the natural response is to create a not-for-profit foundation that is tasked with maintaining the core protocol and promoting the coin, but is not really connected to the coin holders in any meaningful way. This approach has a few issues that have been made evident from the experience of older crypto currency platforms.<br />
<br />
Current crypto foundations are not related to the currency itself by any mechanism that is included in the protocol and are not designed to outlive early adopters when they lose interest. The foundation then struggles to maintain funding until it implodes and core development of the protocol is left scrambling for funding or depending on charity that can’t be counted on and does not allow for proper budgeting and planning. Donations are also unfair to donors because there are always free riders that benefit from the effort done by others without contributing. Other projects have financed themselves by premining coins or running prelaunch sales, which is not a great solution either because control of the funds is centralized and at that stage it is impossible to quantify the future needs of the project.<br />
<br />
Through the network of full nodes and the collateral requirement, BiblePay already has a decentralized network of masternode operators that are heavily invested in the future of the currency, and that as a group can act as stewards of the core protocol development and promotion. We propose a decentralized management system based on the masternode voting mechanism. Masternode operators are not the only ones interested in the success of BiblePay, but they are the most stable ones because, unlike miners, they can’t reuse their asset for any other purpose or coin.<br />
<br />
In the budget system, a portion of the block reward is held in escrow by the network itself, in the name of the operators, to be executed in the development and expansion of the ecosystem according to the vote of the masternodes in different budget proposals. These funds are directed to supporting development and promotion of the coin. Masternode operators vote on specific budgets and projects to be funded, thus defining the direction the coin is taking. This is done in a completely transparent way through a public portal where new initiatives are proposed and masternodes can vote on them. Functioning like a decentralized Kickstarter or Lighthouse, the budget can be used for anything that creates value within the ecosystem.<br />
<br />
This is a 100% decentralized system powered by the masternodes, where budgets are set and paid directly from the blockchain. The blockchain hires core developers in this way and introduces a new concept of paid blockchain contractors, where people work for and are directly compensated by the network, through the decentralized votes of all masternode operators. One advantage of this model is it can survive early adopters. If early masternode operators sell their coins, the new owner can set up a masternode and with it acquire the right to vote on the budgets and projects. This guarantees there is a working system of maintenance as people come and go, making the network capable of sustaining itself on its own without depending on specific actors.<br />
<br />
=Budgets and masternode voting=<br />
The system works as a decentralized voting mechanism set up in the rules governing the blockchain, where budgets for specific projects are proposed, then the masternodes as a whole vote on them. Each project, if it passes, is added to the total budget and paid directly from the blockchain to the person doing the work. This allows BiblePay to hire core developers and pay them directly after approval of the work in a decentralized fashion.<br />
<br />
A masternode votes on a proposal (technically a governance object on the blockchain) using the example command “masternode vote yes”, “masternode vote no” or “masternode vote abstain”. The votes then propagate across the network, and are tallied according to instructions followed by the network itself. Budgets under discussion and voting progress can be viewed using the example command “masternode budget show”.<br />
<br />
A well defined decentralized system of governance allows a cryptocurrency network to endure and survive its original creators. In this way, later generations of masternode operators have a clear way to support the system as defined by the protocol itself, applying wisdom of the crowd techniques and the bond of trust established by the masternode collateral to create a decentralized management system. This creates incredible value within the currency, allowing us to be more agile and compete with other payment systems, such as Bitcoin and credit cards, on a global scale.<br />
<br />
As the system develops, a strong team of productive contractors paid from blockchain rewards will arise and become established. This includes core developers, escrow providers, news and reporting staff, experimental development labs, partnerships with universities, marketing and PR firms and integrations with third party exchanges and payment platforms. The market recognizes the value of the stability of the network as a whole, and that the possibility of reliable and sufficient funding results in faster and more coherent implementation of the BiblePay roadmap and core BiblePay services.<br />
=Reward schedule=<br />
To guarantee long term sustainability of the blockchain, the network keeps a portion of the block rewards back as new blocks are created, with the masternode operators tasked to act as stewards and invest in the maintenance and expansion of the network by voting. This results in faster development and promotion, creating a virtuous cycle that benefits all actors, including miners, masternode operators, investors and users. More importantly, this gives the blockchain itself a self-preservation mechanism that is beyond the control of any individual.<br />
{| class="wikitable"<br />
|-<br />
||'''Description'''<br />
| style="text-align: right;" data-mce-style="text-align: right;"|'''Percentage'''<br />
|-<br />
||Mining reward for Proof-of-BibleHash<br />
| style="text-align: right;" data-mce-style="text-align: right;"|3.0%<br />
|-<br />
||Mining reward for Proof-of-Distributed-Computing<br />
| style="text-align: right;" data-mce-style="text-align: right;"|38.5%<br />
|-<br />
||Masternode reward for Proof-of-Service<br />
| style="text-align: right;" data-mce-style="text-align: right;"|38.5%<br />
|-<br />
||Decentralized governance budget<br />
| style="text-align: right;" data-mce-style="text-align: right;"|20.0%<br />
|}<br />
<br />
<br />
<br />
20% of the mining reward is held back each block and is disbursed monthly by the masternode operators once the results of their votes are tallied, creating the first self-sustaining decentralized cryptocurrency platform organized as a Decentralized Autonomous Organization (DAO). The masternode operators establish a social contract with the network they benefit from and are bound to act as caretakers, dedicating their time, due diligence work and a portion of the network rewards to furthering the ecosystem. This has a ripple effect that benefits all parties involved - especially the end users.<br />
<br />
The value generated by work done implementing proposals is expected to be greater than allocating 100% of rewards to mining because the network has needs beyond only cryptographically securing the blockchain. The expected result is greater net benefit not only for proposal winners, but also masternode operators, miners and normal users. In fact, the introduction of the decentralized governance budget itself was decided by a masternode vote, making the first distributed decision the actual creation of the system, similar to establishing a constitution.<br />
<br />
This approach of distributing the normal block reward in a way that considers all critical elements a cryptocurrency needs for its long term viability, e.g. mining, full nodes, development and promotion, is revolutionary as it is done without changing the emission or creating any additional inflation for investors. The network simply distributes the available resources in a way that is of greater net benefit to all parties.<br />
<br />
=Contractors and proposals=<br />
Contractors of the blockchain can be developers, outreach professionals, team leaders, attorneys or even people appointed to do specific tasks. Proposals generally begin life as simple pre-proposal forum posts on the [http://forum.biblepay.org/index.php?board=5.0 BiblePay Forum], where feedback and suggestions are solicited from the general community. Once the proposal owner decides they have a reasonable chance of passing their proposal, it is created as a governance object on the blockchain. A fee of 2500 BiblePay is associated with this action to prevent spam and ensure only serious proposals make it to this stage. Several tools exist to allow masternode operators to comfortably review and vote on proposals. The net total of yes votes must exceed 10% of the total masternode count at the time votes are tallied in order to pass. If there are more passing proposals than the available block reward can provide for, the proposals with the most yes votes will pass first, creating a cut-off point for less popular proposals. The same process is then repeated every month, and the total amount of BiblePay available for proposals decreases by approximately 19.5% per year, together with the overall block reward.<br />
=Proposal websites=<br />
The community has gathered around the [http://forum.biblepay.org/index.php?board=5.0 BiblePay Forum] as a website to facilitate discussion and voting on proposals formally entered on the BiblePay blockchain. [https://www.biblepay-central.org/en/proposals/ BiblePay Central] and [https://pool.biblepay.org/ Pool.BiblePay] >>> Governance >>> Proposal List are available to view submitted proposals.<br />
<br />
Each proposal should include a description of the proposal goals, details of what work will be done and a breakdown of the requested budget. Many proposals also link to their own website or the pre-proposal discussion, or include a video to validate the identity and sincerity of the proposal owner. <br />
<br />
Masternode owners have the ability to cast a vote by signing a message from the masternode collateral address. Masternodes can vote at any time, and also change their vote at any time until the cutoff block is mined and voting stops. This occurs 1-3 days prior to the superblock. After voting stops, the blockchain executes a decentralized tally and validates all votes. Once consensus is reached, the results are broadcast and the budget is allocated soon after in a superblock.<br />
<br />
Once passed, proposals are able to report back to the network on the [http://forum.biblepay.org/index.php?board=5.0 BiblePay Forum] or via published public channels and social media. Since it is possible to create proposals that pay out over several months, it is also possible to revoke funding from a project by changing the vote if development or spending of already allocated funds is unsatisfactory. This encourages proposal owners to work honestly and diligently to win the trust and approval of the network. Ongoing discussion and gradual improvement over time results in a close bond between the network and those working for the network in supporting roles.<br />
<br />
Voting on proposals is updated in real time every 7 minutes as blocks are mined, so current winning proposals and the total allocation of the available budget are always open and visible to everyone. [https://forum.biblepay.org/cc/governance BiblePay Forum Governance] and[https://www.biblepay-central.org/en/proposals/ BiblePay Central Proposals]are two popular sites used to view current and past proposals.<br />
<br />
=Budget allocation=<br />
The total budget of the network can be calculated by taking 20% of the reward over the period of time between two superblocks, which occur every 6150 blocks or approximately 29.89 days. A voting cutoff occurs 1-3 days before the superblock, and the final votes are tallied at this point. A proposal must satisfy the condition (YES votes - NO votes) > (Total Number of Masternodes / 10) in order to be considered passing. Then, in the superblock, the winning proposals are awarded in the order of the margin by which they are passing until either the entire budget is allocated or no more passing proposals exist. This allows for completely trustless and decentralized allocation of the budget.<br />
<br />
If a proposal has passed the voting threshold but insufficient funds remain to pay the full amount requested, it will not receive partial funding. Instead, any smaller proposals which have also passed the threshold that will fit in the budget will be funded, even if they have lower net approval than the larger proposal. Proposals requesting payment over multiple budget periods will remain in the treasury system for the duration of their validity if they pass the voting threshold, even if insufficient budget is available for funding as described above. Any unallocated budget is simply never created in the superblock, reducing unnecessary inflation.<br />
<br />
Due to the decentralized nature of the masternode system, it is sometimes necessary to form funded organisations, such as committees or companies, to be responsible for some project or task. These are submitted in the same way, but the committee itself receives the funds. Another alternative is to place trusted escrow services between the budget allocation event and the actual submitter of the proposal to ensure that work is paid for in stages, as it is delivered. Some oversight over blockchain contractors is sometimes needed. Each budgeted item requires either a team manager or a committee responsible for implementation of the work. Periodically, this manager is expected to report on budget expenditure and completed work to show the value created from the allocated funds. This allows repeat proposal submitters to build up a reputation and gain trust from the community. Proposals which do not provide regular reports and cannot answer questions about their budget allocation will soon be defunded if it is part of a regular monthly proposal cycle. The result is a kind of self-policing system.<br />
<br />
=Scaling and future uses=<br />
As the number of blockchain contractors increases, a point is reached where masternode operators cannot be realistically expected to evaluate the volume of proposals. At this point funding organizations can be created to act as contractors for the distribution of funds to many smaller decentralized projects, according to current needs.<br />
<br />
The existence of the decentralized budget system puts the power of determining where BiblePay goes in the future in the hands of the masternode network itself. All core development and several peripheral developers are already funded from the budget, and other projects not even conceivable at this time will likely arise in the future. This decouples the survival and value of the blockchain from the current userbase and developers, making the BiblePay blockchain designed to outlive its original users, a self sustainable decentralized cryptocurrency network that can still operate cohesively and bring added value services to end users in a consistent way.<br />
=Conclusion=<br />
Every masternode operator establishes a bond of trust and a social contract with the network in which she is bound to contribute to the development and maintenance of the ecosystem she benefits from. Under this model, a portion of the funds that the operator is bound to receive are in a sense allocated in custody, not in ownership, and are held in escrow by the network to be executed by the operators for the benefit of the ecosystem. Everyone contributes equally and proportionately to the benefits they are receiving and the risks they are taking, there are no privileges and no loopholes. This is complemented by the full node voting mechanism that allows for a distributed group to vote on a continuous basis on practical matters without the need to forfeit their right to decide to others, every few years, like with traditional governments or cooperative corporations.<br />
<br />
We envision a future in which this model of transparent, unbreakable and verifiable contribution to the common good, in combination with continuous participation of the crowd through active voting, is utilized to manage organizations that are owned or operated jointly by its members, who share the benefits and responsibilities of those collectives, like governments, cooperative corporations, unions, DAOs, cryptocurrencies, etc. We call this model decentralized governance by blockchain.<br />
<br />
<br />
----<br />
<br />
Reference: [https://docs.dash.org/en/latest/governance/understanding.html]<br />
<br />
[[Category:Sanctuary (Masternodes)]][[Category:Governance]]</div>Sunk818https://wiki.biblepay.org/index.php?title=UnderstandingGovernance&diff=6147UnderstandingGovernance2019-03-06T05:18:48Z<p>Sunk818: /* Proposal websites */</p>
<hr />
<div>=Understanding BiblePay Governance=<br />
One of the greatest challenges of building a cryptocurrency platform is ensuring you create a decentralized system of governance to manage, fund, maintain and expand the project. This key element has been absent in every major currency to date, so the natural response is to create a not-for-profit foundation that is tasked with maintaining the core protocol and promoting the coin, but is not really connected to the coin holders in any meaningful way. This approach has a few issues that have been made evident from the experience of older crypto currency platforms.<br />
<br />
Current crypto foundations are not related to the currency itself by any mechanism that is included in the protocol and are not designed to outlive early adopters when they lose interest. The foundation then struggles to maintain funding until it implodes and core development of the protocol is left scrambling for funding or depending on charity that can’t be counted on and does not allow for proper budgeting and planning. Donations are also unfair to donors because there are always free riders that benefit from the effort done by others without contributing. Other projects have financed themselves by premining coins or running prelaunch sales, which is not a great solution either because control of the funds is centralized and at that stage it is impossible to quantify the future needs of the project.<br />
<br />
Through the network of full nodes and the collateral requirement, BiblePay already has a decentralized network of masternode operators that are heavily invested in the future of the currency, and that as a group can act as stewards of the core protocol development and promotion. We propose a decentralized management system based on the masternode voting mechanism. Masternode operators are not the only ones interested in the success of BiblePay, but they are the most stable ones because, unlike miners, they can’t reuse their asset for any other purpose or coin.<br />
<br />
In the budget system, a portion of the block reward is held in escrow by the network itself, in the name of the operators, to be executed in the development and expansion of the ecosystem according to the vote of the masternodes in different budget proposals. These funds are directed to supporting development and promotion of the coin. Masternode operators vote on specific budgets and projects to be funded, thus defining the direction the coin is taking. This is done in a completely transparent way through a public portal where new initiatives are proposed and masternodes can vote on them. Functioning like a decentralized Kickstarter or Lighthouse, the budget can be used for anything that creates value within the ecosystem.<br />
<br />
This is a 100% decentralized system powered by the masternodes, where budgets are set and paid directly from the blockchain. The blockchain hires core developers in this way and introduces a new concept of paid blockchain contractors, where people work for and are directly compensated by the network, through the decentralized votes of all masternode operators. One advantage of this model is it can survive early adopters. If early masternode operators sell their coins, the new owner can set up a masternode and with it acquire the right to vote on the budgets and projects. This guarantees there is a working system of maintenance as people come and go, making the network capable of sustaining itself on its own without depending on specific actors.<br />
<br />
=Budgets and masternode voting=<br />
The system works as a decentralized voting mechanism set up in the rules governing the blockchain, where budgets for specific projects are proposed, then the masternodes as a whole vote on them. Each project, if it passes, is added to the total budget and paid directly from the blockchain to the person doing the work. This allows BiblePay to hire core developers and pay them directly after approval of the work in a decentralized fashion.<br />
<br />
A masternode votes on a proposal (technically a governance object on the blockchain) using the example command “masternode vote yes”, “masternode vote no” or “masternode vote abstain”. The votes then propagate across the network, and are tallied according to instructions followed by the network itself. Budgets under discussion and voting progress can be viewed using the example command “masternode budget show”.<br />
<br />
A well defined decentralized system of governance allows a cryptocurrency network to endure and survive its original creators. In this way, later generations of masternode operators have a clear way to support the system as defined by the protocol itself, applying wisdom of the crowd techniques and the bond of trust established by the masternode collateral to create a decentralized management system. This creates incredible value within the currency, allowing us to be more agile and compete with other payment systems, such as Bitcoin and credit cards, on a global scale.<br />
<br />
As the system develops, a strong team of productive contractors paid from blockchain rewards will arise and become established. This includes core developers, escrow providers, news and reporting staff, experimental development labs, partnerships with universities, marketing and PR firms and integrations with third party exchanges and payment platforms. The market recognizes the value of the stability of the network as a whole, and that the possibility of reliable and sufficient funding results in faster and more coherent implementation of the BiblePay roadmap and core BiblePay services.<br />
=Reward schedule=<br />
To guarantee long term sustainability of the blockchain, the network keeps a portion of the block rewards back as new blocks are created, with the masternode operators tasked to act as stewards and invest in the maintenance and expansion of the network by voting. This results in faster development and promotion, creating a virtuous cycle that benefits all actors, including miners, masternode operators, investors and users. More importantly, this gives the blockchain itself a self-preservation mechanism that is beyond the control of any individual.<br />
{| class="wikitable"<br />
|-<br />
||'''Description'''<br />
| style="text-align: right;" data-mce-style="text-align: right;"|'''Percentage'''<br />
|-<br />
||Mining reward for Proof-of-BibleHash<br />
| style="text-align: right;" data-mce-style="text-align: right;"|3.0%<br />
|-<br />
||Mining reward for Proof-of-Distributed-Computing<br />
| style="text-align: right;" data-mce-style="text-align: right;"|38.5%<br />
|-<br />
||Masternode reward for Proof-of-Service<br />
| style="text-align: right;" data-mce-style="text-align: right;"|38.5%<br />
|-<br />
||Decentralized governance budget<br />
| style="text-align: right;" data-mce-style="text-align: right;"|20.0%<br />
|}<br />
<br />
<br />
<br />
20% of the mining reward is held back each block and is disbursed monthly by the masternode operators once the results of their votes are tallied, creating the first self-sustaining decentralized cryptocurrency platform organized as a Decentralized Autonomous Organization (DAO). The masternode operators establish a social contract with the network they benefit from and are bound to act as caretakers, dedicating their time, due diligence work and a portion of the network rewards to furthering the ecosystem. This has a ripple effect that benefits all parties involved - especially the end users.<br />
<br />
The value generated by work done implementing proposals is expected to be greater than allocating 100% of rewards to mining because the network has needs beyond only cryptographically securing the blockchain. The expected result is greater net benefit not only for proposal winners, but also masternode operators, miners and normal users. In fact, the introduction of the decentralized governance budget itself was decided by a masternode vote, making the first distributed decision the actual creation of the system, similar to establishing a constitution.<br />
<br />
This approach of distributing the normal block reward in a way that considers all critical elements a cryptocurrency needs for its long term viability, e.g. mining, full nodes, development and promotion, is revolutionary as it is done without changing the emission or creating any additional inflation for investors. The network simply distributes the available resources in a way that is of greater net benefit to all parties.<br />
<br />
=Contractors and proposals=<br />
Contractors of the blockchain can be developers, outreach professionals, team leaders, attorneys or even people appointed to do specific tasks. Proposals generally begin life as simple pre-proposal forum posts on the [http://forum.biblepay.org/index.php?board=5.0 BiblePay Forum], where feedback and suggestions are solicited from the general community. Once the proposal owner decides they have a reasonable chance of passing their proposal, it is created as a governance object on the blockchain. A fee of 2500 BiblePay is associated with this action to prevent spam and ensure only serious proposals make it to this stage. Several tools exist to allow masternode operators to comfortably review and vote on proposals. The net total of yes votes must exceed 10% of the total masternode count at the time votes are tallied in order to pass. If there are more passing proposals than the available block reward can provide for, the proposals with the most yes votes will pass first, creating a cut-off point for less popular proposals. The same process is then repeated every month, and the total amount of BiblePay available for proposals decreases by approximately 19.5% per year, together with the overall block reward.<br />
=Proposal websites=<br />
The community has gathered around the [http://forum.biblepay.org/index.php?board=5.0 BiblePay Forum] as a website to facilitate discussion and voting on proposals formally entered on the BiblePay blockchain. [https://www.biblepay-central.org/en/proposals/ BiblePay Central] and [https://pool.biblepay.org/ Pool.BiblePay] >>> Governance >>> Proposal List are available to view submitted proposals.<br />
<br />
Each proposal should include a description of the proposal goals, details of what work will be done and a breakdown of the requested budget. Many proposals also link to their own website or the pre-proposal discussion, or include a video to validate the identity and sincerity of the proposal owner. <br />
<br />
Masternode owners have the ability to cast a vote by signing a message from the masternode collateral address. Masternodes can vote at any time, and also change their vote at any time until the cutoff block is mined and voting stops. This occurs 1-3 days prior to the superblock. After voting stops, the blockchain executes a decentralized tally and validates all votes. Once consensus is reached, the results are broadcast and the budget is allocated soon after in a superblock.<br />
<br />
Once passed, proposals are able to report back to the network on the [http://forum.biblepay.org/index.php?board=5.0 BiblePay Forum] or via published public channels and social media. Since it is possible to create proposals that pay out over several months, it is also possible to revoke funding from a project by changing the vote if development or spending of already allocated funds is unsatisfactory. This encourages proposal owners to work honestly and diligently to win the trust and approval of the network. Ongoing discussion and gradual improvement over time results in a close bond between the network and those working for the network in supporting roles.<br />
<br />
Voting on proposals is updated in real time every 7 minutes as blocks are mined, so current winning proposals and the total allocation of the available budget are always open and visible to everyone. [https://forum.biblepay.org/cc/governance BiblePay Forum Governance] and[https://www.biblepay-central.org/en/proposals/ BiblePay Central] are two popular sites used to view current and past proposals.<br />
<br />
=Budget allocation=<br />
The total budget of the network can be calculated by taking 20% of the reward over the period of time between two superblocks, which occur every 6150 blocks or approximately 29.89 days. A voting cutoff occurs 1-3 days before the superblock, and the final votes are tallied at this point. A proposal must satisfy the condition (YES votes - NO votes) > (Total Number of Masternodes / 10) in order to be considered passing. Then, in the superblock, the winning proposals are awarded in the order of the margin by which they are passing until either the entire budget is allocated or no more passing proposals exist. This allows for completely trustless and decentralized allocation of the budget.<br />
<br />
If a proposal has passed the voting threshold but insufficient funds remain to pay the full amount requested, it will not receive partial funding. Instead, any smaller proposals which have also passed the threshold that will fit in the budget will be funded, even if they have lower net approval than the larger proposal. Proposals requesting payment over multiple budget periods will remain in the treasury system for the duration of their validity if they pass the voting threshold, even if insufficient budget is available for funding as described above. Any unallocated budget is simply never created in the superblock, reducing unnecessary inflation.<br />
<br />
Due to the decentralized nature of the masternode system, it is sometimes necessary to form funded organisations, such as committees or companies, to be responsible for some project or task. These are submitted in the same way, but the committee itself receives the funds. Another alternative is to place trusted escrow services between the budget allocation event and the actual submitter of the proposal to ensure that work is paid for in stages, as it is delivered. Some oversight over blockchain contractors is sometimes needed. Each budgeted item requires either a team manager or a committee responsible for implementation of the work. Periodically, this manager is expected to report on budget expenditure and completed work to show the value created from the allocated funds. This allows repeat proposal submitters to build up a reputation and gain trust from the community. Proposals which do not provide regular reports and cannot answer questions about their budget allocation will soon be defunded if it is part of a regular monthly proposal cycle. The result is a kind of self-policing system.<br />
<br />
=Scaling and future uses=<br />
As the number of blockchain contractors increases, a point is reached where masternode operators cannot be realistically expected to evaluate the volume of proposals. At this point funding organizations can be created to act as contractors for the distribution of funds to many smaller decentralized projects, according to current needs.<br />
<br />
The existence of the decentralized budget system puts the power of determining where BiblePay goes in the future in the hands of the masternode network itself. All core development and several peripheral developers are already funded from the budget, and other projects not even conceivable at this time will likely arise in the future. This decouples the survival and value of the blockchain from the current userbase and developers, making the BiblePay blockchain designed to outlive its original users, a self sustainable decentralized cryptocurrency network that can still operate cohesively and bring added value services to end users in a consistent way.<br />
=Conclusion=<br />
Every masternode operator establishes a bond of trust and a social contract with the network in which she is bound to contribute to the development and maintenance of the ecosystem she benefits from. Under this model, a portion of the funds that the operator is bound to receive are in a sense allocated in custody, not in ownership, and are held in escrow by the network to be executed by the operators for the benefit of the ecosystem. Everyone contributes equally and proportionately to the benefits they are receiving and the risks they are taking, there are no privileges and no loopholes. This is complemented by the full node voting mechanism that allows for a distributed group to vote on a continuous basis on practical matters without the need to forfeit their right to decide to others, every few years, like with traditional governments or cooperative corporations.<br />
<br />
We envision a future in which this model of transparent, unbreakable and verifiable contribution to the common good, in combination with continuous participation of the crowd through active voting, is utilized to manage organizations that are owned or operated jointly by its members, who share the benefits and responsibilities of those collectives, like governments, cooperative corporations, unions, DAOs, cryptocurrencies, etc. We call this model decentralized governance by blockchain.<br />
<br />
<br />
----<br />
<br />
Reference: [https://docs.dash.org/en/latest/governance/understanding.html]<br />
<br />
[[Category:Sanctuary (Masternodes)]][[Category:Governance]]</div>Sunk818https://wiki.biblepay.org/index.php?title=UnderstandingGovernance&diff=6146UnderstandingGovernance2019-03-06T05:16:07Z<p>Sunk818: /* Budget allocation */</p>
<hr />
<div>=Understanding BiblePay Governance=<br />
One of the greatest challenges of building a cryptocurrency platform is ensuring you create a decentralized system of governance to manage, fund, maintain and expand the project. This key element has been absent in every major currency to date, so the natural response is to create a not-for-profit foundation that is tasked with maintaining the core protocol and promoting the coin, but is not really connected to the coin holders in any meaningful way. This approach has a few issues that have been made evident from the experience of older crypto currency platforms.<br />
<br />
Current crypto foundations are not related to the currency itself by any mechanism that is included in the protocol and are not designed to outlive early adopters when they lose interest. The foundation then struggles to maintain funding until it implodes and core development of the protocol is left scrambling for funding or depending on charity that can’t be counted on and does not allow for proper budgeting and planning. Donations are also unfair to donors because there are always free riders that benefit from the effort done by others without contributing. Other projects have financed themselves by premining coins or running prelaunch sales, which is not a great solution either because control of the funds is centralized and at that stage it is impossible to quantify the future needs of the project.<br />
<br />
Through the network of full nodes and the collateral requirement, BiblePay already has a decentralized network of masternode operators that are heavily invested in the future of the currency, and that as a group can act as stewards of the core protocol development and promotion. We propose a decentralized management system based on the masternode voting mechanism. Masternode operators are not the only ones interested in the success of BiblePay, but they are the most stable ones because, unlike miners, they can’t reuse their asset for any other purpose or coin.<br />
<br />
In the budget system, a portion of the block reward is held in escrow by the network itself, in the name of the operators, to be executed in the development and expansion of the ecosystem according to the vote of the masternodes in different budget proposals. These funds are directed to supporting development and promotion of the coin. Masternode operators vote on specific budgets and projects to be funded, thus defining the direction the coin is taking. This is done in a completely transparent way through a public portal where new initiatives are proposed and masternodes can vote on them. Functioning like a decentralized Kickstarter or Lighthouse, the budget can be used for anything that creates value within the ecosystem.<br />
<br />
This is a 100% decentralized system powered by the masternodes, where budgets are set and paid directly from the blockchain. The blockchain hires core developers in this way and introduces a new concept of paid blockchain contractors, where people work for and are directly compensated by the network, through the decentralized votes of all masternode operators. One advantage of this model is it can survive early adopters. If early masternode operators sell their coins, the new owner can set up a masternode and with it acquire the right to vote on the budgets and projects. This guarantees there is a working system of maintenance as people come and go, making the network capable of sustaining itself on its own without depending on specific actors.<br />
<br />
=Budgets and masternode voting=<br />
The system works as a decentralized voting mechanism set up in the rules governing the blockchain, where budgets for specific projects are proposed, then the masternodes as a whole vote on them. Each project, if it passes, is added to the total budget and paid directly from the blockchain to the person doing the work. This allows BiblePay to hire core developers and pay them directly after approval of the work in a decentralized fashion.<br />
<br />
A masternode votes on a proposal (technically a governance object on the blockchain) using the example command “masternode vote yes”, “masternode vote no” or “masternode vote abstain”. The votes then propagate across the network, and are tallied according to instructions followed by the network itself. Budgets under discussion and voting progress can be viewed using the example command “masternode budget show”.<br />
<br />
A well defined decentralized system of governance allows a cryptocurrency network to endure and survive its original creators. In this way, later generations of masternode operators have a clear way to support the system as defined by the protocol itself, applying wisdom of the crowd techniques and the bond of trust established by the masternode collateral to create a decentralized management system. This creates incredible value within the currency, allowing us to be more agile and compete with other payment systems, such as Bitcoin and credit cards, on a global scale.<br />
<br />
As the system develops, a strong team of productive contractors paid from blockchain rewards will arise and become established. This includes core developers, escrow providers, news and reporting staff, experimental development labs, partnerships with universities, marketing and PR firms and integrations with third party exchanges and payment platforms. The market recognizes the value of the stability of the network as a whole, and that the possibility of reliable and sufficient funding results in faster and more coherent implementation of the BiblePay roadmap and core BiblePay services.<br />
=Reward schedule=<br />
To guarantee long term sustainability of the blockchain, the network keeps a portion of the block rewards back as new blocks are created, with the masternode operators tasked to act as stewards and invest in the maintenance and expansion of the network by voting. This results in faster development and promotion, creating a virtuous cycle that benefits all actors, including miners, masternode operators, investors and users. More importantly, this gives the blockchain itself a self-preservation mechanism that is beyond the control of any individual.<br />
{| class="wikitable"<br />
|-<br />
||'''Description'''<br />
| style="text-align: right;" data-mce-style="text-align: right;"|'''Percentage'''<br />
|-<br />
||Mining reward for Proof-of-BibleHash<br />
| style="text-align: right;" data-mce-style="text-align: right;"|3.0%<br />
|-<br />
||Mining reward for Proof-of-Distributed-Computing<br />
| style="text-align: right;" data-mce-style="text-align: right;"|38.5%<br />
|-<br />
||Masternode reward for Proof-of-Service<br />
| style="text-align: right;" data-mce-style="text-align: right;"|38.5%<br />
|-<br />
||Decentralized governance budget<br />
| style="text-align: right;" data-mce-style="text-align: right;"|20.0%<br />
|}<br />
<br />
<br />
<br />
20% of the mining reward is held back each block and is disbursed monthly by the masternode operators once the results of their votes are tallied, creating the first self-sustaining decentralized cryptocurrency platform organized as a Decentralized Autonomous Organization (DAO). The masternode operators establish a social contract with the network they benefit from and are bound to act as caretakers, dedicating their time, due diligence work and a portion of the network rewards to furthering the ecosystem. This has a ripple effect that benefits all parties involved - especially the end users.<br />
<br />
The value generated by work done implementing proposals is expected to be greater than allocating 100% of rewards to mining because the network has needs beyond only cryptographically securing the blockchain. The expected result is greater net benefit not only for proposal winners, but also masternode operators, miners and normal users. In fact, the introduction of the decentralized governance budget itself was decided by a masternode vote, making the first distributed decision the actual creation of the system, similar to establishing a constitution.<br />
<br />
This approach of distributing the normal block reward in a way that considers all critical elements a cryptocurrency needs for its long term viability, e.g. mining, full nodes, development and promotion, is revolutionary as it is done without changing the emission or creating any additional inflation for investors. The network simply distributes the available resources in a way that is of greater net benefit to all parties.<br />
<br />
=Contractors and proposals=<br />
Contractors of the blockchain can be developers, outreach professionals, team leaders, attorneys or even people appointed to do specific tasks. Proposals generally begin life as simple pre-proposal forum posts on the [http://forum.biblepay.org/index.php?board=5.0 BiblePay Forum], where feedback and suggestions are solicited from the general community. Once the proposal owner decides they have a reasonable chance of passing their proposal, it is created as a governance object on the blockchain. A fee of 2500 BiblePay is associated with this action to prevent spam and ensure only serious proposals make it to this stage. Several tools exist to allow masternode operators to comfortably review and vote on proposals. The net total of yes votes must exceed 10% of the total masternode count at the time votes are tallied in order to pass. If there are more passing proposals than the available block reward can provide for, the proposals with the most yes votes will pass first, creating a cut-off point for less popular proposals. The same process is then repeated every month, and the total amount of BiblePay available for proposals decreases by approximately 19.5% per year, together with the overall block reward.<br />
=Proposal websites=<br />
The community has gathered around the [http://forum.biblepay.org/index.php?board=5.0 BiblePay Forum] as a website to facilitate discussion and voting on proposals formally entered on the BiblePay blockchain. [https://www.biblepay-central.org/en/proposals/ BiblePay Central] and [https://pool.biblepay.org/ Pool.BiblePay] >>> Governance >>> Proposal List are available to view submitted proposals.<br />
<br />
Each proposal should include a description of the proposal goals, details of what work will be done and a breakdown of the requested budget. Many proposals also link to their own website or the pre-proposal discussion, or include a video to validate the identity and sincerity of the proposal owner. <br />
<br />
Masternode owners have the ability to cast a vote by signing a message from the masternode collateral address. Masternodes can vote at any time, and also change their vote at any time until the cutoff block is mined and voting stops. This occurs 1-3 days prior to the superblock. After voting stops, the blockchain executes a decentralized tally and validates all votes. Once consensus is reached, the results are broadcast and the budget is allocated soon after in a superblock.<br />
<br />
Once passed, proposals are able to report back to the network on the [http://forum.biblepay.org/index.php?board=5.0 BiblePay Forum] or via published public channels and social media. Since it is possible to create proposals that pay out over several months, it is also possible to revoke funding from a project by changing the vote if development or spending of already allocated funds is unsatisfactory. This encourages proposal owners to work honestly and diligently to win the trust and approval of the network. Ongoing discussion and gradual improvement over time results in a close bond between the network and those working for the network in supporting roles.<br />
<br />
Voting on proposals is updated in real time every 7 minutes as blocks are mined, so current winning proposals and the total allocation of the available budget are always open and visible to everyone. [https://www.biblepay-central.org/en/proposals/ BiblePay Central] is a popular site used for this purpose.<br />
=Budget allocation=<br />
The total budget of the network can be calculated by taking 20% of the reward over the period of time between two superblocks, which occur every 6150 blocks or approximately 29.89 days. A voting cutoff occurs 1-3 days before the superblock, and the final votes are tallied at this point. A proposal must satisfy the condition (YES votes - NO votes) > (Total Number of Masternodes / 10) in order to be considered passing. Then, in the superblock, the winning proposals are awarded in the order of the margin by which they are passing until either the entire budget is allocated or no more passing proposals exist. This allows for completely trustless and decentralized allocation of the budget.<br />
<br />
If a proposal has passed the voting threshold but insufficient funds remain to pay the full amount requested, it will not receive partial funding. Instead, any smaller proposals which have also passed the threshold that will fit in the budget will be funded, even if they have lower net approval than the larger proposal. Proposals requesting payment over multiple budget periods will remain in the treasury system for the duration of their validity if they pass the voting threshold, even if insufficient budget is available for funding as described above. Any unallocated budget is simply never created in the superblock, reducing unnecessary inflation.<br />
<br />
Due to the decentralized nature of the masternode system, it is sometimes necessary to form funded organisations, such as committees or companies, to be responsible for some project or task. These are submitted in the same way, but the committee itself receives the funds. Another alternative is to place trusted escrow services between the budget allocation event and the actual submitter of the proposal to ensure that work is paid for in stages, as it is delivered. Some oversight over blockchain contractors is sometimes needed. Each budgeted item requires either a team manager or a committee responsible for implementation of the work. Periodically, this manager is expected to report on budget expenditure and completed work to show the value created from the allocated funds. This allows repeat proposal submitters to build up a reputation and gain trust from the community. Proposals which do not provide regular reports and cannot answer questions about their budget allocation will soon be defunded if it is part of a regular monthly proposal cycle. The result is a kind of self-policing system.<br />
<br />
=Scaling and future uses=<br />
As the number of blockchain contractors increases, a point is reached where masternode operators cannot be realistically expected to evaluate the volume of proposals. At this point funding organizations can be created to act as contractors for the distribution of funds to many smaller decentralized projects, according to current needs.<br />
<br />
The existence of the decentralized budget system puts the power of determining where BiblePay goes in the future in the hands of the masternode network itself. All core development and several peripheral developers are already funded from the budget, and other projects not even conceivable at this time will likely arise in the future. This decouples the survival and value of the blockchain from the current userbase and developers, making the BiblePay blockchain designed to outlive its original users, a self sustainable decentralized cryptocurrency network that can still operate cohesively and bring added value services to end users in a consistent way.<br />
=Conclusion=<br />
Every masternode operator establishes a bond of trust and a social contract with the network in which she is bound to contribute to the development and maintenance of the ecosystem she benefits from. Under this model, a portion of the funds that the operator is bound to receive are in a sense allocated in custody, not in ownership, and are held in escrow by the network to be executed by the operators for the benefit of the ecosystem. Everyone contributes equally and proportionately to the benefits they are receiving and the risks they are taking, there are no privileges and no loopholes. This is complemented by the full node voting mechanism that allows for a distributed group to vote on a continuous basis on practical matters without the need to forfeit their right to decide to others, every few years, like with traditional governments or cooperative corporations.<br />
<br />
We envision a future in which this model of transparent, unbreakable and verifiable contribution to the common good, in combination with continuous participation of the crowd through active voting, is utilized to manage organizations that are owned or operated jointly by its members, who share the benefits and responsibilities of those collectives, like governments, cooperative corporations, unions, DAOs, cryptocurrencies, etc. We call this model decentralized governance by blockchain.<br />
<br />
<br />
----<br />
<br />
Reference: [https://docs.dash.org/en/latest/governance/understanding.html]<br />
<br />
[[Category:Sanctuary (Masternodes)]][[Category:Governance]]</div>Sunk818https://wiki.biblepay.org/index.php?title=UnderstandingGovernance&diff=6145UnderstandingGovernance2019-03-06T05:14:47Z<p>Sunk818: formatting</p>
<hr />
<div>=Understanding BiblePay Governance=<br />
One of the greatest challenges of building a cryptocurrency platform is ensuring you create a decentralized system of governance to manage, fund, maintain and expand the project. This key element has been absent in every major currency to date, so the natural response is to create a not-for-profit foundation that is tasked with maintaining the core protocol and promoting the coin, but is not really connected to the coin holders in any meaningful way. This approach has a few issues that have been made evident from the experience of older crypto currency platforms.<br />
<br />
Current crypto foundations are not related to the currency itself by any mechanism that is included in the protocol and are not designed to outlive early adopters when they lose interest. The foundation then struggles to maintain funding until it implodes and core development of the protocol is left scrambling for funding or depending on charity that can’t be counted on and does not allow for proper budgeting and planning. Donations are also unfair to donors because there are always free riders that benefit from the effort done by others without contributing. Other projects have financed themselves by premining coins or running prelaunch sales, which is not a great solution either because control of the funds is centralized and at that stage it is impossible to quantify the future needs of the project.<br />
<br />
Through the network of full nodes and the collateral requirement, BiblePay already has a decentralized network of masternode operators that are heavily invested in the future of the currency, and that as a group can act as stewards of the core protocol development and promotion. We propose a decentralized management system based on the masternode voting mechanism. Masternode operators are not the only ones interested in the success of BiblePay, but they are the most stable ones because, unlike miners, they can’t reuse their asset for any other purpose or coin.<br />
<br />
In the budget system, a portion of the block reward is held in escrow by the network itself, in the name of the operators, to be executed in the development and expansion of the ecosystem according to the vote of the masternodes in different budget proposals. These funds are directed to supporting development and promotion of the coin. Masternode operators vote on specific budgets and projects to be funded, thus defining the direction the coin is taking. This is done in a completely transparent way through a public portal where new initiatives are proposed and masternodes can vote on them. Functioning like a decentralized Kickstarter or Lighthouse, the budget can be used for anything that creates value within the ecosystem.<br />
<br />
This is a 100% decentralized system powered by the masternodes, where budgets are set and paid directly from the blockchain. The blockchain hires core developers in this way and introduces a new concept of paid blockchain contractors, where people work for and are directly compensated by the network, through the decentralized votes of all masternode operators. One advantage of this model is it can survive early adopters. If early masternode operators sell their coins, the new owner can set up a masternode and with it acquire the right to vote on the budgets and projects. This guarantees there is a working system of maintenance as people come and go, making the network capable of sustaining itself on its own without depending on specific actors.<br />
<br />
=Budgets and masternode voting=<br />
The system works as a decentralized voting mechanism set up in the rules governing the blockchain, where budgets for specific projects are proposed, then the masternodes as a whole vote on them. Each project, if it passes, is added to the total budget and paid directly from the blockchain to the person doing the work. This allows BiblePay to hire core developers and pay them directly after approval of the work in a decentralized fashion.<br />
<br />
A masternode votes on a proposal (technically a governance object on the blockchain) using the example command “masternode vote yes”, “masternode vote no” or “masternode vote abstain”. The votes then propagate across the network, and are tallied according to instructions followed by the network itself. Budgets under discussion and voting progress can be viewed using the example command “masternode budget show”.<br />
<br />
A well defined decentralized system of governance allows a cryptocurrency network to endure and survive its original creators. In this way, later generations of masternode operators have a clear way to support the system as defined by the protocol itself, applying wisdom of the crowd techniques and the bond of trust established by the masternode collateral to create a decentralized management system. This creates incredible value within the currency, allowing us to be more agile and compete with other payment systems, such as Bitcoin and credit cards, on a global scale.<br />
<br />
As the system develops, a strong team of productive contractors paid from blockchain rewards will arise and become established. This includes core developers, escrow providers, news and reporting staff, experimental development labs, partnerships with universities, marketing and PR firms and integrations with third party exchanges and payment platforms. The market recognizes the value of the stability of the network as a whole, and that the possibility of reliable and sufficient funding results in faster and more coherent implementation of the BiblePay roadmap and core BiblePay services.<br />
=Reward schedule=<br />
To guarantee long term sustainability of the blockchain, the network keeps a portion of the block rewards back as new blocks are created, with the masternode operators tasked to act as stewards and invest in the maintenance and expansion of the network by voting. This results in faster development and promotion, creating a virtuous cycle that benefits all actors, including miners, masternode operators, investors and users. More importantly, this gives the blockchain itself a self-preservation mechanism that is beyond the control of any individual.<br />
{| class="wikitable"<br />
|-<br />
||'''Description'''<br />
| style="text-align: right;" data-mce-style="text-align: right;"|'''Percentage'''<br />
|-<br />
||Mining reward for Proof-of-BibleHash<br />
| style="text-align: right;" data-mce-style="text-align: right;"|3.0%<br />
|-<br />
||Mining reward for Proof-of-Distributed-Computing<br />
| style="text-align: right;" data-mce-style="text-align: right;"|38.5%<br />
|-<br />
||Masternode reward for Proof-of-Service<br />
| style="text-align: right;" data-mce-style="text-align: right;"|38.5%<br />
|-<br />
||Decentralized governance budget<br />
| style="text-align: right;" data-mce-style="text-align: right;"|20.0%<br />
|}<br />
<br />
<br />
<br />
20% of the mining reward is held back each block and is disbursed monthly by the masternode operators once the results of their votes are tallied, creating the first self-sustaining decentralized cryptocurrency platform organized as a Decentralized Autonomous Organization (DAO). The masternode operators establish a social contract with the network they benefit from and are bound to act as caretakers, dedicating their time, due diligence work and a portion of the network rewards to furthering the ecosystem. This has a ripple effect that benefits all parties involved - especially the end users.<br />
<br />
The value generated by work done implementing proposals is expected to be greater than allocating 100% of rewards to mining because the network has needs beyond only cryptographically securing the blockchain. The expected result is greater net benefit not only for proposal winners, but also masternode operators, miners and normal users. In fact, the introduction of the decentralized governance budget itself was decided by a masternode vote, making the first distributed decision the actual creation of the system, similar to establishing a constitution.<br />
<br />
This approach of distributing the normal block reward in a way that considers all critical elements a cryptocurrency needs for its long term viability, e.g. mining, full nodes, development and promotion, is revolutionary as it is done without changing the emission or creating any additional inflation for investors. The network simply distributes the available resources in a way that is of greater net benefit to all parties.<br />
<br />
=Contractors and proposals=<br />
Contractors of the blockchain can be developers, outreach professionals, team leaders, attorneys or even people appointed to do specific tasks. Proposals generally begin life as simple pre-proposal forum posts on the [http://forum.biblepay.org/index.php?board=5.0 BiblePay Forum], where feedback and suggestions are solicited from the general community. Once the proposal owner decides they have a reasonable chance of passing their proposal, it is created as a governance object on the blockchain. A fee of 2500 BiblePay is associated with this action to prevent spam and ensure only serious proposals make it to this stage. Several tools exist to allow masternode operators to comfortably review and vote on proposals. The net total of yes votes must exceed 10% of the total masternode count at the time votes are tallied in order to pass. If there are more passing proposals than the available block reward can provide for, the proposals with the most yes votes will pass first, creating a cut-off point for less popular proposals. The same process is then repeated every month, and the total amount of BiblePay available for proposals decreases by approximately 19.5% per year, together with the overall block reward.<br />
=Proposal websites=<br />
The community has gathered around the [http://forum.biblepay.org/index.php?board=5.0 BiblePay Forum] as a website to facilitate discussion and voting on proposals formally entered on the BiblePay blockchain. [https://www.biblepay-central.org/en/proposals/ BiblePay Central] and [https://pool.biblepay.org/ Pool.BiblePay] >>> Governance >>> Proposal List are available to view submitted proposals.<br />
<br />
Each proposal should include a description of the proposal goals, details of what work will be done and a breakdown of the requested budget. Many proposals also link to their own website or the pre-proposal discussion, or include a video to validate the identity and sincerity of the proposal owner. <br />
<br />
Masternode owners have the ability to cast a vote by signing a message from the masternode collateral address. Masternodes can vote at any time, and also change their vote at any time until the cutoff block is mined and voting stops. This occurs 1-3 days prior to the superblock. After voting stops, the blockchain executes a decentralized tally and validates all votes. Once consensus is reached, the results are broadcast and the budget is allocated soon after in a superblock.<br />
<br />
Once passed, proposals are able to report back to the network on the [http://forum.biblepay.org/index.php?board=5.0 BiblePay Forum] or via published public channels and social media. Since it is possible to create proposals that pay out over several months, it is also possible to revoke funding from a project by changing the vote if development or spending of already allocated funds is unsatisfactory. This encourages proposal owners to work honestly and diligently to win the trust and approval of the network. Ongoing discussion and gradual improvement over time results in a close bond between the network and those working for the network in supporting roles.<br />
<br />
Voting on proposals is updated in real time every 7 minutes as blocks are mined, so current winning proposals and the total allocation of the available budget are always open and visible to everyone. [https://www.biblepay-central.org/en/proposals/ BiblePay Central] is a popular site used for this purpose.<br />
===Budget allocation===<br />
The total budget of the network can be calculated by taking 20% of the reward over the period of time between two superblocks, which occur every 6150 blocks or approximately 29.89 days. A voting cutoff occurs 1-3 days before the superblock, and the final votes are tallied at this point. A proposal must satisfy the condition (YES votes - NO votes) > (Total Number of Masternodes / 10) in order to be considered passing. Then, in the superblock, the winning proposals are awarded in the order of the margin by which they are passing until either the entire budget is allocated or no more passing proposals exist. This allows for completely trustless and decentralized allocation of the budget.<br />
<br />
If a proposal has passed the voting threshold but insufficient funds remain to pay the full amount requested, it will not receive partial funding. Instead, any smaller proposals which have also passed the threshold that will fit in the budget will be funded, even if they have lower net approval than the larger proposal. Proposals requesting payment over multiple budget periods will remain in the treasury system for the duration of their validity if they pass the voting threshold, even if insufficient budget is available for funding as described above. Any unallocated budget is simply never created in the superblock, reducing unnecessary inflation.<br />
<br />
Due to the decentralized nature of the masternode system, it is sometimes necessary to form funded organisations, such as committees or companies, to be responsible for some project or task. These are submitted in the same way, but the committee itself receives the funds. Another alternative is to place trusted escrow services between the budget allocation event and the actual submitter of the proposal to ensure that work is paid for in stages, as it is delivered. Some oversight over blockchain contractors is sometimes needed. Each budgeted item requires either a team manager or a committee responsible for implementation of the work. Periodically, this manager is expected to report on budget expenditure and completed work to show the value created from the allocated funds. This allows repeat proposal submitters to build up a reputation and gain trust from the community. Proposals which do not provide regular reports and cannot answer questions about their budget allocation will soon be defunded if it is part of a regular monthly proposal cycle. The result is a kind of self-policing system.<br />
=Scaling and future uses=<br />
As the number of blockchain contractors increases, a point is reached where masternode operators cannot be realistically expected to evaluate the volume of proposals. At this point funding organizations can be created to act as contractors for the distribution of funds to many smaller decentralized projects, according to current needs.<br />
<br />
The existence of the decentralized budget system puts the power of determining where BiblePay goes in the future in the hands of the masternode network itself. All core development and several peripheral developers are already funded from the budget, and other projects not even conceivable at this time will likely arise in the future. This decouples the survival and value of the blockchain from the current userbase and developers, making the BiblePay blockchain designed to outlive its original users, a self sustainable decentralized cryptocurrency network that can still operate cohesively and bring added value services to end users in a consistent way.<br />
=Conclusion=<br />
Every masternode operator establishes a bond of trust and a social contract with the network in which she is bound to contribute to the development and maintenance of the ecosystem she benefits from. Under this model, a portion of the funds that the operator is bound to receive are in a sense allocated in custody, not in ownership, and are held in escrow by the network to be executed by the operators for the benefit of the ecosystem. Everyone contributes equally and proportionately to the benefits they are receiving and the risks they are taking, there are no privileges and no loopholes. This is complemented by the full node voting mechanism that allows for a distributed group to vote on a continuous basis on practical matters without the need to forfeit their right to decide to others, every few years, like with traditional governments or cooperative corporations.<br />
<br />
We envision a future in which this model of transparent, unbreakable and verifiable contribution to the common good, in combination with continuous participation of the crowd through active voting, is utilized to manage organizations that are owned or operated jointly by its members, who share the benefits and responsibilities of those collectives, like governments, cooperative corporations, unions, DAOs, cryptocurrencies, etc. We call this model decentralized governance by blockchain.<br />
<br />
<br />
----<br />
<br />
Reference: [https://docs.dash.org/en/latest/governance/understanding.html]<br />
<br />
[[Category:Sanctuary (Masternodes)]][[Category:Governance]]</div>Sunk818https://wiki.biblepay.org/index.php?title=Economics&diff=6138Economics2019-02-28T19:28:42Z<p>Sunk818: </p>
<hr />
<div>== BiblePay Economics: ==<br />
<br />
== Gross Block Breakdown: ==<br />
<br />
* Block Emission Level: Variable rate between 20000 and 5000, based on the network difficulty level (higher diff, lower block subsidy), deflating at 19.5% per year<br />
* 20% is escrowed for governance for expenses paid via our sanctuary voted budget - emitted as one monthly superblock (10% for charity, 5% IT, 2.5% P2P, 2.5% PR)<br />
* 37.5% is escrowed for Proof-of-distributed Computing (our Cancer Mining Research Budget - emitted in one daily superblock)<br />
* 38.5% is given to the next due Sanctuary<br />
* 4% is allocated to heat-mining (Proof-of-BibleHash POW mining), out of this 4% allocation, 80% goes to the POG Pool (the Sowers) and 20% goes to the one who solved the block (the Reaper)<br />
<br />
== How to calculate a BiblePay reward schedule: ==<br />
<br />
* Block 70,000 has a gross reward of 11,645<br />
* Multiply 11645 * .20 to find the governance budget (2329)<br />
* Multiply 11645 * .375 to find the PODC budget (4308)<br />
* Multiply 11645 * .385 to find the Sanctuary payment (4492)<br />
* Multiply 11645 * .042 to find the POW heat miner allocation (499)<br />
* Multiply 499 * .20 to find the Reaper Reward (100).<br />
* Multiply 499 * .80 to find the POG Pool allocation (399).<br />
* Total : 100%<br />
<br />
== Gross breakdown of Governance Budget: ==<br />
<br />
* Charity and Recurring Orphanage expenses (compassion.com, BLOOM, Cameroon One, Kairos, etc): 50%<br />
* IT Expenses and Payroll: 25%<br />
* PR and Campaigns: 12.5%<br />
* Peer-to-Peer (Letter writing, gospel links, pay to preach): 12.5%<br />
<br />
== Gross breakdown of mining operations (Allocation of 80% of Gross Coinbase Reward): ==<br />
<br />
* 46.5% is given to PODC cancer miners<br />
* 48.5% is given to the Sanctuary<br />
* 5% is given to POW/POG Pool<br />
<br />
== Deflation: ==<br />
<br />
The deflation rate of our emission is 1.5% Per Month, or 19.5% per year compounded.<br />
<br />
See [[Emission Schedule|BiblePay Emission Schedule]] for more details.<br />
<br />
[[Category:BiblePay Economics]]</div>Sunk818https://wiki.biblepay.org/index.php?title=Economics&diff=6137Economics2019-02-28T19:27:07Z<p>Sunk818: </p>
<hr />
<div>== BiblePay Economics: ==<br />
<br />
<br />
<br />
<br />
== Gross Block Breakdown: ==<br />
<br />
* Block Emission Level: Variable rate between 20000 and 5000, based on the network difficulty level (higher diff, lower block subsidy), deflating at 19.5% per year<br />
* 20% is escrowed for governance for expenses paid via our sanctuary voted budget - emitted as one monthly superblock (10% for charity, 5% IT, 2.5% P2P, 2.5% PR)<br />
* 37.5% is escrowed for Proof-of-distributed Computing (our Cancer Mining Research Budget - emitted in one daily superblock)<br />
* 38.5% is given to the next due Sanctuary<br />
* 4% is allocated to heat-mining (Proof-of-BibleHash POW mining), out of this 4% allocation, 80% goes to the POG Pool (the Sowers) and 20% goes to the one who solved the block (the Reaper)<br />
<br />
<br />
== How to calculate a BiblePay reward schedule: ==<br />
<br />
* Block 70,000 has a gross reward of 11,645<br />
* Multiply 11645 * .20 to find the governance budget (2329)<br />
* Multiply 11645 * .375 to find the PODC budget (4308)<br />
* Multiply 11645 * .385 to find the Sanctuary payment (4492)<br />
* Multiply 11645 * .042 to find the POW heat miner allocation (499)<br />
* Multiply 499 * .20 to find the Reaper Reward (100).<br />
* Multiply 499 * .80 to find the POG Pool allocation (399).<br />
* Total : 100%<br />
<br />
<br />
== Gross breakdown of Governance Budget: ==<br />
<br />
* Charity and Recurring Orphanage expenses (compassion.com, BLOOM, Cameroon One, Kairos, etc): 50%<br />
* IT Expenses and Payroll: 25%<br />
* PR and Campaigns: 12.5%<br />
* Peer-to-Peer (Letter writing, gospel links, pay to preach): 12.5%<br />
<br />
<br />
== Gross breakdown of mining operations (Allocation of 80% of Gross Coinbase Reward): ==<br />
<br />
* 46.5% is given to PODC cancer miners</li><br />
* 48.5% is given to the Sanctuary</li><br />
* 5% is given to POW/POG Pool</li><br />
<br />
<br />
<br />
== Deflation: ==<br />
<br />
The deflation rate of our emission is 1.5% Per Month, or 19.5% per year compounded.<br />
<br />
See [[Emission Schedule|BiblePay Emission Schedule]] for more details.<br />
<br />
<br />
[[Category:BiblePay Economics]]</div>Sunk818https://wiki.biblepay.org/index.php?title=Economics&diff=6136Economics2019-02-28T19:25:12Z<p>Sunk818: change to wiki formatting</p>
<hr />
<div>== BiblePay Economics: ==<br />
<br />
<br />
<br />
<br />
== Gross Block Breakdown: ==<br />
<br />
* Block Emission Level: Variable rate between 20000 and 5000, based on the network difficulty level (higher diff, lower block subsidy), deflating at 19.5% per year<br />
* 20% is escrowed for governance for expenses paid via our sanctuary voted budget - emitted as one monthly superblock (10% for charity, 5% IT, 2.5% P2P, 2.5% PR)<br />
* 37.5% is escrowed for Proof-of-distributed Computing (our Cancer Mining Research Budget - emitted in one daily superblock)<br />
* 38.5% is given to the next due Sanctuary<br />
* 4% is allocated to heat-mining (Proof-of-BibleHash POW mining), out of this 4% allocation, 80% goes to the POG Pool (the Sowers) and 20% goes to the one who solved the block (the Reaper)<br />
<br />
<br />
== How to calculate a BiblePay reward schedule: ==<br />
<br />
* Block 70,000 has a gross reward of 11,645<br />
* Multiply 11645 * .20 to find the governance budget (2329)<br />
* Multiply 11645 * .375 to find the PODC budget (4308)<br />
* Multiply 11645 * .385 to find the Sanctuary payment (4492)<br />
* Multiply 11645 * .042 to find the POW heat miner allocation (499)<br />
* Multiply 499 * .20 to find the Reaper Reward (100).<br />
* Multiply 499 * .80 to find the POG Pool allocation (399).<br />
* Total : 100%<br />
<br />
<br />
== Gross breakdown of Governance Budget: ==<br />
<br />
* Charity and Recurring Orphanage expenses (compassion.com, BLOOM, Cameroon One, Kairos, etc): 50%<br />
* IT Expenses and Payroll: 25%<br />
* PR and Campaigns: 12.5%<br />
* Peer-to-Peer (Letter writing, gospel links, pay to preach): 12.5%<br />
<br />
<br />
== Gross breakdown of mining operations (Allocation of 80% of Gross Coinbase Reward): ==<br />
<br />
* 46.5% is given to PODC cancer miners</li><br />
* 48.5% is given to the Sanctuary</li><br />
* 5% is given to POW/POG Pool</li><br />
<br />
<br />
<br />
== Deflation: ==<br />
<br />
The deflation rate of our emission is 1.5% Per Month, or 19.5% per year compounded.<br />
<br />
<br />
[http://wiki.biblepay.org/Emission_Schedule|BiblePay Emission Schedule]<br />
<br />
<br />
[[Category:BiblePay Economics]]</div>Sunk818https://wiki.biblepay.org/index.php?title=UnderstandingGovernance&diff=6127UnderstandingGovernance2019-02-26T17:22:00Z<p>Sunk818: </p>
<hr />
<div>=== Understanding BiblePay Governance === <br />
<br />
One of the greatest challenges of building a cryptocurrency platform is ensuring you create a decentralized system of governance to manage, fund, maintain and expand the project. This key element has been absent in every major currency to date, so the natural response is to create a not-for-profit foundation that is tasked with maintaining the core protocol and promoting the coin, but is not really connected to the coin holders in any meaningful way. This approach has a few issues that have been made evident from the experience of older crypto currency platforms.<br />
<br />
Current crypto foundations are not related to the currency itself by any mechanism that is included in the protocol and are not designed to outlive early adopters when they lose interest. The foundation then struggles to maintain funding until it implodes and core development of the protocol is left scrambling for funding or depending on charity that can’t be counted on and does not allow for proper budgeting and planning. Donations are also unfair to donors because there are always free riders that benefit from the effort done by others without contributing. Other projects have financed themselves by premining coins or running prelaunch sales, which is not a great solution either because control of the funds is centralized and at that stage it is impossible to quantify the future needs of the project.<br />
<br />
Through the network of full nodes and the collateral requirement, BiblePay already has a decentralized network of masternode operators that are heavily invested in the future of the currency, and that as a group can act as stewards of the core protocol development and promotion. We propose a decentralized management system based on the masternode voting mechanism. Masternode operators are not the only ones interested in the success of BiblePay, but they are the most stable ones because, unlike miners, they can’t reuse their asset for any other purpose or coin.<br />
<br />
In the budget system, a portion of the block reward is held in escrow by the network itself, in the name of the operators, to be executed in the development and expansion of the ecosystem according to the vote of the masternodes in different budget proposals. These funds are directed to supporting development and promotion of the coin. Masternode operators vote on specific budgets and projects to be funded, thus defining the direction the coin is taking. This is done in a completely transparent way through a public portal where new initiatives are proposed and masternodes can vote on them. Functioning like a decentralized Kickstarter or Lighthouse, the budget can be used for anything that creates value within the ecosystem.<br />
<br />
This is a 100% decentralized system powered by the masternodes, where budgets are set and paid directly from the blockchain. The blockchain hires core developers in this way and introduces a new concept of paid blockchain contractors, where people work for and are directly compensated by the network, through the decentralized votes of all masternode operators. One advantage of this model is it can survive early adopters. If early masternode operators sell their coins, the new owner can set up a masternode and with it acquire the right to vote on the budgets and projects. This guarantees there is a working system of maintenance as people come and go, making the network capable of sustaining itself on its own without depending on specific actors.<br />
<br />
=== Budgets and masternode voting ===<br />
<br />
The system works as a decentralized voting mechanism set up in the rules governing the blockchain, where budgets for specific projects are proposed, then the masternodes as a whole vote on them. Each project, if it passes, is added to the total budget and paid directly from the blockchain to the person doing the work. This allows BiblePay to hire core developers and pay them directly after approval of the work in a decentralized fashion.<br />
<br />
A masternode votes on a proposal (technically a governance object on the blockchain) using the example command “masternode vote yes”, “masternode vote no” or “masternode vote abstain”. The votes then propagate across the network, and are tallied according to instructions followed by the network itself. Budgets under discussion and voting progress can be viewed using the example command “masternode budget show”.<br />
<br />
A well defined decentralized system of governance allows a cryptocurrency network to endure and survive its original creators. In this way, later generations of masternode operators have a clear way to support the system as defined by the protocol itself, applying wisdom of the crowd techniques and the bond of trust established by the masternode collateral to create a decentralized management system. This creates incredible value within the currency, allowing us to be more agile and compete with other payment systems, such as Bitcoin and credit cards, on a global scale.<br />
<br />
As the system develops, a strong team of productive contractors paid from blockchain rewards will arise and become established. This includes core developers, escrow providers, news and reporting staff, experimental development labs, partnerships with universities, marketing and PR firms and integrations with third party exchanges and payment platforms. The market recognizes the value of the stability of the network as a whole, and that the possibility of reliable and sufficient funding results in faster and more coherent implementation of the BiblePay roadmap and core BiblePay services.<br />
<br />
=== Reward schedule ===<br />
<br />
To guarantee long term sustainability of the blockchain, the network keeps a portion of the block rewards back as new blocks are created, with the masternode operators tasked to act as stewards and invest in the maintenance and expansion of the network by voting. This results in faster development and promotion, creating a virtuous cycle that benefits all actors, including miners, masternode operators, investors and users. More importantly, this gives the blockchain itself a self-preservation mechanism that is beyond the control of any individual.<br />
<br />
{| class="wikitable"<br />
|'''Description'''<br />
|'''Percentage'''<br />
|-<br />
|Mining reward for Proof-of-BibleHash<br />
|3.0%<br />
|-<br />
|Mining reward for Proof-of-Distributed-Computing<br />
|38.5%<br />
|-<br />
|Masternode reward for Proof-of-Service<br />
|38.5%<br />
|-<br />
|Decentralized governance budget<br />
|20.0%<br />
|}<br />
<br />
20% of the mining reward is held back each block and is disbursed monthly by the masternode operators once the results of their votes are tallied, creating the first self-sustaining decentralized cryptocurrency platform organized as a Decentralized Autonomous Organization (DAO). The masternode operators establish a social contract with the network they benefit from and are bound to act as caretakers, dedicating their time, due diligence work and a portion of the network rewards to furthering the ecosystem. This has a ripple effect that benefits all parties involved - especially the end users.<br />
<br />
The value generated by work done implementing proposals is expected to be greater than allocating 100% of rewards to mining because the network has needs beyond only cryptographically securing the blockchain. The expected result is greater net benefit not only for proposal winners, but also masternode operators, miners and normal users. In fact, the introduction of the decentralized governance budget itself was decided by a masternode vote, making the first distributed decision the actual creation of the system, similar to establishing a constitution.<br />
<br />
This approach of distributing the normal block reward in a way that considers all critical elements a cryptocurrency needs for its long term viability, e.g. mining, full nodes, development and promotion, is revolutionary as it is done without changing the emission or creating any additional inflation for investors. The network simply distributes the available resources in a way that is of greater net benefit to all parties.<br />
<br />
=== Contractors and proposals ===<br />
<br />
Contractors of the blockchain can be developers, outreach professionals, team leaders, attorneys or even people appointed to do specific tasks. Proposals generally begin life as simple pre-proposal forum posts on the [http://forum.biblepay.org/index.php?board=5.0 BiblePay Forum], where feedback and suggestions are solicited from the general community. Once the proposal owner decides they have a reasonable chance of passing their proposal, it is created as a governance object on the blockchain. A fee of 2500 BiblePay is associated with this action to prevent spam and ensure only serious proposals make it to this stage. Several tools exist to allow masternode operators to comfortably review and vote on proposals. The net total of yes votes must exceed 10% of the total masternode count at the time votes are tallied in order to pass. If there are more passing proposals than the available block reward can provide for, the proposals with the most yes votes will pass first, creating a cut-off point for less popular proposals. The same process is then repeated every month, and the total amount of BiblePay available for proposals decreases by approximately 19.5% per year, together with the overall block reward.<br />
<br />
=== Proposal websites ===<br />
<br />
The community has gathered around the [http://forum.biblepay.org/index.php?board=5.0 BiblePay Forum] as a website to facilitate discussion and voting on proposals formally entered on the BiblePay blockchain. [https://www.biblepay-central.org/en/proposals/ BiblePay Central] and [https://pool.biblepay.org/ Pool.BiblePay] >>> Governance >>> Proposal List are available to view submitted proposals.<br />
<br />
Each proposal should include a description of the proposal goals, details of what work will be done and a breakdown of the requested budget. Many proposals also link to their own website or the pre-proposal discussion, or include a video to validate the identity and sincerity of the proposal owner. <br />
<br />
Masternode owners have the ability to cast a vote by signing a message from the masternode collateral address. Masternodes can vote at any time, and also change their vote at any time until the cutoff block is mined and voting stops. This occurs 1-3 days prior to the superblock. After voting stops, the blockchain executes a decentralized tally and validates all votes. Once consensus is reached, the results are broadcast and the budget is allocated soon after in a superblock.<br />
<br />
Once passed, proposals are able to report back to the network on the [http://forum.biblepay.org/index.php?board=5.0 BiblePay Forum] or via published public channels and social media. Since it is possible to create proposals that pay out over several months, it is also possible to revoke funding from a project by changing the vote if development or spending of already allocated funds is unsatisfactory. This encourages proposal owners to work honestly and diligently to win the trust and approval of the network. Ongoing discussion and gradual improvement over time results in a close bond between the network and those working for the network in supporting roles.<br />
<br />
Voting on proposals is updated in real time every 7 minutes as blocks are mined, so current winning proposals and the total allocation of the available budget are always open and visible to everyone. [https://www.biblepay-central.org/en/proposals/ BiblePay Central] is a popular site used for this purpose.<br />
<br />
=== Budget allocation ===<br />
<br />
The total budget of the network can be calculated by taking 20% of the reward over the period of time between two superblocks, which occur every 6150 blocks or approximately 29.89 days. A voting cutoff occurs 1-3 days before the superblock, and the final votes are tallied at this point. A proposal must satisfy the condition (YES votes - NO votes) > (Total Number of Masternodes / 10) in order to be considered passing. Then, in the superblock, the winning proposals are awarded in the order of the margin by which they are passing until either the entire budget is allocated or no more passing proposals exist. This allows for completely trustless and decentralized allocation of the budget.<br />
<br />
If a proposal has passed the voting threshold but insufficient funds remain to pay the full amount requested, it will not receive partial funding. Instead, any smaller proposals which have also passed the threshold that will fit in the budget will be funded, even if they have lower net approval than the larger proposal. Proposals requesting payment over multiple budget periods will remain in the treasury system for the duration of their validity if they pass the voting threshold, even if insufficient budget is available for funding as described above. Any unallocated budget is simply never created in the superblock, reducing unnecessary inflation.<br />
<br />
Due to the decentralized nature of the masternode system, it is sometimes necessary to form funded organisations, such as committees or companies, to be responsible for some project or task. These are submitted in the same way, but the committee itself receives the funds. Another alternative is to place trusted escrow services between the budget allocation event and the actual submitter of the proposal to ensure that work is paid for in stages, as it is delivered. Some oversight over blockchain contractors is sometimes needed. Each budgeted item requires either a team manager or a committee responsible for implementation of the work. Periodically, this manager is expected to report on budget expenditure and completed work to show the value created from the allocated funds. This allows repeat proposal submitters to build up a reputation and gain trust from the community. Proposals which do not provide regular reports and cannot answer questions about their budget allocation will soon be defunded if it is part of a regular monthly proposal cycle. The result is a kind of self-policing system.<br />
<br />
=== Scaling and future uses ===<br />
<br />
As the number of blockchain contractors increases, a point is reached where masternode operators cannot be realistically expected to evaluate the volume of proposals. At this point funding organizations can be created to act as contractors for the distribution of funds to many smaller decentralized projects, according to current needs.<br />
<br />
The existence of the decentralized budget system puts the power of determining where BiblePay goes in the future in the hands of the masternode network itself. All core development and several peripheral developers are already funded from the budget, and other projects not even conceivable at this time will likely arise in the future. This decouples the survival and value of the blockchain from the current userbase and developers, making the BiblePay blockchain designed to outlive its original users, a self sustainable decentralized cryptocurrency network that can still operate cohesively and bring added value services to end users in a consistent way.<br />
<br />
=== Conclusion ===<br />
<br />
Every masternode operator establishes a bond of trust and a social contract with the network in which she is bound to contribute to the development and maintenance of the ecosystem she benefits from. Under this model, a portion of the funds that the operator is bound to receive are in a sense allocated in custody, not in ownership, and are held in escrow by the network to be executed by the operators for the benefit of the ecosystem. Everyone contributes equally and proportionately to the benefits they are receiving and the risks they are taking, there are no privileges and no loopholes. This is complemented by the full node voting mechanism that allows for a distributed group to vote on a continuous basis on practical matters without the need to forfeit their right to decide to others, every few years, like with traditional governments or cooperative corporations.<br />
<br />
We envision a future in which this model of transparent, unbreakable and verifiable contribution to the common good, in combination with continuous participation of the crowd through active voting, is utilized to manage organizations that are owned or operated jointly by its members, who share the benefits and responsibilities of those collectives, like governments, cooperative corporations, unions, DAOs, cryptocurrencies, etc. We call this model decentralized governance by blockchain.<br />
<br />
----<br />
<br />
Reference: [https://docs.dash.org/en/latest/governance/understanding.html]<br />
<br />
[[Category:Sanctuary (Masternodes)]]<br />
[[Category:Governance]]</div>Sunk818https://wiki.biblepay.org/index.php?title=Main_Page&diff=6125Main Page2019-02-26T17:16:33Z<p>Sunk818: </p>
<hr />
<div>{| class="wikitable" style="text-align:center; margin-left:2em"<br />
|| BIBLEPAY || 10% Charity, Masternodes (Sanctuaries), ASIC-Resistant, CPU-Mining, 10% to Orphans<br />
|-<br />
|| Mint || Decentralized Proof Of Work<br />
|-<br />
|| Launch Date || August 2017<br />
|-<br />
|| Developed by || Robert Andrews<br />
|-<br />
|| Ticker || BBP<br />
|-<br />
|| Plural || Biblepays<br />
|-<br />
|| Subunit || mBBP =0.001<br />
|-<br />
|| Lowest Unit || 0.00000001 = 1 BBP<br />
|-<br />
|| Operating System || Windows, Linux, macOS<br />
|-<br />
|| Algorithm || Proof-of-BibleHash<br />
|-<br />
|| Current Version || Client v1.0.2.9 mandatory<br />
|-<br />
|| Release Date || July 23rd, 2017<br />
|-<br />
|| Blocktime || avg 7 Minutes<br />
|-<br />
|| Reward || 20,000 Decreasing by 1.5% per month (Approx 19% per year)<br />
|}<br />
<br />
<br />
<p>'''NAME:''' BIBLEPAY</p><br />
<br />
<br />
<p>'''LAUNCH DATE:''' JULY 23, 2017 at 17:00:00 CST</p><br />
<br />
<p>'''BLOCK TARGET RATE:''' 7 MINUTES</p><br />
<br />
<p>'''ALGORITHM:''' PROOF OF BIBLEHASH (POBh) ** NEW **</p><br />
<br />
<p>First coin with the KJV Bible compiled in the source, and utilizing the Bible in the hashing algorithm, while spreading the gospel throughout the IT community. The blocks also hash to chained bible verses.</p><br />
<br />
<p>'''TRANSACTION SPEED:''' SUPPORTS INSTANTSEND</p><br />
<p>'''MASTERNODE(SANCTUARY) SUPPORT:''' Supported after Christmas 2017</p><br />
<p>'''SANCTUARY SUBSIDY BREAKDOWN:''' 10% TO CHARITY, 10% TO MASTERNODES, 80% TO MINER</p><br />
<p>'''FORUM:''' [http://bitcointalk.org/topic=2042657 Bitcointalk]</p><br />
<p>'''Backup Forum:'''[http://forum.biblepay.org/ forum.biblepay.org]</p><br />
<p>'''BLOCK EXPLORER:'''[https://biblepay-explorer.org/ biblepay-explorer.org]</p><br />
<p>'''BLOCK EXPLORER:'''[http://explorer.biblepay.org:3001/ explorer.biblepay.org]</p><br />
<p>'''SOURCE CODE:'''[http://github.com/biblepay/biblepay Github]</p><br />
<p>'''WEB SITE:'''[http://biblepay.org biblepay.org]</p><br />
<p>'''EXCHANGES:'''[https://c-cex.com/?p=bbp-btc c-cex]</p><br />
<p>'''[https://www.southxchange.com/Market/Book/BBP/BTC]</p><br />
<br />
<p>'''TICKER:''' BBP</p><br />
<p>'''Exchange Go Live Date:''' August 15th 2017</p><br />
<p>'''PREMINE:''' NONE</p><br />
<p>'''ICO:''' NONE</p><br />
<p>'''INCONSISTENT REWARDS:''' NONE</p><br />
<p>'''CIRCULATION CHARACTERISTIC:''' DEFLATIONARY</p><br />
<p>'''CIRCULATION RATE:''' DECREASE BY 10% PER YEAR</p><br />
<p>'''TOTAL CIRCULATION:''' 5.2 BILLION BY 2050, DECREASING BY 18% PER YEAR</p><br />
<br />
<p>'''DESCRIPTION:'''</p><br />
<p>A secure blockchain benefiting those in distress - 10% of the emission goes to sponsoring Orphans, with provable contributions, expenses contributed to [http://compassion.com http://compassion.com] - and future charities that are more than 75% efficient. ** NOTE: THE COIN HAS RPC COMMANDS THAT PROVE 100% OF CONTRIBUTIONS ARE SPENT THE WAY INTENDED **</p> <br />
<br />
<br />
<p>Proof of Work has been replaced with Proof Of Biblehash (POBh) - an algorithm that compensates full nodes participation, while preventing GPUs and ASIC by requiring full blockchain transaction referencing in the hashing function, along with chained bible verses. This means biblepay subsidizes full nodes that stay online.</p><br />
<br />
<p>Seven minute block targets minimize the blockchain file size, yet BiblePay does support Dash's instantsend for speedy transactions. MasterNodes (called Sanctuaries) will come online after Christmas, allowing all expenses to be voted on and approved.</p><br />
<p>Expense receipts, to prove the sponshorship of new orphans, will be accessible from inside the wallet and we will even provide phone numbers for auditors to prove </p><br />
100% charity expenditures. (From the rpc, type &#39;run contribution&#39; to see the tithes into the foundation for a time period, and to see the outgoing sponsorship click the wallets &#39;Accountability&#39; button to see a list of orphans, expenses, sponsorship dates, amounts, and the charity phone number, and txid).<br />
<br />
<p>For the first 6 months, 10% of each block will be allocated to the foundation, for sponsoring orphans at 100%. Once per month, we will cash in anything over $40 available on an exchange, and sponsor orphans on our volunteer time. After the sanctuaries go live, the 10% tithe will be diverted to an ongoing budget with DAO governance, voting, allowing the coin to function as a dectralized autonomous charity; at that point the lead dev and volunteers will become a normal part of the community allowing the coin to run by itself.</p><br />
<br />
<p>To avoid wasting energy on meaningless SHA hashing, (or mining), biblepay introduces the BibleHash algorithm, that allows biblepay to <br />
run on common commodity PCs, since the algorithm is resistant to porting to video cards and ASICs and is resistant to running in non-full node environments.</p><br />
<p>In addition to the low energy requirements and high efficiency of POB, the reward per block is set to be relative to the length of time the block took to solve, <br />
(meaning that abusive hash attacks result in subsidy decreases).</p><br />
<p>The network will be high efficiency with low total energy consumption, and the charities sponsored must also be high efficiency (over 75%).<br />
Next, we are deflationary, meaning that we start by issuing a larger amount of coins per block, and each year we tighten the supply by 18%.</p><br />
<br />
The schedule is here: (205 blocks per day, 7 minute block targets):<br />
EMISSION SCHEDULE PROJECTION: http://wiki.biblepay.org/Emission_Schedule<br />
<br />
<p>The block reward breakdown is as follows:</p><br />
<br />
ECONOMICS: http://wiki.biblepay.org/Economics<br />
<br />
<br />
<p>After our sanctuaries go live, we allocate 10% of each block subsidy to our governance committe (a DAO), automatically, with 100% of that being<br />
spent on charity. <br />
<br />
Over time, our sanctuaries will become a charity governance committee, to allow our community to take over the day to day operations of the charity: voting on where the money is spent, how much is spent.<br />
This way, we will not be centralized.</p><br />
<br />
<p>We only partner with charities over 75% efficient, meaning over 75% reach the end-user.</p><br />
<br />
<br />
<p>'''<span style="color:#ff0000">NO PREMINE:</span>'''</p><br />
<p>the lead dev starts with zero, the orphan foundation fund starts with zero, the distribution is entirely fair. NO ICO. The distribution curve is evenly declining with no hidden bumps early.<br />
The self-governance committee and masternode payments are deliberately delayed until Christmas, to allow people to prepare and save up the initial requirement. Running a sanctuary is open to anyone.<br />
The lead dev will sponsor the first 10 orphans out of his own pocket.</p><br />
<p>'''<span style="color:#ff0000">Accountability:</span></p><br />
<p>The wallet will have a reconciliation page built in at go live, to show all charitable income and expenses.</p><br />
<p>The expenses will be auditable - to prove the money actually was spent on orphans.</p><br />
<p>This will be accomplished through the use of : an RPC audit command that tallies the orphan income from the blockchain, and secondly, an API connection to a database that stores the Compassion expenses (until sanctuaries go live), with auditable backing contact info for each expense. We will also provide a web page with pictures of the sponsored orphans clicable from the wallet to show our investors what good we are doing. And finally- we will maintain a copy of receipts in order to maintain 100% accountability.</p><br />
<p>Future Feature: Pay to Preach, in wallet ineractive prayer rooms.</p><br />
<br />
'''ROADMAP:'''<br />
JULY-DECEMBER 2017: GO LIVE, SPONSOR ORPHANS MONTHLY<br />
<br />
JANUARY 2018: MASTERNODES (SANCTUARIES) GO LIVE<br />
<br />
FEBRUARY 2018: MARKETING, IN WALLET PRAYERS<br />
<br />
MAY 2018: MARKET BIBLEPAY AS A 401K ALTERNATIVE<br />
<br />
[[:Category:Roadmap|More roadmap details]]<br />
<br />
'''Novel distinct features of BiblePay:'''<br />
<br />
<p>Proof of Bible Hash algorithm (POBh), getblockinfo shows the chained bible verses required to solve the block, sending money exposes a Tithe checkbox - allowing 10% to be gifted to the orphan foundation, wallet has an in-wallet prayer system, allowing a user to send out a prayer request to the network or store prayers in the chain for the community to pray for from the overview page, Transactions support in-chain messages, Instant Send, Voting, Decentralized Automated Charity Governance Committee, Repentance of Sins, Contributing to the orphan foundation checkbox, and reading the sin list and various staple prayers in wallet.</p><br />
<br />
Further Reading:<br />
[[Special:Categories]]</div>Sunk818https://wiki.biblepay.org/index.php?title=Main_Page&diff=6124Main Page2019-02-26T17:14:06Z<p>Sunk818: </p>
<hr />
<div>{| class="wikitable" style="text-align:center; margin-left:2em"<br />
|| BIBLEPAY || 10% Charity, Masternodes (Sanctuaries), ASIC-Resistant, CPU-Mining, 10% to Orphans<br />
|-<br />
|| Mint || Decentralized Proof Of Work<br />
|-<br />
|| Launch Date || August 2017<br />
|-<br />
|| Developed by || Robert Andrews<br />
|-<br />
|| Ticker || BBP<br />
|-<br />
|| Plural || Biblepays<br />
|-<br />
|| Subunit || mBBP =0.001<br />
|-<br />
|| Lowest Unit || 0.00000001 = 1 BBP<br />
|-<br />
|| Operating System || Windows, Linux, macOS<br />
|-<br />
|| Algorithm || Proof-of-BibleHash<br />
|-<br />
|| Current Version || Client v1.0.2.9 mandatory<br />
|-<br />
|| Release Date || July 23rd, 2017<br />
|-<br />
|| Blocktime || avg 7 Minutes<br />
|-<br />
|| Reward || 20,000 Decreasing by 1.5% per month (Approx 19% per year)<br />
|}<br />
<br />
<br />
<p>'''NAME:''' BIBLEPAY</p><br />
<br />
<br />
<p>'''LAUNCH DATE:''' JULY 23, 2017 at 17:00:00 CST</p><br />
<br />
<p>'''BLOCK TARGET RATE:''' 7 MINUTES</p><br />
<br />
<p>'''ALGORITHM:''' PROOF OF BIBLEHASH (POBh) ** NEW **</p><br />
<br />
<p>First coin with the KJV Bible compiled in the source, and utilizing the Bible in the hashing algorithm, while spreading the gospel throughout the IT community. The blocks also hash to chained bible verses.</p><br />
<br />
<p>'''TRANSACTION SPEED:''' SUPPORTS INSTANTSEND</p><br />
<p>'''MASTERNODE(SANCTUARY) SUPPORT:''' Supported after Christmas 2017</p><br />
<p>'''SANCTUARY SUBSIDY BREAKDOWN:''' 10% TO CHARITY, 10% TO MASTERNODES, 80% TO MINER</p><br />
<p>'''FORUM:''' [http://bitcointalk.org/topic=2042657 Bitcointalk]</p><br />
<p>'''Backup Forum:'''[http://forum.biblepay.org/ forum.biblepay.org]</p><br />
<p>'''BLOCK EXPLORER:'''[https://biblepay-explorer.org/ biblepay-explorer.org]</p><br />
<p>'''BLOCK EXPLORER:'''[http://explorer.biblepay.org:3001/ explorer.biblepay.org]</p><br />
<p>'''SOURCE CODE:'''[http://github.com/biblepay/biblepay Github]</p><br />
<p>'''WEB SITE:'''[http://biblepay.org biblepay.org]</p><br />
<p>'''EXCHANGES:'''[https://c-cex.com/?p=bbp-btc c-cex]</p><br />
<p>'''[https://www.southxchange.com/Market/Book/BBP/BTC]</p><br />
<br />
<p>'''TICKER:''' BBP</p><br />
<p>'''Exchange Go Live Date:''' August 15th 2017</p><br />
<p>'''PREMINE:''' NONE</p><br />
<p>'''ICO:''' NONE</p><br />
<p>'''INCONSISTENT REWARDS:''' NONE</p><br />
<p>'''CIRCULATION CHARACTERISTIC:''' DEFLATIONARY</p><br />
<p>'''CIRCULATION RATE:''' DECREASE BY 10% PER YEAR</p><br />
<p>'''TOTAL CIRCULATION:''' 5.2 BILLION BY 2050, DECREASING BY 18% PER YEAR</p><br />
<br />
<p>'''DESCRIPTION:'''</p><br />
<p>A secure blockchain benefiting those in distress - 10% of the emission goes to sponsoring Orphans, with provable contributions, expenses contributed to [http://compassion.com http://compassion.com] - and future charities that are more than 75% efficient. ** NOTE: THE COIN HAS RPC COMMANDS THAT PROVE 100% OF CONTRIBUTIONS ARE SPENT THE WAY INTENDED **</p> <br />
<br />
<br />
<p>Proof of Work has been replaced with Proof Of Biblehash (POBh) - an algorithm that compensates full nodes participation, while preventing GPUs and ASIC by requiring full blockchain transaction referencing in the hashing function, along with chained bible verses. This means biblepay subsidizes full nodes that stay online.</p><br />
<br />
<p>Seven minute block targets minimize the blockchain file size, yet BiblePay does support Dash's instantsend for speedy transactions. MasterNodes (called Sanctuaries) will come online after Christmas, allowing all expenses to be voted on and approved.</p><br />
<p>Expense receipts, to prove the sponshorship of new orphans, will be accessible from inside the wallet and we will even provide phone numbers for auditors to prove </p><br />
100% charity expenditures. (From the rpc, type &#39;run contribution&#39; to see the tithes into the foundation for a time period, and to see the outgoing sponsorship click the wallets &#39;Accountability&#39; button to see a list of orphans, expenses, sponsorship dates, amounts, and the charity phone number, and txid).<br />
<br />
<p>For the first 6 months, 10% of each block will be allocated to the foundation, for sponsoring orphans at 100%. Once per month, we will cash in anything over $40 available on an exchange, and sponsor orphans on our volunteer time. After the sanctuaries go live, the 10% tithe will be diverted to an ongoing budget with DAO governance, voting, allowing the coin to function as a dectralized autonomous charity; at that point the lead dev and volunteers will become a normal part of the community allowing the coin to run by itself.</p><br />
<br />
<p>To avoid wasting energy on meaningless SHA hashing, (or mining), biblepay introduces the BibleHash algorithm, that allows biblepay to <br />
run on common commodity PCs, since the algorithm is resistant to porting to video cards and ASICs and is resistant to running in non-full node environments.</p><br />
<p>In addition to the low energy requirements and high efficiency of POB, the reward per block is set to be relative to the length of time the block took to solve, <br />
(meaning that abusive hash attacks result in subsidy decreases).</p><br />
<p>The network will be high efficiency with low total energy consumption, and the charities sponsored must also be high efficiency (over 75%).<br />
Next, we are deflationary, meaning that we start by issuing a larger amount of coins per block, and each year we tighten the supply by 18%.</p><br />
<br />
The schedule is here: (205 blocks per day, 7 minute block targets):<br />
EMISSION SCHEDULE PROJECTION: http://wiki.biblepay.org/Emission_Schedule<br />
<br />
<p>The block reward breakdown is as follows:</p><br />
<br />
ECONOMICS: http://wiki.biblepay.org/Economics<br />
<br />
<br />
<p>After our sanctuaries go live, we allocate 10% of each block subsidy to our governance committe (a DAO), automatically, with 100% of that being<br />
spent on charity. <br />
<br />
Over time, our sanctuaries will become a charity governance committee, to allow our community to take over the day to day operations of the charity: voting on where the money is spent, how much is spent.<br />
This way, we will not be centralized.</p><br />
<br />
<p>We only partner with charities over 75% efficient, meaning over 75% reach the end-user.</p><br />
<br />
<br />
<p>'''<span style="color:#ff0000">NO PREMINE:</span>'''</p><br />
<p>the lead dev starts with zero, the orphan foundation fund starts with zero, the distribution is entirely fair. NO ICO. The distribution curve is evenly declining with no hidden bumps early.<br />
The self-governance committee and masternode payments are deliberately delayed until Christmas, to allow people to prepare and save up the initial requirement. Running a sanctuary is open to anyone.<br />
The lead dev will sponsor the first 10 orphans out of his own pocket.</p><br />
<p>'''<span style="color:#ff0000">Accountability:</span></p><br />
<p>The wallet will have a reconciliation page built in at go live, to show all charitable income and expenses.</p><br />
<p>The expenses will be auditable - to prove the money actually was spent on orphans.</p><br />
<p>This will be accomplished through the use of : an RPC audit command that tallies the orphan income from the blockchain, and secondly, an API connection to a database that stores the Compassion expenses (until sanctuaries go live), with auditable backing contact info for each expense. We will also provide a web page with pictures of the sponsored orphans clicable from the wallet to show our investors what good we are doing. And finally- we will maintain a copy of receipts in order to maintain 100% accountability.</p><br />
<p>Future Feature: Pay to Preach, in wallet ineractive prayer rooms.</p><br />
<br />
'''ROADMAP:'''<br />
JULY-DECEMBER 2017: GO LIVE, SPONSOR ORPHANS MONTHLY<br />
<br />
JANUARY 2018: MASTERNODES (SANCTUARIES) GO LIVE<br />
<br />
FEBRUARY 2018: MARKETING, IN WALLET PRAYERS<br />
<br />
MAY 2018: MARKET BIBLEPAY AS A 401K ALTERNATIVE<br />
<br />
[[:Category:Roadmap|More roadmap details]]<br />
<br />
'''Novel distinct features of BiblePay:'''<br />
<br />
<p>Proof of Bible Hash algorithm (POBh), getblockinfo shows the chained bible verses required to solve the block, sending money exposes a Tithe checkbox - allowing 10% to be gifted to the orphan foundation, wallet has an in-wallet prayer system, allowing a user to send out a prayer request to the network or store prayers in the chain for the community to pray for from the overview page, Transactions support in-chain messages, Instant Send, Voting, Decentralized Automated Charity Governance Committee, Repentance of Sins, Contributing to the orphan foundation checkbox, and reading the sin list and various staple prayers in wallet.</p><br />
<br />
{{Special:PrefixIndex/Category:}}</div>Sunk818https://wiki.biblepay.org/index.php?title=Main_Page&diff=6123Main Page2019-02-26T17:13:31Z<p>Sunk818: </p>
<hr />
<div>{| class="wikitable" style="text-align:center; margin-left:2em"<br />
|| BIBLEPAY || 10% Charity, Masternodes (Sanctuaries), ASIC-Resistant, CPU-Mining, 10% to Orphans<br />
|-<br />
|| Mint || Decentralized Proof Of Work<br />
|-<br />
|| Launch Date || August 2017<br />
|-<br />
|| Developed by || Robert Andrews<br />
|-<br />
|| Ticker || BBP<br />
|-<br />
|| Plural || Biblepays<br />
|-<br />
|| Subunit || mBBP =0.001<br />
|-<br />
|| Lowest Unit || 0.00000001 = 1 BBP<br />
|-<br />
|| Operating System || Windows, Linux, macOS<br />
|-<br />
|| Algorithm || Proof-of-BibleHash<br />
|-<br />
|| Current Version || Client v1.0.2.9 mandatory<br />
|-<br />
|| Release Date || July 23rd, 2017<br />
|-<br />
|| Blocktime || avg 7 Minutes<br />
|-<br />
|| Reward || 20,000 Decreasing by 1.5% per month (Approx 19% per year)<br />
|}<br />
<br />
<br />
<p>'''NAME:''' BIBLEPAY</p><br />
<br />
<br />
<p>'''LAUNCH DATE:''' JULY 23, 2017 at 17:00:00 CST</p><br />
<br />
<p>'''BLOCK TARGET RATE:''' 7 MINUTES</p><br />
<br />
<p>'''ALGORITHM:''' PROOF OF BIBLEHASH (POBh) ** NEW **</p><br />
<br />
<p>First coin with the KJV Bible compiled in the source, and utilizing the Bible in the hashing algorithm, while spreading the gospel throughout the IT community. The blocks also hash to chained bible verses.</p><br />
<br />
<p>'''TRANSACTION SPEED:''' SUPPORTS INSTANTSEND</p><br />
<p>'''MASTERNODE(SANCTUARY) SUPPORT:''' Supported after Christmas 2017</p><br />
<p>'''SANCTUARY SUBSIDY BREAKDOWN:''' 10% TO CHARITY, 10% TO MASTERNODES, 80% TO MINER</p><br />
<p>'''FORUM:''' [http://bitcointalk.org/topic=2042657 Bitcointalk]</p><br />
<p>'''Backup Forum:'''[http://forum.biblepay.org/ forum.biblepay.org]</p><br />
<p>'''BLOCK EXPLORER:'''[https://biblepay-explorer.org/ biblepay-explorer.org]</p><br />
<p>'''BLOCK EXPLORER:'''[http://explorer.biblepay.org:3001/ explorer.biblepay.org]</p><br />
<p>'''SOURCE CODE:'''[http://github.com/biblepay/biblepay Github]</p><br />
<p>'''WEB SITE:'''[http://biblepay.org biblepay.org]</p><br />
<p>'''EXCHANGES:'''[https://c-cex.com/?p=bbp-btc c-cex]</p><br />
<p>'''[https://www.southxchange.com/Market/Book/BBP/BTC]</p><br />
<br />
<p>'''TICKER:''' BBP</p><br />
<p>'''Exchange Go Live Date:''' August 15th 2017</p><br />
<p>'''PREMINE:''' NONE</p><br />
<p>'''ICO:''' NONE</p><br />
<p>'''INCONSISTENT REWARDS:''' NONE</p><br />
<p>'''CIRCULATION CHARACTERISTIC:''' DEFLATIONARY</p><br />
<p>'''CIRCULATION RATE:''' DECREASE BY 10% PER YEAR</p><br />
<p>'''TOTAL CIRCULATION:''' 5.2 BILLION BY 2050, DECREASING BY 18% PER YEAR</p><br />
<br />
<p>'''DESCRIPTION:'''</p><br />
<p>A secure blockchain benefiting those in distress - 10% of the emission goes to sponsoring Orphans, with provable contributions, expenses contributed to [http://compassion.com http://compassion.com] - and future charities that are more than 75% efficient. ** NOTE: THE COIN HAS RPC COMMANDS THAT PROVE 100% OF CONTRIBUTIONS ARE SPENT THE WAY INTENDED **</p> <br />
<br />
<br />
<p>Proof of Work has been replaced with Proof Of Biblehash (POBh) - an algorithm that compensates full nodes participation, while preventing GPUs and ASIC by requiring full blockchain transaction referencing in the hashing function, along with chained bible verses. This means biblepay subsidizes full nodes that stay online.</p><br />
<br />
<p>Seven minute block targets minimize the blockchain file size, yet BiblePay does support Dash's instantsend for speedy transactions. MasterNodes (called Sanctuaries) will come online after Christmas, allowing all expenses to be voted on and approved.</p><br />
<p>Expense receipts, to prove the sponshorship of new orphans, will be accessible from inside the wallet and we will even provide phone numbers for auditors to prove </p><br />
100% charity expenditures. (From the rpc, type &#39;run contribution&#39; to see the tithes into the foundation for a time period, and to see the outgoing sponsorship click the wallets &#39;Accountability&#39; button to see a list of orphans, expenses, sponsorship dates, amounts, and the charity phone number, and txid).<br />
<br />
<p>For the first 6 months, 10% of each block will be allocated to the foundation, for sponsoring orphans at 100%. Once per month, we will cash in anything over $40 available on an exchange, and sponsor orphans on our volunteer time. After the sanctuaries go live, the 10% tithe will be diverted to an ongoing budget with DAO governance, voting, allowing the coin to function as a dectralized autonomous charity; at that point the lead dev and volunteers will become a normal part of the community allowing the coin to run by itself.</p><br />
<br />
<p>To avoid wasting energy on meaningless SHA hashing, (or mining), biblepay introduces the BibleHash algorithm, that allows biblepay to <br />
run on common commodity PCs, since the algorithm is resistant to porting to video cards and ASICs and is resistant to running in non-full node environments.</p><br />
<p>In addition to the low energy requirements and high efficiency of POB, the reward per block is set to be relative to the length of time the block took to solve, <br />
(meaning that abusive hash attacks result in subsidy decreases).</p><br />
<p>The network will be high efficiency with low total energy consumption, and the charities sponsored must also be high efficiency (over 75%).<br />
Next, we are deflationary, meaning that we start by issuing a larger amount of coins per block, and each year we tighten the supply by 18%.</p><br />
<br />
The schedule is here: (205 blocks per day, 7 minute block targets):<br />
EMISSION SCHEDULE PROJECTION: http://wiki.biblepay.org/Emission_Schedule<br />
<br />
<p>The block reward breakdown is as follows:</p><br />
<br />
ECONOMICS: http://wiki.biblepay.org/Economics<br />
<br />
<br />
<p>After our sanctuaries go live, we allocate 10% of each block subsidy to our governance committe (a DAO), automatically, with 100% of that being<br />
spent on charity. <br />
<br />
Over time, our sanctuaries will become a charity governance committee, to allow our community to take over the day to day operations of the charity: voting on where the money is spent, how much is spent.<br />
This way, we will not be centralized.</p><br />
<br />
<p>We only partner with charities over 75% efficient, meaning over 75% reach the end-user.</p><br />
<br />
<br />
<p>'''<span style="color:#ff0000">NO PREMINE:</span>'''</p><br />
<p>the lead dev starts with zero, the orphan foundation fund starts with zero, the distribution is entirely fair. NO ICO. The distribution curve is evenly declining with no hidden bumps early.<br />
The self-governance committee and masternode payments are deliberately delayed until Christmas, to allow people to prepare and save up the initial requirement. Running a sanctuary is open to anyone.<br />
The lead dev will sponsor the first 10 orphans out of his own pocket.</p><br />
<p>'''<span style="color:#ff0000">Accountability:</span></p><br />
<p>The wallet will have a reconciliation page built in at go live, to show all charitable income and expenses.</p><br />
<p>The expenses will be auditable - to prove the money actually was spent on orphans.</p><br />
<p>This will be accomplished through the use of : an RPC audit command that tallies the orphan income from the blockchain, and secondly, an API connection to a database that stores the Compassion expenses (until sanctuaries go live), with auditable backing contact info for each expense. We will also provide a web page with pictures of the sponsored orphans clicable from the wallet to show our investors what good we are doing. And finally- we will maintain a copy of receipts in order to maintain 100% accountability.</p><br />
<p>Future Feature: Pay to Preach, in wallet ineractive prayer rooms.</p><br />
<br />
'''ROADMAP:'''<br />
JULY-DECEMBER 2017: GO LIVE, SPONSOR ORPHANS MONTHLY<br />
<br />
JANUARY 2018: MASTERNODES (SANCTUARIES) GO LIVE<br />
<br />
FEBRUARY 2018: MARKETING, IN WALLET PRAYERS<br />
<br />
MAY 2018: MARKET BIBLEPAY AS A 401K ALTERNATIVE<br />
<br />
[[:Category:Roadmap|More roadmap details]]<br />
<br />
'''Novel distinct features of BiblePay:'''<br />
<br />
<p>Proof of Bible Hash algorithm (POBh), getblockinfo shows the chained bible verses required to solve the block, sending money exposes a Tithe checkbox - allowing 10% to be gifted to the orphan foundation, wallet has an in-wallet prayer system, allowing a user to send out a prayer request to the network or store prayers in the chain for the community to pray for from the overview page, Transactions support in-chain messages, Instant Send, Voting, Decentralized Automated Charity Governance Committee, Repentance of Sins, Contributing to the orphan foundation checkbox, and reading the sin list and various staple prayers in wallet.</p><br />
<br />
{{special:AllCategories}}</div>Sunk818https://wiki.biblepay.org/index.php?title=Main_Page&diff=6122Main Page2019-02-26T17:13:18Z<p>Sunk818: </p>
<hr />
<div>{| class="wikitable" style="text-align:center; margin-left:2em"<br />
|| BIBLEPAY || 10% Charity, Masternodes (Sanctuaries), ASIC-Resistant, CPU-Mining, 10% to Orphans<br />
|-<br />
|| Mint || Decentralized Proof Of Work<br />
|-<br />
|| Launch Date || August 2017<br />
|-<br />
|| Developed by || Robert Andrews<br />
|-<br />
|| Ticker || BBP<br />
|-<br />
|| Plural || Biblepays<br />
|-<br />
|| Subunit || mBBP =0.001<br />
|-<br />
|| Lowest Unit || 0.00000001 = 1 BBP<br />
|-<br />
|| Operating System || Windows, Linux, macOS<br />
|-<br />
|| Algorithm || Proof-of-BibleHash<br />
|-<br />
|| Current Version || Client v1.0.2.9 mandatory<br />
|-<br />
|| Release Date || July 23rd, 2017<br />
|-<br />
|| Blocktime || avg 7 Minutes<br />
|-<br />
|| Reward || 20,000 Decreasing by 1.5% per month (Approx 19% per year)<br />
|}<br />
<br />
<br />
<p>'''NAME:''' BIBLEPAY</p><br />
<br />
<br />
<p>'''LAUNCH DATE:''' JULY 23, 2017 at 17:00:00 CST</p><br />
<br />
<p>'''BLOCK TARGET RATE:''' 7 MINUTES</p><br />
<br />
<p>'''ALGORITHM:''' PROOF OF BIBLEHASH (POBh) ** NEW **</p><br />
<br />
<p>First coin with the KJV Bible compiled in the source, and utilizing the Bible in the hashing algorithm, while spreading the gospel throughout the IT community. The blocks also hash to chained bible verses.</p><br />
<br />
<p>'''TRANSACTION SPEED:''' SUPPORTS INSTANTSEND</p><br />
<p>'''MASTERNODE(SANCTUARY) SUPPORT:''' Supported after Christmas 2017</p><br />
<p>'''SANCTUARY SUBSIDY BREAKDOWN:''' 10% TO CHARITY, 10% TO MASTERNODES, 80% TO MINER</p><br />
<p>'''FORUM:''' [http://bitcointalk.org/topic=2042657 Bitcointalk]</p><br />
<p>'''Backup Forum:'''[http://forum.biblepay.org/ forum.biblepay.org]</p><br />
<p>'''BLOCK EXPLORER:'''[https://biblepay-explorer.org/ biblepay-explorer.org]</p><br />
<p>'''BLOCK EXPLORER:'''[http://explorer.biblepay.org:3001/ explorer.biblepay.org]</p><br />
<p>'''SOURCE CODE:'''[http://github.com/biblepay/biblepay Github]</p><br />
<p>'''WEB SITE:'''[http://biblepay.org biblepay.org]</p><br />
<p>'''EXCHANGES:'''[https://c-cex.com/?p=bbp-btc c-cex]</p><br />
<p>'''[https://www.southxchange.com/Market/Book/BBP/BTC]</p><br />
<br />
<p>'''TICKER:''' BBP</p><br />
<p>'''Exchange Go Live Date:''' August 15th 2017</p><br />
<p>'''PREMINE:''' NONE</p><br />
<p>'''ICO:''' NONE</p><br />
<p>'''INCONSISTENT REWARDS:''' NONE</p><br />
<p>'''CIRCULATION CHARACTERISTIC:''' DEFLATIONARY</p><br />
<p>'''CIRCULATION RATE:''' DECREASE BY 10% PER YEAR</p><br />
<p>'''TOTAL CIRCULATION:''' 5.2 BILLION BY 2050, DECREASING BY 18% PER YEAR</p><br />
<br />
<p>'''DESCRIPTION:'''</p><br />
<p>A secure blockchain benefiting those in distress - 10% of the emission goes to sponsoring Orphans, with provable contributions, expenses contributed to [http://compassion.com http://compassion.com] - and future charities that are more than 75% efficient. ** NOTE: THE COIN HAS RPC COMMANDS THAT PROVE 100% OF CONTRIBUTIONS ARE SPENT THE WAY INTENDED **</p> <br />
<br />
<br />
<p>Proof of Work has been replaced with Proof Of Biblehash (POBh) - an algorithm that compensates full nodes participation, while preventing GPUs and ASIC by requiring full blockchain transaction referencing in the hashing function, along with chained bible verses. This means biblepay subsidizes full nodes that stay online.</p><br />
<br />
<p>Seven minute block targets minimize the blockchain file size, yet BiblePay does support Dash's instantsend for speedy transactions. MasterNodes (called Sanctuaries) will come online after Christmas, allowing all expenses to be voted on and approved.</p><br />
<p>Expense receipts, to prove the sponshorship of new orphans, will be accessible from inside the wallet and we will even provide phone numbers for auditors to prove </p><br />
100% charity expenditures. (From the rpc, type &#39;run contribution&#39; to see the tithes into the foundation for a time period, and to see the outgoing sponsorship click the wallets &#39;Accountability&#39; button to see a list of orphans, expenses, sponsorship dates, amounts, and the charity phone number, and txid).<br />
<br />
<p>For the first 6 months, 10% of each block will be allocated to the foundation, for sponsoring orphans at 100%. Once per month, we will cash in anything over $40 available on an exchange, and sponsor orphans on our volunteer time. After the sanctuaries go live, the 10% tithe will be diverted to an ongoing budget with DAO governance, voting, allowing the coin to function as a dectralized autonomous charity; at that point the lead dev and volunteers will become a normal part of the community allowing the coin to run by itself.</p><br />
<br />
<p>To avoid wasting energy on meaningless SHA hashing, (or mining), biblepay introduces the BibleHash algorithm, that allows biblepay to <br />
run on common commodity PCs, since the algorithm is resistant to porting to video cards and ASICs and is resistant to running in non-full node environments.</p><br />
<p>In addition to the low energy requirements and high efficiency of POB, the reward per block is set to be relative to the length of time the block took to solve, <br />
(meaning that abusive hash attacks result in subsidy decreases).</p><br />
<p>The network will be high efficiency with low total energy consumption, and the charities sponsored must also be high efficiency (over 75%).<br />
Next, we are deflationary, meaning that we start by issuing a larger amount of coins per block, and each year we tighten the supply by 18%.</p><br />
<br />
The schedule is here: (205 blocks per day, 7 minute block targets):<br />
EMISSION SCHEDULE PROJECTION: http://wiki.biblepay.org/Emission_Schedule<br />
<br />
<p>The block reward breakdown is as follows:</p><br />
<br />
ECONOMICS: http://wiki.biblepay.org/Economics<br />
<br />
<br />
<p>After our sanctuaries go live, we allocate 10% of each block subsidy to our governance committe (a DAO), automatically, with 100% of that being<br />
spent on charity. <br />
<br />
Over time, our sanctuaries will become a charity governance committee, to allow our community to take over the day to day operations of the charity: voting on where the money is spent, how much is spent.<br />
This way, we will not be centralized.</p><br />
<br />
<p>We only partner with charities over 75% efficient, meaning over 75% reach the end-user.</p><br />
<br />
<br />
<p>'''<span style="color:#ff0000">NO PREMINE:</span>'''</p><br />
<p>the lead dev starts with zero, the orphan foundation fund starts with zero, the distribution is entirely fair. NO ICO. The distribution curve is evenly declining with no hidden bumps early.<br />
The self-governance committee and masternode payments are deliberately delayed until Christmas, to allow people to prepare and save up the initial requirement. Running a sanctuary is open to anyone.<br />
The lead dev will sponsor the first 10 orphans out of his own pocket.</p><br />
<p>'''<span style="color:#ff0000">Accountability:</span></p><br />
<p>The wallet will have a reconciliation page built in at go live, to show all charitable income and expenses.</p><br />
<p>The expenses will be auditable - to prove the money actually was spent on orphans.</p><br />
<p>This will be accomplished through the use of : an RPC audit command that tallies the orphan income from the blockchain, and secondly, an API connection to a database that stores the Compassion expenses (until sanctuaries go live), with auditable backing contact info for each expense. We will also provide a web page with pictures of the sponsored orphans clicable from the wallet to show our investors what good we are doing. And finally- we will maintain a copy of receipts in order to maintain 100% accountability.</p><br />
<p>Future Feature: Pay to Preach, in wallet ineractive prayer rooms.</p><br />
<br />
'''ROADMAP:'''<br />
JULY-DECEMBER 2017: GO LIVE, SPONSOR ORPHANS MONTHLY<br />
<br />
JANUARY 2018: MASTERNODES (SANCTUARIES) GO LIVE<br />
<br />
FEBRUARY 2018: MARKETING, IN WALLET PRAYERS<br />
<br />
MAY 2018: MARKET BIBLEPAY AS A 401K ALTERNATIVE<br />
<br />
[[:Category:Roadmap|More roadmap details]]<br />
<br />
'''Novel distinct features of BiblePay:'''<br />
<br />
<p>Proof of Bible Hash algorithm (POBh), getblockinfo shows the chained bible verses required to solve the block, sending money exposes a Tithe checkbox - allowing 10% to be gifted to the orphan foundation, wallet has an in-wallet prayer system, allowing a user to send out a prayer request to the network or store prayers in the chain for the community to pray for from the overview page, Transactions support in-chain messages, Instant Send, Voting, Decentralized Automated Charity Governance Committee, Repentance of Sins, Contributing to the orphan foundation checkbox, and reading the sin list and various staple prayers in wallet.</p><br />
<br />
{{special:AllCategories:}}</div>Sunk818https://wiki.biblepay.org/index.php?title=Main_Page&diff=6121Main Page2019-02-26T17:12:45Z<p>Sunk818: </p>
<hr />
<div>{| class="wikitable" style="text-align:center; margin-left:2em"<br />
|| BIBLEPAY || 10% Charity, Masternodes (Sanctuaries), ASIC-Resistant, CPU-Mining, 10% to Orphans<br />
|-<br />
|| Mint || Decentralized Proof Of Work<br />
|-<br />
|| Launch Date || August 2017<br />
|-<br />
|| Developed by || Robert Andrews<br />
|-<br />
|| Ticker || BBP<br />
|-<br />
|| Plural || Biblepays<br />
|-<br />
|| Subunit || mBBP =0.001<br />
|-<br />
|| Lowest Unit || 0.00000001 = 1 BBP<br />
|-<br />
|| Operating System || Windows, Linux, macOS<br />
|-<br />
|| Algorithm || Proof-of-BibleHash<br />
|-<br />
|| Current Version || Client v1.0.2.9 mandatory<br />
|-<br />
|| Release Date || July 23rd, 2017<br />
|-<br />
|| Blocktime || avg 7 Minutes<br />
|-<br />
|| Reward || 20,000 Decreasing by 1.5% per month (Approx 19% per year)<br />
|}<br />
<br />
<br />
<p>'''NAME:''' BIBLEPAY</p><br />
<br />
<br />
<p>'''LAUNCH DATE:''' JULY 23, 2017 at 17:00:00 CST</p><br />
<br />
<p>'''BLOCK TARGET RATE:''' 7 MINUTES</p><br />
<br />
<p>'''ALGORITHM:''' PROOF OF BIBLEHASH (POBh) ** NEW **</p><br />
<br />
<p>First coin with the KJV Bible compiled in the source, and utilizing the Bible in the hashing algorithm, while spreading the gospel throughout the IT community. The blocks also hash to chained bible verses.</p><br />
<br />
<p>'''TRANSACTION SPEED:''' SUPPORTS INSTANTSEND</p><br />
<p>'''MASTERNODE(SANCTUARY) SUPPORT:''' Supported after Christmas 2017</p><br />
<p>'''SANCTUARY SUBSIDY BREAKDOWN:''' 10% TO CHARITY, 10% TO MASTERNODES, 80% TO MINER</p><br />
<p>'''FORUM:''' [http://bitcointalk.org/topic=2042657 Bitcointalk]</p><br />
<p>'''Backup Forum:'''[http://forum.biblepay.org/ forum.biblepay.org]</p><br />
<p>'''BLOCK EXPLORER:'''[https://biblepay-explorer.org/ biblepay-explorer.org]</p><br />
<p>'''BLOCK EXPLORER:'''[http://explorer.biblepay.org:3001/ explorer.biblepay.org]</p><br />
<p>'''SOURCE CODE:'''[http://github.com/biblepay/biblepay Github]</p><br />
<p>'''WEB SITE:'''[http://biblepay.org biblepay.org]</p><br />
<p>'''EXCHANGES:'''[https://c-cex.com/?p=bbp-btc c-cex]</p><br />
<p>'''[https://www.southxchange.com/Market/Book/BBP/BTC]</p><br />
<br />
<p>'''TICKER:''' BBP</p><br />
<p>'''Exchange Go Live Date:''' August 15th 2017</p><br />
<p>'''PREMINE:''' NONE</p><br />
<p>'''ICO:''' NONE</p><br />
<p>'''INCONSISTENT REWARDS:''' NONE</p><br />
<p>'''CIRCULATION CHARACTERISTIC:''' DEFLATIONARY</p><br />
<p>'''CIRCULATION RATE:''' DECREASE BY 10% PER YEAR</p><br />
<p>'''TOTAL CIRCULATION:''' 5.2 BILLION BY 2050, DECREASING BY 18% PER YEAR</p><br />
<br />
<p>'''DESCRIPTION:'''</p><br />
<p>A secure blockchain benefiting those in distress - 10% of the emission goes to sponsoring Orphans, with provable contributions, expenses contributed to [http://compassion.com http://compassion.com] - and future charities that are more than 75% efficient. ** NOTE: THE COIN HAS RPC COMMANDS THAT PROVE 100% OF CONTRIBUTIONS ARE SPENT THE WAY INTENDED **</p> <br />
<br />
<br />
<p>Proof of Work has been replaced with Proof Of Biblehash (POBh) - an algorithm that compensates full nodes participation, while preventing GPUs and ASIC by requiring full blockchain transaction referencing in the hashing function, along with chained bible verses. This means biblepay subsidizes full nodes that stay online.</p><br />
<br />
<p>Seven minute block targets minimize the blockchain file size, yet BiblePay does support Dash's instantsend for speedy transactions. MasterNodes (called Sanctuaries) will come online after Christmas, allowing all expenses to be voted on and approved.</p><br />
<p>Expense receipts, to prove the sponshorship of new orphans, will be accessible from inside the wallet and we will even provide phone numbers for auditors to prove </p><br />
100% charity expenditures. (From the rpc, type &#39;run contribution&#39; to see the tithes into the foundation for a time period, and to see the outgoing sponsorship click the wallets &#39;Accountability&#39; button to see a list of orphans, expenses, sponsorship dates, amounts, and the charity phone number, and txid).<br />
<br />
<p>For the first 6 months, 10% of each block will be allocated to the foundation, for sponsoring orphans at 100%. Once per month, we will cash in anything over $40 available on an exchange, and sponsor orphans on our volunteer time. After the sanctuaries go live, the 10% tithe will be diverted to an ongoing budget with DAO governance, voting, allowing the coin to function as a dectralized autonomous charity; at that point the lead dev and volunteers will become a normal part of the community allowing the coin to run by itself.</p><br />
<br />
<p>To avoid wasting energy on meaningless SHA hashing, (or mining), biblepay introduces the BibleHash algorithm, that allows biblepay to <br />
run on common commodity PCs, since the algorithm is resistant to porting to video cards and ASICs and is resistant to running in non-full node environments.</p><br />
<p>In addition to the low energy requirements and high efficiency of POB, the reward per block is set to be relative to the length of time the block took to solve, <br />
(meaning that abusive hash attacks result in subsidy decreases).</p><br />
<p>The network will be high efficiency with low total energy consumption, and the charities sponsored must also be high efficiency (over 75%).<br />
Next, we are deflationary, meaning that we start by issuing a larger amount of coins per block, and each year we tighten the supply by 18%.</p><br />
<br />
The schedule is here: (205 blocks per day, 7 minute block targets):<br />
EMISSION SCHEDULE PROJECTION: http://wiki.biblepay.org/Emission_Schedule<br />
<br />
<p>The block reward breakdown is as follows:</p><br />
<br />
ECONOMICS: http://wiki.biblepay.org/Economics<br />
<br />
<br />
<p>After our sanctuaries go live, we allocate 10% of each block subsidy to our governance committe (a DAO), automatically, with 100% of that being<br />
spent on charity. <br />
<br />
Over time, our sanctuaries will become a charity governance committee, to allow our community to take over the day to day operations of the charity: voting on where the money is spent, how much is spent.<br />
This way, we will not be centralized.</p><br />
<br />
<p>We only partner with charities over 75% efficient, meaning over 75% reach the end-user.</p><br />
<br />
<br />
<p>'''<span style="color:#ff0000">NO PREMINE:</span>'''</p><br />
<p>the lead dev starts with zero, the orphan foundation fund starts with zero, the distribution is entirely fair. NO ICO. The distribution curve is evenly declining with no hidden bumps early.<br />
The self-governance committee and masternode payments are deliberately delayed until Christmas, to allow people to prepare and save up the initial requirement. Running a sanctuary is open to anyone.<br />
The lead dev will sponsor the first 10 orphans out of his own pocket.</p><br />
<p>'''<span style="color:#ff0000">Accountability:</span></p><br />
<p>The wallet will have a reconciliation page built in at go live, to show all charitable income and expenses.</p><br />
<p>The expenses will be auditable - to prove the money actually was spent on orphans.</p><br />
<p>This will be accomplished through the use of : an RPC audit command that tallies the orphan income from the blockchain, and secondly, an API connection to a database that stores the Compassion expenses (until sanctuaries go live), with auditable backing contact info for each expense. We will also provide a web page with pictures of the sponsored orphans clicable from the wallet to show our investors what good we are doing. And finally- we will maintain a copy of receipts in order to maintain 100% accountability.</p><br />
<p>Future Feature: Pay to Preach, in wallet ineractive prayer rooms.</p><br />
<br />
'''ROADMAP:'''<br />
JULY-DECEMBER 2017: GO LIVE, SPONSOR ORPHANS MONTHLY<br />
<br />
JANUARY 2018: MASTERNODES (SANCTUARIES) GO LIVE<br />
<br />
FEBRUARY 2018: MARKETING, IN WALLET PRAYERS<br />
<br />
MAY 2018: MARKET BIBLEPAY AS A 401K ALTERNATIVE<br />
<br />
[[:Category:Roadmap|More roadmap details]]<br />
<br />
'''Novel distinct features of BiblePay:'''<br />
<br />
<p>Proof of Bible Hash algorithm (POBh), getblockinfo shows the chained bible verses required to solve the block, sending money exposes a Tithe checkbox - allowing 10% to be gifted to the orphan foundation, wallet has an in-wallet prayer system, allowing a user to send out a prayer request to the network or store prayers in the chain for the community to pray for from the overview page, Transactions support in-chain messages, Instant Send, Voting, Decentralized Automated Charity Governance Committee, Repentance of Sins, Contributing to the orphan foundation checkbox, and reading the sin list and various staple prayers in wallet.</p><br />
<br />
{{special:AllPages/Category:}}</div>Sunk818https://wiki.biblepay.org/index.php?title=Main_Page&diff=6120Main Page2019-02-26T17:09:43Z<p>Sunk818: </p>
<hr />
<div>{| class="wikitable" style="text-align:center; margin-left:2em"<br />
|| BIBLEPAY || 10% Charity, Masternodes (Sanctuaries), ASIC-Resistant, CPU-Mining, 10% to Orphans<br />
|-<br />
|| Mint || Decentralized Proof Of Work<br />
|-<br />
|| Launch Date || August 2017<br />
|-<br />
|| Developed by || Robert Andrews<br />
|-<br />
|| Ticker || BBP<br />
|-<br />
|| Plural || Biblepays<br />
|-<br />
|| Subunit || mBBP =0.001<br />
|-<br />
|| Lowest Unit || 0.00000001 = 1 BBP<br />
|-<br />
|| Operating System || Windows, Linux, macOS<br />
|-<br />
|| Algorithm || Proof-of-BibleHash<br />
|-<br />
|| Current Version || Client v1.0.2.9 mandatory<br />
|-<br />
|| Release Date || July 23rd, 2017<br />
|-<br />
|| Blocktime || avg 7 Minutes<br />
|-<br />
|| Reward || 20,000 Decreasing by 1.5% per month (Approx 19% per year)<br />
|}<br />
<br />
<br />
<p>'''NAME:''' BIBLEPAY</p><br />
<br />
<br />
<p>'''LAUNCH DATE:''' JULY 23, 2017 at 17:00:00 CST</p><br />
<br />
<p>'''BLOCK TARGET RATE:''' 7 MINUTES</p><br />
<br />
<p>'''ALGORITHM:''' PROOF OF BIBLEHASH (POBh) ** NEW **</p><br />
<br />
<p>First coin with the KJV Bible compiled in the source, and utilizing the Bible in the hashing algorithm, while spreading the gospel throughout the IT community. The blocks also hash to chained bible verses.</p><br />
<br />
<p>'''TRANSACTION SPEED:''' SUPPORTS INSTANTSEND</p><br />
<p>'''MASTERNODE(SANCTUARY) SUPPORT:''' Supported after Christmas 2017</p><br />
<p>'''SANCTUARY SUBSIDY BREAKDOWN:''' 10% TO CHARITY, 10% TO MASTERNODES, 80% TO MINER</p><br />
<p>'''FORUM:''' [http://bitcointalk.org/topic=2042657 Bitcointalk]</p><br />
<p>'''Backup Forum:'''[http://forum.biblepay.org/ forum.biblepay.org]</p><br />
<p>'''BLOCK EXPLORER:'''[https://biblepay-explorer.org/ biblepay-explorer.org]</p><br />
<p>'''BLOCK EXPLORER:'''[http://explorer.biblepay.org:3001/ explorer.biblepay.org]</p><br />
<p>'''SOURCE CODE:'''[http://github.com/biblepay/biblepay Github]</p><br />
<p>'''WEB SITE:'''[http://biblepay.org biblepay.org]</p><br />
<p>'''EXCHANGES:'''[https://c-cex.com/?p=bbp-btc c-cex]</p><br />
<p>'''[https://www.southxchange.com/Market/Book/BBP/BTC]</p><br />
<br />
<p>'''TICKER:''' BBP</p><br />
<p>'''Exchange Go Live Date:''' August 15th 2017</p><br />
<p>'''PREMINE:''' NONE</p><br />
<p>'''ICO:''' NONE</p><br />
<p>'''INCONSISTENT REWARDS:''' NONE</p><br />
<p>'''CIRCULATION CHARACTERISTIC:''' DEFLATIONARY</p><br />
<p>'''CIRCULATION RATE:''' DECREASE BY 10% PER YEAR</p><br />
<p>'''TOTAL CIRCULATION:''' 5.2 BILLION BY 2050, DECREASING BY 18% PER YEAR</p><br />
<br />
<p>'''DESCRIPTION:'''</p><br />
<p>A secure blockchain benefiting those in distress - 10% of the emission goes to sponsoring Orphans, with provable contributions, expenses contributed to [http://compassion.com http://compassion.com] - and future charities that are more than 75% efficient. ** NOTE: THE COIN HAS RPC COMMANDS THAT PROVE 100% OF CONTRIBUTIONS ARE SPENT THE WAY INTENDED **</p> <br />
<br />
<br />
<p>Proof of Work has been replaced with Proof Of Biblehash (POBh) - an algorithm that compensates full nodes participation, while preventing GPUs and ASIC by requiring full blockchain transaction referencing in the hashing function, along with chained bible verses. This means biblepay subsidizes full nodes that stay online.</p><br />
<br />
<p>Seven minute block targets minimize the blockchain file size, yet BiblePay does support Dash's instantsend for speedy transactions. MasterNodes (called Sanctuaries) will come online after Christmas, allowing all expenses to be voted on and approved.</p><br />
<p>Expense receipts, to prove the sponshorship of new orphans, will be accessible from inside the wallet and we will even provide phone numbers for auditors to prove </p><br />
100% charity expenditures. (From the rpc, type &#39;run contribution&#39; to see the tithes into the foundation for a time period, and to see the outgoing sponsorship click the wallets &#39;Accountability&#39; button to see a list of orphans, expenses, sponsorship dates, amounts, and the charity phone number, and txid).<br />
<br />
<p>For the first 6 months, 10% of each block will be allocated to the foundation, for sponsoring orphans at 100%. Once per month, we will cash in anything over $40 available on an exchange, and sponsor orphans on our volunteer time. After the sanctuaries go live, the 10% tithe will be diverted to an ongoing budget with DAO governance, voting, allowing the coin to function as a dectralized autonomous charity; at that point the lead dev and volunteers will become a normal part of the community allowing the coin to run by itself.</p><br />
<br />
<p>To avoid wasting energy on meaningless SHA hashing, (or mining), biblepay introduces the BibleHash algorithm, that allows biblepay to <br />
run on common commodity PCs, since the algorithm is resistant to porting to video cards and ASICs and is resistant to running in non-full node environments.</p><br />
<p>In addition to the low energy requirements and high efficiency of POB, the reward per block is set to be relative to the length of time the block took to solve, <br />
(meaning that abusive hash attacks result in subsidy decreases).</p><br />
<p>The network will be high efficiency with low total energy consumption, and the charities sponsored must also be high efficiency (over 75%).<br />
Next, we are deflationary, meaning that we start by issuing a larger amount of coins per block, and each year we tighten the supply by 18%.</p><br />
<br />
The schedule is here: (205 blocks per day, 7 minute block targets):<br />
EMISSION SCHEDULE PROJECTION: http://wiki.biblepay.org/Emission_Schedule<br />
<br />
<p>The block reward breakdown is as follows:</p><br />
<br />
ECONOMICS: http://wiki.biblepay.org/Economics<br />
<br />
<br />
<p>After our sanctuaries go live, we allocate 10% of each block subsidy to our governance committe (a DAO), automatically, with 100% of that being<br />
spent on charity. <br />
<br />
Over time, our sanctuaries will become a charity governance committee, to allow our community to take over the day to day operations of the charity: voting on where the money is spent, how much is spent.<br />
This way, we will not be centralized.</p><br />
<br />
<p>We only partner with charities over 75% efficient, meaning over 75% reach the end-user.</p><br />
<br />
<br />
<p>'''<span style="color:#ff0000">NO PREMINE:</span>'''</p><br />
<p>the lead dev starts with zero, the orphan foundation fund starts with zero, the distribution is entirely fair. NO ICO. The distribution curve is evenly declining with no hidden bumps early.<br />
The self-governance committee and masternode payments are deliberately delayed until Christmas, to allow people to prepare and save up the initial requirement. Running a sanctuary is open to anyone.<br />
The lead dev will sponsor the first 10 orphans out of his own pocket.</p><br />
<p>'''<span style="color:#ff0000">Accountability:</span></p><br />
<p>The wallet will have a reconciliation page built in at go live, to show all charitable income and expenses.</p><br />
<p>The expenses will be auditable - to prove the money actually was spent on orphans.</p><br />
<p>This will be accomplished through the use of : an RPC audit command that tallies the orphan income from the blockchain, and secondly, an API connection to a database that stores the Compassion expenses (until sanctuaries go live), with auditable backing contact info for each expense. We will also provide a web page with pictures of the sponsored orphans clicable from the wallet to show our investors what good we are doing. And finally- we will maintain a copy of receipts in order to maintain 100% accountability.</p><br />
<p>Future Feature: Pay to Preach, in wallet ineractive prayer rooms.</p><br />
<br />
'''ROADMAP:'''<br />
JULY-DECEMBER 2017: GO LIVE, SPONSOR ORPHANS MONTHLY<br />
<br />
JANUARY 2018: MASTERNODES (SANCTUARIES) GO LIVE<br />
<br />
FEBRUARY 2018: MARKETING, IN WALLET PRAYERS<br />
<br />
MAY 2018: MARKET BIBLEPAY AS A 401K ALTERNATIVE<br />
<br />
[[:Category:Roadmap|More roadmap details]]<br />
<br />
'''Novel distinct features of BiblePay:'''<br />
<br />
<p>Proof of Bible Hash algorithm (POBh), getblockinfo shows the chained bible verses required to solve the block, sending money exposes a Tithe checkbox - allowing 10% to be gifted to the orphan foundation, wallet has an in-wallet prayer system, allowing a user to send out a prayer request to the network or store prayers in the chain for the community to pray for from the overview page, Transactions support in-chain messages, Instant Send, Voting, Decentralized Automated Charity Governance Committee, Repentance of Sins, Contributing to the orphan foundation checkbox, and reading the sin list and various staple prayers in wallet.</p><br />
<br />
{{PAGESINCATEGORY:{{titleparts:{{PAGENAME}}}}}}</div>Sunk818https://wiki.biblepay.org/index.php?title=Main_Page&diff=6119Main Page2019-02-26T17:05:15Z<p>Sunk818: </p>
<hr />
<div>{| class="wikitable" style="text-align:center; margin-left:2em"<br />
|| BIBLEPAY || 10% Charity, Masternodes (Sanctuaries), ASIC-Resistant, CPU-Mining, 10% to Orphans<br />
|-<br />
|| Mint || Decentralized Proof Of Work<br />
|-<br />
|| Launch Date || August 2017<br />
|-<br />
|| Developed by || Robert Andrews<br />
|-<br />
|| Ticker || BBP<br />
|-<br />
|| Plural || Biblepays<br />
|-<br />
|| Subunit || mBBP =0.001<br />
|-<br />
|| Lowest Unit || 0.00000001 = 1 BBP<br />
|-<br />
|| Operating System || Windows, Linux, macOS<br />
|-<br />
|| Algorithm || Proof-of-BibleHash<br />
|-<br />
|| Current Version || Client v1.0.2.9 mandatory<br />
|-<br />
|| Release Date || July 23rd, 2017<br />
|-<br />
|| Blocktime || avg 7 Minutes<br />
|-<br />
|| Reward || 20,000 Decreasing by 1.5% per month (Approx 19% per year)<br />
|}<br />
<br />
<br />
<p>'''NAME:''' BIBLEPAY</p><br />
<br />
<br />
<p>'''LAUNCH DATE:''' JULY 23, 2017 at 17:00:00 CST</p><br />
<br />
<p>'''BLOCK TARGET RATE:''' 7 MINUTES</p><br />
<br />
<p>'''ALGORITHM:''' PROOF OF BIBLEHASH (POBh) ** NEW **</p><br />
<br />
<p>First coin with the KJV Bible compiled in the source, and utilizing the Bible in the hashing algorithm, while spreading the gospel throughout the IT community. The blocks also hash to chained bible verses.</p><br />
<br />
<p>'''TRANSACTION SPEED:''' SUPPORTS INSTANTSEND</p><br />
<p>'''MASTERNODE(SANCTUARY) SUPPORT:''' Supported after Christmas 2017</p><br />
<p>'''SANCTUARY SUBSIDY BREAKDOWN:''' 10% TO CHARITY, 10% TO MASTERNODES, 80% TO MINER</p><br />
<p>'''FORUM:''' [http://bitcointalk.org/topic=2042657 Bitcointalk]</p><br />
<p>'''Backup Forum:'''[http://forum.biblepay.org/ forum.biblepay.org]</p><br />
<p>'''BLOCK EXPLORER:'''[https://biblepay-explorer.org/ biblepay-explorer.org]</p><br />
<p>'''BLOCK EXPLORER:'''[http://explorer.biblepay.org:3001/ explorer.biblepay.org]</p><br />
<p>'''SOURCE CODE:'''[http://github.com/biblepay/biblepay Github]</p><br />
<p>'''WEB SITE:'''[http://biblepay.org biblepay.org]</p><br />
<p>'''EXCHANGES:'''[https://c-cex.com/?p=bbp-btc c-cex]</p><br />
<p>'''[https://www.southxchange.com/Market/Book/BBP/BTC]</p><br />
<br />
<p>'''TICKER:''' BBP</p><br />
<p>'''Exchange Go Live Date:''' August 15th 2017</p><br />
<p>'''PREMINE:''' NONE</p><br />
<p>'''ICO:''' NONE</p><br />
<p>'''INCONSISTENT REWARDS:''' NONE</p><br />
<p>'''CIRCULATION CHARACTERISTIC:''' DEFLATIONARY</p><br />
<p>'''CIRCULATION RATE:''' DECREASE BY 10% PER YEAR</p><br />
<p>'''TOTAL CIRCULATION:''' 5.2 BILLION BY 2050, DECREASING BY 18% PER YEAR</p><br />
<br />
<p>'''DESCRIPTION:'''</p><br />
<p>A secure blockchain benefiting those in distress - 10% of the emission goes to sponsoring Orphans, with provable contributions, expenses contributed to [http://compassion.com http://compassion.com] - and future charities that are more than 75% efficient. ** NOTE: THE COIN HAS RPC COMMANDS THAT PROVE 100% OF CONTRIBUTIONS ARE SPENT THE WAY INTENDED **</p> <br />
<br />
<br />
<p>Proof of Work has been replaced with Proof Of Biblehash (POBh) - an algorithm that compensates full nodes participation, while preventing GPUs and ASIC by requiring full blockchain transaction referencing in the hashing function, along with chained bible verses. This means biblepay subsidizes full nodes that stay online.</p><br />
<br />
<p>Seven minute block targets minimize the blockchain file size, yet BiblePay does support Dash's instantsend for speedy transactions. MasterNodes (called Sanctuaries) will come online after Christmas, allowing all expenses to be voted on and approved.</p><br />
<p>Expense receipts, to prove the sponshorship of new orphans, will be accessible from inside the wallet and we will even provide phone numbers for auditors to prove </p><br />
100% charity expenditures. (From the rpc, type &#39;run contribution&#39; to see the tithes into the foundation for a time period, and to see the outgoing sponsorship click the wallets &#39;Accountability&#39; button to see a list of orphans, expenses, sponsorship dates, amounts, and the charity phone number, and txid).<br />
<br />
<p>For the first 6 months, 10% of each block will be allocated to the foundation, for sponsoring orphans at 100%. Once per month, we will cash in anything over $40 available on an exchange, and sponsor orphans on our volunteer time. After the sanctuaries go live, the 10% tithe will be diverted to an ongoing budget with DAO governance, voting, allowing the coin to function as a dectralized autonomous charity; at that point the lead dev and volunteers will become a normal part of the community allowing the coin to run by itself.</p><br />
<br />
<p>To avoid wasting energy on meaningless SHA hashing, (or mining), biblepay introduces the BibleHash algorithm, that allows biblepay to <br />
run on common commodity PCs, since the algorithm is resistant to porting to video cards and ASICs and is resistant to running in non-full node environments.</p><br />
<p>In addition to the low energy requirements and high efficiency of POB, the reward per block is set to be relative to the length of time the block took to solve, <br />
(meaning that abusive hash attacks result in subsidy decreases).</p><br />
<p>The network will be high efficiency with low total energy consumption, and the charities sponsored must also be high efficiency (over 75%).<br />
Next, we are deflationary, meaning that we start by issuing a larger amount of coins per block, and each year we tighten the supply by 18%.</p><br />
<br />
The schedule is here: (205 blocks per day, 7 minute block targets):<br />
EMISSION SCHEDULE PROJECTION: http://wiki.biblepay.org/Emission_Schedule<br />
<br />
<p>The block reward breakdown is as follows:</p><br />
<br />
ECONOMICS: http://wiki.biblepay.org/Economics<br />
<br />
<br />
<p>After our sanctuaries go live, we allocate 10% of each block subsidy to our governance committe (a DAO), automatically, with 100% of that being<br />
spent on charity. <br />
<br />
Over time, our sanctuaries will become a charity governance committee, to allow our community to take over the day to day operations of the charity: voting on where the money is spent, how much is spent.<br />
This way, we will not be centralized.</p><br />
<br />
<p>We only partner with charities over 75% efficient, meaning over 75% reach the end-user.</p><br />
<br />
<br />
<p>'''<span style="color:#ff0000">NO PREMINE:</span>'''</p><br />
<p>the lead dev starts with zero, the orphan foundation fund starts with zero, the distribution is entirely fair. NO ICO. The distribution curve is evenly declining with no hidden bumps early.<br />
The self-governance committee and masternode payments are deliberately delayed until Christmas, to allow people to prepare and save up the initial requirement. Running a sanctuary is open to anyone.<br />
The lead dev will sponsor the first 10 orphans out of his own pocket.</p><br />
<p>'''<span style="color:#ff0000">Accountability:</span></p><br />
<p>The wallet will have a reconciliation page built in at go live, to show all charitable income and expenses.</p><br />
<p>The expenses will be auditable - to prove the money actually was spent on orphans.</p><br />
<p>This will be accomplished through the use of : an RPC audit command that tallies the orphan income from the blockchain, and secondly, an API connection to a database that stores the Compassion expenses (until sanctuaries go live), with auditable backing contact info for each expense. We will also provide a web page with pictures of the sponsored orphans clicable from the wallet to show our investors what good we are doing. And finally- we will maintain a copy of receipts in order to maintain 100% accountability.</p><br />
<p>Future Feature: Pay to Preach, in wallet ineractive prayer rooms.</p><br />
<br />
'''ROADMAP:'''<br />
JULY-DECEMBER 2017: GO LIVE, SPONSOR ORPHANS MONTHLY<br />
<br />
JANUARY 2018: MASTERNODES (SANCTUARIES) GO LIVE<br />
<br />
FEBRUARY 2018: MARKETING, IN WALLET PRAYERS<br />
<br />
MAY 2018: MARKET BIBLEPAY AS A 401K ALTERNATIVE<br />
<br />
[[:Category:Roadmap|More roadmap details]]<br />
<br />
'''Novel distinct features of BiblePay:'''<br />
<br />
<p>Proof of Bible Hash algorithm (POBh), getblockinfo shows the chained bible verses required to solve the block, sending money exposes a Tithe checkbox - allowing 10% to be gifted to the orphan foundation, wallet has an in-wallet prayer system, allowing a user to send out a prayer request to the network or store prayers in the chain for the community to pray for from the overview page, Transactions support in-chain messages, Instant Send, Voting, Decentralized Automated Charity Governance Committee, Repentance of Sins, Contributing to the orphan foundation checkbox, and reading the sin list and various staple prayers in wallet.</p><br />
<br />
<categorytree style="column-count:3;-moz-column-count:3;-webkit-column-count:3">Extensions by category</categorytree></div>Sunk818https://wiki.biblepay.org/index.php?title=Main_Page&diff=6118Main Page2019-02-26T16:59:45Z<p>Sunk818: </p>
<hr />
<div>{| class="wikitable" style="text-align:center; margin-left:2em"<br />
|| BIBLEPAY || 10% Charity, Masternodes (Sanctuaries), ASIC-Resistant, CPU-Mining, 10% to Orphans<br />
|-<br />
|| Mint || Decentralized Proof Of Work<br />
|-<br />
|| Launch Date || August 2017<br />
|-<br />
|| Developed by || Robert Andrews<br />
|-<br />
|| Ticker || BBP<br />
|-<br />
|| Plural || Biblepays<br />
|-<br />
|| Subunit || mBBP =0.001<br />
|-<br />
|| Lowest Unit || 0.00000001 = 1 BBP<br />
|-<br />
|| Operating System || Windows, Linux, macOS<br />
|-<br />
|| Algorithm || Proof-of-BibleHash<br />
|-<br />
|| Current Version || Client v1.0.2.9 mandatory<br />
|-<br />
|| Release Date || July 23rd, 2017<br />
|-<br />
|| Blocktime || avg 7 Minutes<br />
|-<br />
|| Reward || 20,000 Decreasing by 1.5% per month (Approx 19% per year)<br />
|}<br />
<br />
<br />
<p>'''NAME:''' BIBLEPAY</p><br />
<br />
<br />
<p>'''LAUNCH DATE:''' JULY 23, 2017 at 17:00:00 CST</p><br />
<br />
<p>'''BLOCK TARGET RATE:''' 7 MINUTES</p><br />
<br />
<p>'''ALGORITHM:''' PROOF OF BIBLEHASH (POBh) ** NEW **</p><br />
<br />
<p>First coin with the KJV Bible compiled in the source, and utilizing the Bible in the hashing algorithm, while spreading the gospel throughout the IT community. The blocks also hash to chained bible verses.</p><br />
<br />
<p>'''TRANSACTION SPEED:''' SUPPORTS INSTANTSEND</p><br />
<p>'''MASTERNODE(SANCTUARY) SUPPORT:''' Supported after Christmas 2017</p><br />
<p>'''SANCTUARY SUBSIDY BREAKDOWN:''' 10% TO CHARITY, 10% TO MASTERNODES, 80% TO MINER</p><br />
<p>'''FORUM:''' [http://bitcointalk.org/topic=2042657 Bitcointalk]</p><br />
<p>'''Backup Forum:'''[http://forum.biblepay.org/ forum.biblepay.org]</p><br />
<p>'''BLOCK EXPLORER:'''[https://biblepay-explorer.org/ biblepay-explorer.org]</p><br />
<p>'''BLOCK EXPLORER:'''[http://explorer.biblepay.org:3001/ explorer.biblepay.org]</p><br />
<p>'''SOURCE CODE:'''[http://github.com/biblepay/biblepay Github]</p><br />
<p>'''WEB SITE:'''[http://biblepay.org biblepay.org]</p><br />
<p>'''EXCHANGES:'''[https://c-cex.com/?p=bbp-btc c-cex]</p><br />
<p>'''[https://www.southxchange.com/Market/Book/BBP/BTC]</p><br />
<br />
<p>'''TICKER:''' BBP</p><br />
<p>'''Exchange Go Live Date:''' August 15th 2017</p><br />
<p>'''PREMINE:''' NONE</p><br />
<p>'''ICO:''' NONE</p><br />
<p>'''INCONSISTENT REWARDS:''' NONE</p><br />
<p>'''CIRCULATION CHARACTERISTIC:''' DEFLATIONARY</p><br />
<p>'''CIRCULATION RATE:''' DECREASE BY 10% PER YEAR</p><br />
<p>'''TOTAL CIRCULATION:''' 5.2 BILLION BY 2050, DECREASING BY 18% PER YEAR</p><br />
<br />
<p>'''DESCRIPTION:'''</p><br />
<p>A secure blockchain benefiting those in distress - 10% of the emission goes to sponsoring Orphans, with provable contributions, expenses contributed to [http://compassion.com http://compassion.com] - and future charities that are more than 75% efficient. ** NOTE: THE COIN HAS RPC COMMANDS THAT PROVE 100% OF CONTRIBUTIONS ARE SPENT THE WAY INTENDED **</p> <br />
<br />
<br />
<p>Proof of Work has been replaced with Proof Of Biblehash (POBh) - an algorithm that compensates full nodes participation, while preventing GPUs and ASIC by requiring full blockchain transaction referencing in the hashing function, along with chained bible verses. This means biblepay subsidizes full nodes that stay online.</p><br />
<br />
<p>Seven minute block targets minimize the blockchain file size, yet BiblePay does support Dash's instantsend for speedy transactions. MasterNodes (called Sanctuaries) will come online after Christmas, allowing all expenses to be voted on and approved.</p><br />
<p>Expense receipts, to prove the sponshorship of new orphans, will be accessible from inside the wallet and we will even provide phone numbers for auditors to prove </p><br />
100% charity expenditures. (From the rpc, type &#39;run contribution&#39; to see the tithes into the foundation for a time period, and to see the outgoing sponsorship click the wallets &#39;Accountability&#39; button to see a list of orphans, expenses, sponsorship dates, amounts, and the charity phone number, and txid).<br />
<br />
<p>For the first 6 months, 10% of each block will be allocated to the foundation, for sponsoring orphans at 100%. Once per month, we will cash in anything over $40 available on an exchange, and sponsor orphans on our volunteer time. After the sanctuaries go live, the 10% tithe will be diverted to an ongoing budget with DAO governance, voting, allowing the coin to function as a dectralized autonomous charity; at that point the lead dev and volunteers will become a normal part of the community allowing the coin to run by itself.</p><br />
<br />
<p>To avoid wasting energy on meaningless SHA hashing, (or mining), biblepay introduces the BibleHash algorithm, that allows biblepay to <br />
run on common commodity PCs, since the algorithm is resistant to porting to video cards and ASICs and is resistant to running in non-full node environments.</p><br />
<p>In addition to the low energy requirements and high efficiency of POB, the reward per block is set to be relative to the length of time the block took to solve, <br />
(meaning that abusive hash attacks result in subsidy decreases).</p><br />
<p>The network will be high efficiency with low total energy consumption, and the charities sponsored must also be high efficiency (over 75%).<br />
Next, we are deflationary, meaning that we start by issuing a larger amount of coins per block, and each year we tighten the supply by 18%.</p><br />
<br />
The schedule is here: (205 blocks per day, 7 minute block targets):<br />
EMISSION SCHEDULE PROJECTION: http://wiki.biblepay.org/Emission_Schedule<br />
<br />
<p>The block reward breakdown is as follows:</p><br />
<br />
ECONOMICS: http://wiki.biblepay.org/Economics<br />
<br />
<br />
<p>After our sanctuaries go live, we allocate 10% of each block subsidy to our governance committe (a DAO), automatically, with 100% of that being<br />
spent on charity. <br />
<br />
Over time, our sanctuaries will become a charity governance committee, to allow our community to take over the day to day operations of the charity: voting on where the money is spent, how much is spent.<br />
This way, we will not be centralized.</p><br />
<br />
<p>We only partner with charities over 75% efficient, meaning over 75% reach the end-user.</p><br />
<br />
<br />
<p>'''<span style="color:#ff0000">NO PREMINE:</span>'''</p><br />
<p>the lead dev starts with zero, the orphan foundation fund starts with zero, the distribution is entirely fair. NO ICO. The distribution curve is evenly declining with no hidden bumps early.<br />
The self-governance committee and masternode payments are deliberately delayed until Christmas, to allow people to prepare and save up the initial requirement. Running a sanctuary is open to anyone.<br />
The lead dev will sponsor the first 10 orphans out of his own pocket.</p><br />
<p>'''<span style="color:#ff0000">Accountability:</span></p><br />
<p>The wallet will have a reconciliation page built in at go live, to show all charitable income and expenses.</p><br />
<p>The expenses will be auditable - to prove the money actually was spent on orphans.</p><br />
<p>This will be accomplished through the use of : an RPC audit command that tallies the orphan income from the blockchain, and secondly, an API connection to a database that stores the Compassion expenses (until sanctuaries go live), with auditable backing contact info for each expense. We will also provide a web page with pictures of the sponsored orphans clicable from the wallet to show our investors what good we are doing. And finally- we will maintain a copy of receipts in order to maintain 100% accountability.</p><br />
<p>Future Feature: Pay to Preach, in wallet ineractive prayer rooms.</p><br />
<br />
'''ROADMAP:'''<br />
JULY-DECEMBER 2017: GO LIVE, SPONSOR ORPHANS MONTHLY<br />
<br />
JANUARY 2018: MASTERNODES (SANCTUARIES) GO LIVE<br />
<br />
FEBRUARY 2018: MARKETING, IN WALLET PRAYERS<br />
<br />
MAY 2018: MARKET BIBLEPAY AS A 401K ALTERNATIVE<br />
<br />
[[:Category:Roadmap|More roadmap details]]<br />
<br />
'''Novel distinct features of BiblePay:'''<br />
<br />
<p>Proof of Bible Hash algorithm (POBh), getblockinfo shows the chained bible verses required to solve the block, sending money exposes a Tithe checkbox - allowing 10% to be gifted to the orphan foundation, wallet has an in-wallet prayer system, allowing a user to send out a prayer request to the network or store prayers in the chain for the community to pray for from the overview page, Transactions support in-chain messages, Instant Send, Voting, Decentralized Automated Charity Governance Committee, Repentance of Sins, Contributing to the orphan foundation checkbox, and reading the sin list and various staple prayers in wallet.</p><br />
<br />
{{Special:Categories}}</div>Sunk818https://wiki.biblepay.org/index.php?title=Main_Page&diff=6117Main Page2019-02-26T16:59:15Z<p>Sunk818: </p>
<hr />
<div>{| class="wikitable" style="text-align:center; margin-left:2em"<br />
|| BIBLEPAY || 10% Charity, Masternodes (Sanctuaries), ASIC-Resistant, CPU-Mining, 10% to Orphans<br />
|-<br />
|| Mint || Decentralized Proof Of Work<br />
|-<br />
|| Launch Date || August 2017<br />
|-<br />
|| Developed by || Robert Andrews<br />
|-<br />
|| Ticker || BBP<br />
|-<br />
|| Plural || Biblepays<br />
|-<br />
|| Subunit || mBBP =0.001<br />
|-<br />
|| Lowest Unit || 0.00000001 = 1 BBP<br />
|-<br />
|| Operating System || Windows, Linux, macOS<br />
|-<br />
|| Algorithm || Proof-of-BibleHash<br />
|-<br />
|| Current Version || Client v1.0.2.9 mandatory<br />
|-<br />
|| Release Date || July 23rd, 2017<br />
|-<br />
|| Blocktime || avg 7 Minutes<br />
|-<br />
|| Reward || 20,000 Decreasing by 1.5% per month (Approx 19% per year)<br />
|}<br />
<br />
<br />
<p>'''NAME:''' BIBLEPAY</p><br />
<br />
<br />
<p>'''LAUNCH DATE:''' JULY 23, 2017 at 17:00:00 CST</p><br />
<br />
<p>'''BLOCK TARGET RATE:''' 7 MINUTES</p><br />
<br />
<p>'''ALGORITHM:''' PROOF OF BIBLEHASH (POBh) ** NEW **</p><br />
<br />
<p>First coin with the KJV Bible compiled in the source, and utilizing the Bible in the hashing algorithm, while spreading the gospel throughout the IT community. The blocks also hash to chained bible verses.</p><br />
<br />
<p>'''TRANSACTION SPEED:''' SUPPORTS INSTANTSEND</p><br />
<p>'''MASTERNODE(SANCTUARY) SUPPORT:''' Supported after Christmas 2017</p><br />
<p>'''SANCTUARY SUBSIDY BREAKDOWN:''' 10% TO CHARITY, 10% TO MASTERNODES, 80% TO MINER</p><br />
<p>'''FORUM:''' [http://bitcointalk.org/topic=2042657 Bitcointalk]</p><br />
<p>'''Backup Forum:'''[http://forum.biblepay.org/ forum.biblepay.org]</p><br />
<p>'''BLOCK EXPLORER:'''[https://biblepay-explorer.org/ biblepay-explorer.org]</p><br />
<p>'''BLOCK EXPLORER:'''[http://explorer.biblepay.org:3001/ explorer.biblepay.org]</p><br />
<p>'''SOURCE CODE:'''[http://github.com/biblepay/biblepay Github]</p><br />
<p>'''WEB SITE:'''[http://biblepay.org biblepay.org]</p><br />
<p>'''EXCHANGES:'''[https://c-cex.com/?p=bbp-btc c-cex]</p><br />
<p>'''[https://www.southxchange.com/Market/Book/BBP/BTC]</p><br />
<br />
<p>'''TICKER:''' BBP</p><br />
<p>'''Exchange Go Live Date:''' August 15th 2017</p><br />
<p>'''PREMINE:''' NONE</p><br />
<p>'''ICO:''' NONE</p><br />
<p>'''INCONSISTENT REWARDS:''' NONE</p><br />
<p>'''CIRCULATION CHARACTERISTIC:''' DEFLATIONARY</p><br />
<p>'''CIRCULATION RATE:''' DECREASE BY 10% PER YEAR</p><br />
<p>'''TOTAL CIRCULATION:''' 5.2 BILLION BY 2050, DECREASING BY 18% PER YEAR</p><br />
<br />
<p>'''DESCRIPTION:'''</p><br />
<p>A secure blockchain benefiting those in distress - 10% of the emission goes to sponsoring Orphans, with provable contributions, expenses contributed to [http://compassion.com http://compassion.com] - and future charities that are more than 75% efficient. ** NOTE: THE COIN HAS RPC COMMANDS THAT PROVE 100% OF CONTRIBUTIONS ARE SPENT THE WAY INTENDED **</p> <br />
<br />
<br />
<p>Proof of Work has been replaced with Proof Of Biblehash (POBh) - an algorithm that compensates full nodes participation, while preventing GPUs and ASIC by requiring full blockchain transaction referencing in the hashing function, along with chained bible verses. This means biblepay subsidizes full nodes that stay online.</p><br />
<br />
<p>Seven minute block targets minimize the blockchain file size, yet BiblePay does support Dash's instantsend for speedy transactions. MasterNodes (called Sanctuaries) will come online after Christmas, allowing all expenses to be voted on and approved.</p><br />
<p>Expense receipts, to prove the sponshorship of new orphans, will be accessible from inside the wallet and we will even provide phone numbers for auditors to prove </p><br />
100% charity expenditures. (From the rpc, type &#39;run contribution&#39; to see the tithes into the foundation for a time period, and to see the outgoing sponsorship click the wallets &#39;Accountability&#39; button to see a list of orphans, expenses, sponsorship dates, amounts, and the charity phone number, and txid).<br />
<br />
<p>For the first 6 months, 10% of each block will be allocated to the foundation, for sponsoring orphans at 100%. Once per month, we will cash in anything over $40 available on an exchange, and sponsor orphans on our volunteer time. After the sanctuaries go live, the 10% tithe will be diverted to an ongoing budget with DAO governance, voting, allowing the coin to function as a dectralized autonomous charity; at that point the lead dev and volunteers will become a normal part of the community allowing the coin to run by itself.</p><br />
<br />
<p>To avoid wasting energy on meaningless SHA hashing, (or mining), biblepay introduces the BibleHash algorithm, that allows biblepay to <br />
run on common commodity PCs, since the algorithm is resistant to porting to video cards and ASICs and is resistant to running in non-full node environments.</p><br />
<p>In addition to the low energy requirements and high efficiency of POB, the reward per block is set to be relative to the length of time the block took to solve, <br />
(meaning that abusive hash attacks result in subsidy decreases).</p><br />
<p>The network will be high efficiency with low total energy consumption, and the charities sponsored must also be high efficiency (over 75%).<br />
Next, we are deflationary, meaning that we start by issuing a larger amount of coins per block, and each year we tighten the supply by 18%.</p><br />
<br />
The schedule is here: (205 blocks per day, 7 minute block targets):<br />
EMISSION SCHEDULE PROJECTION: http://wiki.biblepay.org/Emission_Schedule<br />
<br />
<p>The block reward breakdown is as follows:</p><br />
<br />
ECONOMICS: http://wiki.biblepay.org/Economics<br />
<br />
<br />
<p>After our sanctuaries go live, we allocate 10% of each block subsidy to our governance committe (a DAO), automatically, with 100% of that being<br />
spent on charity. <br />
<br />
Over time, our sanctuaries will become a charity governance committee, to allow our community to take over the day to day operations of the charity: voting on where the money is spent, how much is spent.<br />
This way, we will not be centralized.</p><br />
<br />
<p>We only partner with charities over 75% efficient, meaning over 75% reach the end-user.</p><br />
<br />
<br />
<p>'''<span style="color:#ff0000">NO PREMINE:</span>'''</p><br />
<p>the lead dev starts with zero, the orphan foundation fund starts with zero, the distribution is entirely fair. NO ICO. The distribution curve is evenly declining with no hidden bumps early.<br />
The self-governance committee and masternode payments are deliberately delayed until Christmas, to allow people to prepare and save up the initial requirement. Running a sanctuary is open to anyone.<br />
The lead dev will sponsor the first 10 orphans out of his own pocket.</p><br />
<p>'''<span style="color:#ff0000">Accountability:</span></p><br />
<p>The wallet will have a reconciliation page built in at go live, to show all charitable income and expenses.</p><br />
<p>The expenses will be auditable - to prove the money actually was spent on orphans.</p><br />
<p>This will be accomplished through the use of : an RPC audit command that tallies the orphan income from the blockchain, and secondly, an API connection to a database that stores the Compassion expenses (until sanctuaries go live), with auditable backing contact info for each expense. We will also provide a web page with pictures of the sponsored orphans clicable from the wallet to show our investors what good we are doing. And finally- we will maintain a copy of receipts in order to maintain 100% accountability.</p><br />
<p>Future Feature: Pay to Preach, in wallet ineractive prayer rooms.</p><br />
<br />
'''ROADMAP:'''<br />
JULY-DECEMBER 2017: GO LIVE, SPONSOR ORPHANS MONTHLY<br />
<br />
JANUARY 2018: MASTERNODES (SANCTUARIES) GO LIVE<br />
<br />
FEBRUARY 2018: MARKETING, IN WALLET PRAYERS<br />
<br />
MAY 2018: MARKET BIBLEPAY AS A 401K ALTERNATIVE<br />
<br />
[[:Category:Roadmap|More roadmap details]]<br />
<br />
'''Novel distinct features of BiblePay:'''<br />
<br />
<p>Proof of Bible Hash algorithm (POBh), getblockinfo shows the chained bible verses required to solve the block, sending money exposes a Tithe checkbox - allowing 10% to be gifted to the orphan foundation, wallet has an in-wallet prayer system, allowing a user to send out a prayer request to the network or store prayers in the chain for the community to pray for from the overview page, Transactions support in-chain messages, Instant Send, Voting, Decentralized Automated Charity Governance Committee, Repentance of Sins, Contributing to the orphan foundation checkbox, and reading the sin list and various staple prayers in wallet.</p><br />
<br />
{{Special:AllPages}}</div>Sunk818https://wiki.biblepay.org/index.php?title=Main_Page&diff=6116Main Page2019-02-26T16:58:28Z<p>Sunk818: show all pages</p>
<hr />
<div>{| class="wikitable" style="text-align:center; margin-left:2em"<br />
|| BIBLEPAY || 10% Charity, Masternodes (Sanctuaries), ASIC-Resistant, CPU-Mining, 10% to Orphans<br />
|-<br />
|| Mint || Decentralized Proof Of Work<br />
|-<br />
|| Launch Date || August 2017<br />
|-<br />
|| Developed by || Robert Andrews<br />
|-<br />
|| Ticker || BBP<br />
|-<br />
|| Plural || Biblepays<br />
|-<br />
|| Subunit || mBBP =0.001<br />
|-<br />
|| Lowest Unit || 0.00000001 = 1 BBP<br />
|-<br />
|| Operating System || Windows, Linux, macOS<br />
|-<br />
|| Algorithm || Proof-of-BibleHash<br />
|-<br />
|| Current Version || Client v1.0.2.9 mandatory<br />
|-<br />
|| Release Date || July 23rd, 2017<br />
|-<br />
|| Blocktime || avg 7 Minutes<br />
|-<br />
|| Reward || 20,000 Decreasing by 1.5% per month (Approx 19% per year)<br />
|}<br />
<br />
<br />
<p>'''NAME:''' BIBLEPAY</p><br />
<br />
<br />
<p>'''LAUNCH DATE:''' JULY 23, 2017 at 17:00:00 CST</p><br />
<br />
<p>'''BLOCK TARGET RATE:''' 7 MINUTES</p><br />
<br />
<p>'''ALGORITHM:''' PROOF OF BIBLEHASH (POBh) ** NEW **</p><br />
<br />
<p>First coin with the KJV Bible compiled in the source, and utilizing the Bible in the hashing algorithm, while spreading the gospel throughout the IT community. The blocks also hash to chained bible verses.</p><br />
<br />
<p>'''TRANSACTION SPEED:''' SUPPORTS INSTANTSEND</p><br />
<p>'''MASTERNODE(SANCTUARY) SUPPORT:''' Supported after Christmas 2017</p><br />
<p>'''SANCTUARY SUBSIDY BREAKDOWN:''' 10% TO CHARITY, 10% TO MASTERNODES, 80% TO MINER</p><br />
<p>'''FORUM:''' [http://bitcointalk.org/topic=2042657 Bitcointalk]</p><br />
<p>'''Backup Forum:'''[http://forum.biblepay.org/ forum.biblepay.org]</p><br />
<p>'''BLOCK EXPLORER:'''[https://biblepay-explorer.org/ biblepay-explorer.org]</p><br />
<p>'''BLOCK EXPLORER:'''[http://explorer.biblepay.org:3001/ explorer.biblepay.org]</p><br />
<p>'''SOURCE CODE:'''[http://github.com/biblepay/biblepay Github]</p><br />
<p>'''WEB SITE:'''[http://biblepay.org biblepay.org]</p><br />
<p>'''EXCHANGES:'''[https://c-cex.com/?p=bbp-btc c-cex]</p><br />
<p>'''[https://www.southxchange.com/Market/Book/BBP/BTC]</p><br />
<br />
<p>'''TICKER:''' BBP</p><br />
<p>'''Exchange Go Live Date:''' August 15th 2017</p><br />
<p>'''PREMINE:''' NONE</p><br />
<p>'''ICO:''' NONE</p><br />
<p>'''INCONSISTENT REWARDS:''' NONE</p><br />
<p>'''CIRCULATION CHARACTERISTIC:''' DEFLATIONARY</p><br />
<p>'''CIRCULATION RATE:''' DECREASE BY 10% PER YEAR</p><br />
<p>'''TOTAL CIRCULATION:''' 5.2 BILLION BY 2050, DECREASING BY 18% PER YEAR</p><br />
<br />
<p>'''DESCRIPTION:'''</p><br />
<p>A secure blockchain benefiting those in distress - 10% of the emission goes to sponsoring Orphans, with provable contributions, expenses contributed to [http://compassion.com http://compassion.com] - and future charities that are more than 75% efficient. ** NOTE: THE COIN HAS RPC COMMANDS THAT PROVE 100% OF CONTRIBUTIONS ARE SPENT THE WAY INTENDED **</p> <br />
<br />
<br />
<p>Proof of Work has been replaced with Proof Of Biblehash (POBh) - an algorithm that compensates full nodes participation, while preventing GPUs and ASIC by requiring full blockchain transaction referencing in the hashing function, along with chained bible verses. This means biblepay subsidizes full nodes that stay online.</p><br />
<br />
<p>Seven minute block targets minimize the blockchain file size, yet BiblePay does support Dash's instantsend for speedy transactions. MasterNodes (called Sanctuaries) will come online after Christmas, allowing all expenses to be voted on and approved.</p><br />
<p>Expense receipts, to prove the sponshorship of new orphans, will be accessible from inside the wallet and we will even provide phone numbers for auditors to prove </p><br />
100% charity expenditures. (From the rpc, type &#39;run contribution&#39; to see the tithes into the foundation for a time period, and to see the outgoing sponsorship click the wallets &#39;Accountability&#39; button to see a list of orphans, expenses, sponsorship dates, amounts, and the charity phone number, and txid).<br />
<br />
<p>For the first 6 months, 10% of each block will be allocated to the foundation, for sponsoring orphans at 100%. Once per month, we will cash in anything over $40 available on an exchange, and sponsor orphans on our volunteer time. After the sanctuaries go live, the 10% tithe will be diverted to an ongoing budget with DAO governance, voting, allowing the coin to function as a dectralized autonomous charity; at that point the lead dev and volunteers will become a normal part of the community allowing the coin to run by itself.</p><br />
<br />
<p>To avoid wasting energy on meaningless SHA hashing, (or mining), biblepay introduces the BibleHash algorithm, that allows biblepay to <br />
run on common commodity PCs, since the algorithm is resistant to porting to video cards and ASICs and is resistant to running in non-full node environments.</p><br />
<p>In addition to the low energy requirements and high efficiency of POB, the reward per block is set to be relative to the length of time the block took to solve, <br />
(meaning that abusive hash attacks result in subsidy decreases).</p><br />
<p>The network will be high efficiency with low total energy consumption, and the charities sponsored must also be high efficiency (over 75%).<br />
Next, we are deflationary, meaning that we start by issuing a larger amount of coins per block, and each year we tighten the supply by 18%.</p><br />
<br />
The schedule is here: (205 blocks per day, 7 minute block targets):<br />
EMISSION SCHEDULE PROJECTION: http://wiki.biblepay.org/Emission_Schedule<br />
<br />
<p>The block reward breakdown is as follows:</p><br />
<br />
ECONOMICS: http://wiki.biblepay.org/Economics<br />
<br />
<br />
<p>After our sanctuaries go live, we allocate 10% of each block subsidy to our governance committe (a DAO), automatically, with 100% of that being<br />
spent on charity. <br />
<br />
Over time, our sanctuaries will become a charity governance committee, to allow our community to take over the day to day operations of the charity: voting on where the money is spent, how much is spent.<br />
This way, we will not be centralized.</p><br />
<br />
<p>We only partner with charities over 75% efficient, meaning over 75% reach the end-user.</p><br />
<br />
<br />
<p>'''<span style="color:#ff0000">NO PREMINE:</span>'''</p><br />
<p>the lead dev starts with zero, the orphan foundation fund starts with zero, the distribution is entirely fair. NO ICO. The distribution curve is evenly declining with no hidden bumps early.<br />
The self-governance committee and masternode payments are deliberately delayed until Christmas, to allow people to prepare and save up the initial requirement. Running a sanctuary is open to anyone.<br />
The lead dev will sponsor the first 10 orphans out of his own pocket.</p><br />
<p>'''<span style="color:#ff0000">Accountability:</span></p><br />
<p>The wallet will have a reconciliation page built in at go live, to show all charitable income and expenses.</p><br />
<p>The expenses will be auditable - to prove the money actually was spent on orphans.</p><br />
<p>This will be accomplished through the use of : an RPC audit command that tallies the orphan income from the blockchain, and secondly, an API connection to a database that stores the Compassion expenses (until sanctuaries go live), with auditable backing contact info for each expense. We will also provide a web page with pictures of the sponsored orphans clicable from the wallet to show our investors what good we are doing. And finally- we will maintain a copy of receipts in order to maintain 100% accountability.</p><br />
<p>Future Feature: Pay to Preach, in wallet ineractive prayer rooms.</p><br />
<br />
'''ROADMAP:'''<br />
JULY-DECEMBER 2017: GO LIVE, SPONSOR ORPHANS MONTHLY<br />
<br />
JANUARY 2018: MASTERNODES (SANCTUARIES) GO LIVE<br />
<br />
FEBRUARY 2018: MARKETING, IN WALLET PRAYERS<br />
<br />
MAY 2018: MARKET BIBLEPAY AS A 401K ALTERNATIVE<br />
<br />
[[:Category:Roadmap|More roadmap details]]<br />
<br />
'''Novel distinct features of BiblePay:'''<br />
<br />
<p>Proof of Bible Hash algorithm (POBh), getblockinfo shows the chained bible verses required to solve the block, sending money exposes a Tithe checkbox - allowing 10% to be gifted to the orphan foundation, wallet has an in-wallet prayer system, allowing a user to send out a prayer request to the network or store prayers in the chain for the community to pray for from the overview page, Transactions support in-chain messages, Instant Send, Voting, Decentralized Automated Charity Governance Committee, Repentance of Sins, Contributing to the orphan foundation checkbox, and reading the sin list and various staple prayers in wallet.</p><br />
<br />
{{Special:AllPages|namespace=14}}</div>Sunk818https://wiki.biblepay.org/index.php?title=Spiritual-Warfare-I&diff=6115Spiritual-Warfare-I2019-02-26T16:56:42Z<p>Sunk818: </p>
<hr />
<div>Spiritual Warfare is nothing to take lightly. It is a serious battle that your spirit will fight within the second Heaven. <br />
<br />
Fighting directly against the Devil opens a door in your life to spiritual attacks. It also gives the enemy a right to attack your family, your pets and your assets.<br />
<br />
If you are living in sin, do not attempt this battle, as serious damage may come back to you, as if you are not 'covered', the door will be wide open for the enemy to harm you in any way possible.<br />
<br />
You must not be holding grudges against others, you must not be half in the world, you must not be expirimenting in sinful activities (for example drinking alcohol and attempting to repent), <br />
you must be living a committed life for Jesus and picking up your cross daily. <br />
<br />
Additionally a spiritual battle might last an entire year. You have to count the costs before entering the battle, and realize this battle takes sacrifice and perseverance. <br />
<br />
<ul>Some tips before you decide:<br />
<li>You must not have a judgemental attitude towards pastors, men-of-God, or anyone. The reason I mention this, is the last warfare campaign I was readying for, a few warriors raised an issue with Training Materials being supplied by one of the well known church organizations (that they thought were too materialistic). However the materials themselves were professional, solid and backed by scripture. God told our leader: Tell these people they are judgemental, and not to judge my servants! So please, you must be humble.<br />
<li>Strife: You must not react to people who point the finger at you in a spiteful, or mean spirited way. The devil will test you after you spend days battling his demons. He will do this in your most sensitive areas. One way to get at you is to prod you by choosing an e-mail or a job or a co-worker or anyone to tell you something that "pushes your buttons". The key is to not react (and take the bait). If you do you will invite demons of strife into your life, and you cannot risk that as a warrior of God.<br />
<li>Count the Costs: This battle involves dedicated commitment - of time and energy for consistency in the prayer closet, and, involves sacrifice, because you are being asked to pick up your cross and represent Christ in a Holy way. If you don't believe you will make it to the end, please don't volunteer. This is similar to counting the costs before waging war with a King on the National Level.<br />
<li>You must take the armor of God, the protection and covering prayers and the warfare very seriously. Do not shoddily enter battle without all protection on. This is equivalent to giving the enemy an easy shot at you and could result in severe damage to your health, peace and safety, finances, and life in general.<br />
</ul><br />
<br />
Once you decide that you have what it takes, you have to establish daily cover (cover by a Christian friends prayer, cover by God, cover by the armor and cover by daily prayers); we will explain each of these.<br />
<br />
Before entering into spiritual warfare, you must put on the armor:<br />
<br />
Ephesians 6:10-18:<br />
<br />
10 Finally, my brethren, be strong in the Lord, and in the power of his might.<br />
11 Put on the whole armour of God, that ye may be able to stand against the wiles of the devil.<br />
12 For we wrestle not against flesh and blood, but against principalities, against powers, against the rulers of the darkness of this world, against spiritual wickedness in high places.<br />
13 Wherefore take unto you the whole armour of God, that ye may be able to withstand in the evil day, and having done all, to stand.<br />
14 Stand therefore, having your loins girt about with truth, and having on the breastplate of righteousness;<br />
15 And your feet shod with the preparation of the gospel of peace;<br />
16 Above all, taking the shield of faith, wherewith ye shall be able to quench all the fiery darts of the wicked.<br />
17 And take the helmet of salvation, and the sword of the Spirit, which is the word of God:<br />
18 Praying always with all prayer and supplication in the Spirit, and watching thereunto with all perseverance and supplication for all saints;<br />
<br />
To put on the armor, pray this: Lord, I thank you for your Armor! I put on the Belt of Truth, the Breastplate of Righteousness, the Shoes of Peace, the Shield of Faith, the Helmet of Salvation, and the Sword of the Spirit!<br />
<br />
<ul>The weapons are:<br />
<li> Girdle or Belt of Truth <br />
<li> Breastplate of Righteousness<br />
<li> Shoes of the Preparation of the Gospel of Peace (or Shoes of Peace)<br />
<li> Shield of Faith<br />
<li> Helmet of Salvation<br />
<li> Sword of the Spirit<br />
</ul><br />
<br />
See more about the Full Armor of God Here:<br />
https://www.youtube.com/watch?v=lOEYH5SyGfU&feature=youtu.be<br />
<br />
Pray a Preperatory prayer:<br />
<br />
Pray this prayer everyday to get your heart and spirit ready for the battle.<br />
<br />
<pre><br />
"Oh Holy FATHER GOD and LORD JESUS CHRIST in one heart, mind and in agreement together, we dedicate ourselves, <br />
our lives unto YOU and affirm our commitment to do YOUR perfect and sovereign will in this undertaking through <br />
the BiblePay Warfare Team and its leadership in Spiritual Battle and Prayer."<br />
</pre><br />
<br />
Empowered by Your Word, faith, Agape love and Holy Name. <br />
Keep us in continuous union with you through abiding in You so that we live, walk and work in your righteous manner.<br />
<br />
JESUS , YOU are our example to follow in all things. <br />
We seek to live from faith to faith and to accomplish all the work that YOU have for us.<br />
<br />
JESUS, we look to and upon YOU for all things and behold YOU for everything <br />
we need to accomplish YOUR Holy Will as YOU lead, guide and direct us. <br />
<br />
Now lead us by YOUR HOLY SPIRIT in YOUR Work to bring forth YOUR fruit in victory for YOUR Kingdom. <br />
<br />
We lift up YOUR Holy Name forever and plead the Name of JESUS and HIS Blood over this endeavor under YOUR guidance and Will in all things. Amen. “<br />
<br />
Next it is important to pray the Prayer of Protection daily (Psalm 91):<br />
<br />
Lord God, how excellent is Your Name in all the Earth! Lord I am so grateful You have given us psalms of protection to protect us as we go to war against the enemy’s purposes for You. Thank You for the angels You have assigned to protect us in these battles.<br />
<br />
<br />
Thank You, Lord, that Your Word says as I dwell in the secret place of the Most High, I abide under the shadow of the Almighty. <br />
I declare YOU are my refuge and my fortress! <br />
You are my God, and in You only will I trust. <br />
I know You will deliver me from the snare of the fowler, and from the noisome pestilence. <br />
You will cover me with Your feathers, and under Your Wings will I trust.<br />
Your Truth will be my shield and my buckler.<br />
<br />
I will NOT be afraid of the terror by night or the arrows that fly by day; I will NOT fear the pestilence that walks in darkness, nor the destruction that wastes at noonday. <br />
A thousand may fall at my side, and ten thousand at my right hand, but it will NOT come near me! <br />
Only with my eyes will I behold and see the reward of the wicked, because I have made the Lord, which is my refuge, even the Most High, my habitation. <br />
There shall NO evil befall me, neither shall any plague come near my dwelling. <br />
For You shall give Your angels charge over me, to keep me in all my ways. They shall bear me up in their hands, lest I dash my foot against a stone.<br />
<br />
I will tread upon the lion and the adder; the young lion and dragon shall I trample under feet. <br />
Because I have set my love upon You, Your Word says You will deliver me and set me on high, because I have known Your Name. <br />
I will call upon You and Your Word says You will answer me. <br />
You will be with me in any trouble, and You will deliver me, and honor me. With long life will you satisfy me and show me Your Salvation.<br />
<br />
Thank You, Lord, for leading me to what You want me to do. <br />
I look forward to seeing the results of my warfare! I know You will show me the battles that have been won. <br />
I will give You ALL the praise, honor and glory for these victories!<br />
<br><br />
<br />
'''Personal Daily Prayer of Protection'''<br />
<br />
It is also advisable that you create your own personal prayer that you are comfortable with that you pray daily for <br />
protection over Home, Health, Pets, Finances, Job, family. Below is a very good starting prayer (you may adapt to include your own circumstance), and pray this daily, to ensure you are covered before entering spiritual warfare:<br />
<br />
Father God, in the name of and under the authority of Jesus Christ I plead the Blood of Jesus Christ over myself, my spouse and our children. <br />
I pray that You will immerse our spirits, souls and bodies in the precious and pure Blood of the lamb. <br />
I plead the Blood of Jesus over our pets, home, property, belongings, car, business, Ministry, health and well-being.<br />
<br />
I plead the Blood of Jesus against any demonic spirits who are coming against us. I plead the Blood of Jesus against all accidents, attacks, misadventure and catastrophes that may try to come against us. <br />
With the Blood of the Lamb I dismantle every enemy assignment operating against us. <br />
Please reveal to us each day any open doors that allow the enemy access to us.<br />
<br />
I plead the Blood of Jesus against any diseases, viruses, infections or illnesses that are coming against us.<br />
<br />
I ask for a covering of the Blood of Jesus to be placed between us and any people who are coming against us and our lives. <br />
I forgive these people for any attacks against us and I ask You Father God to bless them. <br />
I dismantle every curse and attack coming against us in the name and power of Jesus Christ and I declare Isaiah 54:17 <br />
“That No weapon that is formed against thee shall prosper; and every tongue that shall rise against thee in judgment thou shalt condemn. <br />
This is the heritage of the servants of the LORD, and their righteousness is of me, saith the LORD”.<br />
<br />
Thank You Father God I now have full faith and belief that the Blood of Jesus will fully protect us and everything within our sphere of influence.<br />
<br />
'''A strong spiritual weapon from God'''<br />
<br />
Now that you have most of the tools available in your arsenal, please study Phase II to form a war plan to execute against the enemy.<br />
<br />
<br />
Note that one powerful weapon God has given Christians for individual prayers is Isaiah 54:17:<br />
<br />
No weapon that is formed against thee shall prosper; <br />
and every tongue that shall rise against thee in judgment he shall condemn. <br />
This is the heritage of the servants of the Lord, and his righteousness is of me, saith the Lord.<br />
<br />
[[Category:Theology]]</div>Sunk818https://wiki.biblepay.org/index.php?title=CoinExchange_Requirements&diff=6111CoinExchange Requirements2019-02-25T16:03:48Z<p>Sunk818: </p>
<hr />
<div>Listing Requirements for Exchanges<br />
----------------------------------<br />
<br />
Name: BIBLEPAY<br />
<br />
Logo:<br />
[http://pool.biblepay.org/images/logo.png BiblePay Logo]<br />
<br />
<br />
<br />
<br />
== Section 1 ==<br />
<br />
<br />
; 1a. Please supply a detailed description of your coin : BiblePay is a secure deflationary blockchain developed to benefit those in distress.<br />
; 1b. What is the innovation in your coin? : We are the first coin with the KJV Bible compiled in the source- utilizing the Bible in the hashing algorithm, while spreading the gospel throughout the IT community. The blocks also hash to chained bible verses. We also have a unique proof-of-distributed computing mining algorithm built in that rewards users for cancer mining against Rosetta@Home. See our whitepaper:<br />
https://www.biblepay.org/wp-content/uploads/2018/06/biblepay-whitepaper-single-cover-April2018.pdf<br />
<br />
; 1c. How is it different from other coins? : 10% of our emission goes directly to sponsor orphans through compassion.com and other highly efficient and voted in charities. We also have the PODC (proof-of-distributed-computing) algorithm, which rewards our miners for cancer-mining. We also have Sanctuaries, a flavor of masternodes, with monthly budgets and governance. We are truly a charitable decentralized autonomous organization (DAO). Our POBh algorithm compensates full node participation by rewarding CPU-equipped nodes with the block reward (while not rewarding GPU/ASICS). This means biblepay subsidizes full nodes that stay online. We primarily reward our PODC network for cancer-mining, instead of wasting energy on SHA hashing - meaning our network is doing useful work. We are also deflationary, in that our coin emission rate is reduced by 18% per year.<br />
<br />
; 2. Which coin are you cloned or forked from? : DashPay<br />
<br />
; 3. How long has the coin been in development? : 14 months. <br />
<br />
; 4. How many members in your development team and what country are you based out of? : We have 4 developers and we are primarily based out of the United States. Our team: https://www.biblepay.org/cryptoguru/#team<br />
<br />
; 5. Do any of your core members have previous experience working with or have founded a crypto-related business? : Yes, Robert Andrews has over one million lines of github cryptocurrency related commits across several projects (Stratis-biblepay, biblepayd, Univ of Ruhr Cryptocurrency security mitigation, Major Exchange (NDA) performance commits, and a $10 million project protected by NDA, and the DAHF). Licht has created an entire web site - biblepay-central. Javier has created both the Biblepay android mobile wallet and the iphone wallet. Rob and Licht have created homemade mining pools for biblepay.<br />
<br />
; 6. Is the coin pre-mined? If so, what is the pre-mine amount / percentage? : We had No premine, no foundation block was set aside, and 0% was reserved during go-live for budgetary purposes.<br />
<br />
; 7. Are two members of your development team prepared to provide full ID verification? : Yes<br />
<br />
; 8. What exchanges is your coin / token currently listed on? : BiblePay is listed on C-CEX, QIEX, SouthXChange and CryptoBridge.<br />
<br />
; 9. What is the consensus mechanism of the coin / token? e.g., PoS, PoW, Masternode etc : Our consensus mechanism (for our 205 blocks per day) is Proof-of-Bible-Hash, which is a flavor of POW. This is a CPU mined algorithm.<br />
<br />
; 10. Please provide your complete coin / token specification? : Our POBH Spec: http://pool.biblepay.org/Docs/BiblePay_White_Paper_Old.pdf<br> Our whitepaper: https://www.biblepay.org/wp-content/uploads/2018/06/biblepay-whitepaper-single-cover-April2018.pdf <br> Our PODC Spec: https://wiki.biblepay.org/Distributed_Computing<br />
<br />
; 11. Please provide a detailed explanation of your distribution plan? (Mining / Premine / Airdrop / ICO & other sales / Other) : We have a deflationary emission schedule, (emitting a max of 5.2 billion coins by 2050) and we are currently emitted at 800,000,000 as of August 2018.<br>In summary our blocks generate a deflating reward starting at 20,000 bbp per block, with 38.5% going to Sanctuaries (those are our masternodes). <br>The other 38.5% is given to our cancer-mining budget. <br>17.5% is reserved for our superblock budget (governance). <br>From the 17.5% we pay our charity vendors (recurring orphanage sponsorships). <br>See http://accountability.biblepay.org for detailed revenue and expenses.<br>Out of our 17.5% governance budget, we plan on spending 5% on IT, 2.5% for Public Relations campaigns, and 2.5% for Peer-to-peer (social media, airdrops) and pay-to-preech features.<br />
<br />
; 12. Please provide a percentage breakdown of the distribution : http://wiki.biblepay.org/Economics<br />
<br />
'''Section 2 '''<br />
<br />
; 1. Were funds raised, digital or fiat, to support the launch of your coin? : No, we did not have an ICO, nor were funds raised, and we have no premine.<br />
; If you conducted an ICO (crowdsale), Private Sale or Presale etc., please answer all the following questions to assist us with our review of your coin : BiblePay did not have an ICO.<br />
<html><table background-color=grey><tr><td><small>This section does not apply to BiblePay<br />
<br>When was the ICO / private sale / pre-sale conducted? Please provide dates.<br />
<br> What percentage of your coin / token was offered up for sale?<br />
<br> What was your coin / token sale price? (USD)<br />
<br> How much was raised during the sale? (USD & BTC/ETH)<br />
<br> How many contributors participated in your sale?<br />
<br> Is there any remaining allocation of coins or tokens yet to be distributed?<br />
<br> Please supply a detailed rundown of how the raised funds will be used?<br />
<br> Is the lockup period for team allocated funding and early investors more than 1 year? If not, please explain why.<br />
<br>Please provide an additional written description of the sale which will provide additional information in order to assist us in the review of your project.<br />
</small><br />
</td></table></html><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
''' Section 3 '''<br />
<br />
<br />
; For Bitcoin derived coins we require the following information:<br />
<br />
; 3.1 Github source code URL : https://github.com/biblepay/biblepay<br />
; 3.2 Block explorer URL with the ability to search addresses (required): http://explorer.biblepay.org/<br />
; 3.3 Name of coin: BiblePay<br />
; 3.4 Ticker code of coin: BBP<br />
; 3.5 Website of coin: https://www.biblepay.org<br />
; 3.6 Square logo of at least 100 x 100 px (preferably transparent so it works with our dark theme also): pool.biblepay.org/images/logo.png<br />
<br />
<br />
; For Ethereum ERC20 tokens we require the following information: We are Bitcoin derived<br />
• Contract address: NA<br />
• Token name: NA<br />
• Token ticker code: NA<br />
• Decimal positions: NA<br />
• Square logo of at least 100 x 100 px (preferably transparent so it works with our dark theme also): NA<br />
• Link to contract on etherscan.io: NA<br />
• Website of token: NA<br />
<br />
<br />
<br />
''' Section 4 '''<br />
<br />
<br />
<br> For all coins and tokens please provide as many of the following URLs as possible:<br><br />
<br />
; 4.1 CoinMarketCap : https://coinmarketcap.com/currencies/biblepay/<br />
; 4.2 BitCoinTalk Announcement: https://bitcointalk.org/index.php?topic=2388064.0<br />
; 4.3 Forum : https://forum.biblepay.org <br> https://bitcointalk.org/index.php?topic=2388064.new#new<br />
; 4.4 Twitter : https://twitter.com/biblepay?lang=en<br />
; 4.5 Discord : https://discord.gg/yWgbKdM<br />
; 4.6 Slack Channel : https://join.slack.com/t/biblepay/shared_invite/enQtMjk2OTM4ODAxMjcxLThhMWQyZjMyYzI0MWVmYTg0YWU5NGNmY2Y1NTIzZmRmNjEzNmU1NjhjMWM5MjIxMDU2YjIwNjMxMzAzODA5MDE<br />
; 4.7 Telegram Group : https://t.me/biblepaybbp<br />
; 4.8 YouTube Video (up to 5) : https://www.youtube.com/watch?v=9KbvkQj8pJg<br>https://www.youtube.com/watch?v=4VXUQOf1IZQ<br>https://www.youtube.com/watch?v=nK3iiQC8U8Y<br>https://www.youtube.com/watch?v=caXGtKcKC-s<br>https://www.biblepay.org/the-biblepay-show/<br />
; 4.9 Wallet Link : https://www.biblepay.org/wallet/<br />
<br />
'''Ongoing obligations for Coin / Development teams '''<br />
<br />
1. We are obligated to give at least 14 days notice of any updates or maintenance required e.g., technical problems, significant code or protocol changes. This is extremely critical in terms of hardforks.<br />
<br />
2. Any issues which will affect deposits or withdrawals of your coin / token from an exchange.<br />
<br />
3. Any issues with your coin, including network functionality problems, hacks, as soon as you become aware of them.<br />
<br />
4. If you are conducting a coin swap we require as much notice as possible. We aim to give our community 30 days notice of any impending coin swap. Swaps are approved on a case by case basis and are solely at our own discretion.<br />
<br />
5. A minimum of 30 days notice if you want our assistance with an air drop. Be aware that support for this is solely at our discretion.<br />
<br />
<br />
[[Category:Exchange]]</div>Sunk818https://wiki.biblepay.org/index.php?title=The_Lords_Prayer&diff=6098The Lords Prayer2019-02-25T15:45:54Z<p>Sunk818: </p>
<hr />
<div><html><br />
<body><br />
<br />
<h1><br />
<p><br />
<br />
<h2><br />
Our Father who art in heaven,<br />
<p><br />
hallowed be thy name.<br />
<p><br />
Thy kingdom come,<br />
<p><br />
Thy will be done,<br />
<p><br />
on earth, as it is in heaven.<br />
<p><br />
Give us this day our daily bread,<br />
<p><br />
and forgive us of our trespasses,<br />
<p><br />
as we forgive those that trespass against us.<br />
<p><br />
And lead us not into temptation,<br />
<p><br />
but deliver us from evil.<br />
<p><br />
For thine is the Kingdom and the Power, and The Glory Forever.<br />
<p><br />
Amen<br />
<p><br />
</html><br />
<br />
[[Category:Theology]]</div>Sunk818https://wiki.biblepay.org/index.php?title=BiblePay_DAO&diff=6095BiblePay DAO2019-02-23T07:21:27Z<p>Sunk818: </p>
<hr />
<div><br />
This page explains the organizational structure of the BiblePay Decentralized Autonomous Organization.<br />
<br />
BiblePay is a decentralized organization composed of multiple layers.<br />
<br />
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.<br />
<br />
<br />
== The BiblePay Foundation ==<br />
<br />
The BiblePay Foundation is a non-profit Texas Corporation that manages vendor relationships, vendor payments, orphan fundraisers, cryptocurrency exchanges, taxes and legal decisions.<br />
<br />
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. <br />
<br />
The board will consist of:<br />
Sanctuaries<br />
<br />
<br />
The BiblePay source code is opensource and public and owned by the community members equally (IE every holder of BBP currency).<br />
<br />
The intellectual property concepts that are in development but not yet in production are owned by the Biblepay Foundation, until deployed.<br />
<br />
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.<br />
<br />
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.<br />
<br />
During Phase 3, Five co-developers will be given Spork Signing keys and Release Keys. A supermajority signed spork or release will be required.<br />
<br />
Definition of Phases:<br />
<table border=1><br />
<tr><th>Phase<th>Market Cap<th>Number of Cross-Trained Developers</tr><br />
<tr><td>Phase 1</td><td> 0-20,000,000 <td> 2 or less developers are Cross-Trained<br />
<tr><td>Phase 2 <td> 20,000,001-50,000,000 <td> 3 or more developers are cross-trained<br />
<tr><td>Phase 3 <td>50,000,000+ <td>5 or more developers are cross-trained<br />
</table><br />
<br />
<br />
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.<br />
<br />
When our market cap exceeds 50Mil, we will beef up cross-training and spork signing to be more resilient as Phase 3 shows.<br />
<br />
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.<br />
<br />
<br />
<br />
== Controls ==<br />
<br />
<br />
== Currency Exchange ==<br />
<br />
Vendor Payments exchanged for fiat and paid to vendors: Biblepay currency originating from a superblock payment to a vendor will pass through one of our boardmembers receiving addresses and will be liquidated within 30 days on one of our official exchanges using the BiblePay Foundation Tax ID number. This means our boardmember will not be subject to tax risks. The boardmember will keep a copy of the receipt proving the BBP volume and bitcoin volume. The fiat will be transferred to a BiblePay Organization registered bank, which is registered to the corporation with the same tax-id number. Within 30 days, a biblepay foundation check will be written to the vendor. If the process is violated by a boardmember, a board meeting will be called with the remaining members with a petition to remove that boardmember permanently.<br />
<br />
== Spork and Release Signing ==<br />
<br />
When a developer has access to the spork/release keys, the lead developer will cross-train the co developers on the configuration management and release process. If a co-developer attempts to create an unauthorized release, or is reported for any malicious activity, the remaining developers will notify the biblepay Foundation and a board meeting will be called recommending the developer be stripped of github permissions. If this happens, the foundation will request that new keypairs be made, and the remaining developers will receive the new keys and a new developer will be chosen.<br />
<br />
== Vendor Relationships ==<br />
<br />
When we are approached by a new vendor, one of our boardmembers will be tasked to perform due diligence on the vendor. The boardmember will verify the authenticity of the vendors service and financial information and integrity. If a complaint arises accusing the boardmember of fraud, embezzlement, nepotism, or corruption, a board meeting will be called to investigate the specific case. The other boardmembers will be charged in summarizing if this was a genuine case of corruption. If the boardmember is found guilty by the board, a recommendation to remove the boardmember will be called.<br />
<br />
== Taxes ==<br />
<br />
All revenue and expense transactions will be recorded in a Microsoft SQL Server using the accountability.biblepay.org web pages created for the Foundation. Liquidated BBP for a vendor will be recorded as a transaction, PDF receipts will be stored in the SAN, and checks written to vendors in fiat will be recorded as transactions. All transactions will be recorded with the Biblepay Foundation Tax-ID number.<br />
<br />
At the end of the fiscal year, biblepay will pay an accountant to create and file a professional tax return which will be available for public viewing on our accountability web site. <br />
<br />
<br />
== Data Backups ==<br />
<br />
Since the Biblepay Foundation will have the need for copies of documents, tax returns, and transactions for years after they are recorded to protect for cases of audit, the data will be backed up and stored offsite in case of catastrophe. <br />
<br />
== Disaster Recovery ==<br />
<br />
In the case of a disaster, a developer will create a new accountability web site and restore the SQL server backup for the Foundation. <br />
<br />
== Legal Decisions ==<br />
<br />
The BiblePay Foundation will be contacted by attorneys to certify the currency is a utility and not a security, to ensure we are not misrepresenting our currency as an investment, to ensure we are not promising cryptocurrency gains as those are uncertain, to ensure all of our payments we state have been made to the vendors stated, to ensure all biblepay liquidated has been liquidated to fiat as stated, to audit our tax returns, and for consultation for new features among other things. Therefore our boardmembers will be expected to understand the entire scope of current cryptocurrency issues and have the ability to assess advanced problems and solutions to the best of their ability. <br />
<br />
The bylaws will contain clauses that show that each boardmember must legally make decisions in the best interests of BiblePay DAO, and not in their own interests. It is therefore the boardmembers who will make legal decisions and represent the BiblePay DAO publically. The board will refer to the governance committee for any decisions that affect the entire community that could be discussed as a multiple path problem.<br />
<br />
<br />
[[Category:Governance]]</div>Sunk818https://wiki.biblepay.org/index.php?title=Main_Page&diff=6092Main Page2019-02-21T16:34:50Z<p>Sunk818: </p>
<hr />
<div>{| class="wikitable" style="text-align:center; margin-left:2em"<br />
|| BIBLEPAY || 10% Charity, Masternodes (Sanctuaries), ASIC-Resistant, CPU-Mining, 10% to Orphans<br />
|-<br />
|| Mint || Decentralized Proof Of Work<br />
|-<br />
|| Launch Date || August 2017<br />
|-<br />
|| Developed by || Robert Andrews<br />
|-<br />
|| Ticker || BBP<br />
|-<br />
|| Plural || Biblepays<br />
|-<br />
|| Subunit || mBBP =0.001<br />
|-<br />
|| Lowest Unit || 0.00000001 = 1 BBP<br />
|-<br />
|| Operating System || Windows, Linux, macOS<br />
|-<br />
|| Algorithm || Proof-of-BibleHash<br />
|-<br />
|| Current Version || Client v1.0.2.9 mandatory<br />
|-<br />
|| Release Date || July 23rd, 2017<br />
|-<br />
|| Blocktime || avg 7 Minutes<br />
|-<br />
|| Reward || 20,000 Decreasing by 1.5% per month (Approx 19% per year)<br />
|}<br />
<br />
<br />
<p>'''NAME:''' BIBLEPAY</p><br />
<br />
<br />
<p>'''LAUNCH DATE:''' JULY 23, 2017 at 17:00:00 CST</p><br />
<br />
<p>'''BLOCK TARGET RATE:''' 7 MINUTES</p><br />
<br />
<p>'''ALGORITHM:''' PROOF OF BIBLEHASH (POBh) ** NEW **</p><br />
<br />
<p>First coin with the KJV Bible compiled in the source, and utilizing the Bible in the hashing algorithm, while spreading the gospel throughout the IT community. The blocks also hash to chained bible verses.</p><br />
<br />
<p>'''TRANSACTION SPEED:''' SUPPORTS INSTANTSEND</p><br />
<p>'''MASTERNODE(SANCTUARY) SUPPORT:''' Supported after Christmas 2017</p><br />
<p>'''SANCTUARY SUBSIDY BREAKDOWN:''' 10% TO CHARITY, 10% TO MASTERNODES, 80% TO MINER</p><br />
<p>'''FORUM:''' [http://bitcointalk.org/topic=2042657 Bitcointalk]</p><br />
<p>'''Backup Forum:'''[http://forum.biblepay.org/ forum.biblepay.org]</p><br />
<p>'''BLOCK EXPLORER:'''[https://biblepay-explorer.org/ biblepay-explorer.org]</p><br />
<p>'''BLOCK EXPLORER:'''[http://explorer.biblepay.org:3001/ explorer.biblepay.org]</p><br />
<p>'''SOURCE CODE:'''[http://github.com/biblepay/biblepay Github]</p><br />
<p>'''WEB SITE:'''[http://biblepay.org biblepay.org]</p><br />
<p>'''EXCHANGES:'''[https://c-cex.com/?p=bbp-btc c-cex]</p><br />
<p>'''[https://www.southxchange.com/Market/Book/BBP/BTC]</p><br />
<br />
<p>'''TICKER:''' BBP</p><br />
<p>'''Exchange Go Live Date:''' August 15th 2017</p><br />
<p>'''PREMINE:''' NONE</p><br />
<p>'''ICO:''' NONE</p><br />
<p>'''INCONSISTENT REWARDS:''' NONE</p><br />
<p>'''CIRCULATION CHARACTERISTIC:''' DEFLATIONARY</p><br />
<p>'''CIRCULATION RATE:''' DECREASE BY 10% PER YEAR</p><br />
<p>'''TOTAL CIRCULATION:''' 5.2 BILLION BY 2050, DECREASING BY 18% PER YEAR</p><br />
<br />
<p>'''DESCRIPTION:'''</p><br />
<p>A secure blockchain benefiting those in distress - 10% of the emission goes to sponsoring Orphans, with provable contributions, expenses contributed to [http://compassion.com http://compassion.com] - and future charities that are more than 75% efficient. ** NOTE: THE COIN HAS RPC COMMANDS THAT PROVE 100% OF CONTRIBUTIONS ARE SPENT THE WAY INTENDED **</p> <br />
<br />
<br />
<p>Proof of Work has been replaced with Proof Of Biblehash (POBh) - an algorithm that compensates full nodes participation, while preventing GPUs and ASIC by requiring full blockchain transaction referencing in the hashing function, along with chained bible verses. This means biblepay subsidizes full nodes that stay online.</p><br />
<br />
<p>Seven minute block targets minimize the blockchain file size, yet BiblePay does support Dash's instantsend for speedy transactions. MasterNodes (called Sanctuaries) will come online after Christmas, allowing all expenses to be voted on and approved.</p><br />
<p>Expense receipts, to prove the sponshorship of new orphans, will be accessible from inside the wallet and we will even provide phone numbers for auditors to prove </p><br />
100% charity expenditures. (From the rpc, type &#39;run contribution&#39; to see the tithes into the foundation for a time period, and to see the outgoing sponsorship click the wallets &#39;Accountability&#39; button to see a list of orphans, expenses, sponsorship dates, amounts, and the charity phone number, and txid).<br />
<br />
<p>For the first 6 months, 10% of each block will be allocated to the foundation, for sponsoring orphans at 100%. Once per month, we will cash in anything over $40 available on an exchange, and sponsor orphans on our volunteer time. After the sanctuaries go live, the 10% tithe will be diverted to an ongoing budget with DAO governance, voting, allowing the coin to function as a dectralized autonomous charity; at that point the lead dev and volunteers will become a normal part of the community allowing the coin to run by itself.</p><br />
<br />
<p>To avoid wasting energy on meaningless SHA hashing, (or mining), biblepay introduces the BibleHash algorithm, that allows biblepay to <br />
run on common commodity PCs, since the algorithm is resistant to porting to video cards and ASICs and is resistant to running in non-full node environments.</p><br />
<p>In addition to the low energy requirements and high efficiency of POB, the reward per block is set to be relative to the length of time the block took to solve, <br />
(meaning that abusive hash attacks result in subsidy decreases).</p><br />
<p>The network will be high efficiency with low total energy consumption, and the charities sponsored must also be high efficiency (over 75%).<br />
Next, we are deflationary, meaning that we start by issuing a larger amount of coins per block, and each year we tighten the supply by 18%.</p><br />
<br />
The schedule is here: (205 blocks per day, 7 minute block targets):<br />
EMISSION SCHEDULE PROJECTION: http://wiki.biblepay.org/Emission_Schedule<br />
<br />
<p>The block reward breakdown is as follows:</p><br />
<br />
ECONOMICS: http://wiki.biblepay.org/Economics<br />
<br />
<br />
<p>After our sanctuaries go live, we allocate 10% of each block subsidy to our governance committe (a DAO), automatically, with 100% of that being<br />
spent on charity. <br />
<br />
Over time, our sanctuaries will become a charity governance committee, to allow our community to take over the day to day operations of the charity: voting on where the money is spent, how much is spent.<br />
This way, we will not be centralized.</p><br />
<br />
<p>We only partner with charities over 75% efficient, meaning over 75% reach the end-user.</p><br />
<br />
<br />
<p>'''<span style="color:#ff0000">NO PREMINE:</span>'''</p><br />
<p>the lead dev starts with zero, the orphan foundation fund starts with zero, the distribution is entirely fair. NO ICO. The distribution curve is evenly declining with no hidden bumps early.<br />
The self-governance committee and masternode payments are deliberately delayed until Christmas, to allow people to prepare and save up the initial requirement. Running a sanctuary is open to anyone.<br />
The lead dev will sponsor the first 10 orphans out of his own pocket.</p><br />
<p>'''<span style="color:#ff0000">Accountability:</span></p><br />
<p>The wallet will have a reconciliation page built in at go live, to show all charitable income and expenses.</p><br />
<p>The expenses will be auditable - to prove the money actually was spent on orphans.</p><br />
<p>This will be accomplished through the use of : an RPC audit command that tallies the orphan income from the blockchain, and secondly, an API connection to a database that stores the Compassion expenses (until sanctuaries go live), with auditable backing contact info for each expense. We will also provide a web page with pictures of the sponsored orphans clicable from the wallet to show our investors what good we are doing. And finally- we will maintain a copy of receipts in order to maintain 100% accountability.</p><br />
<p>Future Feature: Pay to Preach, in wallet ineractive prayer rooms.</p><br />
<br />
'''ROADMAP:'''<br />
JULY-DECEMBER 2017: GO LIVE, SPONSOR ORPHANS MONTHLY<br />
<br />
JANUARY 2018: MASTERNODES (SANCTUARIES) GO LIVE<br />
<br />
FEBRUARY 2018: MARKETING, IN WALLET PRAYERS<br />
<br />
MAY 2018: MARKET BIBLEPAY AS A 401K ALTERNATIVE<br />
<br />
[[:Category:Roadmap|More roadmap details]]<br />
<br />
'''Novel distinct features of BiblePay:'''<br />
<br />
<p>Proof of Bible Hash algorithm (POBh), getblockinfo shows the chained bible verses required to solve the block, sending money exposes a Tithe checkbox - allowing 10% to be gifted to the orphan foundation, wallet has an in-wallet prayer system, allowing a user to send out a prayer request to the network or store prayers in the chain for the community to pray for from the overview page, Transactions support in-chain messages, Instant Send, Voting, Decentralized Automated Charity Governance Committee, Repentance of Sins, Contributing to the orphan foundation checkbox, and reading the sin list and various staple prayers in wallet.</p></div>Sunk818https://wiki.biblepay.org/index.php?title=Main_Page&diff=6091Main Page2019-02-21T16:34:10Z<p>Sunk818: </p>
<hr />
<div>{| class="wikitable" style="text-align:center; margin-left:2em"<br />
|| BIBLEPAY || 10% Charity, Masternodes (Sanctuaries), ASIC-Resistant, CPU-Mining, 10% to Orphans<br />
|-<br />
|| Mint || Decentralized Proof Of Work<br />
|-<br />
|| Launch Date || August 2017<br />
|-<br />
|| Developed by || Robert Andrews<br />
|-<br />
|| Ticker || BBP<br />
|-<br />
|| Plural || Biblepays<br />
|-<br />
|| Subunit || mBBP =0.001<br />
|-<br />
|| Lowest Unit || 0.00000001 = 1 BBP<br />
|-<br />
|| Operating System || Windows, Linux, macOS<br />
|-<br />
|| Algorithm || Proof-of-BibleHash<br />
|-<br />
|| Current Version || Client v1.0.2.9 mandatory<br />
|-<br />
|| Release Date || July 23rd, 2017<br />
|-<br />
|| Blocktime || avg 7 Minutes<br />
|-<br />
|| Reward || 20,000 Decreasing by 1.5% per month (Approx 19% per year)<br />
|}<br />
<br />
<br />
<p>'''NAME:''' BIBLEPAY</p><br />
<br />
<br />
<p>'''LAUNCH DATE:''' JULY 23, 2017 at 17:00:00 CST</p><br />
<br />
<p>'''BLOCK TARGET RATE:''' 7 MINUTES</p><br />
<br />
<p>'''ALGORITHM:''' PROOF OF BIBLEHASH (POBh) ** NEW **</p><br />
<br />
<p>First coin with the KJV Bible compiled in the source, and utilizing the Bible in the hashing algorithm, while spreading the gospel throughout the IT community. The blocks also hash to chained bible verses.</p><br />
<br />
<p>'''TRANSACTION SPEED:''' SUPPORTS INSTANTSEND</p><br />
<p>'''MASTERNODE(SANCTUARY) SUPPORT:''' Supported after Christmas 2017</p><br />
<p>'''SANCTUARY SUBSIDY BREAKDOWN:''' 10% TO CHARITY, 10% TO MASTERNODES, 80% TO MINER</p><br />
<p>'''FORUM:''' [http://bitcointalk.org/topic=2042657 Bitcointalk]</p><br />
<p>'''Backup Forum:'''[http://forum.biblepay.org/ forum.biblepay.org]</p><br />
<p>'''BLOCK EXPLORER:'''[https://biblepay-explorer.org/ biblepay-explorer.org]</p><br />
<p>'''BLOCK EXPLORER:'''[http://explorer.biblepay.org:3001/ explorer.biblepay.org]</p><br />
<p>'''SOURCE CODE:'''[http://github.com/biblepay/biblepay Github]</p><br />
<p>'''WEB SITE:'''[http://biblepay.org biblepay.org]</p><br />
<p>'''EXCHANGES:'''[https://c-cex.com/?p=bbp-btc c-cex]</p><br />
<p>'''[https://www.southxchange.com/Market/Book/BBP/BTC]</p><br />
<br />
<p>'''TICKER:''' BBP</p><br />
<p>'''Exchange Go Live Date:''' August 15th 2017</p><br />
<p>'''PREMINE:''' NONE</p><br />
<p>'''ICO:''' NONE</p><br />
<p>'''INCONSISTENT REWARDS:''' NONE</p><br />
<p>'''CIRCULATION CHARACTERISTIC:''' DEFLATIONARY</p><br />
<p>'''CIRCULATION RATE:''' DECREASE BY 10% PER YEAR</p><br />
<p>'''TOTAL CIRCULATION:''' 5.2 BILLION BY 2050, DECREASING BY 18% PER YEAR</p><br />
<br />
<p>'''DESCRIPTION:'''</p><br />
<p>A secure blockchain benefiting those in distress - 10% of the emission goes to sponsoring Orphans, with provable contributions, expenses contributed to [http://compassion.com http://compassion.com] - and future charities that are more than 75% efficient. ** NOTE: THE COIN HAS RPC COMMANDS THAT PROVE 100% OF CONTRIBUTIONS ARE SPENT THE WAY INTENDED **</p> <br />
<br />
<br />
<p>Proof of Work has been replaced with Proof Of Biblehash (POBh) - an algorithm that compensates full nodes participation, while preventing GPUs and ASIC by requiring full blockchain transaction referencing in the hashing function, along with chained bible verses. This means biblepay subsidizes full nodes that stay online.</p><br />
<br />
<p>Seven minute block targets minimize the blockchain file size, yet BiblePay does support Dash's instantsend for speedy transactions. MasterNodes (called Sanctuaries) will come online after Christmas, allowing all expenses to be voted on and approved.</p><br />
<p>Expense receipts, to prove the sponshorship of new orphans, will be accessible from inside the wallet and we will even provide phone numbers for auditors to prove </p><br />
100% charity expenditures. (From the rpc, type &#39;run contribution&#39; to see the tithes into the foundation for a time period, and to see the outgoing sponsorship click the wallets &#39;Accountability&#39; button to see a list of orphans, expenses, sponsorship dates, amounts, and the charity phone number, and txid).<br />
<br />
<p>For the first 6 months, 10% of each block will be allocated to the foundation, for sponsoring orphans at 100%. Once per month, we will cash in anything over $40 available on an exchange, and sponsor orphans on our volunteer time. After the sanctuaries go live, the 10% tithe will be diverted to an ongoing budget with DAO governance, voting, allowing the coin to function as a dectralized autonomous charity; at that point the lead dev and volunteers will become a normal part of the community allowing the coin to run by itself.</p><br />
<br />
<p>To avoid wasting energy on meaningless SHA hashing, (or mining), biblepay introduces the BibleHash algorithm, that allows biblepay to <br />
run on common commodity PCs, since the algorithm is resistant to porting to video cards and ASICs and is resistant to running in non-full node environments.</p><br />
<p>In addition to the low energy requirements and high efficiency of POB, the reward per block is set to be relative to the length of time the block took to solve, <br />
(meaning that abusive hash attacks result in subsidy decreases).</p><br />
<p>The network will be high efficiency with low total energy consumption, and the charities sponsored must also be high efficiency (over 75%).<br />
Next, we are deflationary, meaning that we start by issuing a larger amount of coins per block, and each year we tighten the supply by 18%.</p><br />
<br />
The schedule is here: (205 blocks per day, 7 minute block targets):<br />
EMISSION SCHEDULE PROJECTION: http://wiki.biblepay.org/Emission_Schedule<br />
<br />
<p>The block reward breakdown is as follows:</p><br />
<br />
ECONOMICS: http://wiki.biblepay.org/Economics<br />
<br />
<br />
<p>After our sanctuaries go live, we allocate 10% of each block subsidy to our governance committe (a DAO), automatically, with 100% of that being<br />
spent on charity. <br />
<br />
Over time, our sanctuaries will become a charity governance committee, to allow our community to take over the day to day operations of the charity: voting on where the money is spent, how much is spent.<br />
This way, we will not be centralized.</p><br />
<br />
<p>We only partner with charities over 75% efficient, meaning over 75% reach the end-user.</p><br />
<br />
<br />
<p>'''<span style="color:#ff0000">NO PREMINE:</span>'''</p><br />
<p>the lead dev starts with zero, the orphan foundation fund starts with zero, the distribution is entirely fair. NO ICO. The distribution curve is evenly declining with no hidden bumps early.<br />
The self-governance committee and masternode payments are deliberately delayed until Christmas, to allow people to prepare and save up the initial requirement. Running a sanctuary is open to anyone.<br />
The lead dev will sponsor the first 10 orphans out of his own pocket.</p><br />
<p>'''<span style="color:#ff0000">Accountability:</span></p><br />
<p>The wallet will have a reconciliation page built in at go live, to show all charitable income and expenses.</p><br />
<p>The expenses will be auditable - to prove the money actually was spent on orphans.</p><br />
<p>This will be accomplished through the use of : an RPC audit command that tallies the orphan income from the blockchain, and secondly, an API connection to a database that stores the Compassion expenses (until sanctuaries go live), with auditable backing contact info for each expense. We will also provide a web page with pictures of the sponsored orphans clicable from the wallet to show our investors what good we are doing. And finally- we will maintain a copy of receipts in order to maintain 100% accountability.</p><br />
<p>Future Feature: Pay to Preach, in wallet ineractive prayer rooms.</p><br />
<br />
<p>'''ROADMAP:'''</p><br />
JULY-DECEMBER 2017: GO LIVE, SPONSOR ORPHANS MONTHLY<br />
<br />
JANUARY 2018: MASTERNODES (SANCTUARIES) GO LIVE<br />
<br />
FEBRUARY 2018: MARKETING, IN WALLET PRAYERS<br />
<br />
MAY 2018: MARKET BIBLEPAY AS A 401K ALTERNATIVE<br />
<br />
[[:Category:Roadmap|More roadmap details]]<br />
<br />
<p>Novel distinct features of BiblePay:</p><br />
<br />
<p>Proof of Bible Hash algorithm (POBh), getblockinfo shows the chained bible verses required to solve the block, sending money exposes a Tithe checkbox - allowing 10% to be gifted to the orphan foundation, wallet has an in-wallet prayer system, allowing a user to send out a prayer request to the network or store prayers in the chain for the community to pray for from the overview page, Transactions support in-chain messages, Instant Send, Voting, Decentralized Automated Charity Governance Committee, Repentance of Sins, Contributing to the orphan foundation checkbox, and reading the sin list and various staple prayers in wallet.</p></div>Sunk818https://wiki.biblepay.org/index.php?title=Main_Page&diff=6090Main Page2019-02-21T16:30:12Z<p>Sunk818: </p>
<hr />
<div>{| class="wikitable" style="text-align:center; margin-left:2em"<br />
|| BIBLEPAY || 10% Charity, Masternodes (Sanctuaries), ASIC-Resistant, CPU-Mining, 10% to Orphans<br />
|-<br />
|| Mint || Decentralized Proof Of Work<br />
|-<br />
|| Launch Date || August 2017<br />
|-<br />
|| Developed by || Robert Andrews<br />
|-<br />
|| Ticker || BBP<br />
|-<br />
|| Plural || Biblepays<br />
|-<br />
|| Subunit || mBBP =0.001<br />
|-<br />
|| Lowest Unit || 0.00000001 = 1 BBP<br />
|-<br />
|| Operating System || Windows, Linux, macOS<br />
|-<br />
|| Algorithm || Proof-of-BibleHash<br />
|-<br />
|| Current Version || Client v1.0.2.9 mandatory<br />
|-<br />
|| Release Date || July 23rd, 2017<br />
|-<br />
|| Blocktime || avg 7 Minutes<br />
|-<br />
|| Reward || 20,000 Decreasing by 1.5% per month (Approx 19% per year)<br />
|}<br />
<br />
<br />
<p>'''NAME:''' BIBLEPAY</p><br />
<br />
<br />
<p>'''LAUNCH DATE:''' JULY 23, 2017 at 17:00:00 CST</p><br />
<br />
<p>'''BLOCK TARGET RATE:''' 7 MINUTES</p><br />
<br />
<p>'''ALGORITHM:''' PROOF OF BIBLEHASH (POBh) ** NEW **</p><br />
<br />
<p>First coin with the KJV Bible compiled in the source, and utilizing the Bible in the hashing algorithm, while spreading the gospel throughout the IT community. The blocks also hash to chained bible verses.</p><br />
<br />
<p>'''TRANSACTION SPEED:''' SUPPORTS INSTANTSEND</p><br />
<p>'''MASTERNODE(SANCTUARY) SUPPORT:''' Supported after Christmas 2017</p><br />
<p>'''SANCTUARY SUBSIDY BREAKDOWN:''' 10% TO CHARITY, 10% TO MASTERNODES, 80% TO MINER</p><br />
<p>'''FORUM:''' [http://bitcointalk.org/topic=2042657 Bitcointalk]</p><br />
<p>'''Backup Forum:'''[http://forum.biblepay.org/ forum.biblepay.org]</p><br />
<p>'''BLOCK EXPLORER:'''[https://biblepay-explorer.org/ biblepay-explorer.org]</p><br />
<p>'''BLOCK EXPLORER:'''[http://explorer.biblepay.org:3001/ explorer.biblepay.org]</p><br />
<p>'''SOURCE CODE:'''[http://github.com/biblepay/biblepay Github]</p><br />
<p>'''WEB SITE:'''[http://biblepay.org biblepay.org]</p><br />
<p>'''EXCHANGES:'''[https://c-cex.com/?p=bbp-btc c-cex]</p><br />
<p>'''[https://www.southxchange.com/Market/Book/BBP/BTC]</p><br />
<br />
<p>'''TICKER:''' BBP</p><br />
<p>'''Exchange Go Live Date:''' August 15th 2017</p><br />
<p>'''PREMINE:''' NONE</p><br />
<p>'''ICO:''' NONE</p><br />
<p>'''INCONSISTENT REWARDS:''' NONE</p><br />
<p>'''CIRCULATION CHARACTERISTIC:''' DEFLATIONARY</p><br />
<p>'''CIRCULATION RATE:''' DECREASE BY 10% PER YEAR</p><br />
<p>'''TOTAL CIRCULATION:''' 5.2 BILLION BY 2050, DECREASING BY 18% PER YEAR</p><br />
<br />
<p>'''DESCRIPTION:'''</p><br />
<p>A secure blockchain benefiting those in distress - 10% of the emission goes to sponsoring Orphans, with provable contributions, expenses contributed to [http://compassion.com http://compassion.com] - and future charities that are more than 75% efficient. ** NOTE: THE COIN HAS RPC COMMANDS THAT PROVE 100% OF CONTRIBUTIONS ARE SPENT THE WAY INTENDED **</p> <br />
<br />
<br />
<p>Proof of Work has been replaced with Proof Of Biblehash (POBh) - an algorithm that compensates full nodes participation, while preventing GPUs and ASIC by requiring full blockchain transaction referencing in the hashing function, along with chained bible verses. This means biblepay subsidizes full nodes that stay online.</p><br />
<br />
<p>Seven minute block targets minimize the blockchain file size, yet BiblePay does support Dash's instantsend for speedy transactions. MasterNodes (called Sanctuaries) will come online after Christmas, allowing all expenses to be voted on and approved.</p><br />
<p>Expense receipts, to prove the sponshorship of new orphans, will be accessible from inside the wallet and we will even provide phone numbers for auditors to prove </p><br />
100% charity expenditures. (From the rpc, type &#39;run contribution&#39; to see the tithes into the foundation for a time period, and to see the outgoing sponsorship click the wallets &#39;Accountability&#39; button to see a list of orphans, expenses, sponsorship dates, amounts, and the charity phone number, and txid).<br />
<br />
<p>For the first 6 months, 10% of each block will be allocated to the foundation, for sponsoring orphans at 100%. Once per month, we will cash in anything over $40 available on an exchange, and sponsor orphans on our volunteer time. After the sanctuaries go live, the 10% tithe will be diverted to an ongoing budget with DAO governance, voting, allowing the coin to function as a dectralized autonomous charity; at that point the lead dev and volunteers will become a normal part of the community allowing the coin to run by itself.</p><br />
<br />
<p>To avoid wasting energy on meaningless SHA hashing, (or mining), biblepay introduces the BibleHash algorithm, that allows biblepay to <br />
run on common commodity PCs, since the algorithm is resistant to porting to video cards and ASICs and is resistant to running in non-full node environments.</p><br />
<p>In addition to the low energy requirements and high efficiency of POB, the reward per block is set to be relative to the length of time the block took to solve, <br />
(meaning that abusive hash attacks result in subsidy decreases).</p><br />
<p>The network will be high efficiency with low total energy consumption, and the charities sponsored must also be high efficiency (over 75%).<br />
Next, we are deflationary, meaning that we start by issuing a larger amount of coins per block, and each year we tighten the supply by 18%.</p><br />
<br />
The schedule is here: (205 blocks per day, 7 minute block targets):<br />
EMISSION SCHEDULE PROJECTION: http://wiki.biblepay.org/Emission_Schedule<br />
<br />
<p>The block reward breakdown is as follows:</p><br />
<br />
ECONOMICS: http://wiki.biblepay.org/Economics<br />
<br />
<br />
<p>After our sanctuaries go live, we allocate 10% of each block subsidy to our governance committe (a DAO), automatically, with 100% of that being<br />
spent on charity. <br />
<br />
Over time, our sanctuaries will become a charity governance committee, to allow our community to take over the day to day operations of the charity: voting on where the money is spent, how much is spent.<br />
This way, we will not be centralized.</p><br />
<br />
<p>We only partner with charities over 75% efficient, meaning over 75% reach the end-user.</p><br />
<br />
<br />
<p>'''<span style="color:#ff0000">NO PREMINE:</span>'''</p><br />
<p>the lead dev starts with zero, the orphan foundation fund starts with zero, the distribution is entirely fair. NO ICO. The distribution curve is evenly declining with no hidden bumps early.<br />
The self-governance committee and masternode payments are deliberately delayed until Christmas, to allow people to prepare and save up the initial requirement. Running a sanctuary is open to anyone.<br />
The lead dev will sponsor the first 10 orphans out of his own pocket.</p><br />
<p>'''<span style="color:#ff0000">Accountability:</span></p><br />
<p>The wallet will have a reconciliation page built in at go live, to show all charitable income and expenses.</p><br />
<p>The expenses will be auditable - to prove the money actually was spent on orphans.</p><br />
<p>This will be accomplished through the use of : an RPC audit command that tallies the orphan income from the blockchain, and secondly, an API connection to a database that stores the Compassion expenses (until sanctuaries go live), with auditable backing contact info for each expense. We will also provide a web page with pictures of the sponsored orphans clicable from the wallet to show our investors what good we are doing. And finally- we will maintain a copy of receipts in order to maintain 100% accountability.</p><br />
<p>Future Feature: Pay to Preach, in wallet ineractive prayer rooms.</p><br />
<br />
<p>'''ROADMAP:'''</p><br />
JULY-DECEMBER 2017: GO LIVE, SPONSOR ORPHANS MONTHLY<br />
<br />
JANUARY 2018: MASTERNODES (SANCTUARIES) GO LIVE<br />
<br />
FEBRUARY 2018: MARKETING, IN WALLET PRAYERS<br />
<br />
MAY 2018: MARKET BIBLEPAY AS A 401K ALTERNATIVE<br />
<br />
[[Category:Roadmap|More roadmap details]]<br />
<br />
<p>Novel distinct features of BiblePay:</p><br />
<br />
<p>Proof of Bible Hash algorithm (POBh), getblockinfo shows the chained bible verses required to solve the block, sending money exposes a Tithe checkbox - allowing 10% to be gifted to the orphan foundation, wallet has an in-wallet prayer system, allowing a user to send out a prayer request to the network or store prayers in the chain for the community to pray for from the overview page, Transactions support in-chain messages, Instant Send, Voting, Decentralized Automated Charity Governance Committee, Repentance of Sins, Contributing to the orphan foundation checkbox, and reading the sin list and various staple prayers in wallet.</p></div>Sunk818https://wiki.biblepay.org/index.php?title=Category:Roadmap&diff=6089Category:Roadmap2019-02-21T16:29:47Z<p>Sunk818: Created page with "These are the roadmap documents on this wiki"</p>
<hr />
<div>These are the roadmap documents on this wiki</div>Sunk818https://wiki.biblepay.org/index.php?title=Roadmap&diff=6087Roadmap2019-02-21T16:14:55Z<p>Sunk818: Sunk818 moved page Roadmap to 2018 Q4 Roadmap Update without leaving a redirect</p>
<hr />
<div><br />
<br />
<br />
<table class=wikitable><br />
<br />
<br />
<br />
<tr><th class="th1">BIBLEPAY ROADMAP</th><th colspan=3 class="th1">Helping over 131 Orphans Globally and supporting Hope For Widows</th></tr><br />
<tr><th>Milestone Name</th><th>Milestone Notes</th><th>Milestone Deadline</th><th>Milestone Progress</th></tr><br />
<br />
<br />
<tr><td>Biblepay Goes Live<td>Creating a Sanctuary Economy aligned with Jesus' Principles<td>June 30th, 2017<br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td></tr><br />
<br />
<br />
<tr><td>Sponsoring Orphans<td>Partnering with Compassion, we sponsor orphans through the blockchain<td>July 1st, 2017<br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td></tr><br />
<br />
<tr><td>Sanctuary (Masternodes) Based Governance Committee<br />
<td>Our Sanctuaries form a true Decentralized-Autonomous Charity (DAC)<br />
<td>December 25th, 2017<br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td></tr><br />
<br />
<br />
<br />
<br />
<tr><td>In Wallet Prayer System, Gospel Links<td>Our gospel links reward those that watch edifying Christian videos<br />
<td>March 1st, 2018<br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td><br />
</tr><br />
<br />
<br />
<br />
<tr><td>Partnership with BLOOM<td>Helping 13 additional orphans in Uganda and Sierra Leone<br />
<td>March 1st, 2018</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td><br />
</tr><br />
<br />
<br />
<br />
<tr><td>Proof-Of-Distributed Computing<br />
<td>Cancer Research diverts mining waste heat towards true Research<br />
<td>March 28th, 2018</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td><br />
</tr><br />
<br />
<br />
<br />
<br />
<tr><td>Unbanked Cancer Mining<td>Helping those in third world countries buy groceries with Mobile Phone Mining<br />
<td>April 30th, 2018</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td><br />
</tr><br />
<br />
<br />
<br />
<br />
<tr><td>Marketing Campaigns<td>Phase 1 (Reddit, Facebook, Google)<br />
<td>September 30th, 2018<br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td><br />
</tr><br />
<br />
<br />
<br />
<br />
<br />
<tr><td>Stratis Integration Phase 1 (UI Phase)<br />
<td>Provide a Proof-of-Concept for Stratis Integration (Biblepayd-stratis, syncing to the best block in biblepayd-stratis) - COMPLETE<br />
<td>September 30th, 2018</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td><br />
</tr><br />
<br />
<br />
<br />
<tr><td>Mobile Phone Wallet<td>MIPs iPhone and Android Wallet (Both iPhone and Android are complete - Android deployed to Prod - iPhone waiting for Apple to approve deployment)<br />
<td>November 30th, 2018<br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">90%</div></td><br />
</tr><br />
<br />
<tr><td>Proof-Of-Giving<br />
<td>BiblePay launches Proof-Of-Giving, a novel POW/POS type mining algorithm with integrated pool - rewarding payments based on how generous miners are who tithe to our Orphan Foundation<br />
<td>Feb 25th, 2019</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td><br />
</tr><br />
<br />
<br />
<br />
<br />
<br />
<tr><td>BiblePay IPFS Integration and feature set<br />
<td>BiblePay adds the ability to store IPFS documents and business objects. At this point, we can store expenses, orphans, revenue and gospel links.<br />
<td>March 31st, 2019</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td><br />
</tr><br />
<br />
<br />
<br />
<br />
<tr><td>BiblePay Evolution (Dash) Rebase<br />
<td>BiblePay merges and releases all of the Evolution codebase - and re-launches as BiblePay Evolution.<br />
<td>June 30th, 2019</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:5%">5%</div></td><br />
</tr><br />
<br />
<br />
<tr><td>BiblePay Subway/Walmart Integration in Pool.biblepay.org<br />
<td>We give users the capability to buy Subway gift cards with BiblePay!<br />
<td>June 30th, 2019</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:95%">95%</div></td><br />
</tr><br />
<br />
<br />
<br />
<br />
<tr><td>Marketing Campaigns<td>Phase 2 (Proposal for PR Campaign, Language Translations, Co-advertising with partners, Faucet giveaways)<br />
<td>September 30th, 2019<br />
<td><div class="w3-container w3-blue w3-round-large" style="width:35%">7%&nbsp;</div></td><br />
</tr><br />
<br />
<br />
<br />
<br />
<tr><td>BiblePay IPFS Integration Phase II<br />
<td>We add an IPFS DNS server, regional QOS, IPFS voting, and an IPFS user object.<br />
<td>September 30th, 2019</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:5%">5%</div></td><br />
</tr><br />
<br />
<br />
<br />
<tr><td>Market Biblepay as a Utility<td><br />
BiblePay is working on an IPFS revenue stream derived from leasing fees generated by storing documents in IPFS hosted with BiblePay.<br />
This cements BiblePay as a Utility.<br />
<td>December 25th, 2019</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:20%">0%&nbsp;</div></td><br />
</tr><br />
<br />
<tr><td>Biblepay Debit Card<td>Partnership with VISA/MasterCard/or Generic Branded Debit Card<br />
<td>December 25th, 2019</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:25%">1%&nbsp;</div></td><br />
</tr><br />
<br />
<tr><td>E-Commerce Integration<td>Integration with Retailers accepting Biblepay plug-in<br />
<td>December 25th, 2020</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:25%">25%&nbsp;</div></td><br />
</tr><br />
<br />
<br />
</table><br />
<br />
[[Category:Roadmap]]</div>Sunk818https://wiki.biblepay.org/index.php?title=2018_Q1_Roadmap_Update&diff=60862018 Q1 Roadmap Update2019-02-21T16:13:36Z<p>Sunk818: Sunk818 moved page Gant1 to 2018 Q1 Roadmap Update without leaving a redirect</p>
<hr />
<div>== 2018 March Roadmap ==<br />
<br />
<table class=wikitable><br />
<tr><th class="th1">BIBLEPAY ROADMAP</th><th colspan=3 class="th1">Helping over 200 Orphans Globally</th></tr><br />
<br />
<tr><th>Milestone Name</th><th>Milestone Notes</th><th>Milestone Deadline</th><th>Milestone Progress</th></tr><br />
<br />
<tr><td>Biblepay Goes Live<td>Creating a Sanctuary Economy aligned with Jesus' Principles<td>June 30th, 2017<br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td></tr><br />
<br />
<tr><td>Sponsoring Orphans<td>Partnering with Compassion, we sponsor orphans through the blockchain<td>July 1st, 2017<br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td></tr><br />
<br />
<tr><td>Sanctuary (Masternodes) Based Governance Committe <br />
<td>Our Sanctuaries form a true Decentralized-Autonomous Charity (DAC)<br />
<td>December 25th, 2017<br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td></tr><br />
<br />
<tr><td>In Wallet Prayer System, Gospel Links<td>Biblepay University<br />
<td>March 1st, 2018<br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td><br />
</tr><br />
<br />
<tr><td>E-Commerce Integration<td>In-Wallet purchases through Amazon<br />
<td>March 1st, 2018</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td><br />
</tr><br />
<br />
<tr><td>Partnership with BLOOM<td>Helping 13 additional orphans in Uganda and Sierra Leone<br />
<td>March 1st, 2018</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td><br />
</tr><br />
<br />
<tr><td>Proof-Of-Distributed Computing<br />
<td>Cancer Research diverts mining waste heat towards true Research<br />
<td>March 28th, 2018</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:75%">75%</div></td><br />
</tr><br />
<br />
<tr><td>Partnership with Cameroon-One<td>Helping 10-20 additional orphans in Cameroon Africa<br />
<td>April 30th, 2018</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:40%">40%</div></td><br />
</tr><br />
<br />
<tr><td>Marketing Campaigns<td>Phase 1 (Reddit, Facebook, Google)<br />
<td>September 30th, 2018<br />
<td><div class="w3-container w3-blue w3-round-large" style="width:20%">50%</div></td><br />
</tr><br />
<br />
<tr><td>Stratis Integration Phase 1 (UI Phase)<br />
<td>Provide a Proof-of-Concept for Stratis Integration (Windows Wallet UI only)<br />
<td>September 30th, 2018</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:20%">10%</div></td><br />
</tr><br />
<br />
<tr><td>Help community members in distress<td>Features to provide help for BBP users in distress<br />
<td>December 25th, 2018<br />
<td><div class="w3-container w3-blue w3-round-large" style="width:20%">1%</div></td><br />
</tr><br />
<br />
<tr><td>Marketing Campaigns<td>Phase 2 (Proposal for PR Campaign, Language Translations)<br />
<td>December 25th, 2018<br />
<td><div class="w3-container w3-blue w3-round-large" style="width:20%">5%&nbsp;</div></td><br />
</tr><br />
<br />
<tr><td>Stratis Integration Phase 2 (Blockchain Phase)<br />
<td>Provide a Proof-of-Concept for Stratis Blockchain Integration (Windows UI Wallet Syncing with Stratis)<br />
<td>December 30th, 2018</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:20%">1%</div></td><br />
</tr><br />
<br />
<tr><td>Market Biblepay as a Deflationary Currency<td><br />
Make inroads into businesses seeking to add exposure to cryptocurrencies inside 401k plans<br />
<td>December 25th, 2019</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:20%">0%&nbsp;</div></td><br />
</tr><br />
<br />
<tr><td>Biblepay Debit Card<td>Partnership with VISA based Debit Card<br />
<td>December 25th, 2019</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:20%">0%&nbsp;</div></td><br />
</tr><br />
<br />
<tr><td>E-Commerce Integration<td>Integration with Retailers accepting Biblepay plug-in<br />
<td>December 25th, 2019</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:45%">45%&nbsp;</div></td><br />
</tr><br />
<br />
</table><br />
<br />
<br />
[[Category:Roadmap]]</div>Sunk818https://wiki.biblepay.org/index.php?title=2018_Q1_Roadmap_Update&diff=60832018 Q1 Roadmap Update2019-02-21T16:08:06Z<p>Sunk818: </p>
<hr />
<div>== 2018 March Roadmap ==<br />
<br />
<table class=wikitable><br />
<tr><th class="th1">BIBLEPAY ROADMAP</th><th colspan=3 class="th1">Helping over 200 Orphans Globally</th></tr><br />
<br />
<tr><th>Milestone Name</th><th>Milestone Notes</th><th>Milestone Deadline</th><th>Milestone Progress</th></tr><br />
<br />
<tr><td>Biblepay Goes Live<td>Creating a Sanctuary Economy aligned with Jesus' Principles<td>June 30th, 2017<br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td></tr><br />
<br />
<tr><td>Sponsoring Orphans<td>Partnering with Compassion, we sponsor orphans through the blockchain<td>July 1st, 2017<br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td></tr><br />
<br />
<tr><td>Sanctuary (Masternodes) Based Governance Committe <br />
<td>Our Sanctuaries form a true Decentralized-Autonomous Charity (DAC)<br />
<td>December 25th, 2017<br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td></tr><br />
<br />
<tr><td>In Wallet Prayer System, Gospel Links<td>Biblepay University<br />
<td>March 1st, 2018<br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td><br />
</tr><br />
<br />
<tr><td>E-Commerce Integration<td>In-Wallet purchases through Amazon<br />
<td>March 1st, 2018</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td><br />
</tr><br />
<br />
<tr><td>Partnership with BLOOM<td>Helping 13 additional orphans in Uganda and Sierra Leone<br />
<td>March 1st, 2018</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td><br />
</tr><br />
<br />
<tr><td>Proof-Of-Distributed Computing<br />
<td>Cancer Research diverts mining waste heat towards true Research<br />
<td>March 28th, 2018</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:75%">75%</div></td><br />
</tr><br />
<br />
<tr><td>Partnership with Cameroon-One<td>Helping 10-20 additional orphans in Cameroon Africa<br />
<td>April 30th, 2018</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:40%">40%</div></td><br />
</tr><br />
<br />
<tr><td>Marketing Campaigns<td>Phase 1 (Reddit, Facebook, Google)<br />
<td>September 30th, 2018<br />
<td><div class="w3-container w3-blue w3-round-large" style="width:20%">50%</div></td><br />
</tr><br />
<br />
<tr><td>Stratis Integration Phase 1 (UI Phase)<br />
<td>Provide a Proof-of-Concept for Stratis Integration (Windows Wallet UI only)<br />
<td>September 30th, 2018</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:20%">10%</div></td><br />
</tr><br />
<br />
<tr><td>Help community members in distress<td>Features to provide help for BBP users in distress<br />
<td>December 25th, 2018<br />
<td><div class="w3-container w3-blue w3-round-large" style="width:20%">1%</div></td><br />
</tr><br />
<br />
<tr><td>Marketing Campaigns<td>Phase 2 (Proposal for PR Campaign, Language Translations)<br />
<td>December 25th, 2018<br />
<td><div class="w3-container w3-blue w3-round-large" style="width:20%">5%&nbsp;</div></td><br />
</tr><br />
<br />
<tr><td>Stratis Integration Phase 2 (Blockchain Phase)<br />
<td>Provide a Proof-of-Concept for Stratis Blockchain Integration (Windows UI Wallet Syncing with Stratis)<br />
<td>December 30th, 2018</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:20%">1%</div></td><br />
</tr><br />
<br />
<tr><td>Market Biblepay as a Deflationary Currency<td><br />
Make inroads into businesses seeking to add exposure to cryptocurrencies inside 401k plans<br />
<td>December 25th, 2019</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:20%">0%&nbsp;</div></td><br />
</tr><br />
<br />
<tr><td>Biblepay Debit Card<td>Partnership with VISA based Debit Card<br />
<td>December 25th, 2019</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:20%">0%&nbsp;</div></td><br />
</tr><br />
<br />
<tr><td>E-Commerce Integration<td>Integration with Retailers accepting Biblepay plug-in<br />
<td>December 25th, 2019</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:45%">45%&nbsp;</div></td><br />
</tr><br />
<br />
</table><br />
<br />
<br />
[[Category:Roadmap]]</div>Sunk818https://wiki.biblepay.org/index.php?title=2018_Q1_Roadmap_Update&diff=60822018 Q1 Roadmap Update2019-02-21T16:06:55Z<p>Sunk818: added header</p>
<hr />
<div>== 2018 March Roadmap ==<br />
<br />
<br />
<br />
<table class=wikitable><br />
<br />
<br />
<br />
<tr><th class="th1">BIBLEPAY ROADMAP</th><th colspan=3 class="th1">Helping over 200 Orphans Globally</th></tr><br />
<tr><th>Milestone Name</th><th>Milestone Notes</th><th>Milestone Deadline</th><th>Milestone Progress</th></tr><br />
<br />
<br />
<tr><td>Biblepay Goes Live<td>Creating a Sanctuary Economy aligned with Jesus' Principles<td>June 30th, 2017<br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td></tr><br />
<br />
<br />
<tr><td>Sponsoring Orphans<td>Partnering with Compassion, we sponsor orphans through the blockchain<td>July 1st, 2017<br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td></tr><br />
<br />
<tr><td>Sanctuary (Masternodes) Based Governance Committe <br />
<td>Our Sanctuaries form a true Decentralized-Autonomous Charity (DAC)<br />
<td>December 25th, 2017<br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td></tr><br />
<br />
<br />
<br />
<br />
<tr><td>In Wallet Prayer System, Gospel Links<td>Biblepay University<br />
<td>March 1st, 2018<br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td><br />
</tr><br />
<br />
<br />
<br />
<br />
<tr><td>E-Commerce Integration<td>In-Wallet purchases through Amazon<br />
<td>March 1st, 2018</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td><br />
</tr><br />
<br />
<br />
<tr><td>Partnership with BLOOM<td>Helping 13 additional orphans in Uganda and Sierra Leone<br />
<td>March 1st, 2018</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:100%">100%</div></td><br />
</tr><br />
<br />
<br />
<br />
<tr><td>Proof-Of-Distributed Computing<br />
<td>Cancer Research diverts mining waste heat towards true Research<br />
<td>March 28th, 2018</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:75%">75%</div></td><br />
</tr><br />
<br />
<br />
<br />
<br />
<tr><td>Partnership with Cameroon-One<td>Helping 10-20 additional orphans in Cameroon Africa<br />
<td>April 30th, 2018</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:40%">40%</div></td><br />
</tr><br />
<br />
<br />
<br />
<br />
<tr><td>Marketing Campaigns<td>Phase 1 (Reddit, Facebook, Google)<br />
<td>September 30th, 2018<br />
<td><div class="w3-container w3-blue w3-round-large" style="width:20%">50%</div></td><br />
</tr><br />
<br />
<br />
<br />
<br />
<br />
<tr><td>Stratis Integration Phase 1 (UI Phase)<br />
<td>Provide a Proof-of-Concept for Stratis Integration (Windows Wallet UI only)<br />
<td>September 30th, 2018</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:20%">10%</div></td><br />
</tr><br />
<br />
<br />
<br />
<br />
<br />
<tr><td>Help community members in distress<td>Features to provide help for BBP users in distress<br />
<td>December 25th, 2018<br />
<td><div class="w3-container w3-blue w3-round-large" style="width:20%">1%</div></td><br />
</tr><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<tr><td>Marketing Campaigns<td>Phase 2 (Proposal for PR Campaign, Language Translations)<br />
<td>December 25th, 2018<br />
<td><div class="w3-container w3-blue w3-round-large" style="width:20%">5%&nbsp;</div></td><br />
</tr><br />
<br />
<br />
<br />
<tr><td>Stratis Integration Phase 2 (Blockchain Phase)<br />
<td>Provide a Proof-of-Concept for Stratis Blockchain Integration (Windows UI Wallet Syncing with Stratis)<br />
<td>December 30th, 2018</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:20%">1%</div></td><br />
</tr><br />
<br />
<br />
<tr><td>Market Biblepay as a Deflationary Currency<td><br />
Make inroads into businesses seeking to add exposure to cryptocurrencies inside 401k plans<br />
<td>December 25th, 2019</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:20%">0%&nbsp;</div></td><br />
</tr><br />
<br />
<tr><td>Biblepay Debit Card<td>Partnership with VISA based Debit Card<br />
<td>December 25th, 2019</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:20%">0%&nbsp;</div></td><br />
</tr><br />
<br />
<tr><td>E-Commerce Integration<td>Integration with Retailers accepting Biblepay plug-in<br />
<td>December 25th, 2019</td><br />
<td><div class="w3-container w3-blue w3-round-large" style="width:45%">45%&nbsp;</div></td><br />
</tr><br />
<br />
<br />
</table><br />
<br />
<br />
[[Category:Roadmap]]</div>Sunk818https://wiki.biblepay.org/index.php?title=The_Gentiles_Were_Grafted_In&diff=6081The Gentiles Were Grafted In2019-02-21T16:05:47Z<p>Sunk818: </p>
<hr />
<div><br />
<br />
<html><br />
<br />
<body><br />
<br />
<br />
<p><br />
<br />
(Romans 11:11-31)<br />
<br />
So I ask, did they [the Jews] stumble in order that they might fall?<br />
<p><br />
By no means! Rather, through their trespass salvation has come to the Gentiles,<br />
so as to make Israel jealous.<br />
<br />
<p><br />
(Romans 11:12)<br />
Now if their trespass means riches for the world, and if their failure means riches for the Gentiles, how much more will their full inclusion mean!<br />
<p><br />
(Romans 11:13)<br />
Now I am speaking to you Gentiles.<br />
Inasmuch then as I am an apostle to the Gentiles,<br />
I magnify my ministry<br />
<p><br />
(Romans 11:14)<br />
in order somehow to make my fellow Jews jealous, and thus save some of them.<br />
<p><br />
For if their rejection means the reconciliation of the world, what will their acceptance mean but life from the dead?<br />
If the dough offered as firstfruits is holy, so is the whole lump, and if the root is holy, so are the branches.<br />
<p><br />
(Romans 11:17)<br />
But if some of the branches were broken off, and you, although a wild olive shoot, were grafted in among the others and now share in the nourishing root<br />
of the olive tree,<br />
do not be arrogant toward the branches.<br />
If you are, remember it is not you who support the root, but the root that supports you.<br />
(Romans 11:19)<br />
Then you will say,<br />
“Branches were broken off so that I might be grafted in.”<br />
That is true.<br />
They were broken off because of their unbelief, but you stand fast through faith.<br />
<p><br />
So do not become proud, but fear.<br />
For if God did not spare the natural branches, neither will he spare you.<br />
<p><br />
(Romans 11:22)<br />
Note then the kindness and the severity of God: severity toward those who have fallen, but God's kindness to you,<br />
<p><br />
provided you continue in his kindness. Otherwise you too will be cut off.<br />
(Romans 11:23)<br />
And even they, if they do not continue in their unbelief, will be grafted in, for God has the power to graft them in again.<br />
For if you were cut from what is by nature a wild olive tree, and grafted, contrary to nature, into a cultivated olive tree, how much more will these,<br />
(Romans 11:24)<br />
the natural branches, be grafted back into their own olive tree.<br />
<br />
<p><br />
<br />
<h3><br />
The Mystery of Israel's Salvation<br />
</h3><br />
<br />
<p><br />
Lest you be wise in your own sight, I do not want you to be unaware of this mystery,<br />
brothers:<br />
a partial hardening has come upon Israel, until the fullness of the Gentiles has come in.<br />
<p><br />
(Romans 11:26)<br />
And in this way all Israel will be saved, as it is written,<br />
“The Deliverer will come from Zion,<br />
he will banish ungodliness from Jacob”;<br />
(Romans 11:27)<br />
“and this will be my covenant with them<br />
when I take away their sins.”<br />
<p><br />
<br />
As regards the gospel, they are enemies for your sake. But as regards election,<br />
they are beloved for the sake of their forefathers.<br />
<p><br />
(Romans 11:29)<br />
For the gifts and the calling of God are irrevocable.<br />
(Romans 11:30)<br />
For just as you were at one time disobedient to God but now have received mercy because of their disobedience,<br />
so they too have now been disobedient in order that by the mercy shown to you they also may now receive mercy.<br />
<br />
<br />
<p><br />
<br />
<br />
<p><br />
<br />
</body><br />
</html><br />
<br />
[[Category:Theology]]</div>Sunk818https://wiki.biblepay.org/index.php?title=Is_Once_Saved_Always_Saved_a_False_Teaching&diff=6080Is Once Saved Always Saved a False Teaching2019-02-20T16:09:11Z<p>Sunk818: </p>
<hr />
<div><br />
<html><br />
<br />
<body><br />
<br />
<h1>Reasons the 'Once Saved, Always Saved' Doctrine is a False Teaching</h1><br />
<p><br />
<br />
<br />
<p><br />
<br />
From the macroscopic perspective, the bible does not teach once saved always saved.<br />
<p><br />
<br />
Most proponents of the theory try to show evidence in the bible (for Once Saved Always Saved), for example:<br />
<ul><br />
<li><br />
In John 10:28-30, Jesus says: "I give them eternal life, and they shall never perish; no one can snatch them out of my hand. "<br />
and "My Father, who has given them to me, is greater than all; no one can snatch them out of my Father's hand. I and the Father are one."<br />
<p><br />
However, the inability for Satan to snatch us from Jesus' hand simply means that Jesus is more powerful than Satan.<br />
It means that Jesus is the Good Shepherd, who never turns his back on the flock. He always remembers us and will never leave us.<br />
<p><br />
But consider for a moment that Jesus refers to his obedient children, who are keeping his commandments, and that this does not stop one of his flock from leaving him, and backsliding against his commandments.<br />
<p><br />
<li><br />
"I give them Eternal Life, and they shall never perish":<br />
<p><br />
Jesus says he gives us ETERNAL life (the proponents stress ETERNAL, implying that we cannot lose it once we have it).<br />
But consider for a moment that Eternal Life refers to the moment after being judged and arriving in heaven, not when we are born again.<br />
Consider that being born again is the time that we accept Jesus into our lives, and commit to living like he did.<br />
We are then the good children who pick up their cross and follow him Daily.<br />
<p><br />
That view allows the possibility that one may lose their<br />
salvation, if for example, they became a preacher (after being born again) who started blaspheming the Holy Ghost in front of the church. Could this pastor not lose his salvation despite<br />
being born again? Some say, Oh but that is the unpardonable sin.<br />
Yes, then consider the pastor who was born again at the age of 14, who eventually started a church and slowly stole more and more of the church bank account to fund lavish personal material objects, such as jets, and defrauded the church.<br />
That pastor did not blaspheme the Holy Ghost, but certainly did not follow Jesus' examples.<br />
<p><br />
Eternal life is a gift that we do not deserve. We dont achieve eternal salvation all at once when we are saved, we instead promise to walk in Gods way when we are saved, and then<br />
Jesus hands us the gift of eternal life when we are judged by Jesus.<br />
<p>How do you arrive at that conclusion, brother in Christ? The way we arrive at this is by listening to the opinion of over 50 people on YouTube who have toured Heaven and Hell with Jesus (either from an NDE, or a vision, or a dream).<br />
<br />
They lived to tell about the experience, and the solid consensus is that Lukewarm, Unrepetant, and Backslidden Christians have been seen in Hell.<br />
Most of the time, the story behind the Christian is understandable: they were born again early in life, went to church and thought they were saved and forgot to repent of their new sins.<br />
Or, they committed horrible acts, such as the pastor stealing from the church funds. But consider the lukewarm Christian, who uses Christs blood like a playground.<br />
For one, who has neither forgiven others and held grudges, that lukewarm Christians repentences may not have been heard. For another, who was worldly, attended church, but failed to<br />
spread the gospel to a single person (especially her girlfriends).<br />
<p><br />
After watching these on YouTube, I decided my duty was to summarize the theology behind this concept.<br />
<p><br />
<br />
<br />
</li><br />
<p><br />
<br />
As you can see, the above biblical examples have probably been misconstrued - to allow people to believe they can be saved once in some haphazard manner and then sin the rest of their lives.<br />
<p>Unfortunately, many churches use the same logic to maintain revenue (IE a constant revenue base exists).<br />
<p><br />
As you can see, if you have a little patience and realize the meaning may be Eternal Life after being judged, you may decide it is better to live like Paul the apostle did:<br />
"I pummel my body and lead it as a slave".<br />
<p><br />
<br />
</ul><br />
<br />
<br />
<h1><br />
<br />
Moving on, we find real scriptural evidence that Once Saved Always Saved is False.</h1><br />
<p>On a side note, the bible never actually contradicts itself. We as humans misinterpret things.<br />
In our case here, it is more logical to follow what the bible does say about the subject, leading us to believe that we can lose our salvation if we are not Good Christians:<br />
<p><br />
<br />
<ul><br />
<li> The Bible says that maintaining faith requires great effort, a “hard fight.” (Jude 3, 5).<br />
Early Christians who had already accepted Christ were told: “Keep working out your own salvation with fear and trembling.”—Philippians 2:12.<br />
<li><br />
The Bible warns against serious sins that will keep a person from entering God’s Kingdom in 1 Corinthians: (1 Corinthians 6:9-11) Or do you not know that unrighteous people will not inherit God’s Kingdom?<br />
Do not be misled. Those who are sexually immoral, idolaters, adulterers, men who submit to homosexual acts,<br />
men who practice homosexuality,<br />
thieves, greedy people,<br />
drunkards, revilers, and extortioners will not inherit God’s Kingdom.<br />
<li><br />
The Bible warns against other serious sins in (Galatians 5:19-21) that may keep us from entering Heaven:<br />
Now the works of the flesh are plainly seen, and they are sexual immorality, uncleanness, brazen conduct (disrespecting authority), idolatry,<br />
spiritism, hostility, strife, jealousy, fits of anger, dissensions, divisions, sects, envy, drunkenness, wild parties and things like these.<br />
I am forewarning you about these things, the same way I already warned you, that those who practice such things will not inherit God’s Kingdom.<br />
<li><br />
If salvation could not be lost, such warnings would be meaningless. Instead, the Bible shows that someone who has been saved can fall away by returning to a practice of serious sin.<br />
<p><br />
For example, Hebrews 10:26 states: “If we practice sin willfully after having received the accurate knowledge of the truth, there<br />
is no longer any sacrifice for sins left.” (Hebrews 6:4-6;) (2 Peter 2:20-22)<br />
<li><br />
Jesus emphasized the importance of maintaining faith by giving an illustration in which he likened himself to a vine and his followers to branches on that vine.<br />
Some of them would at one time demonstrate faith in him by their fruits, or actions, yet would later fail to do so and be “thrown out like a [fruitless] branch,” losing their salvation. (John 15:1-6)<br />
<li><br />
The apostle Paul used a similar illustration, saying that Christians who do not maintain their faith “will be lopped off.” (Romans 11:17-22).<br />
<li><br />
Christians are commanded to “keep on the watch.” (Matthew 24:42; 25:13).<br />
Those who fall asleep spiritually, whether by practicing “works belonging to darkness” or by not fully performing the works that Jesus commanded, lose their salvation.<br />
(Romans 13:11-13); (Revelation 3:1-3).<br />
<li><br />
Many scriptures show that those who have been saved must still endure faithfully to the end. (Matthew 24:13; Hebrews 10:36; 12:2, 3; Revelation 2:10)<br />
<li><br />
First-century Christians expressed joy when they learned that fellow believers were enduring in their faith. (1 Thessalonians 1:2, 3; 3 John 3, 4)<br />
<li><br />
Does it seem reasonable that the Bible would stress faithful endurance if those who did not endure would be saved anyway?<br />
<li> Only when his death was imminent did the apostle Paul feel that his salvation was assured. (2 Timothy 4:6-8)<br />
<p>Earlier in his life, he recognized that he could still miss out on salvation if he gave in to fleshly desires.<br />
<p><br />
He wrote: “I pummel my body and lead it as a slave, so that after I have preached to others, I myself should not become disapproved somehow.”—1 Corinthians 9:27; Philippians 3:12-14.<br />
<br />
<li><br />
<p>The unrepetant souls. Those who commit sins as a Christian and do not repent.<br />
<li><br />
The unforgiven sins: Those people who hold grudges and do not forgive others risk having Jesus not forgive them for sins.<br />
<li>Pastors, who have been saved, who have blasphemed the Holy Spirit by spreading False Gospel (the unforgivable sin).<br />
These pastors have been seen in hell in NDEs.<br />
<li>Pastors who Have been saved, who have stolen money from the church and have not repented.<br />
<li>NDE list: Those who have seen Christians in Hell.<br />
<br />
<br />
<p> <a target=_blank href=https://www.youtube.com/watch?v=VErocgTw_m8>Dream of lukewarm Christians Going To Hell</a><br />
<a target=_blank href=https://www.youtube.com/watch?v=29i7eRwgaPk>Part II</a><br />
<p><br />
<li><br />
Training Pastors:<br />
<a target=_blank href=https://www.youtube.com/watch?v=yvdOMwYxASk>Paul Washer explains that Pastors should not promise immediate salvation, but instead a long walk with Christ.<br />
</a><br />
<p><br />
<br />
<li><br />
(Matthew 7:21) Not everyone who says Lord Lord will enter the Kingdom of Heaven, but instead those who do the will of my Father.<br />
</li><br />
</ul><br />
<h1><br />
Twenty One Signs of Becoming a Luke Warm Christian (by Pastor Kevin Shale)<br />
(Since you are lukewarm, I will spit you out) (Rev 3:16)</h1><br />
<small><p><a target=_blank href=https://www.youtube.com/watch?v=sBMuUrygRlo>21 Warning Signs of Becoming a Lukewarm Christian (Video)</a><br />
</h1><br />
<br />
<ul><br />
<li><br />
Prayer is Non Existent or Mechanical<br />
<li><br />
You know the word but do not really live it<br />
<li><br />
Thoughts about Eternal matters no longer grip your heart<br />
<li><br />
You indulge in inward and outward sin without feeling devastated<br />
<li>A longing for holiness and being set apart is not a passion<br />
<br />
<br />
<li>The pursuit of money or posessions grossly overshadows your persuit of Christ<br />
<li>You can listen to Worship music or Carnal music without reasoning or justification<br />
<li>You can hear non-Christians mock God or the Church without feeling grieved<br />
<li>Your main concerns are your own pleasures and comforts<br />
<li>You no longer have a deep hunger for God<br />
<li>You no longer live with a full and grateful heart<br />
<li>You have little concern for the souls of others<br />
<li>You always see your own level of spiritiuality in positive terms<br />
<li>You are more concerned with your own pet doctrines than peoples souls<br />
<li>Sports and Entertainment and Toys and Gadgets are to the point of idolatry in your life<br />
<li>You are more concerned with your outward image than your inward spiritual reality<br />
<li>You have a full head of biblical knowledge but a heart of stone<br />
<li>You are driven by the lust of flesh in a major way: Various addictions: Porn or Sexual Sin, Drugs, Gambling, Alcohol etc.<br />
<li>You admire Gods word but see no major commitment to follow it<br />
<li>You go to church to feel good instead of to hear and respond (obedience)<br />
<li>You desperately pursue validation from Men rather than from God<br />
<br />
<br />
<br />
<br />
</body><br />
</html><br />
<br />
[[Category:Theology]]</div>Sunk818https://wiki.biblepay.org/index.php?title=Is_Once_Saved_Always_Saved_a_False_Teaching&diff=6079Is Once Saved Always Saved a False Teaching2019-02-20T15:44:56Z<p>Sunk818: add category</p>
<hr />
<div><br />
<html><br />
<br />
<body><br />
<br />
<h1><br />
Reasons the 'Once Saved, Always Saved' Doctrine is a False Teaching</h1><br />
<p><br />
<br />
<br />
<p><br />
<h3><br />
From the macroscopic perspective, the bible does not teach once saved always saved.<br />
<p><br />
<br />
Most proponents of the theory try to show evidence in the bible (for Once Saved Always Saved), for example:<br />
<ul><br />
<li><br />
In John 10:28-30, Jesus says: "I give them eternal life, and they shall never perish; no one can snatch them out of my hand. "<br />
and "My Father, who has given them to me, is greater than all; no one can snatch them out of my Father's hand. I and the Father are one."<br />
<p><br />
However, the inability for Satan to snatch us from Jesus' hand simply means that Jesus is more powerful than Satan.<br />
It means that Jesus is the Good Shepherd, who never turns his back on the flock. He always remembers us and will never leave us.<br />
<p><br />
But consider for a moment that Jesus refers to his obedient children, who are keeping his commandments, and that this does not stop one of his flock from leaving him, and backsliding against his commandments.<br />
<p><br />
<li><br />
"I give them Eternal Life, and they shall never perish":<br />
<p><br />
Jesus says he gives us ETERNAL life (the proponents stress ETERNAL, implying that we cannot lose it once we have it).<br />
But consider for a moment that Eternal Life refers to the moment after being judged and arriving in heaven, not when we are born again.<br />
Consider that being born again is the time that we accept Jesus into our lives, and commit to living like he did.<br />
We are then the good children who pick up their cross and follow him Daily.<br />
<p><br />
That view allows the possibility that one may lose their<br />
salvation, if for example, they became a preacher (after being born again) who started blaspheming the Holy Ghost in front of the church. Could this pastor not lose his salvation despite<br />
being born again? Some say, Oh but that is the unpardonable sin.<br />
Yes, then consider the pastor who was born again at the age of 14, who eventually started a church and slowly stole more and more of the church bank account to fund lavish personal material objects, such as jets, and defrauded the church.<br />
That pastor did not blaspheme the Holy Ghost, but certainly did not follow Jesus' examples.<br />
<p><br />
Eternal life is a gift that we do not deserve. We dont achieve eternal salvation all at once when we are saved, we instead promise to walk in Gods way when we are saved, and then<br />
Jesus hands us the gift of eternal life when we are judged by Jesus.<br />
<p>How do you arrive at that conclusion, brother in Christ? The way we arrive at this is by listening to the opinion of over 50 people on YouTube who have toured Heaven and Hell with Jesus (either from an NDE, or a vision, or a dream).<br />
<br />
They lived to tell about the experience, and the solid consensus is that Lukewarm, Unrepetant, and Backslidden Christians have been seen in Hell.<br />
Most of the time, the story behind the Christian is understandable: they were born again early in life, went to church and thought they were saved and forgot to repent of their new sins.<br />
Or, they committed horrible acts, such as the pastor stealing from the church funds. But consider the lukewarm Christian, who uses Christs blood like a playground.<br />
For one, who has neither forgiven others and held grudges, that lukewarm Christians repentences may not have been heard. For another, who was worldly, attended church, but failed to<br />
spread the gospel to a single person (especially her girlfriends).<br />
<p><br />
After watching these on YouTube, I decided my duty was to summarize the theology behind this concept.<br />
<p><br />
<br />
<br />
</li><br />
<p><br />
<br />
As you can see, the above biblical examples have probably been misconstrued - to allow people to believe they can be saved once in some haphazard manner and then sin the rest of their lives.<br />
<p>Unfortunately, many churches use the same logic to maintain revenue (IE a constant revenue base exists).<br />
<p><br />
As you can see, if you have a little patience and realize the meaning may be Eternal Life after being judged, you may decide it is better to live like Paul the apostle did:<br />
"I pummel my body and lead it as a slave".<br />
<p><br />
<br />
</ul><br />
<br />
<br />
<h1><br />
<br />
Moving on, we find real scriptural evidence that Once Saved Always Saved is False.</h1><br />
<p>On a side note, the bible never actually contradicts itself. We as humans misinterpret things.<br />
In our case here, it is more logical to follow what the bible does say about the subject, leading us to believe that we can lose our salvation if we are not Good Christians:<br />
<p><br />
<h3><br />
<ul><br />
<li> The Bible says that maintaining faith requires great effort, a “hard fight.” (Jude 3, 5).<br />
Early Christians who had already accepted Christ were told: “Keep working out your own salvation with fear and trembling.”—Philippians 2:12.<br />
<li><br />
The Bible warns against serious sins that will keep a person from entering God’s Kingdom in 1 Corinthians: (1 Corinthians 6:9-11) Or do you not know that unrighteous people will not inherit God’s Kingdom?<br />
Do not be misled. Those who are sexually immoral, idolaters, adulterers, men who submit to homosexual acts,<br />
men who practice homosexuality,<br />
thieves, greedy people,<br />
drunkards, revilers, and extortioners will not inherit God’s Kingdom.<br />
<li><br />
The Bible warns against other serious sins in (Galatians 5:19-21) that may keep us from entering Heaven:<br />
Now the works of the flesh are plainly seen, and they are sexual immorality, uncleanness, brazen conduct (disrespecting authority), idolatry,<br />
spiritism, hostility, strife, jealousy, fits of anger, dissensions, divisions, sects, envy, drunkenness, wild parties and things like these.<br />
I am forewarning you about these things, the same way I already warned you, that those who practice such things will not inherit God’s Kingdom.<br />
<li><br />
If salvation could not be lost, such warnings would be meaningless. Instead, the Bible shows that someone who has been saved can fall away by returning to a practice of serious sin.<br />
<p><br />
For example, Hebrews 10:26 states: “If we practice sin willfully after having received the accurate knowledge of the truth, there<br />
is no longer any sacrifice for sins left.” (Hebrews 6:4-6;) (2 Peter 2:20-22)<br />
<li><br />
Jesus emphasized the importance of maintaining faith by giving an illustration in which he likened himself to a vine and his followers to branches on that vine.<br />
Some of them would at one time demonstrate faith in him by their fruits, or actions, yet would later fail to do so and be “thrown out like a [fruitless] branch,” losing their salvation. (John 15:1-6)<br />
<li><br />
The apostle Paul used a similar illustration, saying that Christians who do not maintain their faith “will be lopped off.” (Romans 11:17-22).<br />
<li><br />
Christians are commanded to “keep on the watch.” (Matthew 24:42; 25:13).<br />
Those who fall asleep spiritually, whether by practicing “works belonging to darkness” or by not fully performing the works that Jesus commanded, lose their salvation.<br />
(Romans 13:11-13); (Revelation 3:1-3).<br />
<li><br />
Many scriptures show that those who have been saved must still endure faithfully to the end. (Matthew 24:13; Hebrews 10:36; 12:2, 3; Revelation 2:10)<br />
<li><br />
First-century Christians expressed joy when they learned that fellow believers were enduring in their faith. (1 Thessalonians 1:2, 3; 3 John 3, 4)<br />
<li><br />
Does it seem reasonable that the Bible would stress faithful endurance if those who did not endure would be saved anyway?<br />
<li> Only when his death was imminent did the apostle Paul feel that his salvation was assured. (2 Timothy 4:6-8)<br />
<p>Earlier in his life, he recognized that he could still miss out on salvation if he gave in to fleshly desires.<br />
<p><br />
He wrote: “I pummel my body and lead it as a slave, so that after I have preached to others, I myself should not become disapproved somehow.”—1 Corinthians 9:27; Philippians 3:12-14.<br />
<br />
<li><br />
<p>The unrepetant souls. Those who commit sins as a Christian and do not repent.<br />
<li><br />
The unforgiven sins: Those people who hold grudges and do not forgive others risk having Jesus not forgive them for sins.<br />
<li>Pastors, who have been saved, who have blasphemed the Holy Spirit by spreading False Gospel (the unforgivable sin).<br />
These pastors have been seen in hell in NDEs.<br />
<li>Pastors who Have been saved, who have stolen money from the church and have not repented.<br />
<li>NDE list: Those who have seen Christians in Hell.<br />
<br />
<br />
<p> <a target=_blank href=https://www.youtube.com/watch?v=VErocgTw_m8>Dream of lukewarm Christians Going To Hell</a><br />
<a target=_blank href=https://www.youtube.com/watch?v=29i7eRwgaPk>Part II</a><br />
<p><br />
<li><br />
Training Pastors:<br />
<a target=_blank href=https://www.youtube.com/watch?v=yvdOMwYxASk>Paul Washer explains that Pastors should not promise immediate salvation, but instead a long walk with Christ.<br />
</a><br />
<p><br />
<br />
<li><br />
(Matthew 7:21) Not everyone who says Lord Lord will enter the Kingdom of Heaven, but instead those who do the will of my Father.<br />
</li><br />
</ul><br />
<h1><br />
Twenty One Signs of Becoming a Luke Warm Christian (by Pastor Kevin Shale)<br />
(Since you are lukewarm, I will spit you out) (Rev 3:16)</h1><br />
<small><p><a target=_blank href=https://www.youtube.com/watch?v=sBMuUrygRlo>21 Warning Signs of Becoming a Lukewarm Christian (Video)</a><br />
</h1><br />
<h3><br />
<ul><br />
<li><br />
Prayer is Non Existent or Mechanical<br />
<li><br />
You know the word but do not really live it<br />
<li><br />
Thoughts about Eternal matters no longer grip your heart<br />
<li><br />
You indulge in inward and outward sin without feeling devastated<br />
<li>A longing for holiness and being set apart is not a passion<br />
<br />
<br />
<li>The pursuit of money or posessions grossly overshadows your persuit of Christ<br />
<li>You can listen to Worship music or Carnal music without reasoning or justification<br />
<li>You can hear non-Christians mock God or the Church without feeling grieved<br />
<li>Your main concerns are your own pleasures and comforts<br />
<li>You no longer have a deep hunger for God<br />
<li>You no longer live with a full and grateful heart<br />
<li>You have little concern for the souls of others<br />
<li>You always see your own level of spiritiuality in positive terms<br />
<li>You are more concerned with your own pet doctrines than peoples souls<br />
<li>Sports and Entertainment and Toys and Gadgets are to the point of idolatry in your life<br />
<li>You are more concerned with your outward image than your inward spiritual reality<br />
<li>You have a full head of biblical knowledge but a heart of stone<br />
<li>You are driven by the lust of flesh in a major way: Various addictions: Porn or Sexual Sin, Drugs, Gambling, Alcohol etc.<br />
<li>You admire Gods word but see no major commitment to follow it<br />
<li>You go to church to feel good instead of to hear and respond (obedience)<br />
<li>You desperately pursue validation from Men rather than from God<br />
<br />
<br />
<br />
<br />
</body><br />
</html><br />
<br />
[[Category:Theology]]</div>Sunk818https://wiki.biblepay.org/index.php?title=Genealogical_Ages&diff=6078Genealogical Ages2019-02-19T17:52:37Z<p>Sunk818: </p>
<hr />
<div><table class=wikitable><br />
<br />
<br />
<br />
<tr><th class="th1">GENEALOGICAL AGES</th><th colspan=3 class="th1">Ages of Man in Genesis</th></tr><br />
<tr><th>Person</th><th>Lifespan</th><th>Year Deceased (BC/AD)</th></tr><br />
<br />
<br />
<tr><td>Adam<td>930<td>4114 BC</tr><br />
<tr><td>Seth<td>912<td>3984 BC</tr><br />
<tr><td>Cainan<td>917<td>3789 BC</tr><br />
<tr><td>Noah<td>950<td>3058 BC</tr><br />
<br />
<tr><td>Shem<td>600<td>2556 BC</tr><br />
<br />
<br />
<br />
<tr><td>Peleg<td>239<td>2357 BC</tr><br />
<br />
<br />
<br />
<tr><td>Abram<td>175<td>2107 BC</tr><br />
<tr><td>Jacob<td>147<td>2021 BC</tr><br />
<br />
<tr><td>Moses<td>120<td>1407 BC</tr><br />
<br />
<br />
<tr><td>King David<td>70<td>971 BC</tr><br />
<tr><td>Saint John<td>93<td>100 AD</tr><br />
<br />
</table><br />
<br />
<br />
<table class=wikitable id="q-graph"><caption>Age Trend</caption><br />
<tr><br />
<th class="sent">Lifespan</th><br />
</tr><br />
<br />
<tr class="qtr" id="q1"><br />
<th scope="row">4114 BC</th><br />
<td class="sent bar" style="height: 290px;"><p>930</p></td><br />
</tr><br />
<tr class="qtr" id="q2"><br />
<th scope="row">3058 BC</th><br />
<td class="sent bar" style="height: 299px;"><p>950</p></td><br />
</tr><br />
<tr class="qtr" id="q3"><br />
<th scope="row">2556 BC</th><br />
<td class="sent bar" style="height: 155px;"><p>600</p></td><br />
</tr><br />
<tr class="qtr" id="q4"><br />
<th scope="row">971 BC</th><br />
<td class="sent bar" style="height: 40px;"><p>70</p></td><br />
</tr><br />
<br />
<br />
<br />
</table><br />
<br />
<div id="ticks"><br />
<div class="tick" style="height: 59px;"><p>1000</p></div><br />
<div class="tick" style="height: 59px;"><p>800</p></div><br />
<div class="tick" style="height: 59px;"><p>600</p></div><br />
<div class="tick" style="height: 59px;"><p>250</p></div><br />
<div class="tick" style="height: 59px;"><p>100</p></div><br />
<br />
</div><br />
<br />
[[Category:Theology]]</div>Sunk818https://wiki.biblepay.org/index.php?title=Jesus_Concise_Commandments&diff=6077Jesus Concise Commandments2019-02-19T17:52:13Z<p>Sunk818: </p>
<hr />
<div><br />
<html><br />
<br />
<body><br />
<br />
<br />
<br />
<h1><br />
Jesus' Commandments by Samuel Mills<br />
<br />
</h1><br />
<p><br />
<h2><br />
The Commandments of Jesus must not be confused with the “Ten Commandments” in the Old Testament.<br />
</h2><br />
<br />
<p><br />
<h4><br />
<br />
Jesus said, "If ye love me, keep my commandments," (John 14:15, KJV).<br />
<p><br />
<br />
As you study these commandments (orders) of Jesus it will become very clear that God is not only the God of Grace, He is also the God of expectations.<br />
You will also see that obeying the Commandments of Jesus will bring rewards beyond measure.<br />
<p><br />
<br />
For example, “Ye must be born again” (Jn 3:7), is considered to be one of the Commandments of Jesus. Those who obey receive Eternal Life!<br />
<p><br />
The Old Testament Commandments beautifully teach what God considers to be sin, but they require perfection, and no person has ever been perfect (good enough), so it can only bring condemnation.<br />
<p><br />
However, Jesus, being the "Son of God" and therefore perfect, could and did live up to the requirements of the Old Testament Law, and by doing so was qualified to die in the place of all who would accept Him as their Savior.<br />
<p><br />
There is now no condemnation for those who are in Christ Jesus. (Rom 8:1). Jesus paid it all!<br />
<p><br />
<br />
<br />
<br />
<p><br />
<br />
<br />
"The Greatest Commandment"<br />
<p><br />
Jesus was asked: "Teacher, which is the greatest commandment in the Law?" Jesus replied: " 'Love the Lord your God with all your heart and with all your soul and with all your mind.'<br />
This is the first and greatest commandment.<br />
And the second is like it: 'Love your neighbor as yourself.' All the Law and the Prophets hang on these two commandments," (Matt 22:36-40, Amp).<br />
<p><br />
<br />
"The Golden Rule"<br />
<p><br />
"So in everything, do to others what you would have them do to you, for this sums up the Law and the Prophets," ((Matt 7:12 NIV).<br />
<br />
<p><br />
<br />
<br />
Although these Commandments of Jesus are not in numerical order as are the Ten Commandments in the Old Testament, most Bible Scholars agree that they are most assuredly the Commandments of Jesus.<br />
<br />
<br />
<br />
<ul><br />
The Commandments of Jesus From the Four Gospels<br />
<br />
<li><br />
1. "When you stand praying, forgive"<br />
<p><br />
"And when you stand praying, if you hold anything against anyone, forgive him,<br />
so that your Father in heaven may forgive you your sins." But if you <b>do not forgive, neither will your Father who is in heaven forgive your sins." (Mark 11:25-26 NIV)</b><br />
<li><br />
2. "You must be born again"<br />
<p>"You should not be surprised at my saying, 'You must be born again." (John 3:7 KJV)<br />
<br />
<li><br />
<br />
3. "Remain in Me and I will remain in you"<br />
<p><br />
When you ask Jesus into your heart and He becomes your Lord and Savior, the Holy Spirit actually lives in you, and you in Him. Here Jesus uses a grape vine to compare our relationship with Him. "Remain in me, and I will remain in you. No branch can bear fruit by itself; it must remain in the vine. Neither can you bear fruit unless you remain in me." ( John 15:4 NIV)<br />
<li><br />
4. "Let your light shine before men"<br />
<p><br />
"You are the light of the world. A city on a hill cannot be hidden. " In the same way, let your light shine before men, that they may see your good deeds and praise your Father in heaven," (Matt 5:14;16 NIV).<br />
<li><br />
5. "Settle matters quickly with your adversary"<br />
<p><br />
"Settle matters quickly with your adversary who is taking you to court. Do it while you are still with him on the way, or he may hand you over to the judge, and the judge may hand you over to the officer, and you may be thrown into prison." (Matt 5:25 NIV)<br />
<li><br />
6. "Get rid of whatever causes you to sin"<br />
<p><br />
"If your right eye causes you to sin, gouge it out and throw it away. It is better for you to lose one part of your body than for your whole body to be thrown into hell. And if your right hand causes you to sin, cut it off and throw it away. It is better for you to lose one part of your body than for your whole body to go into hell." (Matt 5:29-30 NIV)<br />
<li><br />
7. "Do Not Swear at All"<br />
<p><br />
"But I tell you, Do not swear at all: either by heaven, for it is God's throne; or by the earth, for it is his footstool; or by Jerusalem, for it is the city of the Great King. And do not swear by your head, for you cannot make even one hair white or black. Simply let your 'Yes' be 'Yes,' and your 'No,' 'No'; anything beyond this comes from the evil one," (Matt 5:34-37 KJV).<br />
<li><br />
8. "Do Not Resist an Evil Person"<br />
<p><br />
(Turning the other cheek.)<br />
<br />
"You have heard that it was said, 'Eye for eye, and tooth for tooth.’ But I tell you, Do not resist an evil person. If someone strikes you on the right cheek, turn to him the other also," (Matt 5:38-39 NIV).<br />
<li><br />
9. "Giving More than is Demanded" (Going the extra mile)<br />
<p><br />
"And if someone wants to sue you and take your tunic, let him have your cloak as well. If someone forces you to go one mile, go with him two miles. Give to the one who asks you, and do not turn away from the one who wants to borrow from you," (Matt 5:40-42 NIV).<br />
<li><br />
10. "Love Your Enemies"<br />
<p><br />
"You have heard that it was said, 'Love your neighbor and hate your enemy.' But I tell you: Love your enemies and pray for those who persecute you, that you may be sons of your Father in heaven. He causes his sun to rise on the evil and the good, and sends rain on the righteous and the unrighteous," (Matt 5:43-45 NIV).<br />
<li><br />
11. "Give to Please God, Not to be Seen"<br />
<p><br />
"Be careful not to do your 'acts of righteousness' before men, to be seen by them. If you do, you will have no reward from your Father in heaven," (Matt 6:1 NIV).<br />
<li><br />
12. "Pray Privately, Not to be Seen of Men"<br />
<p><br />
"And when you pray, do not be like the hypocrites, for they love to pray standing in the synagogues and on the street corners to be seen by men. I tell you the truth, they have received their reward in full. But when you pray, go into your room, close the door and pray to your Father, who is unseen. Then your Father, who sees what is done in secret, will reward you. And when you pray, do not keep on babbling like pagans, for they think they will be heard because of their many words,"<br />
(Matt 6:5-7 NIV).<br />
<br />
<li><br />
<br />
13. "This, then, is how you should pray"<br />
<p><br />
"This, then, is how you should pray: " 'Our Father in heaven, hallowed be your name, your kingdom come, your will be done on earth as it is in heaven.<br />
Give us today our daily bread. Forgive us our debts, as we also have forgiven our debtors. And lead us not into temptation, but deliver us from the evil one.'<br />
<p><br />
For if you forgive men when they sin against you, your heavenly Father will also forgive you. But if you do not forgive men their sins, your Father will not forgive your sins," (Matt 6:9-15 NIV).<br />
<li><br />
14. "Fast Without Fanfare"<br />
<p><br />
"When you fast, do not look somber as the hypocrites do, for they disfigure their faces to show men they are fasting. I tell you the truth, they have received their reward in full," (Matt 6:16 NIV).<br />
<li><br />
15. "Do not Store up Treasures on Earth"<br />
<p><br />
"Do not store up for yourselves treasures on earth, where moth and rust destroy, and where thieves break in and steal. But store up for yourselves treasures in heaven, where moth and rust do not destroy, and where thieves do not break in and steal. For where your treasure is, there your heart will be also,"<br />
(Matt 6:19-21 NIV).<br />
<li><br />
16. "Do not Worry about Your Needs"<br />
<p><br />
"Therefore I tell you, do not worry about your life, what you will eat or drink; or about your body, what you will wear. Is not life more important than food, and the body more important than clothes? Look at the birds of the air; they do not sow or reap or store away in barns, and yet your heavenly Father feeds them. Are you not much more valuable than they?" (Matt 6:25-26 NIV). Commandments of Jesus<br />
<li><br />
17. "Do not Worry about Tomorrow"<br />
<p><br />
"Therefore do not worry about tomorrow, for tomorrow will worry about itself. Each day has enough trouble of its own," (Matt 6:34 NIV).<br />
<li><br />
18. "Place God First"<br />
<p><br />
"But seek ye first the kingdom of God, and his righteousness; and all these things shall be added unto you," (Matt 6:33 NIV).<br />
<li><br />
19. "Do not Judge"<br />
<p><br />
"Do not judge, or you too will be judged. For in the same way you judge others, you will be judged, and with the measure you use, it will be measured to you,"<br />
(Matt 7:1-2 NIV).<br />
<li><br />
20. "Guard what is Sacred"<br />
<p><br />
"Do not give dogs what is sacred; do not throw your pearls to pigs. If you do, they may trample them under their feet, and then turn and tear you to pieces,"<br />
(Matt 7:6 NIV).<br />
<li><br />
21. "Ask, Seek, and Knock"<br />
<p><br />
"Ask and it will be given to you; seek and you will find; knock and the door will be opened to you,"<br />
(Matt 7:7 NIV).<br />
<li><br />
22. "Care for Those in Distress"<br />
<p><br />
"Then the King will say to those on his right, 'Come, you who are blessed by my Father; take your inheritance, the kingdom prepared for you since the creation of the world. For I was hungry and you gave me something to eat, I was thirsty and you gave me something to drink, I was a stranger and you invited me in, I needed clothes and you clothed me, I was sick and you looked after me, I was in prison and you came to visit me,"<br />
(Matt 25:34-36 NIV).<br />
<li><br />
23. "Enter Through the Narrow Gate"<br />
<p><br />
"Enter through the narrow gate. For wide is the gate and broad is the road that leads to destruction, and many enter through it. But small is the gate and narrow the road that leads to life, and only a few find it,"<br />
(Matt 7:13-14 NIV).<br />
<li><br />
24. "Watch out for false prophets"<br />
<p><br />
"Watch out for false prophets. They come to you in sheep's clothing, but inwardly they are ferocious wolves," (Matt 7:15 NIV).<br />
<li><br />
25. "Exercise Spiritual Power"<br />
<p><br />
"He called his twelve disciples to him and gave them authority to drive out evil spirits and to heal every disease and sickness," (Matt 10:1 NIV).<br />
<p><br />
"Heal the sick, raise the dead, cleanse those who have leprosy, drive out demons. Freely you have received, freely give," (Matt 10:8 NIV)."<br />
<br />
<br />
<li><br />
26. "Do not Despise Childlike Believers"<br />
<p><br />
"See that you do not look down on one of these little ones. For I tell you that their angels in heaven always see the face of my Father in heaven," (Matt 18:10 NIV). Commandments of Jesus<br />
<li><br />
27. "Do not Exalt Yourself"<br />
<p><br />
"But you are not to be called 'Rabbi,' for you have only one Master and you are all brothers. And do not call anyone on earth 'father,' for you have one Father, and he is in heaven. Nor are you to be called 'teacher,' for you have one Teacher, the Christ. The greatest among you will be your servant. For whoever exalts himself will be humbled, and whoever humbles himself will be exalted," (Matt 23:8-12 NIV).<br />
<li><br />
28. "Settle Disputes Between Believers in this Manner..."<br />
<p><br />
"If your brother sins against you, go and show him his fault, just between the two of you. If he listens to you, you have won your brother over. But if he will not listen, take one or two others along, so that 'every matter may be established by the testimony of two or three witnesses.' If he refuses to listen to them, tell it to the church; and if he refuses to listen even to the church, treat him as you would a pagan or a tax collector,"<br />
(Matt 18:15-17 NIV).<br />
<li><br />
29. "Do not Oppose Other Christian Groups"<br />
<p><br />
"Teacher," said John, "we saw a man driving out demons in your name and we told him to stop, because he was not one of us."<br />
<br />
"Do not stop him," Jesus said. "No one who does a miracle in my name can in the next moment say anything bad about me, for whoever is not against us is for us," (Mark 9:38-40 NIV).<br />
<li><br />
30. "Have Complete Faith in God"<br />
<p><br />
"Have faith in God," Jesus answered. "I tell you the truth, if anyone says to this mountain, 'Go, throw yourself into the sea,' and does not doubt in his heart but believes that what he says will happen, it will be done for him. Therefore I tell you, whatever you ask for in prayer, believe that you have received it, and it will be yours," (Mark 11:22-24 NIV).<br />
<li><br />
31. "Do as the Good Samaritan Did"<br />
<p><br />
"The expert in the law replied, 'The one who had mercy on him.' Jesus told him, "Go and do likewise,"<br />
(Luke 10:30-37 NIV).<br />
<li><br />
32. "Love One Another"<br />
<p><br />
(This commandment of Jesus summarizes all the others.)<br />
<br />
"My command is this: Love each other as I have loved you," (John 15:12 KJV).<br />
<li><br />
33. "Do this in Remembrance of Me"<br />
<p><br />
"And he took bread, gave thanks and broke it, and gave it to them, saying, 'This is my body given for you; do this in remembrance of me.'"<br />
"In the same way, after the supper he took the cup, saying, 'This cup is the new covenant in my blood, which is poured out for you,'" (Luke 22:19-20 NIV).<br />
<li><br />
34. "You Should also Wash One Another's Feet"<br />
<p><br />
"Now that I, your Lord and Teacher, have washed your feet, you also should wash one another's feet,"<br />
(John 13:14 NIV).<br />
<li><br />
35. "Be Merciful"<br />
<p><br />
"Be merciful, just as your Father is merciful,"<br />
(Luke 6:36 NIV).<br />
<li><br />
36. "Go and Make Disciples of All Nations, Baptizing Them"<br />
<p><br />
"Therefore go and make disciples of all nations, baptizing them in the name of the Father and of the Son and of the Holy Spirit, and teaching them to obey everything I have commanded you. And surely I am with you always, to the very end of the age,"<br />
(Matt 28:19-20 NIV).<br />
<li><br />
37. "Obey What I Command"<br />
<p><br />
"If you love me, you will obey what I command,"<br />
(John 14:15 NIV).<br />
<li><br />
38. "You Must be Ready"<br />
<p><br />
"You also must be ready, because the Son of Man will come at an hour when you do not expect him,"<br />
(Luke 12:40 NIV).<br />
<br />
<br />
<br />
<br />
</body><br />
</html><br />
<br />
[[Category:Theology]]</div>Sunk818https://wiki.biblepay.org/index.php?title=Talk:God%27s_Time_Clock_System_Of_Sevens&diff=6076Talk:God's Time Clock System Of Sevens2019-02-18T16:47:50Z<p>Sunk818: Created page with "Mark 13 ESV: No One Knows That Day or Hour 32 "But concerning that day or that hour, no one knows, not even the angels in heaven, nor the Son, but only the Father."</p>
<hr />
<div>Mark 13 ESV:<br />
<br />
No One Knows That Day or Hour<br />
32 "But concerning that day or that hour, no one knows, not even the angels in heaven, nor the Son, but only the Father.</div>Sunk818https://wiki.biblepay.org/index.php?title=God%27s_Time_Clock_System_Of_Sevens&diff=6075God's Time Clock System Of Sevens2019-02-18T16:16:44Z<p>Sunk818: </p>
<hr />
<div><br />
<html><br />
<br />
<body><br />
<br />
<br />
<br />
<ul><h3>God's Clocks</h3><br />
<br />
<h4><br />
<p>Many examples, starting with Genesis in the bible, shows that God works in patterns or series of 7's.<br />
(Six days of work, and one day of rest).<br />
<br />
<h1><b><li><h1>God's Seven Day Week (A week):</b></h1><br />
<p><h4><br />
“In the beginning God created the heavens and the earth.” (Genesis 1:1).<br />
About 6,000 years ago on earth’s very first day God created time, starting with the day.<br />
He said, “the evening and the morning were the first day”. (Genesis 1:5).<br />
For six days God did His work of creating the heavens and the earth. Then God did something completely different.<br />
On the seventh day He stopped creating and rested. He blessed and sanctified the seventh day of the week and He called it the Sabbath.<br />
<p><br />
“On the seventh day God ended His work which He had done, and He rested on the seventh day from all His work which He had done.”<br />
(Genesis 2:2).<br />
“The seventh day is the Sabbath of the LORD your God. In it you shall do no work.” (Exodus 20:10).<br />
So as you can see, the second purpose of the 7th day is a day of worship, keep this day holy in thanks to the LORD.<br />
<br />
<p><br />
<br />
<li><h1>God's Seven Year Pattern (A Sabbath):<br />
<h6><br />
He told the children of Israel to plant and to harvest their land for six years and then let the land rest the seventh year.<br />
<p><br />
He called the seventh year a sabbath. It is also called a sabbatical.<br />
<p><br />
“Six years you shall sow your field, and six years you shall prune your vineyard, and gather its fruit; but in the seventh year there shall be a sabbath of solemn rest for the land, a sabbath to the LORD.<br />
<p><br />
You shall neither sow your field nor prune your vineyard.” (Leviticus 25:3,4).<br />
This seven-year clock started in 1416 BC when God brought the children of Israel into the land of Canaan. (See: When did the children of Israel enter Canaan?)<br />
<p><br />
<br />
“Speak to the children of Israel, and say to them: ‘When you come into the land which I give you, then the land shall keep a sabbath to the LORD.’” (Leviticus 25:2).<br />
This seven-year pattern has been repeating for over 3,000 years.<br />
Six years of working the land are always followed by one year of letting the land rest.<br />
After teachers have taught for six years in a row they are sometimes offered a one-year sabbatical for rest.<br />
<br />
<br />
<br />
<li><h1>God's Seven Thousand Year Clock:<br />
<p><br />
<h6><br />
For almost 6,000 years people have been corrupting the earth by their sins. In 2016 the 6,000 years will be completed and people will be removed from the earth. Then the earth will have a sabbath rest for 1,000 years.<br />
<br />
The seven-thousand-year clock started a few years after creation when Adam and Eve first sinned.<br />
<br />
<br />
<li><h1>God's Seven Sabbaticals Clock - (A Jubliee):<br />
<p><br />
<br />
<h4><br />
Seven sabbaticals brought God’s people to the Jubilee, which is another one-year sabbath.<br />
<p><br />
The Jubilee cycle is a 49-year repeating pattern.<br />
<p><br />
<h4><br />
It consists of seven sabbatical cycles, followed by a 50th year called the Jubilee.<br />
<p><br />
During the Jubilee year the land rests, debts are cancelled, and land is returned to its original owner.<br />
<p><br />
“You shall count seven sabbaths of years for yourself, seven times seven years; and the time of the seven sabbaths of years shall be to you forty-nine years.<br />
<p><br />
Then you shall cause the trumpet of the Jubilee to sound on the tenth day of the seventh month;<br />
on the Day of Atonement you shall make the trumpet to sound throughout all your land.<br />
<p><br />
And you shall consecrate the fiftieth year, and proclaim liberty throughout all the land to all its inhabitants.<br />
It shall be a Jubilee for you.” (Leviticus 25:8-11).<br />
<p><br />
Every seventh sabbatical, on the Day of Atonement, the trumpet announced the start of the Jubilee.<br />
<p><br />
The 50th year Jubilee is also the 1st year of the next Jubilee cycle.<br />
<br />
<br />
<br />
</body><br />
</html><br />
<br />
[[Category:Theology]]</div>Sunk818https://wiki.biblepay.org/index.php?title=Spiritual-Warfare-I&diff=6074Spiritual-Warfare-I2019-02-18T16:16:17Z<p>Sunk818: </p>
<hr />
<div>Spiritual Warfare is nothing to take lightly. It is a serious battle that your spirit will fight within the second Heaven. <br />
<br><br />
<br />
Fighting directly against the Devil opens a door in your life to spiritual attacks. It also gives the enemy a right to attack your family, your pets and your assets.<br />
<br><br />
If you are living in sin, do not attempt this battle, as serious damage may come back to you, as if you are not 'covered', the door will be wide open for the enemy to harm you in any way possible.<br />
<br />
You must not be holding grudges against others, you must not be half in the world, you must not be expirimenting in sinful activities (for example drinking alcohol and attempting to repent), <br />
you must be living a committed life for Jesus and picking up your cross daily. <br />
<br />
<br><br />
Additionally a spiritual battle might last an entire year. You have to count the costs before entering the battle, and realize this battle takes sacrifice and perseverance. <br />
<br />
<ul>Some tips before you decide:<br />
<li>You must not have a judgemental attitude towards pastors, men-of-God, or anyone. The reason I mention this, is the last warfare campaign I was readying for, a few warriors raised an issue with Training Materials being supplied by one of the well known church organizations (that they thought were too materialistic). However the materials themselves were professional, solid and backed by scripture. God told our leader: Tell these people they are judgemental, and not to judge my servants! So please, you must be humble.<br />
<li>Strife: You must not react to people who point the finger at you in a spiteful, or mean spirited way. The devil will test you after you spend days battling his demons. He will do this in your most sensitive areas. One way to get at you is to prod you by choosing an e-mail or a job or a co-worker or anyone to tell you something that "pushes your buttons". The key is to not react (and take the bait). If you do you will invite demons of strife into your life, and you cannot risk that as a warrior of God.<br />
<li>Count the Costs: This battle involves dedicated commitment - of time and energy for consistency in the prayer closet, and, involves sacrifice, because you are being asked to pick up your cross and represent Christ in a Holy way. If you don't believe you will make it to the end, please don't volunteer. This is similar to counting the costs before waging war with a King on the National Level.<br />
<li>You must take the armor of God, the protection and covering prayers and the warfare very seriously. Do not shoddily enter battle without all protection on. This is equivalent to giving the enemy an easy shot at you and could result in severe damage to your health, peace and safety, finances, and life in general.<br />
</ul><br />
<br />
Once you decide that you have what it takes, you have to establish daily cover (cover by a Christian friends prayer, cover by God, cover by the armor and cover by daily prayers); we will explain each of these.<br />
<br />
Before entering into spiritual warfare, you must put on the armor:<br />
<br />
Ephesians 6:10-18:<br />
<br />
10 Finally, my brethren, be strong in the Lord, and in the power of his might.<br />
11 Put on the whole armour of God, that ye may be able to stand against the wiles of the devil.<br />
12 For we wrestle not against flesh and blood, but against principalities, against powers, against the rulers of the darkness of this world, against spiritual wickedness in high places.<br />
13 Wherefore take unto you the whole armour of God, that ye may be able to withstand in the evil day, and having done all, to stand.<br />
14 Stand therefore, having your loins girt about with truth, and having on the breastplate of righteousness;<br />
15 And your feet shod with the preparation of the gospel of peace;<br />
16 Above all, taking the shield of faith, wherewith ye shall be able to quench all the fiery darts of the wicked.<br />
17 And take the helmet of salvation, and the sword of the Spirit, which is the word of God:<br />
18 Praying always with all prayer and supplication in the Spirit, and watching thereunto with all perseverance and supplication for all saints;<br />
<br><br />
<br />
To put on the armor, pray this: Lord, I thank you for your Armor! I put on the Belt of Truth, the Breastplate of Righteousness, the Shoes of Peace, the Shield of Faith, the Helmet of Salvation, and the Sword of the Spirit!<br />
<br />
<ul>The weapons are:<br />
<li> Girdle or Belt of Truth <br />
<li> Breastplate of Righteousness<br />
<li> Shoes of the Preparation of the Gospel of Peace (or Shoes of Peace)<br />
<li> Shield of Faith<br />
<li> Helmet of Salvation<br />
<li> Sword of the Spirit<br />
</ul><br />
<br />
<br><br />
<br />
<br />
See more about the Full Armor of God Here:<br />
https://www.youtube.com/watch?v=lOEYH5SyGfU&feature=youtu.be<br />
<br />
[[Category:Theology]]</div>Sunk818https://wiki.biblepay.org/index.php?title=The_Four_Temples&diff=6073The Four Temples2019-02-18T16:16:00Z<p>Sunk818: </p>
<hr />
<div><br />
<html><br />
<br />
<body><br />
<br />
<br />
<ul>The Temples in Jerusalem<br />
<br />
<li> <span><h1>#1</h1><br />
The first Temple was built in 957 BC by King Solomon. The temple was destroyed in 586 BC by the Babylonians (it lasted just under 300 years).<br />
<br />
<li><h1>#2</h1><br />
The second Temple was built in 538 BC (after the fall of the Babylonian empire), authorized by Cyrus the Great, completed 23 years later during the reign of Darius the Great (March 515 BC).<br />
<p><br />
This temple lasted until 70 AD.<br />
<p><br />
This is the temple that Jesus visited, and drove out the money changers (~27 AD).<br />
<br />
<p><br />
<li><h1>#3</h1><br />
The Third Temple - Not built Yet:<br />
Note that the Temple Institute in Jerusalem already have <a href=http://www.templeinstitute.org/blueprints-for-the-holy-temple.htm>Blueprints</a> drawn to rebuild the temple (the year is now 2018).<br />
<p><br />
The plans are based on the original Second Temple plans.<br />
<p><br />
<br />
Note that (The Temple Institutes) view on Ezekiels Temple, agreeing with the bible, is that Ezekiels Temple will be lowered from Heaven in the Future<br />
(Our Christian view is that Jesus will build this temple, lower it from Heaven and rule from it during his 1000 year Millenial Reign - the period with Satan being bound)<br />
<a href=https://www.templeinstitute.org/future_temple.htm>The Future Temple - The Temple Institute</a><br />
<br />
<p><br />
Note that right now, plans are being finalized at the Temple institute for the third temple based on the architecture of the Second Temple, and this fulfills bible verses,<br />
(Matthew 24:15) The abomination of desolation standing in the most holy place, (Daniel 9:27) He will confirm a convenant with many for one seven; he will stop the sacrifices. (Daniel 12:11) From the time the daily sacrifice is stopped and the abomination of desolation is set up, there will be 1290 days.<br />
<p><br />
These verses allude to the third temple being built so that a peace convenant with many is signed, and the antichrist can be revealed. When all 70 countries surround Israel, a world war will break out,<br />
and this temple will be destroyed in the midst of all the fighting (every country wants Jerusalem).<br />
When Jesus returns, he will destroy and bind Satan.<br />
<p><br />
This brings up the point, that if the purpose of the temple is to worship and to conduct blood sacrifices, and Jesus, being our ultimate sacrifice already died for our sins, why would the current Israelites consider<br />
animal sacrifices in the current day and age? Partially, consider that 80% of the Israelite Jews are non-Christian (they are pure Judaic).<br />
<p><br />
Does the current Rabbi, involved in executing the animal sacrifices for the Temple Institute plan on conducting actual animal sacrifices, and what is his view?<br />
According to Rabbi Rav Kook, the current Rabbi responsible, the temple institute will go back to all of its historical practices of the second temple, that includes animal sacrifices. <a href=http://ravkooktorah.org/VAYIKRA58.htm>See here.</a><br />
<br />
<p><br />
Why is blood sacrifice required for the atonement of sins? <a href= https://www.gotquestions.org/blood-sacrifice.html>See more here on the reason for Blood Sacrifice</a>.<br />
<p><br />
To summarize this situtation, we have the Israelites, a predominantly Judaic group of Non-Christians, desiring the temple to be rebuilt, and approving animal sacrifices. In one sense, it is a slap in the face<br />
to Jesus, as he was the ultimate sacrifice and performed everything necessary for our salvation as sinners. However, it is also Bible Prophecy unfolding that requires this temple to be built in order to usher<br />
in the great falling away, the abomination, the peace covenant with many and the great tribulation. It also sets the stage correctly for Jesus to come and expose the shameful behavior of those who did not believe<br />
in him, allow him to destroy the antichrist and the temple, and bring forth the majestic Fourth temple.<br />
<br />
<li><br />
<h1>#4</h1><br />
The Fourth Temple - The Millenial Temple<br />
<p><br />
<br />
Note that in the book of Ezekiel, (Ez 40-48), Ezekiel lays out the plans from God to build a future temple, but this temple is so majestic,<br />
it requires certain geographic changes in Israel (Mt of Olives needs to be bigger and flatter, the<br />
temple takes up the entire city of Jerusalem, etc).<br />
<br />
<p><br />
The Bible explains that Ezekiels vision describes the temple during the Millenial Reign.<br />
<br />
<a href=http://www.templemount.org/ezektmp.html>(More about Ezekiels Temple here.)</a><br />
<br />
<br />
<p>After the birds eat the flesh of mighty men and Kings, and the bodies are buried, the fourth temple will be lowered from heaven, and the Millenial Reign will be ushered in for our King of Kings: Jesus Christ.<br />
<p><br />
(Isaiah 11:6) And the wolf will dwell with the lamb, and leopard will lie down with the young goat...<br />
<br />
<br />
</body><br />
</html><br />
<br />
[[Category:Theology]]</div>Sunk818https://wiki.biblepay.org/index.php?title=Miracles_In_The_Wilderness&diff=6072Miracles In The Wilderness2019-02-18T16:15:45Z<p>Sunk818: </p>
<hr />
<div><br />
<ul><br />
<br />
<li>An angel of&nbsp;God and a pillar of cloud and fire guarded the multitude <span class="nb">(Exodus 13:21-22; 14:19).</span></li><br />
<br />
<li>A strong wind made a path for the Israelites through the sea <span class="nb">(Exodus 14:21-29).</span></li><br />
<br />
<li>The Egyptian&#39;s chariot wheels were made to swerve; the army was drowned in the sea <br />
<span class="nb">(Exodus 14:25-31)</span></li><br />
<br />
<li>Bitter waters were made sweet and drinkable <span class="nb">(Exodus 15:22-25).</span></li><br />
<br />
<li>Manna rains from heaven for bread. Quail are sent to provide meat<span class="nb">(Exodus 16:4,13-18).</span></li><br />
<br />
<li>Water comes from a rock <span class="nb">(Exodus 17:2-6)</span></li><br />
<br />
<li> Moses&rsquo;s raised hand allows the Israelites to prevail over Amalek <br />
<span class="nb">(Exodus 17:9-13).</span></li><br />
<br />
<li>God speaks from the mountain at Sinai <span class="nb">(Exodus 19:2-6; 16-21)</span></li><br />
<br />
<li>The wind brings the quail (Numbers 11:31)</li><br />
<br />
<li>Miriam&#39;s rebellion and leprosy (Numbers 12:5-10)</li><br />
<br />
<li>The ground opens and swallows Korah (Numbers 16:19-35)</li><br />
<br />
<li>The budding of Aaron&#39;s staff (Numbers 17:1-11)</li><br />
<br />
<li>Water from the rock and Moses&rsquo;s sin (Numbers 20:2-13)</li><br />
<br />
<li>The bronze snake on a pole (Numbers 21:4-9)</li><br />
<br />
<li>The crossing of the Jordan (Joshua 3)</li><br />
<br />
</ul><br />
<br />
[[Category:Theology]]</div>Sunk818https://wiki.biblepay.org/index.php?title=The_Apostles_Creed&diff=6071The Apostles Creed2019-02-18T16:15:32Z<p>Sunk818: </p>
<hr />
<div><br />
<html><br />
<body><br />
<br />
<h2><br />
<p><br />
I believe in God, the Father Almighty,<br />
<p><br />
the Creator of heaven and earth,<br />
<p><br />
and in Jesus Christ, his only Son, our Lord;<br />
<p><br />
Who was conceived by the Holy Spirit,<br />
<p><br />
born of the Virgin Mary,<br />
<p><br />
suffered under Pontius Pilate,<br />
<p><br />
was crucified, died, and was buried.<br />
<p><br />
<br />
He descended to the dead.<br />
<p><br />
The third day he arose again from the dead.<br />
<p><br />
He ascended into heaven<br />
<p><br />
and sits at the right hand of God the Father Almighty,<br />
<p><br />
whence he shall come to judge the living and the dead.<br />
<p><br />
I believe in the Holy Spirit,<br />
<p><br />
the holy universal Church,<br />
<p><br />
the communion of saints,<br />
<p><br />
the forgiveness of sins,<br />
<p><br />
the resurrection of the body,<br />
<p><br />
and the life everlasting.<br />
<p><br />
Amen.<br />
<p><br />
<br />
<br />
</body><br />
</html><br />
<br />
[[Category:Theology]]</div>Sunk818