Linux and Open Source Blog

  • Home
  • WordPress Plugins
  • About
  • Contact

Decentralization, Scalability, and Fault Tolerance of Bitcoin

Posted on January 12, 2015 by Linewbie.com Posted in quotes & thoughts .
Posted by Stan Larimer & Daniel Larimer on January 12, 2015.
Bitcoin is all about decentralizing the control over money through objective consensus on ownership. What often gets lost in the discussion is the difference between decentralization, scalability, and fault tolerance. Bitcoin is an example of a decentralized system whose scalability is limited by the power of an individual node rather than the combined power of all nodes. This means that a system’s ability to become distributed for fault tolerance, decentralized for control, and scalable for performance are not linked together by the number of nodes. In fact we could say that attempts to combine these roles via the same mechanism will carry with it the combined limitations rather than the combined benefits. Hence economies of scale and free market competition will tend to minimize unnecessary fault tolerance (redundancy) while centralizing for performance. If we are not careful this will result in centralization of control.When the BitShares developers get a little uppity, I love to remind them that what they are doing is not exactly rocket science.But, while trying to find a way to communicate the architecture of BitShares to folks on other forums, I’ve stumbled on the following description, drawing on my past experience with continuously reconfiguring fault-tolerant flight control systems. (Yes I wrote a technical report with that title back before there was an Internet or even a word processor.) See if you buy this way of describing the BitShares architecture:

We tend to get three different attributes mixed up causing endless confusion even among men of good will.

  1. Throughput Scalability
  2. Fault Tolerance
  3. Decentralized Control

These are three different concepts.

Fault Tolerance

We are saying 101 highly-reliable, tested and proven, hand-picked parts dispersed across the globe and selected by the entire owner population is sufficient redundancy to achieve reliable fault tolerance. The only thing those parts can do is – do their job to spec. We can observe their performance and swap them out in ten seconds if they don’t perform to spec. So, really, they are just interchangeable slave machines. Producing the blocks is a mindless task.

Selecting which parts make up the machine is where the power lies.

Decentralized Control

The total decentralized population of the all owners participate in selecting the most reliable machines to run the network. Those 101 parts have no power over the owners. 101 dispersed redundant parts is a decentralization red herring! That’s not where control lies. Those 101 chosen nodes can be completely reconfigured or replaced by the fully decentralized participating owners in 10 seconds.

BitShares has decentralized p2p control
of a distributed, fault-tolerant computer
implementing an autonomous unmanned company
running a decentralized crypto currency exchange
which produces stable smart-coin products.

Throughput Scalability

Any of the 101 nodes can scale up by adding parallel machines, side chains, and a thousand inventions we haven’t dreamed of. When we get to a billion owners and need a thousand machines per node, we can do that. It will still be decentralized enough to ensure that the 101 (now bigger) parts that make up the distributed, fault-tolerant machine will perform their mindless slave jobs reliability – from positions scattered across 24 time zones.

Those million decentralized owners do not want to have to think about managing more than 101 redundant parts to their machine. 101 is plenty, maybe too many, for the average owner to keep track of how they are performing. Adding more parts reduces the degree to which each part can be vetted and therefore reduces the system’s reliability. Total reliability is a combination of node redundancy and node reliability via reputation-based vetting.

In BitShares, absolute control is fully decentralized down to the votes of every single atomic BTS satoshi. You can’t get more decentralized than that.

Bytemaster’s Conclusions

At the end of the day it is all about decentralization of influence. It doesn’t matter that everyone is theoretically able to enter the lottery to gain the honor to produce a block if the same people win the lottery the majority of the time. Economies of scale will always force systems toward centralization via the removal of unnecessary redundancy in order to compete in the free market. Absent a means of delegating block producing influence to another party, any proof-of-something system will tend to deny small players any influence.

Bitcoin & Nxt both support delegation of influence through mining pools and leased forging. Bitcoin and all of the alt-coins have proven that left to its own devices the market will realistically support no more than 10 pools. As the network scales block producers will be competing to lower fees. This inevitably means placing their full nodes in locations with cheap bandwidth and computers optimized for signature verification and database speeds. Users of the network will eventually start creating transactions with fees lower than would be profitable for any unspecialized block producer to process. It just isn’t worth the time, money, and effort for companies to run a block producing node at scale.

Nxt leasing and Bitcoin mining pools will ultimately result in fewer than a dozen organizations producing over 51% of all blocks within the confirmation window. I did a random sampling of Nxt block producers and in a matter of minutes identified 10 people who have collectively produced 30% of all blocks in Nxt history. At this rate I could likely find that 51% of blocks being produced by fewer than 40 people. There may be over 300 people participating, but the vast majority of blocks are produced by a small minority.

What we learn from this is that we must decentralize control with a different mechanism than we achieve fault tolerance. It is more important to have decentralized control over who produces blocks than to have no control over who produces blocks. If token holders don’t control who produces blocks, then centralized block producers will control who owns the tokens.

1 Comment
« Stripe will soon accept Bitcoin payments
Looting of the Fox: The Story of Sabotage at ShapeShift »

