 So look into it, we will be able, yeah, it will be a very. It takes about five, 10 seconds to get it going, just one second. All right, you are live on YouTube? Hello, Isaac. Hello, how are you guys? Sorry, I was a minute late. No worries, no worries. So, Andreas, you're live if you want to kick it off. Yeah, so, hello, everyone. Hey, Andreas. Nice to meet you. Yeah, and you will handle this to me hosting. And if I would like to share, okay. Yeah, you're host now and you should be able to, everybody should be able to share their screen. Yeah, okay, so I would like to introduce first of all, guys, I would like to start. I hear somebody speaking, but I do not see. Ah, okay, it's an echo, yeah. Okay, hello, everyone. We have our webinar at Hyperledger. David, I have a problem because I have very strong echo in my headphones. Do you know how to? I'm not hearing any echo on my end. Yeah, I don't know on your end. Maybe I'm not sure what might be going on. Ah, sorry, I guess I know because, yeah, guys, I understand. This is Echo from YouTube, I open stream. Oh, yeah, yeah, yeah, to close the, yeah, or mute the YouTube, yeah. Okay, so, hello, everyone. And today we have webinar at Hyperledger Vilnius. We are welcome all virtually who are visiting Vilnius today in Lithuania. So we here at Lithuania, we have regular Hyperledger project related meetups. And today it is my big pleasure to present our presenters who will talk about Hyperledger technologies. But what is more interesting, we'll talk about solution for suppliers, for suppliers management. And this is, I guess, especially for us in Lithuania could be important part because significant part of Lithuanian industry or let's say visible part of Lithuanian industry is working as a suppliers for big manufacturers. Especially nowadays when challenges to sign contracts or delivery some goods from Asia as a traditional suppliers. It is a tendency that Europe manufacturers looking near short production facilities and Lithuania, it is one of the place. And I hope such webinar which we will have today will support our exporters and will give understand what information, to understand what is coming in the near future, especially what is related to supply chain digitalization. I hope I pronounced correctly. So, Gigi, could you please introduce your team and stage yours. Thank you, Andreas. Good afternoon, everyone. Our good evening. I'm Gigi Joseph. I'm the vice president of Blockchain Services at Chain Yard. And I have two colleagues joined here today with me, Isaac and Murali. I'm Isaac Murali, I want to introduce you as well. Sure, I'm Isaac Honkel. I run our consulting services business. I'm based in Morrisville, North Carolina, which is basically the research triangle park area of North Carolina. I work closely with Gigi on a day-to-day basis. Murali? Hi, this is Murali Sapa here. I'm vice president for engineering. And my main focus is T.Y.S. in Chain Yard on the Blockchain Technologies. Thank you. Okay, thank you Murali. Thank you, Isaac. So what I am, I would put the presentation into a, the PPT into presentation mode. Can you guys see that? Yes. See it well? Okay, thank you. So we structured the presentation into three parts. And the first part is, I would give you a brief introduction about Chain Yard. Chain Yard is a company who owns and operate, who created this trustier supply solution. And followed by Isaac could walk you through the details of the solution, the business model mostly, and the current status of the trustier supplier. And at the end, Murali will give you a brief about the technology, which is hyper ledger, and used especially on the security aspect, on the data protection and the privacy and all those aspects. And a brief about the architecture. So, it's a ticket started for Chain Yard. Chain Yard has been, you know, Chain Yard's parent company is called IT People Corporation. So we have been in the industry for the last 21 years. We are founded in 1999, based out of North Carolina. It is a beautiful place over search triangle park. I mean, some of you would recollect the search triangle park is an upcoming technology idea. So we started 2015. We started our blockchain journey when IBM started a hyper ledger fabric at their labs. So we were right across IBM. So we got very fortunate to work with IBM at the labs doing the testing of the fabric, making all the quarterly releases. I mean, testing all the quarterly releases. So until recently, for the last five years, it has been Chain Yard, who is doing all the quarterly testing performance, functional testing of the fabric. So we continued there in and did many blockchain applications for IBM as well as some of our customers like the law, and a few customers out of Europe as well. So in 2017, 18, we had this idea about procurement issues and challenges faced by suppliers and buyers in procurement space. And we thought about creating the solution by ourselves. So when they hit, when they gain and met IBM procurement, IBM CPS, Bob Murphy. So he liked the solution, the approaches we suggested. So we partnered together. So trust your solution, trust your supplier is a solution by jointly by IBM as well as Chain Yard. So Chain Yard not only create the solution, we, our services side, continue to develop digital transformation services in customer experience, blockchain, AI and automation and cloud and DevOps and in the cyber security areas. So I kind of mentioned about this slide. I mean, we overall has done more than 36 blockchain solutions. I mean, digital transformation, I mean, has been going on for the last 21 years, but very specifically to blockchain. We have a large blockchain team, 90 plus members. So in a blockchain, that's a very, very big team compared to majority of the companies who has only a few blockchain members and 300 plus team working on the overall digital transformation. So we are a member of Hyperledger Fabric, Hyperledger and last week, the OpenIDL was announced and we are part of OpenIDL as well. So over the period, we created many built-in components, many pre-built components, which we could use in the trust your supplier. So this is consistent with many of the consulting companies. We do consulting, engineering and operations. The only thing which we are different from other services companies is the consortium building practice, which we offer. So in any private enterprise blockchain world, you need to create a consortium. You need to manage the consortium. You need to create the governance model of the consortium. Now you need to create the business, consideration as well as technical consideration, like how do you add a member? How do you remove a member? Who gets paid? Who manages the node? Like how do you ensure that a smart contract has not impacted when you do an upgrade? Now all these aspects has to be considered when you are creating a consortium. So we do the consulting of that. So that's brief about Chania and I think Isaac can continue with trust yours, very specific to trust your supplier. All right, thanks, Jeejo. Hey, you guys, we have a pretty small group today, right? So feel free to stop me and ask questions or put your questions in the chat. We wanna make sure you're taken away from this as much as possible, right? We're doing this so we can add value and help the hyperledger ecosystem. Of course, we're happy to always talk about Chania to trust your supplier, but we wanna make sure hyperledger ecosystem is growing and we can do that by sharing our information and learning from you guys as well. So anyway, thank you. So trust your supplier. It really, yeah, thank you. So what is trust your supplier? As the name sounds, it's all about establishing trust. And we call it trust your supplier because it's really focused on buyer and supplier relationships and bringing trust to that relationship. These relationships exist today. So we're trying to increase the amount of trust. We're also trying to ensure privacy and security of information. And lastly, we're trying to create a better way of doing certain parts of the business which specifically are the supplier onboarding and supplier information management processes that take place today. Next slide. P.Johm. So just real quickly, what does that process look like today? And I don't wanna read this to you, but basically there's a buyer or a category manager at a company is trying to find a supplier for a specific need, whether it be something in their manufacturing supply chain or it could be something as simple as we need to get paper for our copiers and we're looking for new suppliers there. You guys know that big companies have lots of needs across the board. After they find a supplier, they have to qualify them as being able to meet their needs. And then the next part is to validate. Validate the attestations that the supplier has made in terms of their capabilities. And then once that's been done, they onboard and then they move into what we call life cycle manager and supplier. And this is really all about information management of the supplier and ensuring that they are maintaining any potential certificates that are required. So for example, if you have a company that's transporting chemicals for you, they have to have certain qualifications. They need to make sure that those qualifications are maintained. They want to make sure that their suppliers who are critical to their supply chain maintain financial that they stay in shape in terms of their finances and they're not going to potentially go bankrupt and those kinds of things. And so big companies and small companies alike are looking at their supply chains and trying to manage risk. And this is what the process looks like. Unfortunately today, because especially going all the way up to onboarding, this is an area that doesn't get a lot of attention in the existing systems today. So what we see is a lot of pain points due to the current processes and technology. So let me just stop, I'm gonna spend a little bit of time in this slide just to explain how those inefficiencies are created. So what you have here on the right hand side is a supplier. So a supplier has relationships with all of their buyers, right? And each of those today looks very different from one another. They're similar, but they're all different. They're different in terms of the timing of when they were brought in, how often they have to potentially renoal. What questions and information they have to provide to that buyer? All of those kind of things are different. And that puts an onus on the supplier to keep up with that information not only when they're onboarding and trying to get that first transaction, but throughout the lifecycle of that relationship. And so if you're a supplier that's dealing with just a couple dozen companies, that's probably manageable, right? But what about companies who are dealing with thousands of buyers? And vice versa, what about buyers who are dealing with literally tens of thousands of suppliers? And those are the companies that are looking at trusted suppliers a new and better way. And why? Because today's process is constantly slow and inefficient. Why is it constantly slow and inefficient? Because it's manual in many cases, because today often it's still email, spreadsheets, word documents, and then it's a manual qualification to go through that data that's, that's been basically on a spreadsheet or in a word document. We see more and more pressure on supply or excuse me, buyers and suppliers from a regulatory perspective and making sure that that relationship they're adhering to all the regulations. I already mentioned the chemical transportation company as one example, being able to keep up with those kinds of things. And that pressure is putting more pressure on procurement organizations. And in terms, it's putting more pressure on their suppliers to meet those requirements. Can you go back, please? G.J., can you go back? And the last thing is, because the supplier is dealing with these different threads and they're dealing with different systems or dealing with different processes, there's really no way today to leverage what you've done with one buyer from a supplier perspective to another if they are completely mutually exclusive, if you will. And so we saw an opportunity here and we also saw an opportunity where blockchain can shine and Morali's gonna talk about that a little bit later. All right, next slide. So supplier pain points, redundant work. I just mentioned they're doing this for every one of their buyers. And to the level they have to do it to varies. It could be very light process. It could be a very heavy process. But what we found in all those processes that we're looking at a 30 to 60 day onboarding process because of the way it works today and being manual in terms of the qualification as well as just getting through the systems and getting into the system where you can actually be a verified and onboarded supplier to start doing that business. Another problem and everybody has this and we're all suppliers to some extent, right? We're always looking for customers is trying to get noticed and trying to be discovered so you can find new customers. And that's another area that's a pain for all suppliers and everybody in business, but we also see an opportunity with trusted supplier to help companies in that area. And we see that as a significant opportunity actually long-term as this network grows. That's one of the things where a network effective this blockchain network will be really, really shine. And again, it's a costly process. It's manual and you have to repeat it over and over and over and over for every one of those relationships. And that just adds up over time. So again, we're talking about companies that have significant number of buyers or customers and each of those touchpoints being able to significantly reduce up to 90% of the time and overhead associated with maintaining those relationships. And on the buyer side, they have very similar pain points, right? It's a lengthy time, it's manual, they have to go through the discovery and qualification process and they have to actually go in and qualify that the information that the supplier provided is actually accurate, right? Not everybody's above board. And this is part of managing their risks as a company. And again, the more important that supplier is to their supply chains, the more evaluation that goes on and the more risk management that takes place. And again, talking about tens of thousands of suppliers, this adds up, right? Some companies have teams of dozens of people who work on this full-time in terms of the procurement organizations in terms of just the onboarding process and all those things associated with that process I described earlier. And it just takes time. And again, 30 to 60 days is being very generous. We've seen some longer and of course some a little bit shorter. But what we're talking about is trying to reduce those time cycles by 75 to 90%. And that's what we're seeing in the market today. Next slide. So before I go into the slide, do you guys have any questions? I don't see any up there, but feel free if there's anything that's not clear, if questions about the process or whatever, just shout out. So when we looked at all these problems and opportunities and how blockchain could be leveraged, we said, okay, can it be? Is there enough commonality in the onboarding process, specifically the data collection process that we can be collecting that information and then potentially reusing it from relationship to relationship. And so we did an evaluation and what we found after going working, and this is where IBM was our partner, we worked closely with our procurement organization who not only procures for with their 20 something thousand suppliers, but they also do it as a business, as a service for another 50 large companies in the world. So they have lots of experience. And what we found is 50% of the questions right off the bat are common across, I wanna say all, that makes it sound like a lot, but most organizations. And then when we found another 20 to 25% are common across the industry, yeah, they may be worded a little bit differently, but when you get it right down to it, they're asking similar for similar type of information. Then you get to geography specifics, you get 10 to 15%. And then you have company or buyer specific questions. And we found that that was 5% or less. So we said, there's a great opportunity. And by the way, this pyramid of questions helps us in our solution to organize our questionnaires very similarly. So a buyer can then put them, put together the right set of questionnaires, standardized questionnaires to use across their organization. And so we said, yes, there's an opportunity and that commonality is what created the opportunity. Next slide. So what came out of this, the trust your supplier solution. And I will tell you, like all good solutions, this one's been going around for a while. We're actually starting our fourth year thinking about this solution. It's actually been in the market about 18 months now, but it continues to evolve and get better and better. It actually originally started as know your supplier, right? Before it was actually out in the wild. So we called it KYS for a long time, very similar to KYC. But then we ended up with trust your supplier after going through some marketing and branding exercises with IBM. Anyway, we're pretty excited about trust your supplier. And what does it do? At the end, in the end, it enables a supplier to create a single identity. And we call that a digital passport. And they can share that with any buyer. Now one of the things you'll see today is that data is still just data that the supplier has created. And how can they trust that data? Well, that's because we've brought in third party verifiers to the solution who verify this data. And these are the same providers who are doing this today, but it's more of a manual process for the procurement organizations and who are securing licenses with these companies to use that data for verification purposes. Because now the process has been moved from spreadsheets and Word documents. Could you go back, please? Into a system and it's digitized. So now we can automate certain things. So that information can easily verify and then update it in real time. And if there's an issue, whether it's a verification issue or an update that causes a supplier to be out of compliance with certain rules, then those things are caught by the system and notifications can be set. And our buyers have the ability to set trigger these things based on rules that they set in the system. And I mentioned the third party verifiers are bringing data into the system. That data is now bringing the ability, excuse me, digitized data that comes in, helps us automate certain verifications, brings in ratings to help manage risk. So again, these things were happening manually today but before, but now they're automated and then we can provide scores based on a Dunn and Bradstreet rating and a EcoVotis rating and a RapidRatings rating. These are things that companies are using today and we can bring them all together and help create a risk profile automatically within the system. And one of the things before we go to the next slide is we can do this for suppliers even before they've ever established a relationship with a new buyer. So they can now go and buyer can discover them and see that this supplier, potential supplier already meets all their needs and based on some high level information that that supplier has exposed for the organization. And I say it that way because suppliers control their own data and they decide which data is exposed publicly and which data they wanna share privately. And that's one of the things that blockchain enables. Next slide. So what's the ecosystem look like? Well, today it's primarily buyers, suppliers and the third party verifiers. Happy to say we also have some third party developers who are now building on top of this. Most of those builders are building solutions that are tied closely with the verifiers. And there's a slide that we'll cover in a second but most of these verifiers are providing certain amount of data for free. And then of course afterwards they're selling that data just like they do today. But we have a nice integration layer that lets us pull that those licenses right into the solution and again leverage that data for automation and for automated verification. So it's really nice and makes us a buyer and procurement organization's life much easier. We also see in the future auditors working in this network. I don't think we have any specifically today that are outside of the buyers organizations. And then we do see certificate issuers in the system today. And some of those certificate issuers are our verifiers already. For example, EcoVotis, there's different levels of sustainability ratings and certificates that they provide. And those badges can be associated with your digital passport based on establishing that relationship and getting that information pulled into your profile. So that's an example. So this is the ecosystem. We do think that over time we can see other organizations joining many types of organizations. Think about insurance companies who provide certificates of insurance that's usually part of a requirement of a buyer-supplier relationship. They could be part of this in bringing those certificates right into the network. And I could even see the day where that stuff is automated. So instead of today happening through email and requests, it could happen through a request through the system and an insurance company could provide that automatically based on the insurance that that supplier has in place for their buyers. So it's a really great ecosystem. And we have a slide in a few minutes. We'll show you that shows who's in the network today. And it's quite a list of good names. Next slide. So I mentioned the marketplace. So these companies like Dunn and Bradstreet, EcoVotis, rapid ratings, and I will say there's at least another nine or 10 that are part of the solution today. And I think there's another couple of dozen that are lined up that would like to be part of the solution. But we can only handle integrations of so many at a time. Are part of this in bringing their data into the system to improve the ability to automatically verify and in the end, in the end, manage the risks in these supply chains. I mentioned that most of these companies are bringing premium models into the marketplace, but they are also then offering premium offerings. So that's why they're participating because one, their customers are in this ecosystem. And two, it's giving them a new way to sell their data and their services that they haven't had before. And so that's why we have so many joining. And I'll give you an example. Dunn and Bradstreet today sells licenses all day, all night, but they usually are selling it to the buyers. And these are the big companies and they have these big licenses. Now they're seeing an opportunity, and this is where a new business model is forming, that they can sell smaller licenses to the suppliers, information about the suppliers or they can pull right into their passport to give them a better profile. So when they are being exposed, when they expose their information through this solution, they have a chance to do more business and increase their sales. And we see that as another really huge benefit for not only the verifiers, but also for the suppliers. And I'm gonna just go off in a tangent here and tell you like every decision that's made in the roadmap, there's always the question asked, is this going to be like valuable to all of our ecosystem members? And if something's not valuable to a certain ecosystem member or worse yet could harm that ecosystem member, there's a deep discussion that goes on is to make sure that we assage that issue and make sure there is value for everybody. And that's one of the core principles we've had since the beginning. And so going off on the last benefit here, I mentioned how we can automate the onboarding and the qualification process and all. We also are looking at pulling this data together to do more things with actionable insights. I mentioned the risk management profile already. There's many other things we can do like tying to AI solutions that are scanning the web for potential nefarious information that could reflect badly on a supplier, but more importantly, cause it an issue to a big buyer. And we have seen that in the press over the last few years. And we can, with all this data and all these connections and all this digitized data we can help automate many of those things. And we are tying into the AI in the backend for those insights. Next slide. So supplier benefits, I mentioned all these already. They have a single identity that they can share because they can share it, it remains redundancy of managing each of those relationships. I should say managing each of those relationships a hundred percent, right? There's still always gonna be that five to 10% worth each relationship that they have to manage, but that significantly reduces their efforts. Suppliers own their own data. If I haven't stressed that enough, they own their own identity and they own their own data. So they decide what they're gonna expose publicly to be discovered. And they just, as a matter of fact, a buyer has to, once they've seen a supplier and what they've provided, if they're interested in taking that relationships to the next level, they actually have to make a request to the supplier to see if they are willing to share more of their passport with them so they can continue to evaluate them. So sovereignty of data is important. I mentioned the new business opportunities. Of course, we're leveraging blockchain to ensure security and privacy of data and information. And then the marketplace, the marketplace, there really is no limit to how far it can go other than we're just managing that to make sure that things that are added there are valuable to the ecosystem. But today, we're only focused on onboarding and supplier information management, but we can see where this goes further down the road in terms of those relationships. And of course, the buyers have benefits too. Next slide, you know, very, oops, back one. You know, very similar to the suppliers, they're reducing the lag time, they're reducing touch points, they're managing their risk better. They also have additional business opportunities. So it's very complimentary to both sides of that relationship buyers and suppliers. I already mentioned the third party verifier benefits. All right, what does the ecosystem look like today? Yeah, so this is probably from March. I think it's fairly up to date. Probably noticeable, what's noticeable is we have recently onboarded General Motors representing the automotive industry to our governance board. Not all members of our governance board are so completely onboarded to the solution yet, but they are all participating and have been for the last, many of these for the last year and a half in our quarterly meetings. And we're really, really proud of this network in. We're really happy where it's going from a governance perspective in our last quarterly meeting, first quarter of this year. And we hope in the next one, which happens in two weeks, we've seen the governance board and these big companies starting to take a lead and drive the roadmap and have ideas. And the traction is tremendous. And I'm gonna give you a real quick example. Vodafone earlier this year started inviting their suppliers to the network. And they actually created their own 30-second video that they shared with their suppliers of why they should be joining this network, not only because they want them to and they're asking to do business more efficiently, but there's all the valuable things that I just mentioned. So when you see your governance board making those kind of investments and outlay to help this ecosystem, we really feel like we're headed in the right direction. You know, it's even though we've been doing this for 18 months, in many cases, it still feels like day zero. I'm sure Morale thinks differently since we've had like three iterations of the interface, the user interface and all, but it is a tremendous solution. And we're very proud of it. So I'm gonna hand this off now to Morale to go into more about the technology, but maybe that was a good time to see if there's any questions I haven't a chance to look at the chat. Yeah, please everyone, if any questions, we have a good opportunity to ask people who are involved in global supply chain solution implementation and definitely could share a lot of interesting and valuable information. Yeah, yeah, it's a great point. It is global solution and today it's available in 70 countries. And this is just one network running for all 70 countries. So yeah, definitely global. All right, well, just shout out any questions. It's very small group. So we can certainly take that. Yeah, we could be very open, but please do not forget that we have a live stream on YouTube. Yeah, thank you. All right, Morale, all yours. Thank you, Isaac. So Isaac has summarized what he wants this, but I just want to summarize it once again. It's a trusted network of buyers and suppliers and ecosystem partners, right? And when we're talking about these buyers and suppliers, we're also talking about the information that is being exchanged, the data that we are holding on behalf of these entities, right? When it comes to that, there is a lot of personally identifiable information that is stored on the platform. And there is also sensitive information related to the revenues or the banking, all those things are also said. And the magnitude of this data, to get a picture, you can think about thousands of buyers and millions of suppliers, right? And the data of all these suppliers and the admins of those entities, all this information is being stored. And on top of it, we have deployed, like Isaac has mentioned, in 70 plus countries already, and we are going global, adding more and more countries as we speak. So when we do this kind of a thing, most of the enterprise application challenges, they apply, right? Some of them are related to the security, how do we engineer our network such that it is secure and how do we scale, right? When we're talking about millions of these entities, we had to scale. And also, how do we make sure that business continuity is ensured, right? So all these things we're taking into consideration and that is one of the reasons why we went with the blockchain. If you look at this following chart, you would see that without a blockchain in the picture, when these entities had to communicate, they either had to hold the data with them, right? The entity has to own the data and it should host it, as well as they had to share some of this information with others. So we get into shared databases which are easy to hack. And also we had to rely on multiple intermediaries to validate this information. So with the blockchain, the single shared ledger, right? Which would help us providing a tamper proof solution. So this is a distributed ledger where the data is validated by all the participating organizations. So it is guaranteed to be valid and you can always audit it anytime and the records are immutable. So these are all the advantages that the blockchain brings into this solution. In a sense, that makes us into a trusted common, a single version of the truth. We'll get to the next slide. If you have any questions on any one of this, you can ask me immediately. Don't have to wait for the end. So all the advantages of the blockchain are realized. So we make sure that our solution leverages on all the benefits, including the decentralization or the transparency of the information where any participating organization has access to this. But at the same time, we make sure that we encrypt the information so that it is not compromised easily, right? And immutability of the records is always there. We'll get to the next slide. When we talk about data, like I said, we are holding a lot of personally identifiable information, right? And there is a lot of sensitive information related to the business operations, like the ownership or the locations or the payment data, everything is there, right? So data is one part and normally we talk about security and privacy as one thing, but if you look at it, we have to layer them, right? This data has to be made secure. That is the first step, right? When we talk about security, we are talking about unauthorized access to the data, right? We are talking about protecting against malicious threats. So the data security has to be both, we had to make sure wherever the data is hosted, that physical location is secure, right? And as well as the computing infrastructure that is hosting the data, that also has to be secure. On top of it, the network where this application is running and accessing all the data that has to be secure. So under the security you'll see, we had to take into account a lot of things like sanitizing or one of the major requirements with the PI information is when a party which owns the data, like Isaac has mentioned, the data is sovereign, right? The entity, either a supplier or a buyer, they own their data and they decide whom to share the data with. So when that kind of a requirement is there, if a party wants to get out of the network, we had to make sure the data is clean, and it is no longer accessible, right? We had to make sure the data is encrypted, backed up so that whenever there is a problem, we will be able to recover the data. And we had to make sure all of our development machines, so they have policies for the removable media. And the data, again, we are talking about data from multiple organizations kept in the same system. So we had to make sure it is properly segmented and isolated from each other, right? The sharing is by the organizations constantly. And we also had to take into account the malware management. So we integrated a set of tools into our application which continuously checks for any data that is uploaded into the system for any virus signatures. And we also took care of checking this kind of malware checks on all the data, that is all the modules that we are using, the application modules that we are using. And also make sure that we are patching and keeping the system up to date, right? And on top of it, we also do penetration testing and search for static code analysis of the code to see if any patterns of code that is vulnerable for this kind of hacks. So some of these things we had to take into account for security, right? Once the data is secure, we get into the privacy concerns, right? When we have deployed it in multiple countries, we had to take into account the compliances, the regulations and compliances of all those countries. The European Union has one set of regulations whereas California has another set and now Brazil came up with its own set of regulations for data access. So we had to put policies in place so that we don't share the data, right? We use the data responsibly, right? We don't use it for any marketing or any other thing or we don't publish the data to unauthorized entities for mining, right? We take into account the sensitivity of the data so we make sure it is processed and it is stored and transmitted in accordance with all these policies and compliance rules, right? This also includes the data that is used for discovery. Like when we talk about multiple buyers and one of the value propositions that we are giving to our buyers is the ability to discover suppliers who are dealing with a particular product or who are operating in a particular region, et cetera. So when a buyer discovers a supplier, we show only the information that is not part of any of these sensitive data. And once they establish a business relationship with these suppliers, that is when the entire data is accessible to them. The data includes the information that the answers to the questionnaires that the buyer has given to the supplier, which we have talked about earlier, right? And we also make sure that the data is classified and the consents are captured. Like when a supplier shares the data with a buyer, we make sure that the consent is there. And when we talk about the third party validators and others, we are also very careful about the data that is exchanged with these third parties to make sure none of this data is compromised. So this comes into the privacy part of it. Thus, we made sure that the data is secure and privacy is ensured. Any questions on the data, privacy or security? If not, we'll go to the next slide. We'll go to the next slide. We have two questions on our chat. Would you like to answer now? Yes, please. When you talk about P2, what do you collect? Do you collect individual P2 or business P2? We do both. PIA. PIA. Right, we do both. It's a personal identifiable information we are talking about, right? So for instance, in case of the business, the business is operating in a particular location. It may have offices in a set of locations. So all that location information is one of them. And when it comes to the persons who are marked for managing those entities, the admins of those entities, right? We have the email information. We have the first name, last name, information, etc. And when a supplier establishes a business relationship with a buyer, as part of the questionnaire, they'll be exchanging information related to their financials, last three years of financial information, for instance, or their ownership, like if it is a corporation, if it is a privately owned or it is publicly owned and who owns what percentage of that corporation, all that goes into that and the contacts related to those entities. So it's both the business. It's the second part is also what is payment data? Right, payment data. That is because a supplier, right? Right now the way TYS is structured is there is a subscription fee for the supplier. So they had to enter the payment information. This is one part. And then for the buyers also, they had to provide the payment information so that when that is taken into their ERP and other stages for doing the business, like the bank account information, for instance. Okay, no more questions. No more questions. Please continue. Okay. Like I said earlier, this is nothing but an enterprise application, but with a stringent data related requirements, right? So we leveraged IBM blockchain platform for all its capabilities, including the disaster recovery or backups and things like that. On top of it, we made sure that we build security into the solution, right? It's not an afterthought, but we architected such that security as well as the scalability are built into the solution because we know that we'll be dealing with millions of these entities. So that's one part of it. And when it comes to the leveraging the blockchain capabilities themselves, you'll see that we had to make use of everything, including the channels and the certificate authority that is provided by the IBM blockchain platform so that the data related to a buyer or a supplier is encrypted with the certificates that are owned by them. And we also made sure that we deployed this application in multiple regions and zones so that if anyone fails, we still have access to the network. And wherever possible, we have utilized open source components to make sure that we can build it faster and securely. The other thing that we did is, when it comes to the identity management or access management, we also made sure that we can integrate into an entity like a buyer's SSO. So the buyer admins can log in with the same credentials as their organizational credentials. Any questions on the principles? Just one, it is one question. I would like to listen about Oracle issues if there is some approach. Oracle is about Oracle's blockchain or Oracle as a company and data provider, databases provider. Is it clear for you the question? No, it's not clear. I think it is Oracle's blockchain or somebody is reporting all the data. So there are no issues as such there, right? We're compliant with... So is there anything specific or ultimately you can send us an email and we'll reply to that? There's a question about Oracle's morally. Right, but what is the question about... Okay, it's an update. In terms of some approach without Oracle protocol like a band or China link. China link. I'm not sure about it. We don't use an Oracle like chain. Morally, I'll take this. We don't really use an Oracle like chain link. I understand that concept. But if you think about it, the third party verifiers are... They're like the oracles, right? They're providing the trusted data and then helping to validate the data before it ever gets written into the system. So I would view them as the oracles set of trusted data that they can help with us with verification. If that makes sense. Okay, I got it. One small note, sorry. I guess we had only six minutes to the end of our webinar. So please pay attention to that. So for the verification, it is not the chain code as Isaac pointed out, but the third party does the verification and provides the information which we store. We'll go to the next slide quickly. So the left-hand side, you have the TYS application access, right? We have a service layer that we use to access the application. And that access is the blockchain API to get to the IBM cloud... And we also have a key management solution that we are using from the IBM, which we use to encrypt the data in the MongoDB. There are two... There is off-chain data and there is on-chain data in order to be compliant with GDPR, et cetera. What we did was none of the PI information is put on the chain. Instead, we put it in the MongoDB encrypted with the keys of the buyers and the suppliers. So you'll see a off-chain database and also the digital identifier service which can validate an ID that is specified or an API layer that can be used to integrate into the third parties, including the buyers ERP systems. So that's only a high-level view of it. On top of it, we also have this deployed in multiple zones and regions and we make sure that the firewalls and other things are all put in place, right? And a monitoring solution using syslogs and sysdiag and logDNA and other things are in place. The internal communication is all made secure using TLS as well as using white-listing to make sure that it is not compromised. Any questions on this? Here on the chat we... I will fix it again my question about, could you please use the microphone maybe to ask your question. I guess it will be more appropriate way. Hello. Hello, please. Hi. Let me introduce myself personally. My name is Haesul Lim from South Korea. Yeah. What I wanted to know about chain yard or what chain yard try to approach has own solution about Oracle solution only without 10 protocol or chain link protocol. So if it is just smart contracts, right? We can put it on any blockchains. Chain yard would be able to help you with that. Isaac, do you want to take that question? We have consulting assignments. Yeah, I think the question is what was our motivation for doing it this way as opposed to a public blockchain? I think the answer to that is in the state of where blockchain is today, especially acceptance with big enterprises, it still needed to be considered to be a more private because of the concerns around data privacy even though we all know you can trust blockchain but companies don't necessarily trust it and the regulatory environment as well. It's a great first step and of going with a private blockchain and using our own ways to verify the data with third party verifiers who are already part of the process. So it wasn't a complete revamp of the solution but just I would say a modernization of how it's being done to add the efficiencies. Actually I gave them what can to embarrass you guys actually I just only wanted to know yeah in a way if someone used private blockchain in supply chain definitely I I guess there's a lot of problem about Oracle issues so I actually wanted to listen about that firstly that's all okay thank you Jesus any more questions because our time is almost over so any last sentence from UISAC or anyone else and I guess if no more questions we could close so please final work from UISAC sure I just wanted to say thank you to Hyperledger and the Meetup Group for allowing us to share our journey and experience and we're always willing to spend time outside of this call with anybody to help you with your journey or as I was just noted with help you with your projects if you have something you need help with definitely also thank you ChainYard for letting us know and introduction of Trasio Supplier Solution as I mentioned at the beginning big part of Lithuanian industries acting as suppliers so I hope this webinar will be very useful for part of our supply chain industry so thank you very much UISAC and all of you and we'll see you next time thanks everyone and I'll get to this on the YouTube channel right after this thank you