Hedera fundamentals course

https://101blockchains.com/course/hedera-fundamentals/#experts

Transcript

1. Hedera Fundamentals
2. MODULE LIST Module -1: Technology / Terminology Overview Module-2: Hedera Overview Module-3: Hedera Governance and Applications Module-4: Hedera Services Explained Module-5: Hedera Stable Coin Use Case Module-6: Hands-On Final Exam
3. THIS COURSE IS FOR YOU IF YOU WANT TO Get an overview of Hedera Hash graph Technology and fit into the DLT Landscape Understand the advantages this technology offers over other blockchain variants in the space Learn about the services offered and how they can be leverage to quickly satisfy a use case like Stable Coin
4. WHO SHOULD TAKE THIS COURSE? Product & Program Managers building and deploying Enterprise Apps on DLTs in production Innovation Leaders and Entrepreneurs Software developers building DApps on blockchain DLT / Blockchain / Web 3.0 enthusiast
5. DISCLAIMER The course is not intended to provide any investment advice and should not be taken as such. Claims made in this course do not constitute investment advice and should not be taken as such. Do your own research!
 
 While the information contained in this document and course has been obtained from sources believed to be reliable, 101 Blockchains disclaims all warranties as to the completeness or accuracy. 
 Although 101 Blockchains research and training may address business, financial, investment and legal issues, 101 Blockchains does not provide any business, financial, legal or investment advice and this training should not be construed or used as such. 
 101 Blockchains shall not be responsible for any loss sustained by any person who relies on this training.
