The primary purpose of this proposal is for the approval for us as a community to use Proof-of-Distributed Computing as a major reward algorithm in biblepay, and as a tool to help bust the botnet.
Please read some of the background info on PODC here:
http://wiki.biblepay.org/Distributed_ComputingBlock Security
===========
With Proof-of-distributed-computing enabled, I propose that we continue to use the existing consensus algorithm, PoBH (proof-of-bible-hash), for block security.
This is so our chains integrity can be maintained, and will not be completely trusted to any 3rd party. We continue to use DGW (Dark Gravity Wave ) for our difficulty algorithm, this helps us stay less prone to 51% attacks (attacks formed by buying out a percent of biblepay on the market).
The existing POBH-POW algorithm for chain security ensures that we have a structurally sound blockchain that syncs from zero consistently, and that it is easy for the core wallet to detect forks.
( This is a major concern, and must be taken seriously).
(This is in contrast a common problem with proof-of-stake consensus systems- where hackers have an attack vector potential created by solving blocks on multiple chains, making it hard for the core wallet to recognize which chain has the most work). In POW based chains, it is easy for the core wallet to stay on track, as the chain with the most work is usually a magnitude more than other chains.
I recommend that we keep the existing POBH-POW-heat mining system for block security, and for chain sync consistency. However, we reduce the payments on the POW-Heat side by 90%, so that we starve off the botnet first of all, by raising the PODC rewards up by 90%.
Imo, no botnet is going to choose to Heat Mine for 90% less when they can choose Rosetta mining for 90% more.
(This is proven in practice in all casinos).
I propose that we promote POBH mining only on the controller wallets, since those wallets would perform sending/receiving of biblepay funds, starting/stopping sanctuaries, managing Rosetta CPIDs, CPID association, and also mining on one thread for our block security.
It has been raised as an issue that if we lower rewards on the heat side by 90%, most strong miners will go away thereby leaving our security more vulnerable to an entity with large dormant hashpower, meaning that they will attempt to come in with a quick hash attack, and take over the chain and issue a double spend.
To combat this, I propose that we limit the ability to solve blocks to only Researchers with Active CPIDs in the chain (associated cancer researchers), with existing Magnitude and coins earned in the last superblock, and limit CPIDs from solving only one block per 6 block period. What this does is ensures that one researcher cannot enable massive hashpower and solve another block in the confirm period duration. This would require distinct CPIDs to join in-lessening the chances of an attack. Since the CPIDs must be actively crunching with RAC and magnitude and be in the prior superblock, a horizonal scaling attempt is not possible (as it will take at least 2 days to ramp up a new CPIDs magnitude and be paid, while the attackers Old cpids will be diminishing in power). In addition, DGW already adjusts to the current difficulty level, so a brute hashpower attack is very unlikely to win, with our low nonce rule, the attackers difficulty would rise by exponential amounts per solved block, and if any non-hacker CPID solves a block in between (which is highly likely due to the low nonce rule), the attack is not successful.
Security:
In this solution, we require Rosetta CPIDs to actually type in their credentials to become associated with Biblepay. All other biblepay researchers check the burn transaction in the memory pool, to verify the CPID is actually owned by the owner. So therefore it is not possible to be rewarded research rewards for any CPID not owned by the owner and verified with the burn transaction. Once the burn is checked, the researchers signature is set in the chain, and we respect future signed CPID messages from this researcher. Replay attacks are not possible.
The SanctuaryQuorum votes on the daily Magnitude file. We have a system in place to ensure only the official CPID magnitudes will pass in the vote (as a net 10% have to vote on the correct hashed contract) in order for the contract to be recognized as valid for the daily superblock.
In addition, the research payments are constructed in a way that divides the magnitudes by the superblock available budget, so if a Rosetta error would occur, the payment error would be relative to that superblocks budget, and would not result in a chain block overpayment (IE we never pay more than the total budget per day) and we divide the rewards by the share of each researchers weight per day.
Unlimited Scalability:
The daily superblock reward system was chosen so that biblepay may scale to allow up to 32767 researchers to be paid concurrently per day. Since there are currently 48,000 Rosetta servers actively crunching, this system could accomodate every Rosetta CPID as a potential biblepay user! We also do not require the researcher to quit their team, but through our advanced security, they may come onboard as a loyal biblepay user. This results in great PR for biblepay.
In summary, this is what I am proposing:
Proof-Of-Work rewards drop to approx 600 BBP per block (a reduction of 90%)
Proof-Of-Distributed-Computing rewards increase to approx 5500 BBP per block (an increase of 90%)
One superblock per day airdrops the researcher rewards, allowing up to 32767 research payments per day
Theory to bust the botnet:
Since POW rewards would decrease by 90%, the botnet would quit heat mining and start cancer mining
POW would require a signed CPID to solve a block
POW would require a CPID to be active and have prior payments to solve a block
Biblepay would have a feature, if no CPID is available in 31 minutes to solve a block, we would allow any heat miner to solve the block (so chain never gets frozen, in case of Rosetta being down etc)
These rules would lower the chances of an outside 51% attack to almost zero, when combined with DGW's protection
I recommend POL to be disabled for now (proof-of-loyalty) and that we instead research ways to include an element of POL in each Rosetta work unit to raise the trust and integrity level of Proof-of-distributed-computing to the highest level for the masses.
^ If POL is trusted as a sole consensus algorithm, then PODC+POL may be a potential global leading candidate in the future.
PODC also will allow us to achieve a great future milestone: Mining for the unbanked. Since Rosetta cancer mining supports ARM tablets and ARM cell phones, it is possible for the unbanked through cancer research to earn enough to live on or at least buy groceries in third world countries. This is more than we currently have, since POBH currently runs on PCs only.
The financial renumeration for this proposal is only 10 BBP, as our budget is mostly consumed.
Please vote for this if you believe this will not only allow us to be a humanitarian force - one facet of our community is doing what Jesus would do : help heal others, but also if you believe we will help remove the influence of the botnet and take our community back.
Show Posts
Feature!