Category

Blog

UN-pluggable Consensus With Hyperledger Sawtooth

By | Blog, Hyperledger Sawtooth

We have an exciting technical update to share! Hyperledger Sawtooth now supports un-pluggable consensus. That means you can easily change all blockchain settings by submitting a transaction to the network – including changing the consensus algorithm on the fly. This transition happens, like all state, at the block boundary.

When we designed our 0.8 architecture this year a big part of it was putting all blockchain configuration on the chain itself. That includes the selection of consensus algorithm.

The benefit is you can start a network with a small-scale or lax byzantine consensus algorithm and change as your network grows. And that change does not require you to stop all validators, flush your state, and start over with a new genesis block. There’s no outage at all involved in changing consensus. Coordination among peers to change consensus is implicit with this being a blockchain transaction.

In our 0.8 stable builds you can submit transactions to change between DevMode, PoET, and PoET-SGX. The initial development to add Raft is underway. We anticipate adding full support for Raft after we get Hyperledger Sawtooth 1.0 release completed this year.

For more information, you can review this presentation:

If you’re interested, you can learn more about Hyperledger Sawtooth and see real world examples of how the technology is being used. You can also read the documentation, join the community on RocketChat or pull the code from GitHub to kick the tires today.

 

Developer Showcase Series: Chris Kowalski, Blockchain Tech Labs

By | Blog

Our Developer Showcase blog series serves to highlight the work and motivations of developers, users and researchers collaborating on Hyperledger’s incubated projects. Next up is Chris Kowalski an engineer at Blockchain Tech Labs.

What advice would you offer other technologists or developers interested in getting started working on blockchain? 

My advice to offer other technologist is to start right on. The blockchain space offers a dynamic set of unique opportunities to work in a field that is not that explored from other developers hence you can easily stand out. The parallels with the foundation of the web in the 90s are so many and working on blockchain projects can empower developers, so they leave their footprint. Not to underestimate the demand for skilled engineers from financial perspective however with blockchain coming more and more to surface this is an area that offers endless opportunities. There are many projects out there looking to pay premium salary for the top talent in this area.

Getting into blockchain development will require dedication, continuous improvement and a lot of reading but it’s definitely worth it in the long run.

Give a bit of background on what you’re working on, and let us know what was it that made you want to get into blockchain?

I have been involved with cryptography since my university years. In addition for the last 5 years I have been working on various blockchain projects including ATMCoin, Clinicubes and others. For me as a software engineer, this was an interesting challenge and offered me the chance to meet really amazing, talented people. We are lucky to have some of the smartest developers working on Blockchain/DLT projects and this had motivated me to be a part of this technology.

What project in Hyperledger are you working on? Any new developments to share? Can you sum up your experience with Hyperledger?

We have started with Hyperledger Fabric and had been successfully implementing several Proof of concepts such as a Supply Chain demo, Mortgages product and Clinical Trails Management infrastructure. When Hyperledger Composer came out it was the natural move for us. It made development and testing so much easier. Since we grew in numbers within Blockchain Technology Labs it made it easier and faster for our new team members to adapt to Hyperledger quicker.

What do you think is most important for Hyperledger to focus on in the next year?

I would say building more developer tools and improving on the awesome work done on the Composer framework but also getting some out-of-the-box testing and automation tools.

Where do you hope to see Hyperledger and/or blockchain in 5 years?

Hyperledger would still be the preferred infrastructure for permissioned based blockchain and thus preferred for Enterprise applications. I don’t see that changing anytime soon. The adoption and support from Intel and IBM is key for this success. I expect blockchain type of protocols to be everywhere and replacing centralized infrastructure.

Meet the TSC: Binh Nguyen, State Street

By | Blog, Hyperledger Fabric

Back to our blog series that focuses on the motivations and backgrounds of the individuals that make up Hyperledger’s Technical Steering Committee (TSC). The TSC is a group of community-elected developers drawn from a pool of active participants and is a core element of Hyperledger’s Open Governance model. The TSC is responsible for all technical decisions – from which features to add, how to add them and when, among others.

Now let’s introduce the next Hyperledger TSC member, Binh Nguyen from State Street. Let’s see what he had to say about Hyperledger, his role in the TSC and the community!

Describe your current role, background and why you wanted to be a part of the Hyperledger TSC?