6. MODULE 1 Technology / Terminology Overview
7. What Will You Learn? Get an overview of DLT Get aligned on the same terminology Understand the different kinds of DLTs
8. MODULE OVERVIEW Lesson-1: What are distributed ledger technologies (DLTs)? Lesson-2: DLTs vs Blockchain Lesson-3: Different kinds of Ledgers
9. LESSON 1 What are distributed ledger technologies (DLTs)?
10. What are DLTs?
11. LESSON 2 DLT vs Blockchain
12. DLT vs Blockchain Categories DLT Blockchain Definition A distributed transactional database maintained and validated by multiple participants and nodes Form of DLT made up of immutable digitally recorded data stored in blocks Ordering and Consensus Techniques Proof of Work, Proof of Stake, DAGs, Graphs …etc. Proof of Work, Proof of Stake N/W Examples IOTA, Hedera Hash Graph Bitcoin, Ethereum
13. LESSON 3 What are the different types of Ledgers?
14. Different Kinds of Ledgers Permissionless : Allows People/ Nodes to transact anonymously Permissioned: People / Nodes transacting are known Private (Closed): People need to be approved to participate Public (Open): Anyone can send a transaction Bitcoin Ethereum Ethereum Alliance Corda N/W Hybrid Hyperperledger Fabric Corda Private N/W https://101blockchains.com/permissioned-vs-permissionless-blockchains/
15. Different Kinds of Ledgers Factors Public Permissionless Public Permissioned Private Permissionless Private Permissioned Identities Unknown / Anonymous Partially Unknown Partially Known Known Governance Decentralized - Open and transparent Decentralized - Open and restricted Centralized – other participating nodes as determined by owner of ledger Centralized – Private Operator(s) – controlled by a single owner Or Consortium (Equal weight to members) Transaction s Write all and read all Write all and read restricted. Write restricted and read all. Write and read restricted. Consensus / Validation Anyone can become a node and validate Permissioned users (nodes) Only can validate Authorized users can become a node and validate Network Operator Only Or All or subset of authorized participants # of Users Millions Few Hundreds to Millions Dozens to few hundreds Dozens Types of use cases Peer2Peer Digital Governance B2B B2B, B2C Use Case Examples Cryptocurrencies, Games Voting, Land Titles, Educational Credentials Supply Chain, Record Keeping, Chain of Custody, Track and Trace Tax Returns, Medical Records, instant payment n/w, Vaccines / Medicine Track and Trace
16. Blockchain Graph DAG DLT Key Take Aways Blockchain is a type of DLT Different use cases dictate different ways of configuring and deploying ledgers from private to public and permissionless to permissioned or somewhere in between
17. MODULE 2 Hedera Overview
18. What Will You Learn? What is Hedera and its mission? Who created Hashgraph? What is the crypto currency for Hedera? What is the Hedera advantage? What is the Hedera Governing Council and What do they do?
19. MODULE OVERVIEW Lesson-1: Hedera Origins & History Lesson-2: Hashgraph Consensus Algorithm Lesson-3: The Hedera Advantage Lesson-4: Hedera Cryptocurrency Lesson-5: Hedera Governing Council
20. LESSON 1 Hedera Origin and History
21. Hedera Origin & History Founded by Dr. Leemon Baird & Mance Harmon Team Bios @ Hedera.com Hedera Journey: 2015: Hashgraph Consensus algorithm Invented under Swirlds 2017: Hashgraph Consensus Algorithm was introduced to the world 2018: • Hedera introduced in NY as a “Public Hashgraph Network” with the intent to create a world class governing council • Main-net launched • 50 Billion native tokens minted Hedera Journey Continued: 2019: Hedera Consensus Service & Open Network Access launched with Governing council member nodes 2020: Surpasses daily transaction volume of Ethereum in 9 months 2021: HBar Foundation announced to drive adoption and growth in the Hedera ecosystem. HBAR Ecosystem Statistics live @ https://app.dragonglass.me/hedera/ home
22. LESSON 2 Hashgraph Consensus Algorithm
23. Hashgraph Consensus
24. Hashgraph Consensus
25. Hashgraph Consensus
26. LESSON 3 The Hedera Advantage
27. The Hedera Advantage
28. The Hedera Advantage
29. The Hedera Advantage
30. The Hedera Advantage
31. LESSON 4 Hedera Cryptocurrency
32. Dual role of HBAR HBAR is the native, energy-efficient cryptocurrency of the Hedera public network. Hbars are used to power decentralized applications and protect the network from malicious actors. Network fuel: Developers use hbars to pay for network services, such as transferring hbars, managing fungible and non-fungible tokens, and logging data. For each transaction submitted to the network, hbars are used to compensate network nodes for bandwidth, compute, and storage Network Protection: Hedera’s proof-of-stake public network uses hbars, which are staked or proxy staked (coming soon) to a network node, to weight votes on transactions when reaching consensus. Weighted voting with hbars makes it difficult and expensive for a bad actor to maliciously affect consensus
33. LESSON 5 Hedera Governing Council
34. Hedera Governing Council Hedera’s governance is decentralized by design. The 39 members will be distributed fairly across time, region, and industry.
35. Hedera Governing Council
36. MODULE 3 Hedera Ecosystem
37. What Will You Learn? Get an overview of the different use cases is already addressing Get Insights into Upcoming features & functionality Know how to get engaged with Hedera Dispel some commonly held myths about Hedera
38. MODULE OVERVIEW Lesson-1: Use cases Lesson-2: Roadmap Lesson-3: Hedera Resources Lesson-4: Myths
39. LESSON 1 Use cases
40. Use cases
41. Use cases Hedera’s currently has 50+ applications many of them are in production (Main-net) Hedera Use cases are across all of Web 3.0 categories with initial focus on enabling enterprise adoption for Asset Tokenization, Track and trace, Fraud mitigation, Trust in ERP,CRM integrations, Identity and authentication, Permissioned Blockchain
42. LESSON 2 Roadmap
43. Roadmap
44. LESSON 3 Hedera Resources
45. Hedera Resources
46. Hedera Partners
47. LESSON 4 Myths
48. Myths Hedera is centralized: • As discussed in a prior module their governance council is very de-centralized. • While Hedera has initially focused on enterprises they fully intend to become decentralized . Below are some high level milestones for Hedera’s path to Decentralization (white paper) ❑ Phase 1: Permissioned Hedera Council member consensus nodes ❑ Phase 2: Many permissioned consensus nodes ❑ Phase 3: Permissionless nodes Hedera’s is not open/transparent : The hashgraph algorithm is protected by patents. The patents are a tool designed to inhibit forking and the associated instability and loss of network effects. The absence of enterprise-grade applications running on the public networks today is partly due to the possibility of those networks splitting into competing networks and cryptocurrencies. This represents risk to anyone considering building mission critical applications on those networks. The patents will allow Hedera to make a commitment to such enterprises that we will never authorize a fork. Hedera network services are open sourced under Apache 2.0 license and the platform is open for open review meaning the consensus algorithm source code is available for anyone to read, recompile, and verify that it is correct. More info @Hedera
49. MODULE 4 Hedera Architecture & Services
50. What Will You Learn? Get a comprehensive view of the key services of Hedera and where they stand in the general Hedera architecture Conceptual and logical view of how the services can be leveraged to build out DApps Understand how pricing of these services are structured
51. MODULE OVERVIEW Lesson-1: Hedera Architecture & Services Lesson-2: Hedera Consensus Service Lesson-3: Hedera Token Service Lesson-4: Other Hedera Services Lesson-5: Hedera Infrastructure & Core Concepts Lesson-6: Service Fees
52. LESSON 1 Hedera Architecture & Services
53. Hedera Architecture
54. LESSON 2 Hedera Consensus Service
55. HCS
56. HCS
57. LESSON 3 Hedera Token Service
58. HTS
59. HTS
60. LESSON 4 Other Hedera Services
61. Other Hedera Services
62. Other Services • File Service • Cryptocurrency (HBAR) • Smart Contracts Service
63. LESSON 5 Hedera Infrastructure & Core Concepts
64. Hedera Infrastructure Networks • Main net • Test net • Preview net Nodes • consensus node (main node) • mirror node ◦ A Beta Mirror Node is a node that receives pre-constructed files from the Hedera mainnet. These pre-constructed files include transaction records and account balance files ◦ community mirror nodes ▪ dragonglass ▪ kabuto
65. Hedera Infrastructure
66. Accounts • Accounts are stored on the public ledger and hold hbar which are used to pay for the transaction and query fees • Hedera accounts can be created, updated, or deleted and are represented by an account ID • To create an account, you need an existing account that can pay for the associated transaction fees for the new account and to optionally fund the new account with an initial balance
67. Accounts
68. Keys and Signatures ▪ Each account has a public and private key pair • The private key of the account is used to authorize and sign transactions for that account • The public key is what is visible to others on the network when account information is requested ▪ The key for an account can be a list of keys, with three options available: • Key List: M out of M signatures (multi-signature) • Threshold: M out of N signatures • Nested: A complex hierarchy of signatures required. Can include key lists and thresholds
69. Transactions and Queries ▪ Transactions are requests sent by a client to the network for processing. Each transaction has an associated transaction fee that compensates the Hedera network for that processing and subsequent maintenance in consensus state • Scheduled transactions enable execution when time and signature requirements are met, which makes them ideal for multi-signature transactions when you don’t have all required signatures immediately available ▪ Queries are sent by clients to a single node to retrieve some aspect of the current consensus state, like the balance of an account
70. Transactions and Queries
71. Transactions and Queries ▪ Confirmations are receipts, records, and state proofs • Receipts (minimal information) indicate whether a transaction was successfully processed into consensus state • Records (more information) indicate transaction details like the consensus timestamp or the results of a smart contract function call • State proofs (coming soon) document network consensus on the contents of a record and includes signatures from most of the network nodes
72. Transactions and Queries
73. LESSON 6 Services Fees
74. Services Fees • Hedera's fee schedule is set by the Hedera Governing Council and always based in USD — making it easy to estimate API call costs. • When you are paying for an API you are paying for all transactions on the Hedera network including service, network, and node fee all in one. Fee Estimator • Hedera has been designed to fight price volatility experienced by cryptocurrencies by pegging the price of their APIs to the USD and taking payments in HBAR.
75. Service Fees
76. Fee Estimator
77. MODULE 5 StableCoin Transfer Use Case
78. DISCLAIMER The use-case described hereafter is a POC and has not yet been deployed as a production publicly available application
 
 
 
 All of the intelectual rights belong to Shinhan bank, Standard bank and Hedera
 
 
 
 The material presented here is for learning purposes and demonstrate the potential practical real-world application of Hedera platform and services
 