One Response

  1. ucTede says
    February 16, 2017 at 2:25 pm

    Hi

    Offering free trials of Email bombs on

    http://bitcoin-advertising.com/

    Hacking Service , calls & text bombs , CC’s , Spam tools

    Your Welcome , Much love

    Wild Hacker Team

    Reply

Leave a comment

Leave a comment Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • Does an un-confirmed Bitcoin transaction expire?
  • Looting of the Fox: The Story of Sabotage at ShapeShift
  • Decentralization, Scalability, and Fault Tolerance of Bitcoin
  • Stripe will soon accept Bitcoin payments
  • Zynga announces Bitcoin acceptance in game
  • How to import very large sql dump via phpmyadmin
  • How to compare the content of two folders automatically
  • Top 5 reasons to start experimenting with Linux
  • The day our mind became open sourced
  • Mark Shuttleworth wants to turn canonical (ubuntu) into the next Apple Inc.

Categories

  • applications/software (26)
    • browsers (2)
    • development (1)
    • information management (1)
    • Mobility (1)
    • multimedia (5)
    • office suites (2)
    • security (6)
    • servers (6)
    • system (2)
  • audio/video/pics (3)
  • Bitcoin (3)
  • books & literature (1)
  • cms/portals (1)
  • desktop environments (7)
    • gnome (2)
    • kde (5)
  • events/shows (3)
    • interviews (1)
    • people (1)
    • surveys (1)
  • games & gaming (2)
  • general topics (4)
  • guides (112)
    • how to (105)
    • tips (87)
    • tutorials (86)
  • hardware (8)
    • desktop & laptop pc (5)
    • gadgets & mobiles (2)
  • howtoforge (47)
  • internet/web (4)
    • design & development (2)
  • linux and open source blog (49)
  • linux.com (76)
  • linux/unix/os distros (113)
    • debian/ubuntu based (10)
    • mac/osx (2)
    • other distros (3)
  • news (217)
  • open source (8)
    • business & foss (2)
  • other (26)
    • uncategorized (26)
  • Programming (3)
    • PHP (2)
  • quotes & thoughts (10)
  • random stuff (4)
    • cool stuff (3)
    • funny stuff (1)
  • review/preview/tests (7)
  • wordpress/blogging (3)

Archives

  • July 2016
  • April 2016
  • January 2015
  • April 2014
  • January 2014
  • November 2013
  • February 2013
  • November 2012
  • April 2012
  • March 2012
  • January 2012
  • December 2011
  • August 2011
  • March 2008
  • February 2008
  • January 2008
  • December 2007
  • November 2007
  • October 2007
  • September 2007
  • August 2007
  • July 2007
  • June 2007
  • May 2007
  • April 2006

Recent Posts

  • Does an un-confirmed Bitcoin transaction expire?
  • Looting of the Fox: The Story of Sabotage at ShapeShift
  • Decentralization, Scalability, and Fault Tolerance of Bitcoin
  • Stripe will soon accept Bitcoin payments
  • Zynga announces Bitcoin acceptance in game
  • How to import very large sql dump via phpmyadmin
  • How to compare the content of two folders automatically
  • Top 5 reasons to start experimenting with Linux
  • The day our mind became open sourced
  • Mark Shuttleworth wants to turn canonical (ubuntu) into the next Apple Inc.

Categories

  • applications/software (26)
    • browsers (2)
    • development (1)
    • information management (1)
    • Mobility (1)
    • multimedia (5)
    • office suites (2)
    • security (6)
    • servers (6)
    • system (2)
  • audio/video/pics (3)
  • Bitcoin (3)
  • books & literature (1)
  • cms/portals (1)
  • desktop environments (7)
    • gnome (2)
    • kde (5)
  • events/shows (3)
    • interviews (1)
    • people (1)
    • surveys (1)
  • games & gaming (2)
  • general topics (4)
  • guides (112)
    • how to (105)
    • tips (87)
    • tutorials (86)
  • hardware (8)
    • desktop & laptop pc (5)
    • gadgets & mobiles (2)
  • howtoforge (47)
  • internet/web (4)
    • design & development (2)
  • linux and open source blog (49)
  • linux.com (76)
  • linux/unix/os distros (113)
    • debian/ubuntu based (10)
    • mac/osx (2)
    • other distros (3)
  • news (217)
  • open source (8)
    • business & foss (2)
  • other (26)
    • uncategorized (26)
  • Programming (3)
    • PHP (2)
  • quotes & thoughts (10)
  • random stuff (4)
    • cool stuff (3)
    • funny stuff (1)
  • review/preview/tests (7)
  • wordpress/blogging (3)

Archives

  • July 2016
  • April 2016
  • January 2015
  • April 2014
  • January 2014
  • November 2013
  • February 2013
  • November 2012
  • April 2012
  • March 2012
  • January 2012
  • December 2011
  • August 2011
  • March 2008
  • February 2008
  • January 2008
  • December 2007
  • November 2007
  • October 2007
  • September 2007
  • August 2007
  • July 2007
  • June 2007
  • May 2007
  • April 2006
Privacy Policy

Est. 2002

linewbie.com serving the linux and open source community since April 09, 2002

CyberChimps WordPress Themes

© Linux and Open Source Blog