I am currently a development director at State Street. I founded Open Blockchain, an open source project, which became the initial codebase of Hyperledger Fabric. I have been the chief architect of Hyperledger Fabric project since genesis and been working passionately with the community on architecture and implementation of Fabric. With my hands-on experience in blockchain, serving the community as a TSC member would allow me to help:

1) guide our technical projects in the right direction

2) involve in building and growing our community

3) learn from other members for my professional and personal development

4) be visible: after all, it’s not about who you know, it’s about who knows you

Binh Nguyen, State Street

What are the benefits of Hyperledger’s open governance model?

I’ve been working on open source projects and learned to appreciate the model, more so for blockchain due to its potential to transform our economy, governance systems and businesses. No one company or organization should have control of the technology but by an open governance, we can ensure it is driven by the interests of the community and humanity. This is, to me, the number one reason why we do what we do in Hyperledger.

What advice would you offer other technologists or developers interested in getting started working on blockchain?

For those who want to work on shaping blockchain technologies, I would say read up and join Hyperledger; we are always welcome more developers. For those who are looking at building blockchain applications, my advice is to start small with a clear use-case, like bitcoin, a very simple but powerful and elegant application of blockchain. The key is to maximize the network effect between members participating in the blockchain. If you can crystalize that, you have a good blockchain application use-case.

What’s the one thing you hope to accomplish by being a part of Hyperledger’s TSC?

I am grateful for having been elected to TSC. My key objective is to help our community foster leading exemplar of blockchain projects for the good of everyone.

What use cases are you most excited about with Hyperledger and/or blockchain?

I am excited about a lot of blockchain use-cases as this technology can be applied to many different areas, both public and private sectors. From voting records to asset titles management to shipping and logistics. But the set of use cases that I think would have the most immediately impact on everyone of us is finance: from clearing and settlements to capital markets to payments. Financial institutions are facing once-in-a-lifetime disruption, and that’s what I am so excited about blockchain.

 

Developer Showcase: Vishwasrao Salunkhe, Virtusa

By | Blog, Hyperledger Composer, Hyperledger Fabric

Our Developer Showcase blog series serves to highlight the work and motivations of developers, users and researchers collaborating on Hyperledger’s incubated projects. Next up is Vishwasrao Salunkhe, a lead consultant at Virtusa.

What advice would you offer other technologists or developers interested in getting started working on blockchain?

First start with the basic concepts of Blockchain like Cryptography, Consensus algorithm, Peer to Peer communication, distributed applications. Once you are comfortable I recommend completing the below course to get high level overview of Blockchain:

https://developer.ibm.com/courses/all/blockchain-essentials/

After this course, you can start playing with Hyperledger Composer Playground and start with existing examples, understand how to define business network, Assets, Participants, Transactions and Events.

You should be familiar with JavaScript. You will be able to define business network in Hyperledger Composer with a JavaScript like Language. Also with help of NodeJS SDK you will be able to talk to the underlining Hyperledger Fabric network. So, only with the JavaScript Language you will be able to develop applications (frontend, backend) around Hyperledger Fabric.

Vishwasrao Salunkhe, Lead Consultant, Virtusa

What project in Hyperledger are you working on? Can you sum up your experience with Hyperledger?

I am working on Hyperledger Fabric. I started working with Fabric 0.6. Once I got basics of it, I started writing a smart contract in the Go Language. There were few issues I was facing like setting the Hyperledger Fabric network, writing smart contracts in Go (new language for me) and deploying the smart contracts.

Hyperledger Composer is life savior for me, it made my job so easy that I am able to define my business network, assets, transactions etc with a JavaScript like language, deploy locally and test it. Before defining my own business network, I went through all existing demo business network and tried to run them, then changed few things like assets attributes, participant’s attributes and transactions.

What do you think is most important for Hyperledger to focus on in the next year?

Make developers’ lives easy. Until we have an ecosystem of tools around Hyperledger to design, develop, test, deploy blockchain applications, developers will not be able to move fast with Hyperledger

With Hyperledger Composer, it’s easy to get started, so we need more tools like composer.

Also, we need to evangelize Hyperledger projects through online talks, webinars, workshops and conferences to spread word.

As Hyperledger’s incubated projects start maturing and hit 1.0s and beyond, what are the most interesting technologies, apps, or use cases coming out as a result from your perspective?

Prior to the 1.0 release of Hyperledger Fabric, people had so many business cases to solve with blockchain but they were not enough tools to get beyond POCs. But with 1.0, people started going beyond POCs or MVPs. Some businesses are already started to use Hyperledger Fabric in production. This is good sign. Also, now new apps, tools frameworks are sprouting up all over.

