Hyperledger Foundation Hyperledger Project Demos, 30 Sep 2021

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: Hyperledger Grid v0 2 Release Party

Description

A recording of the Sept 30, 2021 Hyperledger Grid v0.2 Release Party to celebrate the second step of a long journey. See a demo of foundational features that power our vision for virtual, vertically-integrated supply chains built on open industry standards. - Some of the key questions that will be addressed: What are the existing challenges that hinder B2B collaboration across supply chains? How can we optimize processes and outcomes with integrated capabilities? What does a tangible capability powered by Hyperledger Grid look like?

More about Hyperledger Grid is at: https://www.hyperledger.org/use/grid

----
Hyperledger – Open Source Blockchain Technologies

Hyperledger is an open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments.
It serves as a neutral home for various distributed ledger frameworks including Hyperledger Besu, Fabric, Sawtooth, Indy, as well as tools like Hyperledger Avalon, Cactus and libraries like Hyperledger Aries, Ursa. Learn more about Hyperledger projects: https://www.hyperledger.org/use

Case Studies: https://www.hyperledger.org/learn/case-studies
Training & Certification: https://www.hyperledger.org/learn/training
Tutorials: https://www.hyperledger.org/use/tutorials
Webinars: https://www.hyperledger.org/learn/webinars
Events: https://www.hyperledger.org/events
Vendor Directory: https://www.hyperledger.org/use/vendor-directory

Subscribe to the Hyperledger Newsletter: https://www.hyperledger.org/newsletter

Follow-us on Twitter @Hyperledger

Learn about Hyperledger Membership: https://www.hyperledger.org/about/join

#Hyperledger #HyperledgerGrid #Blockchain

A

Welcome to the grid 0.2 release party part of the one of the major hyperledger projects dedicated to supply chain solutions built on a distributed ledger. My name is jack fishneski, I'm part of the grid team, leading our community development and for the next 42 minutes.

A

I and other members of the grid team will be hosting you on this release party very simple agenda for the next 42 minutes.

A

Once I'm done with this little intro, I will turn it over to david checky, one of the key sponsors and thought leaders for the grid project he's going to briefly explain the vision and the philosophy behind the overall digital supply chain platform and the hyperledger grid project.

A

Specifically, once he's done with that, we're going to give the lion's share of the time for this 40-minute session to shannon t lander and myself, and we're going to be doing a demo of the features that we've released as part of grid 0.2 right before I turn it over to david checky. I just want to note as a reminder that this is a public meeting, by which I mean it is not affiliated with any specific company or business, so we will not be discussing uh business interests during this session.

A

This session is focused on the hyperledger grid project, an open source project for uh building integrated supply chain solutions on a distributed ledger. That will be the focus of our time today. We're really glad that you all have uh taken some time out of your days to join and with that david checky. The floor is yours,.

B

Thanks jack, great uh great kickoff and awesome uh music selections to ease us into what is truly a great milestone for the team and community uh working on grid couldn't be happier to be here to talk to this entire audience about where we're at with grid the 0.2 release and to get into a demo. uh Let's just talk briefly, I know what jack even said brief on the slide.

B

Here I will say I'm like personally, I'm very excited about what we're doing with grid, and I can talk at length about it and uh I will do my best to keep it brief again. I'm dave checky. uh I really try to guide the the vision and strategy for a grid as a product and evolution, but that is a community effort and it is we're going to talk about how it's open, open source, uh open governance and open standards. As we get into this a little bit, uh I think jack is driving here.

B

I'm going to have him, go ahead and right on advance right, so just to set the stage a little bit really seeking to integrate our supply chains in digital ways.

B

Looking at technology as an enabler to establish more effective supply chain, connectivity is something that many many organizations are doing and many uh software products are seeking to to help enable. This is a vision that I think is widely recognized and has been for some time as super opportunistic.

B

With hyperledger grid, we're really seeking to do that in deliberate ways, taking advantage of uh modern technology and modern, uh modern platforms uh we'll go ahead to the next next slide as well. I want to set the stage a little bit more, that this is a hyperledger project. For those of you not familiar with hyperledger hyperledger is a linux foundation.

B

Project umbrella project- that is a great home uh both uh in this picture metaphorically, but also uh as a community uh for enterprise, centric and or uh just general blockchain or distributed ledger based solutions.

B

