Hyperledger — DAY THREE

iOS
2 min readAug 30, 2018

--

DAY TWO — https://medium.com/@tommarler/hyperledger-daily-articles-for-next-149-days-day-two-fd4ba57a81bc

Today I am going to summarize what I have learned about blockchain so far. I will explain in more detail about how blocks are created, validated and added to the blockchain.

Blockchain reminds me of a link list because blocks are linked together creating a chain of blocks. Each block has data, a unique hash and the hash of the previous block. As blocks are added the chain grows, creating a ordered list of transactions.

Maintaining a order list of transactions is crucial to data integrity. When a transaction takes place it is sent to all nodes in the distributed network. All nodes work together to validate the correctness of the transaction.

Nodes validate the transaction by using consensus. Consensus is how network nodes agree on what is considered a valid transaction. Proof-of-Work is a consensus algorithm were all nodes in the network race to solve a cryptographic puzzle, the node that solves the puzzle the quickest gets to mine that block and add it to the blockchain.

Questions for next Friday 8/31 Article:

  • All things Hyperledger

DAY FOUR Article — Hyperledger frameworks — COMMING SOON!!!!

DAY FOUR part 2 — Hyperledger fabric — COMMING SOON!!!

Suggestions and comments are appreciated! Looking forward to sharing and learning again tomorrow :) Thanks for reading!!!

Please checkout the below links

Linkedin — https://www.linkedin.com/in/tom-m-bb4857112/

Sign up to discover human stories that deepen your understanding of the world.

Free

Distraction-free reading. No ads.

Organize your knowledge with lists and highlights.

Tell your story. Find your audience.

Membership

Read member-only stories

Support writers you read most

Earn money for your writing

Listen to audio narrations

Read offline with the Medium app

--

--

iOS
iOS

Written by iOS

iOS Developer, Go, Java, C#, Blockchain enthusiast, Data junkie

No responses yet

Write a response