I would like to see more tools and frameworks come up which will help to speed blockchain implementations. Also, giants like IBM, SAP, Oracle will come up with integrations of their existing applications with Hyperledger.

Where do you hope to see Hyperledger and/or blockchain in 5 years?

Internet made people to come close, now blockchain will make businesses to come close

As per hype made in media that blockchain will be mostly used in financial sector, I think not only in finance but fields like supply chain, Insurance, retail and most importantly government sectors will also be covered by blockchain. And Hyperledger will be leading blockchain.

Consider Shipping/Logistics scenario with IoT enabled shipping containers:

Participants: Sender, receiver, freight companies, customs, and banks, Insurance Companies

Assets: Cargo Properties, shipping documents

Business Rule: temperature in containers should always be more than 5 degree.

Sender  =====è  Transporter 1(Ship)      ======è Transporter 2 (Road)  ===è Receiver

                              Insurance Company 1             Insurance Company2   

Blockchain in Logistics/Supply Chain Example (Image Credit)

Goods moved from sender to receiver go through various transportation mode and different insurance companies are involved.

Containers are IoT enabled and data sent from them are stored into Blockchain network. Now when goods are with Transporter 1 and while transporting he does not follow business contract (E.g. Temp of containers should be below 5 degree all time), because of that some containers are not damaged/not useful, then T1 will get penalized based on smart contract and claim processing of these damaged goods will be trigger automatically for Insurance Company 1.

Also, once T1 hands over container to T2, his payment gets triggered

 

VIDEO: Hyperledger, A Greenhouse Incubator for Blockchain Projects

By | Blog, Hyperledger Burrow, Hyperledger Cello, Hyperledger Chaintool, Hyperledger Composer, Hyperledger Explorer, Hyperledger Fabric, Hyperledger Indy, Hyperledger Iroha, Hyperledger Sawtooth

Hyperledger hosts and incubates multiple technology projects, all advancing business blockchain frameworks and modules through open source collaboration. Currently, Hyperledger hosts 6 open source frameworks and 3 open source blockchain tools.

To introduce the concept of blockchain technologies and the Hyperledger organization, we created an explainer video illustrating Hyperledger as a greenhouse incubator for these open source blockchain projects. Intended to serve as a starting point suitable for all audiences wanting to learn about Hyperledger and business blockchain technologies, we hope this 3-minute explainer video will shed light on the following:

1. A distributed ledger is a common system of record with no central authority.

A ledger contains a record of your transactions, along with other transactions in the network. Distributed ledgers are multi-party databases with no central trusted authority. Blockchains can be used to record promises, trades, transactions or simply items we never want to disappear.

2. It’s vitally important to know that your copy of the ledger is identical to everyone else’s

All businesses participating in a commercial ecosystem need a ledger to contain a record of transactions. As a result, across the global market there are ledgers that organizations and individuals alike must trust. Mirrored exactly across all nodes in a given network, distributed ledgers allow everyone in an ecosystem to keep a copy of the common system of record, free from discrepancies. Nothing can ever be erased or edited; parties can only add to the ledger.

3. Hyperledger provides the underlying open source software, on top of which anyone can set up blockchain apps and services to meet business needs.

Hyperledger is incubating and promoting enterprise grade, open source business blockchain technologies, including distributed ledgers, smart contract engines, client libraries, graphical interfaces, utility libraries, and sample applications. Built under technical governance and open collaboration, individual developers, service and solution providers, government associations, corporate members and end users alike are all invited to participate in the development and promotion of these thriving technologies.

4. Hyperledger is a global, cross-industry, collaborative open source consortium.

With 170+ member organizations working across industries and competitive lines, and 400+ code contributors, Hyperledger is the fastest growing consortium in the history of The Linux Foundation’s collaborative projects. Just like you see in this greenhouse, with the help of The Linux Foundation and Hyperledger’s open source approach, everyone does their part to ensure the success of the whole, nurturing these blockchain ecosystems for evolution, expansion and continued growth.

The most renowned leaders in finance, healthcare and supply chain across the globe trust Hyperledger to build their business blockchain technologies. Who will you trust with your trust network?

We encourage developers to join our efforts on Hyperledger via github, Rocket.Chat, the wiki or the mailing lists. You can also follow Hyperledger on Twitter or email us with any questions: info@hyperledger.org.

 Watch and Share the video:

Hyperledger Fabric v1.1.0-preview is now available