79. What Will You Learn? Understand what StableCoin is and why it is important Use-case overview Understand how Hedera perfectly suits as a platform for the use-case Architecture and flow
80. MODULE OVERVIEW Lesson-1: Understanding Stablecoin Lesson-2: Stablecoin use-case: overview Lesson-3: Stablecoin use-case: architecture
81. LESSON 1 Understanding Stablecoin
82. Understanding Stablecoin Stablecoins are digital currencies designed to maintain a stable value, typically linked to a fiat currency like the U.S. dollar. • Fiat-collateralized • Commodity-collateralized • Crypto-collateralized • Non-collateralized (algorithmic) Stablecoins marry the reliability, trust, and price-stability of fiat currency with the accessibility, security, and speed of cryptocurrencies.
83. LESSON 2 Stablecoin international transfer
84. SWIFT Transfer
85. Why Hedera?
86. Stablecoin Transfer
87. LESSON 3 StableCoin Transfer - Architecture
88. Stablecoin Transfer architecture
89. Stablecoin POC Results
90. MODULE 6 Hands-on & Final exam
91. What Will You Learn? Overview of the hands-on environment and resources Stablecoin use-case: hands-on Hands-on #1: Emit token Hands-on #2: Transaction consensus
92. MODULE OVERVIEW Lesson-2: Environment set up Lesson-3: Hands-on #1: Token emission Lesson-4: Hands-on #2: Transaction consensus Lesson-1: StableCoin Transfer API Interactions Final Exam
93. LESSON 1 StableCoin Transfer API Interactions
94. Stablecoin Transfer Functional Flow • Alice buys X amount of SKRW stablecoin • Alice transfers X amount of SKRW = Y amount of SZAR to Bob • Bob converts Y amount of SZAR stablecoin into ZAR fiat
95. Stablecoin Transfer API Interactions
96. Stablecoin Transfer API Interactions
97. Stablecoin Transfer API Interactions
98. Stablecoin Transfer API Interactions
99. Stablecoin Transfer API Interactions
100. Stablecoin Transfer - E2E Flow
101. LESSON 2 Environment set up
102. SDKs Hedera and the developer community contribute to and maintain Hedera SDKs across various languages. Hedera supported • JavaScript • Java • Go Community supported • .NET • Python
103. Environment set up ❏ Create TestNet account ❏ Install required SDK and libraries ❏ Test Hedera client ❏ Check-out code: https://github.com/thatwist/hedera-course-demo
104. LESSON 3 Hands-on #1: Token emission
105. Hands-on #1: Sequence diagram
106. DEMO
107. LESSON 4 Hands-on #2: Transaction consensus
108. Hands-on #2: Sequence diagram
109. DEMO
110. Final exam
111. Thank You © 2021 101 Blockchains LTD. All rights reserved. This document may not be distributed, transmitted or reproduced in any form or by any means without 101 Blockchains’ prior written permission. While the information contained in this document has been obtained from sources believed to be reliable, 101 Blockchains disclaims all warranties as to the completeness or accuracy. Although 101 Blockchains research may address business, financial, investment and legal issues, 101 Blockchains does not provide any business, financial, legal or investment advice and this document should not be construed or used as such. 101 Blockchains shall not be responsible for any loss sustained by any person who relies on this publication.