Skip to main content

Blockchains and Distributed Ledgers

Today I'll continue a review of the Linux Foundation's first Hyperledger blockchain class on edX, "Blockchain for Business - An Introduction to Hyperledger Technologies." Today's post will focus on distributed ledger technology.

Chapter One:
A lot of the course's first of eight chapters regards the blockchain in general, the different blockchains that exist, and how they are similar and different. By the end of the first chapter we begin to focus on the Hyperledger blockchain.

The course does a nice job of presenting its material in bite-sized portions in the form of either text or video. The slides that are all text rarely require scrolling on a laptop while the videos are rarely longer than four minutes in length. 

A Key Takeaway From Chapter One
So what is the blockchain? The blockchain is a distributed ledger. OK, well, what's that? Traditionally, we have had to deal with ledgers that are centralized, not distributed. Examples of centralized ledgers includes banks that keep ledgers of accounts and governments that keep records of real estate property deeds. Unfortunately, because these ledgers are centralized and there is only one copy of the ledger everyone suffers if the bank or government agency is hacked or their records destroyed. 

Decentralized or distributed ledgers, on the other hand, combat this problem by creating and sharing multiple copies of ledgers that are immutable: That is, the information on the blockchain cannot be changed. The most popular case is the Bitcoin blockchain. Traditionally, for two people to perform a monetary transaction, they have to go through a bank. With Bitcoin two individuals can transfer money directly, no intermediary necessary. If one party has a dispute with the transaction they can check the Bitcoin blockchain to see what all the other ledgers out there have in their records. The more records there are in the Bitcoin blockchain network the more difficult it is to pull a fast one.

In other words, if 99 people have copies of Reggie's Bitcoin transfer to Sonya and Sonya is the only person who says the amount of the transfer is different from what everyone else has, there's a good chance Sonya is incorrect or, worse, a malicious actor. That's the power of a distributed ledger. 

Up Next: Permissioned and permissionless blockchains

Comments

Popular posts from this blog

The Proof of Work consensus algorithm

Today I'll continue a review of the Linux Foundation's first Hyperledger blockchain class on edX, " Blockchain for Business - An Introduction to Hyperledger Technologies ." Today's post will focus on how the  Proof of Work (PoW)  consensus algorithm works. People have  explained  PoW to me a few different times and each time I walked away with questions and an incomplete understanding of the subject. This includes the edX course which does a good job of explaining the concept, but still didn't provide a good visual of how PoW works or connect all the dots. I'll try to provide a more comprehensive explanation here.  Please keep in mind why consensus algorithms such as PoW are necessary and important: They provide trust between different untrusting parties. Without trust there are no transactions between the parties. How do the consensus algorithms provide trust? As a process created by third-party developers consensus algorithms such as PoW do not b...

Achieving Consensus

Today I'll continue a review of the Linux Foundation's first Hyperledger blockchain class on edX, " Blockchain for Business - An Introduction to Hyperledger Technologies ." Today's post will focus on how participants in a blockchain transaction agree on the data that goes to the blockchain. This process is called consensus. Normally, when two people achieve or come to a consensus it means that after some discussion all parties have come to an agreement. In terms of the blockchain, consensus means " achieving agreement among the network participants as to the correct state of data on the system." This "leads to all nodes sharing the exact same data." If there is no consensus then not only can the participants in a blockchain not  agree on what data to commit to the blockchain, but they cannot  distribute their information away from a centralized location. Achieving consensus quickly, flawlessly, cheaply, and consistently is essential to the ...

Permission Granted

Today I'll continue a review of the Linux Foundation's first Hyperledger blockchain class on edX, " Blockchain for Business - An Introduction to Hyperledger Technologies" with a focus on permissioned and permissionless blockchains. One Pager on Permissioned and Permissionless Blockchains Prior to this class I knew that some blockchains were permissioned and others permissionless, but I didn’t have a firm grasp of what those terms meant mainly because permission typically takes a preposition after it; notably, permission to do something or permission from someone. The shorthand terms permissioned and permissionedless, unfortunately, didn't spell out the rest. Today I'll make that a little more clear.  Some blockchains such as the Bitcoin and Ethereum blockchains are permissionless. This means those who want to participate in them do not require permission from any central authority to do so. This makes sense for Bitcoin and Ethereum, two crypto...