By | Blog, Hyperledger Fabric

Guest post: Hyperledger Fabric 1.1 release managers, Chris Ferris & Dave Enyeart

The maintainers are pleased to announce that the Hyperledger Fabric v1.1.0-preview release has been published. Download the binaries and images here: http://hyperledger-fabric.readthedocs.io/en/v1.1.0-preview/samples.html#download-platform-specific-binaries

The v1.1.0-preview release includes Hyperledger Fabric, Hyperledger Fabric CA, and the SDK for Node.js. Note that we are not yet feature complete for the eventual 1.1 release… that will come with the next published release, v1.1.0-alpha. However, we wanted to get the following functionality published to gain some early community feedback on the following features:

FAB-2231 Node.js Chaincode Support

FAB-5363  Node.js SDK Connection Profile

  • Simplify how your applications connect to Fabric with new connection management capabilities and this Tutorial.

FAB-830 Encryption library for chaincode

  • Encrypt your data using the new chaincode encryption library, see the Example.

FAB-5346 Attribute-based Access Control

FAB-6089 Chaincode APIs to retrieve client identity

  • Obtain transaction submitter identify (certificate, MSP ID, attributes) to make access control decisions using these Chaincode APIs.

FAB-6421 Performance improvements

  • Many performance optimizations to significantly improve transaction throughput and response time.

Additionally, there are the usual bug fixes, documentation and test coverage improvements, UX improvements based on user feedback and changes to address a variety of static scan findings.

Many thanks to the 77 developers representing 13 companies and individuals that contributed to this preview release thus far. We continue to see increasing diversity of contribution from member companies. We encourage all developers to join our efforts on Hyperledfer Fabric and other incubated projects. We welcome any feedback you may have, either via this mailing listJIRA or RocketChat . You can also follow Hyperledger on Twitter or email us with any questions: info@hyperledger.org.

Happy coding!

[VIDEO] Hyperledger Interviews Rob Palatnick of DTCC

By | Blog

Rob Palatnick is the chief technology architect and managing director at DTCC. Rob is working with DTCC to investigate and research blockchain to find out where its best use cases are going to be.

According to Rob, blockchain’s ability to share information in near real time with perfect security, immutability and privacy between industry participants can create enormous efficiencies in the post trade processing landscape for the financial community.

Hyperledger provides DTCC the perfect opportunity to contribute back as they look at the different business opportunities and use cases. DTCC wanted to take advantage of working with the entire industry and the open source community in finding the right avenues to leverage the technology. DTCC sees blockchain as a way to bring about efficiencies, and improve risk and controls — all at a lower cost. Everyone can look at the same information that is shared and be confident that it is accurate and correct with blockchain.

Rob says Hyperledger gives DTCC the opportunity to be in a leadership role and ensure that the financial markets understand how this technology can be implemented in the most risk organized and efficient manner possible.

 

Productionizing Blockchain Solutions – A Pragmatic Approach

By | Blog

Guest post: Hitarshi Buch, Blockchain COE Lead, Wipro Ltd.

The small but ever expanding world of blockchain has slowly but surely gone past the proof-of-concept / proof-of-technology stage. Gone are the days when organizations were satisfied with prototyping on blockchain and ticking the proverbial check box by spending some dollars from their innovation budget.

Now, I am not jumping the gun and suggesting that blockchain has entered mainstream and we will see plethora of productionized blockchain solutions. At the same time, the fact remains that organizations have developed a fair understanding of blockchain and now want to know what it takes to implement a production-grade blockchain based solution. Since blockchain solutions involve a multiparty ecosystem and consortium kind of model, given below are some of the questions that need to be resolved.

  •      Who will setup the blockchain network in a multi-party ecosystem?
  •      Who will manage the onboarding / off boarding of members in the consortium e.g. adding new nodes or removing existing nodes?
  •      Where will the blockchain nodes be hosted? What type of network connectivity will be required?
  •      Who will own the blockchain network and how will it be funded?
  •      What is the total cost of ownership of the blockchain based solution?

It would be fair to assume that nobody has definite answers because firstly “it depends” on several factors such as the use case being implemented and the business agreements between different participants of the ecosystem. Second factor is the decentralized nature of blockchain, which leads stakeholders to treat this problem statement differently than any other IT system, which is where I beg to differ.