Hyperledger grid you can see in this picture- is aligned with a domain domain, specific capabilities in particular around enabling supply chain integration in this uh in this family. uh So a little bit more background on grid, then on the next slide. Here, that's setting the stage it's part of hyperledger and the hyperledger foundation. So really what is grid grid is a platform for building supply chain solutions.

B

Many of us talk a lot about the value of common process, data and technology. Aligning those types of anchoring values across supply chains can drive meaningful efficiencies, value and business outcomes.

B

Different trading partners, working with different data or working in different ways with different processes or using different types of technologies, are the reality of our supply chains every day and they create friction and unnecessary uh effort and costs. uh Doing things like reconciling uh invoices or or uh keeping aligned.

B

Data about the products that we are exchanging in a supply chain are just exact common examples of the types of custom integration that we put up with in our in our supply chains in order to just operate and execute internally. In many organizations, we've sought to optimize, but we don't talk a lot about how to optimize process data and technology across our industries.

B

Hyperledger grid seeks to provide a platform and a framework for implementing common process data and technology solutions across supply chains. We've anchored hyperledger grid to existing industry standards, we're not reinventing process data and technology. We are, uh we are evolving and we are implementing uh in new ways.

B

So uh as an example of that is what we're seeing today, with 0.2's release, is about establishing some common core data concepts in particular product data product data has a very well managed and governed set of standards, in particular with gs1 gs1 and g10, and serializable g10s and other dimensions of product data exist in our industries and uh and our obvious ways that we could start to seek alignment for collaboratively sharing and managing those important data assets.

B

Other examples include gs1 standards like gln how we define locations in our supply chains, really building out these uh core concepts, location, product, customer kind of the essence of most business transactions, so we anchor those things to industry standards.

B

In addition, hyperledger grid, of course, being in hyperledger, provides open source flexibility. This is not a a vendor solution. This is an open source project that is, uh it is driven by the community.

B

The team- that's here, has worked across organizations to deliver 0.2 and has been a great collaborative community effort, and we welcome other contributions, be they be. They subject matter expertise, ideas or technical contributions as well. Fundamentally, we just we see grid as open standards, open governance, open source, implementations of common process, data and technology.

B

It's a really really powerful set of capabilities, all right. Let's talk about the roadmap quickly and then we'll get into the demo. So where are we at? Our short-term focus is really anchored on, like I talked about those uh big nouns pricing, I'm sorry, pricing, data, location data, product data, some core workflow capabilities and we're already building purchasing and purchase order capabilities.

B

uh You can see in that first bullet on the left side in the core that we're working that we just released 0.2. That's why we're here in july, and that we are already underway on 0.3, focusing on purchasing looking out, you can imagine where we're going with the roadmap, but we also spelled more of it out here thinks about thinking about quality specification.

B

How do we collaborate more effectively on our product specifications in a supply chain? How do we resolve disputes more effectively and efficiently across parties? How do we handle invoicing and payment or evolve into more supplier, managed, purchasing or customer uh driven forecasting solutions getting into product catalogs and bill of lading? These are things that we in a supply chain collaborate on all the time today. We just think there are more effective digital ways to do this really driving a virtually vertically integrated orientation.

B

Longer term features like integrated forecasting and planning, uh really digging deeper into uh traceability and uh product journey is, are all things that we think and talk a lot about. We're really tying the the features to what we see: users of this environment, getting value out of uh it's not necessarily purely aspirational.

B

It's practical uh in the features that we're building so again today, we're here to celebrate, to learn more and to talk about the grid 0.2 release, and with that uh in particular, about how we're managing product let's get to the demo.

B

A

You thank you. Thank you. uh Are you able to hear me testing.

B

Yes, just yes, indeed,.

A

Okay cool. Thank you very much. Thank you very much all right so for this next section, which is going to take the rest of the time. Shannon t lander is joining me to do this demo. Shannon. Are you able to share your screen.

C

Yes, I certainly can.

A

Thank you folk, shannon is also a key member of our team engineer. Extraordinaire manages project as well. Thank you shannon. I can see your screen um if, uh if you can see shannon's screen, please either say yes in the chat window thumbs up emoji, you know whatever. Whatever your speed is.

A

All right, I'm getting some yeses get some thumbs up cool we're gonna go. So what are you looking at? We thought the best most effective way to uh demo. The grid 0.2 features is actually to simulate. You know how they might work in concert, for um you know a real use case, and so the way we're going to play this out is uh you've got two organizations alpha and beta.

