Divi Beta Notes: Scalability II

View this thread on: d.buzz | hive.blog | peakd.com | ecency.com
·@mark-waser·
0.000 HBD
Divi Beta Notes: Scalability II
<html>
<p>My <a href="https://steemit.com/cryptocurrency/@mark-waser/divi-beta-notes-scalability-i">last post</a> explained how the number &nbsp;of miners in proof-of-work (PoW) cryptocurrencies and the size of the &nbsp;consensus pool in proof-of-stake (PoS) cryptocurrencies limit the scalability of each. &nbsp;Anyone who claims that this isn’t the case for their coins bears the burden of proving all of the other cryptocurrency experts wrong.&nbsp;</p>
<p><img src="https://blog.diviproject.org/content/images/2018/05/Beta-Scalability-2-3.png" width="820" height="312"/></p>
<p>As far as we know, there are only three viable workarounds for this &nbsp;problem. &nbsp;For Bitcoin, the only real option is to eliminate the need for scaling on the main network through the use of side-chains (e.g., &nbsp;Lightning). PoS cryptocurrencies can reduce the size of the consensus &nbsp;pool via a variety of methods including minimum stake size and delegated &nbsp;proof of stake (Steem is a particularly effective example of the &nbsp;latter). &nbsp;Finally, new blockchains (or existing blockchains with strong &nbsp;enough governance) can be designed to break into collections of inter-operable block-chains (“sharding”). For example, Ethereum is &nbsp;planning to move to sharding.&nbsp;</p>
<p>As far as Divi is concerned, what must be remembered is that what is most important is the features that our network provides and its &nbsp;opportunities for growth. Divi currently runs on a fork of Peercoin &nbsp;which is a PoS fork of an old version of Bitcoin (0.10 versus the &nbsp;current 0.15). &nbsp;We <em><strong>could</strong></em> upgrade our current &nbsp;PoS fork infrastructure so that it is running the newest version of &nbsp;Bitcoin – but Lightning is anything but a panacea and would need to be &nbsp;included in a substantial percentage of the heaviest usage wallets &nbsp;before it would have any real effect.&nbsp;</p>
<p>We could switch to run atop an empty new copy of Ethereum. This would &nbsp;also immediately give us an upgrade to having user-defined contracts. &nbsp;Unfortunately, Ethereum contracts have proven to have a raft of unsolved &nbsp;problems, and the planned upgrades to PoS and sharding are farther in &nbsp;Ethereum’s future than we prefer. The real killer, however, is &nbsp;Ethereum’s reliance upon gas to run transactions – which effectively &nbsp;prevents micro-transactions.&nbsp;</p>
<p>We could switch to run atop a new Eos blockchain. There is risk in &nbsp;going with something so new – but Dan Larimer’s two previous &nbsp;blockchains, Bitshares and Steem, are thriving in the top 40 and &nbsp;maintaining transaction rates better than Ethereum’s. &nbsp;Further, Eos is &nbsp;starting with sharding baked into its original design. Best of all, &nbsp;Steem has proven the flexibility of its economic model by running &nbsp;without fees and supporting micro-transactions as a necessary large part of its paid blogging ecosystem.&nbsp;</p>
<p>Indeed, the only choice that would be a truly bad one would be for us &nbsp;to roll our own brand new blockchain infrastructure. Just as we forked PIVX to start with the most advanced technologies of masternodes and &nbsp;proof of stake, we will continue to include as much existing proven &nbsp;infrastructure as possible. Market share and partnerships are the key to cryptocurrency success, and we have every intention of positioning &nbsp;ourselves to take full advantage of both wherever possible.&nbsp;</p>
<p>My technical take is that Eos would be the best choice – but the decision still has yet to be made. In any case, we will have all of &nbsp;Divi’s advantages in addition to those which come with the chosen infrastructure (not to mention those that could be provided by some of our proposed new partnerships). As I said in my last post, the Divi &nbsp;Project is adamant that we will have scalability on par with any other &nbsp;cryptocurrency.&nbsp;</p>
<p><br></p>
<p>This post is being co-published simultaneously <a href="https://blog.diviproject.org/divi-beta-notes-scalability-2/">here</a> on the Divi blog&nbsp;&nbsp;</p>
<p>Visit the Divi Project at <a href="https://diviproject.org/">https://diviproject.org/</a> to sign up to have updates sent directly to your e-mail.&nbsp;</p>
</html>
👍 , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,