Therefore, I would like to propose a practical and pragmatic approach for productionizing blockchain solutions, which will be following a permissioned, consortium model. The first and foremost aspect is to accept the fact that some degree of centralization will be required not only for setting up the blockchain nodes and network but also to ensure a sound governance model to make the solution sustainable. At the risk of sounding too prescriptive, here are some tenets for productionizing blockchain solutions.

What? Why?
     Host the blockchain nodes and network on a cloud platform      Ease of provisioning, dynamic scaling as well as dedicated, customizable subnet

     Security and privacy concerns on cloud are unfounded – revisit the decision of why confidential/private data needs to be maintained on blockchain

     Onboarding / off-boarding of nodes can be managed centrally, mainly for private, permissioned blockchain

     Each participant can take responsibility for integrating their existing enterprise systems to their blockchain node

     Leverage a PKI management solution which is complementary to the blockchain platform being used      Participants of the blockchain network will sign transactions using digital certificates to prove their identity

     Each participant will need to securely generate and store their private keys

     Blockchain topology for production environment should ensure minimum viable configuration      Blockchain inherently supports a decentralized model but a minimum set of nodes have to be up and running to ensure business continuity

     Introducing additional nodes solely to eliminate blockchain network failure / downtime will be required

     Use decentralized storage for data availability and blockchain’s efficiency

     Storing large sized documents and/or data entities on blockchain is counter-productive as all nodes need to get synced up every time

     Off chain storage mechanism of critical data entities should be complementary to the decentralized model of blockchain

     Largest stakeholder should be the process owner and manage smart contract development lifecycle till minimum go-live of the blockchain solution      In a private, permissioned blockchain setup all parties would have to transact using the same version of smart contracts

     Largest stakeholder will have the greatest motivation to ensure that smart contract versioning and releases do not disrupt the business continuity

     Blockchain network management should be done by a 3rd party network provider      Technical complexities on provisioning, administering, monitoring and maintaining the blockchain should be contracted out to a 3rd party network provider

     Self-governing and self-healing blockchain models are not available yet

     Track contribution and consumption of consortium members on blockchain      In order to arrive at a funding / cost model, the metering of contribution and consumption of each participant can be tracked and stored in blockchain

     Subscription and invoicing can be based on this collated data once the solution stabilizes

     Largest stakeholder should be the solution sponsor till minimum go-live of the blockchain solution      This will resolve the Omni-present conundrum of who will bear the cost of ownership

     Benefits derived from the minimum go-live will help participants arrive at a workable ownership and funding model

     Implement multi-tenant DApp and integration layer which can be used by majority of participants      All participants of blockchain may not have the technology expertise or business motivation to build off chain components required to interact with blockchain

     As a bare minimum the largest stakeholder can bundle DApp and integration components, which can be deployed on each node with minimal configuration

     Formalize multiparty agreement after the initial pilot is rolled out and adopted      One of the biggest roadblocks to onboarding of participants is the inability of consortium members to arrive on common rules of engagement

     Side-stepping this obstacle at least till the pilot phase is recommended

     Adopt BPM Governance principles such as defining process owners, participant roles and responsibilities as well as measurement of process KPIs      Blockchain cannot and should not be seen as technology replacement only. The objective should be to achieve business process improvement and efficiency

     Smart contract enabled blockchain platforms are more aligned to BPM (as described in my previous blog) where the process participants are inter-enterprise rather than intra-enterprise

While there is no silver bullet for productionizing blockchain solutions, there is definitely a need to take the learnings out of successfully implemented solutions using centralized aka “traditional” methods. Certain grey areas will remain, which will only get resolved as blockchain platforms gain maturity, scalability and come bundled with tools and techniques required for production-grade adoption.

 

Developer Showcase: Chuck Buhecker, Federal Reserve Bank of Boston

By | Blog, Hyperledger Composer, Hyperledger Explorer, Hyperledger Fabric

What advice would you offer other technologists or developers interested in getting started working on blockchain?

My advice is two-fold.

First, start now. There’s so much to learn. Begin by exploring and understanding the theory behind DLTs; then get your hands dirty with as many examples as you can find. There is a lot of learning involved with the technologies incorporated within Fabric. After working primarily with Java and a few other languages sprinkled in for 18 years, I found YAML files, Golang, and Docker all to be eye-openers.

Second, be patient. Be prepared to do a lot of reading, coding, and experimenting. Even if you have been told by an “expert” in the field that what you are trying to accomplish won’t work, still give it a shot. What you learn along the way is invaluable.