A

Shannon is playing. The part of alpha alpha is the orange box in the top right that will represent where alpha is interacting on grid and making commands alpha's a supplier. Alpha supplies many different types of products, including absolutely delicious steaks, with lots of marbling to many different customers. One of those customers is beta and I will be playing the beta organization.

A

You can see beta in the white box in the bottom right and uh I'm a customer who I buy delicious steaks and many other things from alpha, and I also buy lots of products from lots of other suppliers.

A

So you know why are alpha and I and I talking here about grid well, uh you know some of the challenges that I, as a customer with many different suppliers, have had have included, first of all, very disparate experiences in having to log into many different supplier portals to interact and engage with those suppliers up to and including, multiple different portals for a single supplier.

A

In addition to that, it's not just you know how we interact from a portal perspective, but also when it actually comes to the information that we need to exchange to do business. It comes in many different forms, many different manners and that's proved a challenge as well.

A

For me as a customer when it comes to reconciling all these different products that I'm buying across all these suppliers, and so in this simulation, shannon is the alpha organization is going to guide me beta through uh how we can to start with level set on the products that we share between each other using a grid, and specifically the 0.2 features so then, to help all of us here with seeing that come to life.

A

You'll see in the top left is kind of our cheat sheet for the different commands and technical steps that we'll be running through. If you are someone who likes to see well, what's the actual you know command line or code that we're running through it's all there for you to look at as we're going um and then in the bottom left are the specific features that we're going to be demoing in order, so that, as we're going through this, you can track where we are in our journey.

A

Our ultimate goal is that I, as beta, can see the products that I'm buying from alpha and they're able to supply the products and I'm able to make changes to those products to reflect how I want them to look so with that we're going to get started. The first thing that alpha and beta need to do in order to transact on the grid distributed ledger is set up. Something called a splinter circuit, shannon.

C

Yeah, so I am going to propose as the alpha organization that we create a splinter circuit, and so what this is going to do is this is going to allow our organizations to privately communicate on the splinter network and if, um in the future we want to add more trade partners, we can bring them into this splinter network and create different circuits with those people or with those organizations. But this circuit that we're creating is just private between our two organizations.

C

So, first off I as the alpha organization, I'm going to propose that we create a splinter circuit, and so now um it is up to the beta organization.

C

They can see that circuit that I've just proposed for them, and if we go into the alpha organization, we should also be able to see that same circuit proposal that was submitted, and so now as the alpha organization jack. Would you like to accept my circuit proposal.

A

As the beta organization, I totally accept your proposal for a circuit. Let's do business.

C

Cool all right, so now we should be able to see that circuit that we just created from both of our organizations and so now uh now that we have a grid circuit running, we will be able to perform grid transactions.

A

Super great, so what types of uh transactions are we able to perform on the circuit that we have.

C

Yeah, so we can check that out uh by looking at um the pre-loaded smart contracts that grid offers, um so I'm just going to quickly um go into my splinter service cli and I'm going to specify the circuit that my alpha organization is running just to tell it exactly which circuit I'm on and so now I can list all of the contracts that are available on that circuit that we just created.

C

So you can see that grid service id is being used, and so we can see these are all of the uh smart contracts that are loaded onto our um circuit, and so we can perform uh transactions that are defined by these smart contracts.

A

Oh super great super great, so if I'm reading this correctly, um the smart contracts on our private circuit between alpha and beta include location data uh we'll get to pike later, we can do purchase orders, we can exchange product and schema information. um Am I am I reading that correctly, shannon.

C

Yeah, exactly that's exactly right, so the um schema smart contract. um It enables us to define a reusable and kind of standard uh product properties that we are transacting within grid and then product enables us to share that gs1 compatible product data in grid based on the gs1 compatible schemas, that we create and then grid location offers an ability to share location master data between all of the trade partners.

C

Purchase sorter, as you would assume, has purchase order, specific functionality and then grid pike. The final one is allows for permissioning across grid, so you can allow certain agents and organizations to do um specific tasks.

A

C

A

Yeah and um if just so I understand before we move on to uh milestone three as our relationship as alpha and beta organizations evolve, we could add additional smart contracts to this circuit and that would be independent of any other circuits. We have either of us with other organizations. Is that correct.

C

