Hyperledger community update February 2018
•Descargar como PPTX, PDF•
1 recomendación•777 vistas
Presented to the 1st Miami Hyperledger Meetup Feb 1, 2018
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Similar a Hyperledger community update February 2018
Similar a Hyperledger community update February 2018 (20)
Último
Último (20)
Hyperledger community update February 2018
- 1. Hyperledger Community Update Christpher Ferris, IBM CTO Open Technology @christo4ferris February, 2018
- 2. About me IBM Distinguished Engineer and CTO Open Technology 38+ years in IT and distributed systems architecture & development Technical Leader in open standards and open source since 1999 Sun Microsystems - email, MOM, Java, XML, ebXML, SOAP IBM – WS-I, Web Services Reliable Messaging, Industry Standards, OpenStack, Cloud Foundry, IBM Cloud, Docker, Kubernetes, DevOps, Developer Advocacy, Hyperledger
- 3. 3 Today's Agenda • What is Hyperledger? • How was Hyperledger created? • Hyperledger Projects • Technical overview: Fabric • What is next for the Hyperledger community? • Hyperledger and IBM • Getting Started • Call to Action • Additional Resources • Q&A
- 4. 4 What is Hyperledger? Open source organization for enterprise blockchain technology Open Source not-for-profit accelerating the development and adoption of business blockchain technologies. Businesses with the most stringent blockchain requirements Trust Hyperledger because: Hosted by The Linux Foundation, the experts at accelerating open technology development and commercial adoption Neutral and collaborative, Hyperledger will always: • be open to all who wish to participate • produce open source technologies • remain immune to the commercial interests of any single company Industry-standard blockchain technology by business for business Hyperledger blockchain technologies emphasize key enterprise requirements: • Support for differing levels of access • Sub-universal validation • Cross-chain transactions • Modularity
- 5. 5 How was Hyperledger created? IBM initiated effort at LF to host “blockchain for the enterprise” IBM Open Blockchain which became Hyperledger Fabric 2016 2014
- 6. 2 years since launch 25k+ Commits 4 Tools 5 Frameworks 2 Production Releases Hyperledger Fabric v1.0 Sawtooth v1.0 200+ Members (30+ in China) 12 Active Community Working Groups 80+ Meetups Worldwide 20k+ Meetup Participants 600+ Media Clips Per Month 6 Hyperledger Momentum
- 7. 7 Note on Enterprise Ethereum Alliance • Led by Microsoft and Consensys (also a Hyperledger member) • Focused on making Ethereum relevant to enterprise use • Claims to be the largest blockchain org • Focused on development of standards for Ethereum, not developing open source • Though will deliver a “reference implementation” • In the year or so since it was launched, it has undergone some organizational churn and has accomplished little of substance • Should not be considered “competitor” to Hyperledger • Hyperledger actually has Ethereum projects and if EEA develops standards, Hyperledger will implement where appropriate
- 8. 9 ● First project that was contributed to Hyperledger ● Contributed by Digital Asset and IBM ● Smart contracts called “chaincode” are written in Golang (and with 1.1 Javascript) and run in secure Docker containers ● Channels ensure that only the participants involved in a transaction see the transaction Hyperledger Fabric Business Blockchain Framework
- 9. 10 Hyperledger Fabric First project incubated, first to graduate, first to reach 1.0
- 10. 11 ● Hyperledger’s second project contributed by Intel ● Second project to reach 1.0 maturity ● Supports both permissioned and permissionless deployments ● Includes a novel consensus algorithm, Proof of Elapsed Time (PoET), which mimics proof of work without the high energy consumption ● Uses the secure enclave on an Intel chip to provide a random wait timer to each of the validators (nodes) on the network ● First validator whose timer expires generates the next block ● Supports the EVM through a collaboration with the Hyperledger Burrow community Hyperledger Sawtooth Business Blockchain Framework
- 11. 12 ● Contributed by Soramitsu, Hitachi, NTT Data and Colu ● Written in C++ ● Emphasis on mobile application development ● Provides both Android and iOS SDKs Hyperledger Iroha Business Blockchain Framework
- 12. 13 ● Contributed by the Sovrin Foundation ● Focuses on identities rooted on blockchains ● Utilizes zero-knowledge proofs to provide verifiable claims ● These verifiable claims can be used to prove something about the identity without providing access to the underlying data Hyperledger Indy Business Blockchain Framework
- 13. 14 ● Contributed by Monax ● The first permissioned ledger with support for the Ethereum Virtual Machine (EVM) ● Originally named ErisDB ● Uses Tendermint as its consensus mechanism Hyperledger Burrow Business Blockchain Framework
- 14. 15 ● Contributed by IBM and Oxchains ● Suite of tools to quickly develop your blockchain business networks ● Modeling language allows you to have your business people specify the participants, assets, and transactions ● Developers write transaction logic in JavaScript ● Ability to generate a REST API and Angular application from the model Hyperledger Composer Business Blockchain Tool
- 15. 16 ● Contributed by IBM, with sponsors from Soramitsu, Huawei and Intel ● Used for DevOps ● Allows you to quicly deploy your blockchain networks ● Provides the ability to monitor your blockchain networks ● Blockchain network can be deployed on baremetal, virtual machine, or cloud Hyperledger Cello Business Blockchain Tool
- 16. 17 ● Originally contributed by IBM, Intel and DTCC. Recent release contributed by OneChain ● Allows you to visualize the blockchain ○ Blocks ○ Transactions ○ Network information ○ Chaincodes or Transaction families Hyperledger Explorer Business Blockchain Tool
- 17. 18 ● Contributed by NTT Data and Ripple ● Java implementation of the Interledger protocol ● Interledger protocol provides: ○ atomic swaps between ledgers (even non-blockchain or distributed ledgers) ○ a single account namespace for accounts within each ledger Hyperledger Quilt Business Blockchain Tool
- 18. 19 Hyperledger Fabric: Technical Overview Modular, permissioned blockchain platform for enterprise Network tools IBM provides tools for monitoring, logging, and for compliance reasons backup/restore Permissioned membership Operate a trusted blockchain network with known participants and regulatory oversight Channels Enable multi-party transactions with the privacy and confidentiality needed for regulated industries Transaction history Searchable transaction history for efficient auditing and dispute resolution Partitioned execution Optimize network performance by separating chaincode execution and transaction ordering Modularity Select preferences for number of peers, consensus, identity management, and encryption to dynamically grow a business network Confidentiality Production workloads
- 19. 20 Hyperledger Fabric Architecture O O O O Ordering Service Client Application SDK (HFC) Membership Services Provider Peer Endorser Ledger Committer A Chaincode B !Events
- 20. 21 Single Channel Network • Similar to v0.6 PBFT model • All peers connect to the same system channel (blue). • All peers have the same chaincode and maintain the same ledger • Endorsement by peers E0, E1, E2 and E3 E0 A B E3 E2 E1 A B A B A B OO O O Endorser Ledger Committing Peer Application Ordering Node Smart Contract (Chaincode) Endorsement Policy Key: Client Application SD K P Ordering-Service Hyperledger Fabric
- 21. 22 Multi Channel Network • Peers E0 and E3 connect to the red channel for chaincodes Y and Z • Peers E1 and E2 connect to the blue channel for chaincodes A and B E0 Z Y E3 E2 E1 A B A B Y Z OO O O Endorser Ledger Committing Peer Application Ordering Node Smart Contract (Chaincode) Endorsement Policy Key: Client Application SD K P Ordering-Service Client Application SD K P Hyperledger Fabric
- 22. 23 What's next for the Hyperledger Fabric community? • Hyperledger is the fastest growing project at the LF • Hyperledger Fabric • Rapid growth (code & community) – 27 companies and 159+ devs • Finds itself needing to "slow down" at times to ensure stability • Publishing periodic stable releases (quarterly is the plan) • Working through various development workflow approaches • Toolchain consistency between various adjacent projects is an issue • Working towards Hyperledger Composer 1.0 release in 1Q 2018 • Working towards Hyperledger Fabric 1.1 release in 1Q 2018 • Integration across projects (Burrow, Indy, Sawtooth) • Architecture WG and Performance and Scale WG deliverables Managing Growth
- 23. Hyperledger Roadmap 2018 Roadmap focus on developer experience and active network acceleration with common services 1Q 2Q 3Q 4Q Hyperledger Fabric Version 1.0 fixpacks Version 1.1 Javascript chaincode Connection Profile Performance and Scale improvements Technical Preview: Private channel data, Identity Mixer, Service Discovery (no SDK) support) Version 1.1 Fixpacks Version 1.2 Ledger Archive and Pruning RAFT Consensus Tech Preview of Zero Knowledge Proof, Identity Mixer Service Discovery Burrow EVM integration Version 1.3 Zero Knowledge Proof Byzantine FaultTolerance Identity Miixer Version 1.4 Hyperledger Composer Version 1.0 Links External Requires Account Services (preview) PBSA Integration – MMO (preview) Version 1.1 Account Services GA Extended Platform support for Windows developers and z/OS PBSA Integration – MMO GA Version 1.2 Industry Samples (unsupported support Pac) Extended Platform support for OPEN Linux PBSA Integration - SDS Version 1.3 Operational Console PBSA Integration – Provenance Engine Hyperledger Indy Revocation GPG support INDY reference Agent Extensible Agent APIs DID Auth Verifiable Claims support Schema Enhancement Shared Crypto Library Issuer Discovery TLS DID requests Proof request Hyperledger Cello Version 0.8 Ansible provisioning with Kubernetes support Version 0.9 Kubernetes Fabric deployment
- 24. 25 Hyperledger at IBM • IBM is a founding Premier member with a seat on the Governing Board • IBM’s Chris Ferris chairs the Technical Steering Committee (TSC). IBM’s Arnaud Le Hors is the other elected member of the TSC • IBM actively participates in most of the active WGs and Board committees of Hyperledger. • Hyperledger projects (Fabric and Composer) are the preferred platform for all IBM blockchain offerings and solutions, though we do work with customers on alternate platforms when requested The Foundation for IBM Blockchain Platform & Solutions
- 25. 26 Hyperledger Fabric and Composer: Let's Get Started • Development Guide • Getting Started Guide and tutorials for Hyperledger Fabric • Getting Started Guide for Hyperledger Composer • Help: Ask on the appropriate email or RocketChat channel, or on StackOverflow (hyperledger, hyperledger-fabric, hyperledger-composer) • Looking for work: • Backlog of issues in JIRA – many many open issues • Contributor experience, testing, "process" related activities • Find us on our RocketChat channel and ask questions! • Journeys & Education • Journeys - https://developer.ibm.com/code/journey/category/blockchain/ • developerWorks Blockchain Developer Center • IBM Blockchain - https://www.ibm.com/blockchain/
- 26. • Get involved • Meet up communities • Conferences • Membership • Read the research paper: https://arxiv.org/abs/1801.10228v1 Ensure the strength and longevity of a core technology to your business. Publicly proclaim your leadership in the blockchain space. Work with other blockchain leaders to develop on and promote Hyperledger projects. Call to Action
- 27. More Resources
- 28. 29 Where is the Hyperledger community? • GitHub • https://github.com/hyperledger/ • Communications • http://hyperledger.org/community • Mailing list: • https://lists.hyperledger.org/mailman/listinfo • Weekly Technical Steering Committee Meeting • Conferences (SIBOS, Consensus, various others) • Lots of WGs and SIGs (special interest groups) • Each with their own RocketChat channel, mailing lists, regular calls, ...
- 29. 30
- 30. Thank you! @christo4ferris Q & A 31
Notas del editor
- Hyperledger is a collaborative project of the Linux Foundation, founded in 2016 by IBM and 20 co-sponsors with the objective of creating an organization under open governance to develop blockchain and distributed ledger technologies for the enterprise. The primary focus is around “permissioned” blockchain network, which means that rather than a permission-less public network where the participants are all anonymous, the participants are explicitly granted access and known to each other.
- In late 2014, early 2015, IBM began exploring the blockchain space extensively. We tried out all the available platforms, especially those available as open source, and we also engaged a number of our enterprise customers to better understand requirements for a hypothetical blockchain solution. We came to the conclusion that none of the existing platforms really met enterprise level requirements. We then embarked on developing our own, borrowing heavily from the experience with the other blockchain platforms. Early on in this process we recognized that to be successful in the market, that the technology would need to be open sourced. So, we engaged with the Linux Foundation to begin a process of standing up what eventually became the Hyperledger organization. In December of 2015 we pre-announced the intention to form the organization and invited prospective co-sponsors to help us shape the open governance model. In February of 2016, the organization was formally launched with 30 initial members and 11 Premier members, including IBM.
- There are four blockchain platform projects: Fabric, which was originally contributed by IBM and became the first incubating project of Hyperledger, the first to exit incubation into Active status and the first to rech a 1.0 level of maturity. Iroha is a similarly architected platform to Fabric, written in C++ and oriented to fintech solutions. They have implemented a novel but as yet un-proven consensus model and have mobile SDKs to access a set of APIs that are consistent with those found in Fabric. Sawtooth was originally contributed by Intel and implements some interesting concepts including an alternative to Proof of Work that they call PoET (Proof of Elapsed Time) which requires a trusted execution environment (notably their SGX chip). Finally there is project Burrow, which is Hyperledger’s first Ethereum-based project. Project Indy is an implementtion of self-soveriegn identity system that implements its own blockchain foundation (plenum). Composer was originally designed to be a front-end for Fabric to enable a business analyst to model a business network, assets and state transitions in a business process and have the model generate the deployment artifacts to Hyperledger Fabric to implement that network. Cello is a platform provisioning framework and Explorer is effectively a UI into the inner-workings of the blcokchain network.
- As noted, the Hyperldger Fabric was the first project incubated, first to graduate to Active status, and the first to reach a 1.0 level of maturity, as determined by its maintainers (representing IBM, State Street Bank, Huawei and HACERA). The factoids above speak for themselves. The important theme to get across is that Hyperledger Fabric is NOT just an IBM project, but has a diverse maintainership, a large pool of engineers from a large number of major vendors and startups as well as a few individuals. We have delivered significant innovation in record time and have systems in production and various stages of nearing production being implemented by a variety of Hyperledger members and non-members.
- These six capabilities define Hyperledger Fabric fairly well. Should be self-evident.
- The architecture of Hyperledger Fabric consists of four primary components: peer, ordering service, membership service provider and the client application, which would typically leverage one of the provided language specific SDKs (Node.js, Java, and coming soon python, go and REST/JSON).
- This slide is an example of a Hyperledger Fabric network which is very similar to a v0.6 PBFT network. All peers run the same chaincode and are part of concensus.
- This slide is an example of a Hyperledger Fabric network with 2 channels.
- Self explanatory. Link to Burrow EVM integration with Fabroc
- Self explanatory
- Self explanatory
- get involved, meet up communities, conferences, membership links, contributing links etc
- get involved, meet up communities, conferences, membership links, contributing links etc
- As noted, Hyperledger is a collaborative project of the Linux Foundation. The code is on GitHub, but maintained in Gerrit - in a manner similar to OpenStack. The community uses RocketChat, a chat system similar to Slack (but open source and free to self-hosting) and mailing lists. There are a variety of working groups each with their own RocketChat channel and mailing list and periodic meeting schedule published in the Hyperledger Calendar. The community is led by engineers and architects from IBM, Intel, Csco, RedHat, Evernym, Huawei and Oracle.