This technology is continuously evolving, and what works in one version may not work in the next. I’ve mostly seen positive outcomes from experimentation. Don’t be tempted to throw your hands up in disgust. Okay, maybe once or twice… but persistence is a virtue!

Chuck Buhecker, Senior application developer, Federal Reserve Bank of Boston

Give a bit of background on what you’re working on, and let us know what was it that made you want to get into blockchain?

I was a latecomer to blockchain and DLT. About a year ago, I started working on a simple AngularJS UI by interacting with Spring REST, and in turn calling Ethereum APIs for a proof of concept (POC) at the Federal Reserve Bank of Boston.

Upon completion of our initial POC, we began looking at Hyperledger Fabric v0.6. That’s when I knew there was no turning back. I very much liked working with v0.6 and the documentation served as a solid foundation for me to enhance my understanding of the underlying technologies. Now, with v1.0, I am continuing to expand my skillset.

At the Boston Fed, we’re getting our hands dirty experimenting with DLT to determine applicability, potential benefits, and risks. What better way to learn about the technology than exploring it first hand?  

What project in Hyperledger are you working on? Any new developments to share? Can you sum up your experience with Hyperledger?

The Hyperledger umbrella has so many great sub-projects – I just wish there were more hours in the day to explore them all, reminiscent of the Jakarta Apache days. I have predominantly been working with Fabric sub-umbrella Fabric Core, the Fabric Java SDK, and the Fabric Node SDK, as well as briefly looking into Hyperledger Composer, Hyperledger Blockchain Explorer, and Hyperledger Fabric-SDK-Go.

I am grateful that the documentation has been well maintained. Hyperledger’s YouTube channel has also been incredibly helpful, especially in regards to the v1.0 chaincode deployment strategy.

As Hyperledger’s incubated projects start maturing and hit 1.0s and beyond, what are the most interesting technologies, apps, or use cases coming out as a result from your perspective?

I see a lot of good implementations that don’t necessarily have a great use case, but from my perspective that is fine. Low-risk, low-use projects using DLT can help develop skills. Then, when there is a need for a mission-critical application, the learning curve isn’t so steep.

I’ve also seen many great third-party applications used in their infancy for Blockchain monitoring, streamlined Blockchain genesis, and Fabric APIs that are less cumbersome and easier to understand than some under the Hyperledger umbrella.

What is the best piece of developer advice you’ve ever received?

Don’t over-engineer to solve a problem. With the wonderful world of dynamic class loading, abstraction, aspecting, and more, it’s easy to develop an overwrought, complex solution for a simple problem.

What technology could you not live without?

If I had to limit it to one technology, I’d say software in general. I don’t know what I’d do with my life if I didn’t write software. Actually, I might be a photographer, but I probably wouldn’t get paid very well because I’m no Ansel Adams!

Wind River Unveils SParts Project at Open Source Summit 2017

By | Blog, Hyperledger Sawtooth

Guest post: Mark Gisi, Director of Intellectual Property and Open Source at Wind River

The SParts project (https://github.com/Wind-River/sparts)  developed a Hyperledger Sawthooth based Software Parts Ledger to track the open source components from which today’s manufactured products and devices are constructed. A number of important benefits are obtained by knowing which open source components are used such as:

1) ensuring manufactures are able to identify and secure the distribution (licensing) rights for all open source components;

2) understanding the impact of open source based security vulnerabilities;

3) enable identification of cryptography technologies (e.g., FIPS 140-2 certification, export licensing);

4) enable accurate reporting on all open source parts as a requirement to obtaining functional safety certification for safety critical products (e.g., medical devices, aircraft, autonomous vehicles, elevators, …)

The Software Part ledger establishes trust between a manufacture and its suppliers by tracking suppliers, their software parts, the open source components used and their corresponding compliance artifacts (e.g., source code, legal notices, Open Source BOM, SPDX data, cryptography data). This is particular helpful for manufactures who build products by utilizing software from many different suppliers (and sub-suppliers). To achieve accountability a mechanism is need to maintain global state information about suppliers; their parts and compliance artifacts for all participate across the supply chain. To establish trust among all participants, these records need to be i) transparent, ii) immutable, while iii) removing the dependence on third party information brokers (middlemen). We obtain the required level of trust by utilizing the Hyperledger Sawtooth platform to construct a Software Parts Ledger.

A demo of the Software Parts Ledger will be given in Intel’s booth at Linux Foundation’s Open Source Summit Europe on October 23rd, 24thand 25th. Come on by to see it in action!