Difference between revisions of "Nutrition Information"
| Line 48: | Line 48: | ||
<tr><td>Deterministic Sanctuaries <td> <td>X <td>No <td><td></tr> | <tr><td>Deterministic Sanctuaries <td> <td>X <td>No <td><td></tr> | ||
| − | <tr><td>Deflationary Emission schedule <td>X <td>X <td>X <td><td></tr> | + | <tr><td>Deflationary Emission schedule (-19.5% per year compounded)<td>X <td>X <td>X <td><td></tr> |
<tr><td>Benefiting charities in a partially-decentralized way (88 orphans) through vendor liquidations <td>X <td>X <td>No <td><td></tr> | <tr><td>Benefiting charities in a partially-decentralized way (88 orphans) through vendor liquidations <td>X <td>X <td>No <td><td></tr> | ||
Revision as of 17:34, 6 April 2019
- DO NOT SHARE - NOT FOR PUBLIC CONSUMPTION **
| BiblePay Nutritional Information Guide | Helping over 87 Orphans Globally and supporting Hope For Widows | ||||
|---|---|---|---|---|---|
| Description | Feature Available Now | Released in Evolution (June 2019) | Comparison to #25, DogeCoin | Available in December, 2019 | Available in the Future |
| Anti GPU (AES512, BibleHashing, Limited nonces) | X | X | No | ||
| Anti GPU phase 2 (Signed CPKs with ABN weight) | X | No | |||
| Commodity PC Mining (POBH) | X | X | No | ||
| Anti-Asic | X | X | X | ||
| Full Nodes required to mine | X | X | No | ||
| Anti-Botnet (ABN) | X | No | |||
| Data Storage (We can store keys, values, prayers, campaigns, points, and more) | X | X | No | ||
| Daily Generic Smart Contracts | X | No | |||
| Multiple Campaign support for users (POG, Healing) | X | No | |||
| Soft Consensus Business Logic (See: Stable-Prod) | X | No | |||
| Security (POW, POBH, DGW) | X | X | X | ||
| 51% Attack Prevention (ChainLocks) | X | No | |||
| Anti-Fork technology (POW + Dash ChainLocks) | X | No | |||
| Reliable Prod Environment (Limited hard consensus changes GSC environment) | X | X | |||
| In-Wallet Prayers | X | X | No | ||
| In-Wallet Bible Reader | X | X | No | ||
| Church Tithing | X | No | |||
| Mobile Wallet for sending/receiving | X | X | X | ||
| Mobile Wallet Staking | X | No | |||
| Physical Healing Campaigns | X | No | |||
| Spiritual Warfare Campaigns | X | No | |||
| Bearing Real Fruit (Healing, Warfare, Prayers, Sharing Gospel, and Tithing) | X | No | |||
| Quantitative Tightening (If voted in) | X | No | |||
| SegWit, Lightning compatibility, DAAP compatibility, Bitcoins most modern Security commits | X | X | |||
| Non financial transaction support | X | X | |||
| Deterministic Sanctuaries | X | No | |||
| Deflationary Emission schedule (-19.5% per year compounded) | X | X | X | ||
| Benefiting charities in a partially-decentralized way (88 orphans) through vendor liquidations | X | X | No | ||
| Decentralize charity payments in smaller shares | No | X | |||
| 501c3 for tax-deductible donations | No | X | |||
| In-wallet Chat | X | X | No | ||
| Integrated Watchman-on-the-wall (Automatic budgeting) | X | No | |||
| Generation II UI Design (Sleek modern menus and modern theme) | X | X | X | ||
| Governance, Sanctuary Voting, decision support system, dispurspements, superblocks | X | X | No | ||
| Voting for Christian Objects | No | X | |||
| Christian Spaces (HTML5) | No | X | |||
| Stratis Integration | No | X | |||
| Corporate Integration Features and C# (partially similar to NEM, Stratis use cases) | No | X | |||
| BiblePay compatible Debit Card | X | X | |||
| Integration with Shopping cart for retailers | X | X | |||
| Novel Mining Algorithms (POBH + POG + Healing) | X | No | |||
| Staking derived Rewards? (POG, Healing) | X | No | |||
| Turnkey/Oneclick Sanctuaries | X | X | No | ||
| In wallet proposal view/add | X | X | No | ||
| Fulfilling James 1:27 | X | X | No | ||
Key:
ABN - Anti-Bot-Net Mining. This feature requires a certain amount of ABN weight to be present in a mined block. BiblePay accomplishes this by requiring UTXOs with coin*age to be present in the ABN transaction. Effectively, this limits how many blocks a bot-net may mine as they spend their coin-age.
Stable-Prod. This feature splits our GSC (Generic Smart contract) payment interface between the client and server. The business logic is stored in the sanctuary (this allows sancs to come to soft consensus by voting on GSC contents by PAM hash). What this means is we do not need to release consensus changes to Prod between release cycles. This will give Prod a very high reliability.