Yes, that's exactly right, so grid 0.2 just allows these initial smart contracts to be loaded onto any grid circuit, but any changes that we want to make or additional smart contracts that we want to add to the circuit can definitely be added in the future.

A

Sweet okay! So now that we've created the circuit and we've seen our smart contracts, we have two additional pieces of setup to do before we start transacting on product right.

C

Yes, so now that we have our splinter circuits set up between our organizations, we are going to make an organization um a grid representation of our organization, so we're going to create a grid pike organization to represent both the alpha organization and the beta organization from our separate nodes here.

C

So I'm going to go ahead and once again notify the my grid instance. What circuit we are using, and so this tells it uh where to create that organization, and so I will create my alphaorg and now I can go into the betas terminal and also create the data organization.

C

All right now, after I create both of these organizations, we are able to view those organizations from both of these nodes because we created these organizations on the same circuit.

C

And so, if I call grid organization list, I should be able to see yep both the alpha and the beta organization and then, uh like I said before, this is viewable from both nodes. So both nodes can see the organizations that are created in the circuit.

A

Super great super great, so you just showed us also that from alpha and beta's point of view in these uh two different command lines that we've got here orange and white, we're seeing the same uh state of the data.

C

A

Right on right on so now that we've got these organizations there's one more step. If I remember correctly before we start transacting.

C

Yes, so now that we have our uh grid organization set up, uh we need to um set the permission so that we can actually perform some grid transactions, and so uh what I'm going to do so as the alpha organization, since I'm the one creating the products, I'm going to create a role called product owner, and so this will give me the ability to create schemas and products and delete them and update them. um Basically, a pretty inclusive uh permissions for dealing with uh products within grid, and so now I've created that role.

C

For my um I've created that role for my organization, we can see now that the product owner role is added for my organization um and now I'm going to assign that role that I just created product owner to my agent, and so my agent is tied to my public key that I have so you'll see that it's pulling in my alpha agent's public key that I have stored, and so now this agent is able to perform all of the uh transactions that are protected by these permissions.

C

So uh specific schema permissions like can create, can update um and then certain product permissions like can create, can update and can delete product.

A

Super great and- and I think the important takeaway here too, is that, with these pike roles in these pike organizations, we can define all sorts of different relationships uh between participants on a circuit in this particular case right alpha being the supplier absolutely needs the capability to create products, upload data about products- and perhaps it wouldn't make as much sense in this particular relationship for beta to have the ability to create products um given that they're buying them, but they're, not necessarily creating them.

A

However, right in different relationships with different organizations, we can get very granular and specific in honoring the many different, diverse, complex relationships between participants in a supply chain.

A

So now that we've got you know all the all the infrastructure and our relationships set up within the grid ecosystem like we're here to we're here to look at some products right shannon. Can you create a product that you sell to me.

C

Yeah, of course, so I'm going to first uh create the schema for my gs1 product, and so this basically just tells grid um the uh kind of the format of this product that it's expecting um so it validates it.

C

uh It validates the product that I create based on that schema that I just submitted um and as you can see, this is a gs1 uh product that I'm creating, and so now I can go ahead and run that submission, and if I go ahead and list the products, you should be able to see that product that I just created and once again, if we go over to the beta organization, you should also be able to see a product that I just created. Jack.

A

I would love to see it, let's see it in the command line and then is there another way. I can look at it too.

C

Yes, of course, there is so we have a little ui for our product management, and so um I'm just signed in as an alpha uh agent, and so what this allows us to do is see all of the products that I have um access to across all the different circuits um that I am also a part of, and so I believe, if I create all right, and so we can see that that is the circuit that I created um just a bit ago, and so, if I go ahead and switch over to that circuit, there we can see my test regulated product name uh product that I just created for you jack is that is that what you expected.

A

I mean I definitely am glad to see that there's a product there, I will say that test regulated product name is not what what beta calls what we buy from alpha. You know we call it stake. Is there a way that can we update this so that it looks like what I'm buying from you.

C

Yeah, so I think if you want to make those updates, I, as the alpha organization, I'm going to go ahead and give you the permission to run that transaction yourself to make the updates to the product. Okay,.

A

I, like that yeah, I can just do it myself. That sounds great.

C

Exactly so, I'm going to create an a role called beta product owner within my alpha organization, and so we can see that this role only has the can update product permission. So that means that an agent with this permission would not be able to create or delete a product.

C

