Main navigation

Centralized, Decentralized, Distributed Networks, Explained

Thu, 02/22/2018 - 00:44
article image
David Dinkins
Decentralized isn’t always good enough; here’s the difference between centralized, decentralized and distributed.
Centralized, Decentralized, Distributed Networks, Explained
Cover image via U.Today
Read U.TODAY on
Google News

CryptoTip #1

Centralized networks are controlled by a single entity, who can do absolutely anything. Such networks have a central point of failure and therefore are not fault tolerant. While people usually think of digital currency as being decentralized, that’s not always the case. There are some currencies, such as Ripple and Tether, that are controlled by centralized companies. More of these tokens can actually be created at any time, although the companies have rules about when and if they’ll actually do that.

CryptoTip #2

Decentralized networks rely on a hub-and-spoke model, where end users are connected to trusted nodes that are interconnected with each other. Certain “light wallets” work in a decentralized fashion, such as Electrum. Such a wallet doesn’t require the end user to download or verify the Blockchain; instead, users connect to one of many possible servers. These servers then communicate with each other.

CryptoTip #3

Most cryptocurrencies rely on distributed networks to function. Distributed networks are peer-to-peer (p2p), with each user being able to connect with any other user on the network. Such networks are the most fault tolerant of all, lacking any form of centralization. Some who criticize certain Bitcoin scaling solutions do so out of fear that such solutions will turn Bitcoin’s distributed network into a mere decentralized one.

article image
About the author

David Dinkins is a freelance writer who holds a Master of Arts in history from Louisiana Tech University and has extensive teaching experience both at LSU – Shreveport and University of Phoenix. He got involved with cryptocurrency in early 2014 working as part of the Dash Core Team and have served in the role of writer/editor (mostly editor) during that time. He has edited a huge number of documents for the Core Team, including the Evolution whitepaper, the PrivateSend whitepaper, and many of Evan Duffield’s communications with the Dash Community.