Generic Smart Contracts - Revision history

Admin at 22:36, 4 March 2021

2021-03-04T22:36:05Z

2019-06-12T17:39:26Z

2019-06-12T17:38:20Z

changed tithe amount and frequency

2019-06-12T17:36:06Z

added how to join project #2 healing

2019-03-25T15:23:14Z

2019-03-25T15:22:33Z

added concepts category

2019-03-25T01:17:52Z

2019-03-25T00:09:40Z

2019-03-25T00:09:22Z

2019-03-25T00:08:52Z

@@ Line 283: / Line 283: @@
   pog_foundationdonation=1000
   This will make your node send 1000 BBP per GSC transmission.
 [[Category:Concepts]]
 [[Category:Evolution]]

@@ Line 274: / Line 274: @@
   The node uses half of your coins by default, once every 24 hours (1 hour in testnet).  To change this, change the key:
-  pog_coinagepercentage=.80
+  pog_coinagepercentage=0.80
   This will make your node use 80% of your coins.
@@ Line 280: / Line 280: @@
 How do I change the default foundation donation amount per day?
-  The node tithes 2.5 BBP every 12 hours by default.  To change this, change the key:
+  The node tithes 2.5 BBP once every 12 hours by default.  To change this, change the key:
   pog_foundationdonation=1000
   This will make your node send 1000 BBP per GSC transmission.

@@ Line 266: / Line 266: @@
 <br>
 How do I know if my node contributed to POG?
   Look for a transaction on the transaction list labeled "GSC transmission"
@@ Line 271: / Line 272: @@
 How do I change the default quantity of coins my node accesses for a GSC transmission?
   The node uses half of your coins by default, once every 24 hours (1 hour in testnet).  To change this, change the key:
   pog_coinagepercentage=.80
@@ Line 277: / Line 279: @@
 How do I change the default foundation donation amount per day?
-  The node tithes 7 BBP per day by default.  To change this, change the key:
   pog_foundationdonation=1000
   This will make your node send 1000 BBP per GSC transmission.

← Older revision		Revision as of 15:22, 25 March 2019
Line 276:		Line 276:
	pog_foundationdonation=1000		pog_foundationdonation=1000
	This will make your node send 1000 BBP per GSC transmission.		This will make your node send 1000 BBP per GSC transmission.
		+
		+	[[Category:Concepts]]

← Older revision		Revision as of 01:17, 25 March 2019
Line 245:		Line 245:
	<br>		<br>
	<br>		<br>
		+	'''RPC COMMANDS'''
		+
		+
		+	<br>
		+
		+	How do I create a CPK (Christian-public-keypair)?
		+	exec cpk nickname
		+
		+
		+	<br>
		+
		+	How do I join Project #1 - POG?
		+
		+	exec join pog
		+
		+	<br>
		+	How do I know if my node contributed to POG?
		+	Look for a transaction on the transaction list labeled "GSC transmission"
		+
		+	<br>
		+
		+	How do I change the default quantity of coins my node accesses for a GSC transmission?
		+	The node uses half of your coins by default, once every 24 hours (1 hour in testnet). To change this, change the key:
		+	pog_coinagepercentage=.80
		+	This will make your node use 80% of your coins.
		+
		+
		+	How do I change the default foundation donation amount per day?
		+	The node tithes 7 BBP per day by default. To change this, change the key:
		+	pog_foundationdonation=1000
		+	This will make your node send 1000 BBP per GSC transmission.

@@ Line 111: / Line 111: @@
 After the release of Evolution, our IT team will continue to develop the Corporate integration, additional new campaigns, and HTML5 integration.
 <br>
 ''' BiblePay Architecture Changes for Reliability, Mass Development and Mass Adoption '''
+<br>
 <br>

← Older revision		Revision as of 00:09, 25 March 2019
Line 100:		Line 100:

	<br>		<br>
		+	<br>
		+
	'''Deployment Timeline and Roadmap changes'''		'''Deployment Timeline and Roadmap changes'''
		+	<br>

@@ Line 108: / Line 108: @@
 After the release of Evolution, our IT team will continue to develop the Corporate integration, additional new campaigns, and HTML5 integration.
 <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:
 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>
 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>
 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.