They would not be able to create schemas, um they are only able to update a product, and so now that I have created that role within the alpha organization, the beta organization can update the beta agent with that role, and so now I believe you should be able to update that product jack.

A

I'm ready I'm ready all right.

A

So we're uploading some fresh xml here.

C

Let's see if that actually caused all right, I think that was just a little bit of an error from the uh response, but I think that we should be able to see our stake.

C

So here is the updated product.

C

A

I am looking ah yeah. That's right! That's! What's up, that's what I buy. That makes a lot of sense. All right.

C

I think we just got a little bit of an invalid uh response there from uh the splinter game and it looks like, but uh the transaction went through, and I can tell that because I just looked at my logs um and I can see that the grid daemon inserted one product, which means that product was in fact updated.

C

So just a little issue there with the response. But there you go. You see that you now have uh specified what exactly this product is and the image.

A

Right on so folks that was that was the whole demo. To recap: real quick, we just showed um six different. You know features within grid 0.2. We created that splinter circuit.

A

We looked at the smart contracts that we had available within it. We set up our organizations within that circuit and defined what each of us was going to be able to do to reflect our relationship as alpha and beta. We created a product whose data aligned with open and industry standards that were enforced on entry into the system, and then we gave the customer in this case the ability to update the data around that product to better reflect what was meaningful information for the customer.

A

So a couple takeaways that I I want to add from this demo for y'all to think about one, even with the capabilities in grid 0.2, it's 0.2 it's early days right. We have a long journey ahead of us as you, as you saw with the roadmap, but there's already a lot of power here to honor and represent the complex and individual relationships of participants throughout the supply chain, from origination all the way to consumer facing whether retail or what have you?

A

Second of all, what we did here with creating and updating some product data. Imagine extending that to other activities within the supply chain take purchase order for an example. What, if I is the beta organization, want to delegate to my suppliers to log purchase orders on my behalf to cut out costs and complexity and how I do business with them. That's possible with uh these feature, sets that you saw here third, the way that you saw the technology actually working right.

A

Most of it was in the command line, but we also very briefly demoed a simple user interface for grid. What I want to emphasize is that the way that we're building this platform, it is open and flexible for multiple ways for organizations to use and participate in this ecosystem. What do I mean by that? Well, the command line, demonstration that we were showing you know you don't need a user interface if you're engaged in fully automated or autonomous transactions between businesses um or organizations.

A

We hypothesize that there's many cases where uh the grid ecosystem could be used to actually automate portions of relationships between supply chain participants, um and in that case you don't need a user interface in circumstances where you do like we demoed, we do have a simple one that a uh makes it easy for you know a supply chain planner, or what have you right to navigate not just from one specific relationship of a supplier but actually from all of the different circuits that might be active in an organization and also to within each of those circuits, see what are all the different smart contracts?

A

Things that I can do. What is the state of my relationship with this other person in the supply chain? Third, we aren't limited excuse me to that specific user interface. As uh checky noted in the chat.

A

There are many circumstances and we imagine that many of the early adopters especially will be more interested in actually integrating the grid distributed ledger with existing interfaces that they have through erp systems and other data management systems that are already being used in their organization and that's absolutely possible as well. So you know, to put it very simply right. The grid distributed ledger can meet organizations where they are.

A

With that, that's all we had to demo. We have 10 minutes left here in this release party and we're going to open it up, for if anyone has questions or comments, we have multiple members of the grid project team. Here to uh take your questions, there is no such thing as a dumb question, wherever you're coming, whatever walk of life, uh we're happy to respond, you want to unmute yourself and raise a question. Go for it if you want to type it in the chat window. I will look at that and moderate those as well.

A

The floor is open.

D

Thank you jack. Another here, awesome demo. If somebody want to on board on the technical side of contributing to this grid, what is the scripting language the person should know or what technical details the person should know um to contribute.

B

Yeah, it's a great question and I know the like the. I think the whole engineering team from the community is probably on the call, uh I think, like there's a couple ways to just get involved quickly and hyper ledger.

B

Has public chat rooms, they're rocket chat based rooms that are a great way to reach out and learn more about specifically about the technology uh grid itself is written primarily in rust uh if you're looking to do core code contributions, uh a lot of it is the smart contracts are written in rust, but there is also plenty of other things that can be engineered around grid, in particular the integration layer and some other things that you know would benefit from other types of skill sets as well uh so again like reaching out and engaging with the the engineering community.

