Wwc developing hyperledger applications v4
- 1. An Introduction to Blockchain and Hyperledger Lennart Frantzell IBM Developer Advocate San Francisco alf@us.ibm.com V1.2 February 1 2019 Blockchain Explored Series IBM Blockchain Platform Explored Fabric Explored Composer Explored Whatβs New Architectures Explored
- 3. 3 Breaking News: Hyperledger Fabric Now Supports Ethereum Smart Contracts β’ Enterprise blockchain Hyperledger Fabric has introduced support for Ethereum smart contracts. Fabric is designed to be modular with four main components. These are the main ledger, the consensus mechanism, identity management, and smart contracts called chaincode. The latest announcement provides an alternative to chaincode. β’ Ethereumβs large pool of developers are comfortable with its Solidity smart contract language, so the integration should make Fabric more appealing to Ethereum developers. Additionally, many coders use Web3 a Node.js set of tools to build Ethereum decentralized apps (Dapps). By integrating with the EVM, these developers can work with Fabric and even migrate smart contracts and Dapps over to Hyperledger Fabric. β’ https://www.ledgerinsights.com/hyperledger-fabric-integrates-ethereum-smart-contracts-evm-blockchain/
- 4. Global Financial Crisis 2008 4
- 5. 5
- 6. 6 The Blockchain Story β’ Hyperl edger
- 7. 7 The Ledger problem inefficient, expensive, vulnerable Participant Aβs records Participant Bβs records Bank records Insurer records Regulator records Auditor records
- 8. 8 Blockchain Participant Aβs records Participant Bβs records Bank records Insurer records Regulator records Auditor records The Ledger Solution A shared, replicated, permissioned ledgerβ¦ β¦with consensus, provenance, immutability and finality
- 10. 10 Linux Foundation Open Source Hyperledger β’ App Layer: Hyperledger Sawtooth Supply Chain Cargill https://sawtooth.hyperledger.org/examples/seafood.html In December 2015, the Linux Foundation announced the creation of the Hyperledger Project. Visual Studio Code
- 11. Roadmap β’ Channels β’ Selective endorsement β’ SOLO/Kafka orderers β’ LevelDB or CouchDB β’ Javascript chaincode β’ Connection profile β’ Encryption library β’ Attribute access control β’ CouchDB indexes β’ Channel based events β’ ACLs β’ Service discovery β’ Pluggable endorsement and validation β’ Private Data Collections β’ State based endorsement β’ Java chaincode β’ CouchDB pagination β’ Identity Mixer β’ Local collections β’ SDK improvements β’ Lifecycle changes β’ Revocation for Idemixer β’ Tokenisation β’ RAFT β’ Operational metrics and logging β’ SDK and SHIM improvements β’ Burrow EVM β’ Long Term Service (LTS) support 07/17 03/18 06/18 10/18 4Q/18 * 1Q/19 * Based on https://wiki.hyperledger.org/projects/fabric/roadmap - Dates determined by the Hyperledger community - (*) Subject to change v1 v1.1 v1.2 v1.3 v1.4 v2.0
- 12. 12 Hyperledger functionality https://cachin.com/cc/talks/20170106-blockchain-rwc.pdf
- 13. 13 Pluggable Consensus β’ https://www.slideshare.net/MattLucas3/blockchain-whats-new-in-hyperledger-fabric-oct-2018 β’ This modular architecture allows the platform to rely on well-established toolkits for CFT (crash fault-tolerant) or BFT (byzantine fault-tolerant) ordering. β’ In the currently available releases, Fabric offers a CFT ordering service implemented with Kafka and Zookeeper. Kafka is fault tolerant, but not Byzantine fault tolerant β’ In subsequent releases, Fabric will deliver a Raft consensus ordering service implemented with etcd/Raft and a fully decentralized BFT ordering service.
- 14. 14 The Blockchain β’ https://hyperledger-fabric.readthedocs.io/en/release-1.4/ledger/ledger.html?highlight=blockchain#a- blockchain-ledger Each block contains a cryptographic hash of the previous block,[and transaction data (generally represented as a merkle tree root hash).
- 15. 15 IBM Blockchain Platform Platform Architecture Overview Application SDK Membership Services Peer Endorser Ledger Committer A Chaincode B !Events Ordering-Service O O O Fabric-CAExternal-CA optionaloptional Admin Users CACA Hardware Security Module(*) IBP UI (*) Enterprise Plan Certificate Authority IBM Blockchain Platform
- 16. 16 The Ledger, Blockchain and World State Database https://hyperledger-fabric.readthedocs.io/en/release-1.4/ledger/ledger.html#example-ledger-fabcar world state β a database that holds a cache of the current values of a set of ledger states. The world state makes it easy for a program to directly access the current value of a state rather than having to calculate it by traversing the entire transaction log (= Blockchain).
- 17. 17 Hyperledger Fabric components β’ Hyperledger has three components: β membership services β which manages digital certificates and access, β ordering service β which keeps the peers in alignment, β and peers β which hold the ledger. β’ A peer is also where chaincode, also known as smart contracts, are executed. β’ Membership and ordering services align well to being centralized. β Peers, on the other hand, can be distributed and placed anywhere you desire in the world. β Each member of the Hyperledger network should have their own peer. β The channels (databases) that a peer subscribes to, and transacts against, determines the memberβs role and capabilities in the blockchain network. https://www.ibm.com/blogs/systems/blockchain-how-should-you-organize-your-peers/
- 18. 18IBM Blockchain Platform How applications interact with the IBM Blockchain Platform Blockchain Developer Develops Chaincode Submits 0 1 2 3 Ledger Blockchain WorldState Get, Put, Delete Record SDK Application ! Emits Emits ! Peer Accesses
- 19. 19 Developing Hyperledger Apps, following the process
- 20. 20 What makes a good Blockchain Use Case? β’ β’ A Business problem that cannot easily be solved with existing techniques β’ An identifiable business network β’ With a shared ledger β’ With Participants, Assets and Transactions β’ A need for embedded trust but no Trusted Third Party
- 22. 22 Step 1) Re-use existing Blockchain Use Cases β’ https://www.ibm.com/blockchain/use-cases/
- 23. 23 Step 2) Leverage existing frameworks and libraries
- 24. 24 3) Re-use IBM Code Patterns for Blockchain β’ IBM Code Patterns for Blockchain: https://developer.ibm.com/patterns/category/blockchain/ β’ 10 Lessons: Design Thinking for Blockchain https://www.ibm.com/blogs/insights-on-business/government/10-lessons-design-thinking-blockchain/
- 25. 25 Blockchain, IoT and Smart Contracts in Supply Chain β’
- 26. 26 On-chain/Off-chain/Oracles Accessing existing data off-chain https://developer.ibm.com/tutorials/cl-extend-blockchain-smart-contracts-trusted-oracle/ https://developer.ibm.com/tutorials/cl-extend-blockchain- smart-contracts-trusted-oracle/ Oracles β’ Augur β’ Prediction Market β’ Game Theory β’ Human Oracles
- 27. 27 Introducing a trusted oracle β’ The architectural approach described in the previous section provides a reliable means to externalize complex decision rules. However, in the case of volatile information (such as interest rate), how can you reliably enrich a smart contract with such information? β’ One possibility is to delegate this responsibility to the client application: The client application retrieves the current interest rate and includes it in its payload to the smart contract. But why would the network trust the client application to always provide such information reliably and accurately? Hence, instead of delegating this responsibility to the client application, a better option is to: β’ Delegate the processing for obtaining volatile information to a third-party known as the oracle β’ Deterministically agree on the value to use for a volatile piece of information https://developer.ibm.com/articles/cl-extend-blockchain-smart-contracts-trusted-oracle/
- 28. 28 Integrating with existing systems - possibilities
- 30. 30 Step 4: Trade-offs Between Non-Functional Requirements Consider the trade-offs between performance, security and resiliency! Performance o The amount of data being shared o Number and location of peers o Latency and throughput o Batching characteristics Security o Type of data being shared, and with whom o How is identity achieved o Confidentiality of transaction queries o Who verifies (endorses) transactions Resiliency o Resource failure o Malicious activity o Non-determinism
- 31. Step 5) Use Visual Studio Code 31
- 32. IBM Blockchain Platform for Visual Studio Code 32 https://marketplace.visualstudio.com/items?itemName=IBMBlockchain.ibm -blockchain-platform
- 33. IBM Blockchain Plugin to VSCode 33 1. Create smart contract Project 2. Edit / write smart contract files 3. Package a smart contract project 4. Export a smart contract package 5. Connect to local_fabric runtime 6. Teardown the local_fabric runtime
- 34. 34 Example: The Blockchain Bean in the Supply Chain Space https://www.ibm.com/thought-leadership/blockchainbean/ YourCup NJB123
- 35. 35
- 36. 36
- 37. 37 Coffee exported original document
- 38. 38
- 39. 39
- 40. 40 IBM Cloud and Hyperledger SaaS
- 42. 42
- 43. 43
- 44. 44 How do we host our Blockchain application?
- 45. 45 IBM Enterprise Blockchain Platform
- 46. 46 Where do we go from here? LinkedIn: lennartfrantzell IBM Blockchain: https://www.ibm.com/blockchain Build for free on IBM Cloud: https://ibm.biz/Bd2L5W https://developer.ibm.com/startups/ Startup with IBM. Build. Scale. Win. With $120,000 in free IBM Cloud credits, Startup with IBM can put your business on the path to transformative growth. Disrupt your industry with IBM.