B

The the team, that's building uh the code side of grid uh through that rocket chat channel is a great way to start. Thank.

D

B

It's a really cool demo that showcases uh this distributed collaborative management of product data, as I talked about in the beginning, that same pattern of collaborating and working together and transacting, really submitting transactions updating a product, but that same transaction could be things like.

B

uh You know, issuing a purchase order or collaborating on a dispute, or you know even other more transformative things we can imagine shared views of inventory, uh shared views of plans and forecasts and collaborating in really more effective digital ways across supply chains. Then.

A

Turning some of that into yeah go ahead. Sorry, I'm sorry to interrupt you david, but we do have a question in the chat. I'll read it out: it's coming from riju: how does the grid integrate with existing erp and master data management systems in, for example, the cargill ecosystem with regards to purchase, orders and erps and product master data and product syndication tools.

B

Yeah great question uh grid offers a a set of event driven uh capabilities. So when things change in grid, uh it can publish events so that organizations that are running grid can capture. Those events in like a pub sub type way, for example, and distribute them grid is also like, of course, fully api enabled and there's a lot of different ways to integrate to and from that.

B

Lastly, we are working on an integration framework called griddle that will further ease enterprise integration scenarios between like the trend, the business transactions and processes that are running on grid and the back office systems that businesses run today.

B

So a lot of capabilities again, grounded in very practical implications for running these types of distributed solutions in in a modern enterprise.

A

Sweet next question is coming from eric, who asks: what would you say is the main difference is with a fabric. Another hyperledger project, for example, which is already used in supply chain applications.

B

Yeah, I want to talk about like why what grid is uh like what we see is great about grid uh comparing and contrasting with other solutions.

B

Maybe a different conversation. I'd point out that grid is a open source implementation of supply, chain capabilities, I'll clarify that fabric for those on the phone that don't know fabric is a distributed ledger on this demo, we used a distributed application platform named splinter grid itself is a like more of a business application.

B

Not not just a infrastructure thing like splinter or fabric is grid is a business application that provides supply chain capabilities in open ways based on open standards, open governance, community driven and free and open source uh principles, uh and you know that stands in contrast to an entire industry, full of vendor driven solutions that are commercially licensed and so on and so forth. So we really think it's important when we're building grid that it maintains that open collaborative community driven orientation.

E

And this is burn more ahead. I'm also, I have a good opportunity, get a good chance to work with david and jack, and I would just add, on the uh the grid, on the first question on the earlier question, from um from ruju on the integration with existing erps. um This is true for cargo. That's true for other and other companies as well. The key place to think of where the um of, where splinter of where our grid lives, is between companies and so the opportunity to connect these.

E

uh The um the in-house back-end systems inside uh a distributor or a producer, and a per and uh and a customer is to is to remember that this uh grid is a form of glue. It's a form of interaction. It's a form of achieving agreement um through processes between these companies. That's really the key between these companies is, is the application where we see the most use um and also, and that's just to build on what they were saying, and also on the question of um being open, open source.

E

What this means in practical terms, who care you know? Who who? um What does this mean in practical terms? This means that when two partners are working together, uh one of those partners can turn and say to all of their other suppliers. Here's a great piece of software uh there's, no one charging you at the door find your best party to work with implementing this, including your own developers, and uh you can also be working with us. That's really the scalability.

E

The ability to uh to provide our sector a way to drive forward is incredibly valuable and incredibly exciting to see. So uh thanks for thanks for letting me jump in there guys right on right on.

A

And with that, I think we're going to conclude the release party here. I want to thank you all for taking time out of your busy days to attend to get a little taste. A little show not tell about uh where grid is in its journey with 0.2 again, if you'd like to learn more, I'm pasting into the chat window, the hyperledger grid website, which includes the detailed roadmap and feature releases for 0.10.2 and what's coming in 0.3.

A

It also includes a glossary of terms for those of you who are maybe newer to this space, whether it's to how do supply chains work, how does a distributed ledger work and finally, it has a links to our community spaces. We have a rocket chat with direct access to the main project team. In case you want to ask any questions about how the platform is built. um That's also the best way to to you know, ask any other questions related to um you know.

A

How do you want like learning more about actually using or testing out the platform uh within your space organization? So with that again? Thank you. Everyone have a great rest of your day. Be well be safe, take care of yourself and those around you. Thank you.