 Okay. All the best to every team. Welcome to Hyperledger Challenge Prototype Evaluation. We have our jury panels and three of our eminent jury members on the call today. We have Mr. Ganesh, who is CEO and founder of Fiducia AI. It's a unique blend of different technologies. So how can blockchain be working together with AI technology and what can we achieve with the combination? So it would be interesting if you can interact with him on these topics. And then we have Mr. Arvind. He is from Ideasoft. He is an executive VP at Ideasoft. So he is into blockchain space no matter what kind of problem you have, let's say. So he is into all spaces, right? So you can imagine, you can consider him to be a blockchain maestro for any of your use case that you may have. And then we have Dr. Jubilant on the call. He is head of the department at St. Gates College. And he also participates on open source within Hyperledger community. You might have seen him leading some of the special interest group related activities as well. And we hope you're doing well, sirs, and welcome to all the jury members. We'll get started with the teams, right? So the first team to go would be Merit, media tracking platform to tackle online piracy. So if we have team members from the team, who will be Swapnil and Ramaguru. So please start your presentations at eight minutes time. You will be given a notification to that your time is up for the presentation. So all the best everyone. And yeah, let's get started. Thank you. Good evening. Am I audible? Yes, please. So our project is Merit. This is a short form of media rights tracking. I am Swapnil Khandagure. I'm a student in M.T.C. Cyber Security. And my partner in this project is my assistant professor, Ramaguru Radhakrishnan sir. So our problem statement basically deals with piracy and tracking any kind of pirated material that is available on the web or the dark. Since the corporate infringement has been rising for a decade at an enormous rate. So its protection is as important and basically where it is being incensed, where it is being used without your permission. It needs to be the law enforcement and both the copyright owners or IP owners need to know that. So what our solution does is it's cross all over the, it's just like any ordinary search engine, the difference being it collects data from the surface as well as the doctor. It cross everything and the user who are actually the IP owner can set up an entry bucket, put up the upload their files or upload their files like videos or images on it. And our solution downloads those files and sends it to a AWS service known as Amazon recognition. And with their from the collected data in our, which is being stored in our blockchain database, we fetch that data as well and then compare it face to face. I mean, we give it to Amazon commission and tell it to check whether it is the same media file it whether it is the same image or the same kind of video file. So that way, the transfer detection actually increase for property for inference materials. This is a schematic diagram of our solution architecture. The webcrawlers will be using our code in PHP. And the database we'll be using would be basically the typology of a blockchain setup using distributed literature. That's also, we also are trying to incorporate the bloom filter. So, as I mentioned earlier, the users, the IP owners upload their files in the three buckets. So we also store a hash of those video of those media files. And whenever we whenever another media file is captured on our blockchain, we take it generally most generally like social media websites what they do is they just grab the metadata but if you actually go on some piracy kind of site they don't, they don't bother with the metadata because it actually requires more resources and more and more and a bigger development team for that. So we can compare that hash and this hash and this way, we can actually check that whether it's the same problem. Since the IP owners would be able to find the find their IP institution by themselves. So, if they want to complain to law enforcement about an instance, they already have that all the data all the material where they're, whether they're IP, on which website, if they are being influenced or being violated, they have all the data and this actually fast tracks the law enforcement process and the governance process of the IP right. This is our roadmap right now we are working on a prototype, we are halfway in creating that Amazon that Amazon recognition service and let me show you. Okay, this is our login screen. Maybe I'm not seeing the login screen. Is it visible now. Not yet. We see your PPTs. So we are still seeing your slides. Yeah, I think you need to share the whole screen. Okay. Is it visible now? Yeah. Okay, not visible. Yes. This is the admin panel. Right now we are only dealing with callers. So, from here, the admin can start callers, the website manager that would be basically we can start callers, check our callers status whether it's actually running right now or not. And stop it. According to our will the same with the deep app caller. We can start callers we can check whether it's running or not on and stop it. Now let me take you to the user dashboard. So this actually looks like a search engine. The whole concept is this concept of the solutions basically on a search engine. It just lets you search for more efficiently using your. All kinds of data and you can specify your own keyword. The IPM can specify your own keywords and everything would be available here. You can filter it according what you're searching like images, videos, or some kind of news article or documents like your research paper or something. And in order to make it sync with your S3 bucket. You can specify your as your can update your access key ID, secret, secret access key and the bucket name here. So the moment you do it automatically everything in your S3 bucket itself. It is sent to Amazon recognition and it is verified and it checks whether the files are uploaded already have a have already been indexed into our database or not in the blockchain database. The same, this update a free file search button. It just fetches the, it fetches all the files, notes down their hash and then verify it with the other files that have been indexed in the data in the blockchain. Okay, that would be all I guess. I have a one or two questions and that's okay. Thank you. Yes, you can go ahead. So eight minutes. Hi. So, Hi for the foundation for your solution. And the problem that you're trying to solve is IP protection right content fingerprint is taken. I can go inject a simple extra QR code and change the fingerprint and then upload it. I can alter an image and upload it but still copy. So how we want to address the IP protection overall. That's one. The second part second question primarily is, can you elaborate for me and all of us on the call. Why blockchain for this particular solution. So that way, you all start to learn right so it's all new blockchain is very very new. So if you would like to learn your view of why you chose hyper ledger that would be very valuable. To compare whether the media is being in French. We use the Amazon we use the AWS recognition. So any kind of media like video or image. So the index into our database is sent over there along with any free database, any, any file stored in the S3 bucket of any user and then we compare. So everything is done by that recognition service it has its own ML algorithm. It verified and it has been actually been proven that it is quite efficient in detecting whether a file is similar or not even if you actually corrupt the video or change the metadata, because it is. It is using machine learning and it just come it suppose I upload a video file, it divides into frames takes another video, which we have index divide that into frames and then compare to frame by frame. So that's a higher so we actually get a higher chance of detection, rather than just relying on metadata. Like most websites, for example, say Facebook, someone upload something on Facebook, they what Facebook does is whenever you upload it it just cracks all the metadata removes all the metadata from your image and input your phone. But even but in this in our solution, even if you just crap all the metadata, it would be of no use because we are checking a frame by frame. We are letting the ML algorithm see for itself, whether it is the same. Then why do you need hatch comparison. Yeah, sorry to interrupt. So one is then what is the real value in terms of doing the integrity check by comparing the hashes that that is one. And second, you know, hyperlegia fabric is a permission block chain. So who are the stakeholders will be maintaining the notes, basically, the hashes are basically a preliminary check, so that we don't need to burden the AWS recognition. Suppose if someone has uploaded as additive, the metadata still going to remain and the hatch is going to remain the same. It is just a preliminary check if your file isn't found in the in the hash database, then it goes to the AWS recognition. But just for hashing you need not go to blockchain. Right, you can use the graphic function so what is the intent behind blockchain so who are the stakeholders will be maintaining notes. So can I take it this question. Yes, sir. Thank you for the question. So, there is, sir, the reason one to answer what I think, I think, I also asked this. Yes, the reason why we wanted to go for blockchain is because of the design, the principles of hyperlegia and the open source community. And secondly, the reason for going to blockchain and regarding the stakeholders is like, we are looking for a solution, which could include multiple stakeholders like the copyright firms, government could be the stakeholder. And there are sites like for example if you take journals or the solution providers for the media like the media houses who normally release the music or video. So these people can be the stakeholders who can take and they can be. So these are the possible stakeholders we are currently looking at. Okay, so you mean all the stakeholders will put this as an evidence so that all those things can be used later that is what you mean. Yes, sir. Okay, my question on the hash. This thing as Harissa also asked like we are looking at a bus business model also looking at like a product productizing this idea. Like the main intention is yesterday when we when a common man wants to do a copyright thing it is very costly like I cannot go and pay for a copyright trackers and see that if my content is infringed or not. So this is going to be a solution that anyone can use like there could be different levels like we will be using some level of service like free service like whoever creates an account like user account, we will be giving a free service so we can use a simple hash, or something like a similarity ashing algorithm could be the hash that I use to detect which I will use it in bloom filter so the filter will tell whether this particular as has been already detected or has been crawled somewhere or not. So this could be some free service that I provide to a common man who quickly wants to check whether his content has been infringed or not. So that similarity ashing will answer the question of what if someone slightly managed like he wrote it same age or just add a watermark dash is going to change. So we are not going to use that traditional cryptographic algorithm but we are working on our own customized similarity ashing algorithm. So that is one part which will take care of that and for a premium kind of service at different levels we will be sending it to the machine learning algorithm. So looking at the business model also we thought that it should be in different levels so that is why we are still using ash and there is one high end machine learning also. So sorry to interrupt that we are over the time. I have just one important question. Is intent open source and then continue to work with the community as you build solution or something that is a question. Is a plan to. Can you repeat sir? Yes sir I am much more interested to work and collaborate with the hyper ledger community. Thank you. Thank you sir thank you. Thank you very much. It was a pleasure knowing what you guys said and thank you. Thanks for the questions sir sir. So we are over the time for this team 15 minutes alerted and so next teams please do make sure that you are able to answer the questions in short and brief and let's acknowledge that we have many teams writing in the pipeline. Thanks team edit our next team is mosaic decentralized workflows. Are you ready. Yes, actually, let me just reshare my screen again so I can share with audio share sound. There we go. That's not what I want to do. That works. Okay, so. Let me move this off. No. I'm going to try this one more time. I want to swap presenter and slash or if I can take this away. Okay. I'm today I'm going to present mosaic decentralized workflows as part of the hyper ledger challenge. So the developers and our team are Dr. Masha time, who is the director of the cybersecurity security research lab that we operate out of. I'm presenting today I'm Dave McKay and the technical lead of the lab, and our lead developer for this project is Vladimir. So the problem statement. The blockchains were not designed for multi step workflow process transactions so blockchains were originally for backing cryptocurrencies that just have a transfer step. And inter organizational workflows involve multiple prescribed steps roles instances accumulated data and application interfaces. So if you're trying to represent real world business workflows and processes, they're very sophisticated. And then we write decentralized systems that offer enforced workflows for everybody all the participants, and all of the instances that are running. So this is a problem that came out of building decentralized systems for industry. And we've realized that we had to take a step back and solve this problem. So our proposed solution to this is mosaic. So mosaic is a blockchain system that allows for collective development of business processes in a decentralized system. So how do we go about doing this. So what we do is a starting point is you take your workflow whether it's a governance workflow or a business process workflow, you represent that as a state machine in a diagram. We take that we encode that into a JSON template that has a very specific format, and then we, we take that and we then present to people in a user interface. Exactly how that'll look. And the interesting thing is you can use these workflows for the governance body can use it himself and they can modify their own governance as well as the workflows that the governance represents. So what kind of benefits we get out of this well, you get consistent workflows if if you're trying to code workflows which a whole bunch of API calls, you're not guaranteed that people are going to call these one after the other. So having a state machine gives us the consistent workflows, putting the, the templates into data as opposed to code means there's reduced development blockchain development is very slow and very expensive, and is very collaborative so if it's just modifying the signatures on that. That's a way easier way of doing it. It's very easy to integrate with your existing systems, because we're presenting back display information without prejudice to how it's displayed encourages participation because the there's built in system for everyone to provide governance on the system, and the way that that governance works. We're looking at methods for making this highly equitable. So what's sort of unique about our system. It's, it's data driven. So it's data driven and where that's useful is business workflows change all the time so let's say if it's insurance or real estate or supply chain. Those things change and so if you have to code those all the time. That's, that's a lot of work and a lot of people have to agree to that code all the different parties because it's an essential system. It's very easy with existing application so if everybody has their centralized application that's integrating this part. If someone changes the workflow, if they have to go in and change their code to match that your system will fall apart. So it's almost like a web system where we're providing the interface or at least the, what needs to be displayed on the interface. It's an essential system so we use the workflows for our governance which in turn is how you change the workflows. So it's, it's a very interesting concept there. So I'm going to show. I have a video. And this is our demo in this demonstration I will show the workflow templates and the parser and render subsystems of the mosaic system. This is a state machine diagram. In this case, I'll use our component test system diagram as an example. The state machine starts and you can select different test states and return back to the starting state. The state diagram is converted to a JSON template that represents the states actions roles transitions and display objects. For this demo we have manually built the template and we'll be putting it into a Mongo database for the launch challenge. This is a visual editor and we'll use couch DB that is part of the hyperledger fabric blockchain. Let's take a look at the start page of this template. This web page is a rendered version of the start state and default role of the state machine. The buttons on this page matched the transition lines in the state diagram. Let's take a look at the text test state. On this page we're in the test state where we display the different text options we have for display objects. Display objects are abstract versions of what to display with no prejudice towards how they're displayed or on what type of system. They should be able to be displayed in browsers, mobile apps, desktop applications, and even embedded system displays. This is a decentralized system. We allow the participants to connect using any interface they prefer and from within any application. To render a page, the user requests to start or continue with the state they are in in the workflow. The parser retrieves the data for that state from the template and based on the role in previous inputs, it creates a set of display objects to send to the renderer. The renderer then interprets the display objects to build up the user interface. Having the interface rendered from the state data allows any application to integrate with the workflow and not to have to redevelop or recompile when it changes made to the workflow template. The render code can be enhanced to add any type of style to the basic objects. We're not sending HTML. We're not trying to force a visual representation. We want people to be able to decorate the data and controls to match their existing design choices. Here is an example of a real world workflow for transparent bidding in a real estate transaction. This example workflow comes from our experience in attempting to build a real estate blockchain system to reduce fraud in real estate transactions. While building the system, we realized that we'd created a central web application to access the system. We were forced to do that as we did not have a way to enforce the smart contract calls to enforce the workflow order. We also had a problem with guaranteeing that people who were self onboarding were qualified to hold the roles in the system that they claimed. All of these problems led to this work on the Mosaic project. This concludes the demonstration of Mosaic. Okay, and now I'm going to jump back to the presentation is here. There we go. So what's our roadmap. We want to build a visual template editor because trust me building these templates by hand in JSON is a lot of hard work and very error prone. A visual template editor will allow us to do that very quickly and easily. And it'll also allow people who are involved in the business process. So actual business analysts and not to be able to validate that the template, the workflow is correct. You don't need them to have to read programming code to do that. We're going to stick our parser into chain code and hyper ledger fabric. And we're going to move the Mongo database we have over the couch DB under fabric. And we're going to generate our first full governance template. So thank you that that concludes the presentation and I'm ready to take questions now. Yeah. Yeah. Yeah. Yeah, you can go ahead. Yeah. Good. Yeah. Dave, definitely an a project which can really bring down a lot of hassle for developers because even we have a product called trust flow for a supply chain. Cross organizational workflows and all yes this is real pain point, which everyone is facing today. And again, we tried something like templatizing the business processes based on SAP is one domain model and various other things. But how do you bring the context into the scope right into the smart contracts. So that is one question for you. Okay. And second thing. So are you enabling this as a platform so that people can create their own templates or what is a model you're looking at. Okay, so we actually have, there's three databases one is the template itself. And another is a context one which is going to provide the, the language images, things like that so a template can be reused by different groups for different things. So if you had a voting template, that could be a common voting template but people can change the language and things in there, and the language might not just be changing the wording but it could be changing the actual language maybe you want to have an English French and Spanish versions of it for for North America. So the instance database so the instance is every time you spin up a new state machine workflow, there's an instance there. And so the instance knows the template it's using it knows the context that it's using. And so it, and then it keeps track of the data as that you, you gather data as you go through the workflow, and all of that is brought in together and rendered and sent as display objects over to the, the, the, whether it's a mobile application it does top application or web application that can then show the user interface. That's the approach there. This is, this is an open source project, and it's a decentralized thing so anybody can run this. And anybody can create templates for it, but to get the templates accepted into the system, you have to go through the governance workflow so you have to. You would strap people with a set of governance templates, and as organizations are on boarded into let's say a channel in fabric. They are then added to this and their voice is put in there, because they can vote on the governance workflows. So if a template is to be changed. That's a proposal that's put into the system, and the proposal gets voted on. There's a whole debate process and the proposal gets voted on. If it's accepted, it'll go to someone to actually make the change, and that changes put in people review that vote on that accept that, and then immediately the template is changed. And so right then and there as long as the majority of people have agreed to that template change that will immediately change it across the whole system. Okay, and to what level, you can make it industry ready. And how do you think, what are the challenges you face when you think you can function and make it functional in the industrial level. So it was the last week there. So I'd like to know about the challenges how when you make it industrial level implemented in the industrial level. Oh, for for industry. Yeah. Okay, so two things how do we make this industry ready. So as I'm explaining we need to have a visual editor. So that's a major part to it. And we need to have our base set of governance templates. So the governance templates is how you get started with the system. Once we have that, then we're ready for at least our first implementations which are going to be, it'll be a little rough. How do we get this up to kind of an industrial standard enterprise or standard. That's going to take some work in how we configure this for hyper ledger fabric so we haven't built the chain code yet that's what we'd like to do for the, the next challenge. And that's going to enforce who can do what so there's going to be different roles. Eventually our goal is to attach the hyper ledger areas project having verifiable credentials being used to enforce the roles. Until that point, then it's up to each organization using their membership services to track who has which roles in the system. First is to reflect on what you shared. I mean conceptually it's very, very relevant and these are the applications which will start to thrive on hyper ledger or any blockchain for that matter. So, sincerely appreciate the thought that has gone into what we're working on to build enterprise create solution. Oftentimes we run into performance issues. Blockchain is in its very nascent stage and we all know transactions very soon can go drastically high. So what is philosophically how are you looking at it and I'll tell our own experience right so 100 200 300 transactions per second we really have to start to find you the systems to really make it work. Today, that's where we are. So how do you look at it I asked this question is a tough question by the way and nobody has a clear answers. We're all trying to figure this out. Have you started thinking about it. It's more relevant for you because I see this as enterprise great already. Yeah, so our selection of hyper ledger fabric was for several solutions. Also that it does have a high throughput, a lot of the activity with mosaic is going to be read only but there will be rights. So for example I was showing a form there right to it. And so, to begin with we're going to write our chain code in JavaScript but eventually we're going to move that over to go for a higher performance. It's where we're at the mercy of the speed that hyper ledger fabric can handle transactions. It's not really our capacity to be able to update the way hyper ledger fabric works. And only this is just reflecting on our own experience since technology is nice and we have to be very careful and deciding which transaction goes where that will go a long way. A big thing for us is the types of governance that will be covering. So I do a lot of work with the hyper ledger areas community. And so we need governance for the networks that we provide. And so in there there's, there aren't a lot of participants and there's not a lot of writing. So we're not going to see the types of thousands of transactions per second on this that you would see in let's say if it was a supply chain for perishable goods. We had the selection of the implementations that makes sense for the throughput that we have. Wonderful. Very eloquently explained. Thanks for the mistake. Thank you team. Thanks to you. Thanks to music. Our next team is dead using me can be catered for you with supplementing. If you're joining in now. So we are running 15 minutes delayed. Okay. Hi. Thank you. Yeah, let me get started. Yeah, so this project was, yeah, some work we've been doing on the problem of reducing methane emissions in the oil and gas supply chain. Our project consists of myself, but you say Shin. Sorry, are you sharing the screen sorry to interrupt so yeah. Yeah, I am. Let me try again. I'm not able to see. Yeah. Let me try again. There we go. I think that should get. Yes, now it's visible. Yeah. Yeah. So we've been we've been working on this for the past several months, and using technology stack that's been developed under the hyper ledger existing hyper ledger labs project called blockchain carbon accounting. So I was looking at carbon accounting tools. Yeah, to solve some of the world's climate problems. So the specific problem we're looking at is this issue of waste emissions from other gas industry for use for those of you that are familiar the oil and gas industry flares methane, which is primary component of natural gas, and also events that directly the energy sector to the tune of more than $60 billion of potential value as far as the value of this waste and resource. There are many reasons why they do this, but there are many reasons why they don't need to or their opportunities to reduce these emissions. There's a sense, you know, almost double what the you imports from from Russia current currently as as natural gas, which obviously is an important problem for the energy security, but also up to 1.3 billion cars of emissions just from this waste and other gas industry, it's just lost. So there's a need to reduce us. So the real economic opportunity as well. Now, the problem is, in the past, a lot of government data has been wrong about the about the problem they've been under, there's underestimating the scale of the emissions, and industry wasn't really measuring it. There have been a lot of efforts to improve that now and independent sources like satellite data actually looking from space at what's being emitted by the gas industry. So the reality is only gas will remain important in, you know, into the into future a lot of projections suggest that we're going to continue using a lot of gas, there are a lot of efforts to try and decarbonize but these are essential fuels. And there's very fractured data landscape, there are a lot of different government agencies, companies that are self reporting on site senate site instrumentation and certification that's being done. And as I mentioned, satellite data and new efforts to try and certify all this data to produce like certificates about what the only gas industry is emitting. Either, you know, for regulatory purpose like to use the stick to say okay industry you need to reduce these amounts of emissions or to use a carrot and actually motivate companies or incentivize companies that are emitting below sort of benchmark values in the only gas industry. So the solution that we've been been developing essentially looks at certifying these sort of waste emissions, so that the data can flow across the supply chain. So we have all producers on the far left of the screen, which would have this sort of tokenized emissions that that that we've developed this is sort of contract system for tokenizing this emission data. And this information can then flow through from energy producers all the way down to the consumer so they can have a view of what are the ways this missions in this place and I'll talk a little bit about what are the sort of business cases or how one would use these type of tokens in the real world. Before I get into that let me just talk about the sort of how we framed this our initial prototype and our specific application. So what we wanted to look at was waste emissions from the only gas producers in some of the major production basins in the US. So Buck and Neobrara and Permian, these are just large oil and gas on the gas fields. They're supplying this gas or oil and gas to utility companies say in western states and these utility companies are want to know what's the the sort of impact the waste produced by the gas that they're buying. In order to implement a system where we could, you know, set up set up this we put together this this tech stack. But as I mentioned as part of the broader blockchain carbon accounting project, where we use both hyperledger fabric for managing high volumes of data flow. For example, facility or company level data hyperledger best network to implement these emission certificate contracts to create emission tokens and enable trading of emission data between supply chain partners. So looking at different public networks where these contracts can be deployed, you know, including the finance marching and hinder a hashgraph so that these token networks can then emission token networks can operate in a public space. We've also been using hyperledger cactus in order to slight the connection between say hyperledger fabric and these these public networks. The key elements that I'll be showing in this prototype are, I've been developed using a hyperledger best you implementation. And we just in a development environment right now what we're deploying everything in hard hat, just an environment for development. So what is our sort of competitive edge while we present a solution where we can really incorporate all sources of data, you know we're really open where we're agnostic to the source, we're creating a system in which we can bring together auditors, which are essential for creating these certificates the companies that have the data independent data providers that can sort of verify independently verify what companies reported, and then enable the certificates to be connected to the these consumers right whether it's a gas utility company or an end consumer, we're open and transparent, and we enable the transfer certificate certificates through a supply chain. And before I get into the market opportunity and let me just close this, and I don't have the demo running right now I'm in a sheet but I can just run you guys through quickly the video recording that we put together for our submission. So, um, as I mentioned, yeah we have this this problem, we've created this portal for tracking issuing these emission certificates as part of the net emission token network right this is this. This Ethereum smart contract. D app that we've set up, we have this tracking feature where, say an auditor that's registered with this network can issue an emission certificate. We're here. So in this case we just have a US, an emission auditor that belongs that owns this address is going to issue an emission certificate for some generic US well and gas producer. For example, data, for example. The amount of tons of CO2 that were emitted for example tons of CO2 that was flared in CO2 equivalent, the timeframe in which the emissions were realized, and some descriptive factors about it for example location and the sort of scope the scope data, as well as perhaps location and information where was this data sourced for this prototype. We've just gathered a bunch of data from different sources like the international energy agency on flaring model and flaring Intel for a variety of different regional oil and gas production cut producers at country level but also these basins for example in the US. Let's go back to you quickly so yeah once these tokens are issued using this data right transaction submit to network. So we have these certificates the others issued and they may need to add product information to these certificates right so we have the information about total gas flare total methane leaked into the atmosphere. And we want to know what are the products associated with these emissions now what these products tells us is the how much emissions exist per unit of a fuel say that's traded to a consumer. So here we have this emission data and we now have product data that's being added to emission certificate, for example, oil and gas. And we add some amount or some unit. So now we finally have these certificates to final certificate that's been issued. Right. Now I've gone ahead and seated the network with a bunch of emission certificates for all of these different oil and gas producers and different basins, and they've been color coded. To demonstrate or illustrate the emission factor so this is the total gas flared or vented by a given producer per unit of energy produced either tons of oil equivalent or 1000 cubic meters, and they're compared relative to a US average oil level so what this tells. They may say a natural gas utility that wants to buy gas from one of these producers, you know what are the waste emissions associated and they may value for example gas from the New York bar basin at a premium, because it has a much lower emission factor this 60 kilograms per ton of oil at 53 for 1000 cubic meters relative to US average emissions. So now a utility company can log into this to this network. Right say we have an industry. Or say the natural gas company can log in and has been issued the certificate for the oil and gas produced, and they can now transfer products from one of its certificates. Okay, this is the new brahra producer can now request to transfer its products. But your time is running out. We want to be Q&A so can we get started with that please. Yeah, sure, we can go ahead. I'll close this out sorry about that. Just before we get into the Q&A would just talk a little about the business application. So there are two elements to this there's a emission verification and order contract pool. So this is sort of being set up as a Dow to the process of verifying data about that go into these emissions certificates. And then there's the actual emissions certificates issued in the marketplace that involves things like consumer commodity differentiation. So differentiating, you know, one unit of fuel from another from a different basin, but also compliance with investor environmental sustainability governments requirements so this is things like requiring an only gas producer to demonstrate and reducing its total emissions in order to access funding. So these are the type of sort of business models that we're looking at deploying with this with this solution. All right, sounds good. Can we have the Q&A? Yeah, a good combination but why NFTs. The reason why we deploy these emission certificates as NFTs is because they are, they're not a fungible token, right, they're a specific token that represents the emissions of a particular say producer or facility. We use the NFT just as a model so we're developing the contracts. We're using this Open Zeppelin standard. So we just use the NFT standard to develop it. Now it could be implemented in any sort of contract framework. Right, sort of, you know, because the unit of, yeah, see the unit of gas or whatever methane or is pretty much same across the world, right. So obviously you can take that as a unit of value. The unit for the emission certificate is actually the emission factor, which is unique to a specific facility. You're right, a product which we represent as a token is actually a fungible token and the product itself can be traded not as it's not an NFT, it's just a product that you can sell to your consumers. This is just a combination of different token types. We represent the emission certificate itself, which embodies all of this information, information about the emissions and information about the products which are fungible tokens into a non fungible token that enables us tracking of embodied emissions. Okay. That's a nice presentation and I would like to know to what level this can be industry ready just because the current runners are really strong and they will be having an existing space over there and how do you think your system can make some impact on a new scenario in the industry. Yeah, so there are a lot of existing solutions and new companies emerging. I'm currently looking at a company called Valadir this Canadian company that's providing cloud solutions to manage information about you know barrels of oil or gas for companies and they're providing these cloud services. The we're talking with them about how we can facilitate really tracking this value associated with the embodied emissions and giving you a fuel across the supply chain so that's taking it from the producer to the refinery unit down to the consumer. So really there's transparency of this information and that's where we believe blockchain in these public networks can facilitate the existing solutions out there that are facilitating sort of data analysis is big data analysis for gas producers. So we're really connecting that information across the supply chain. So that's where we believe our solution and our sort of blockchain innovation can can help some of the existing work which is also still very, very, it's very in the early stage, but is more evolved as far as industry engagement. But then it's really fascinating to see at least the functional flow of what you're trying to accomplish. The level is very, very high. I just want to reflect on that. I want to learn from you. Applications such as what we're discussing right now will be successful if you start to see engagement from the certification bodies participation from various folks right it's not just the two of us. There's a lot of different entities including government and others as well. Can you reflect for us here on the call how you're approaching that to ensure while there's a lot of technical merit to what you're actually saying which is very visible and kudos to that. How you're approaching that. So we've been in discussion with some of the major standard setting bodies like Vera right and interestingly Vera region recently announced that it's going to halt issuing of emission credits offset credits on blockchain networks. All right so this copying of the credits that they issue. Now, we do not deal in offsets for this prototype we're just looking at how do we facilitate the auditing process. And this is essentially what a lot of the standard set of bodies are doing right they put together, you know industry and auditors to create these certificates. We're trying to engage with the certification bodies to say here are tools you can use to facilitate that process and even bring down costs costs in the sort of, at least in the offset credit space and also the mission certification space which is we're looking at can be very high. Because you have a lot of different transaction costs against across different players to solve these problems to solve these problems and create these certificates. So we're trying to engage them to say okay here are tools to facilitate what you're trying to do and obviously at some point regular regulators could be involved in these mark in these type of tools for facilitating for more sort of mandatory carbon markets, right but right now we're just looking at a certain. I think we're running a bit out of time. I mean, I think we should all kind of be cognizant that there are a lot of teams right so let's try to keep the demos within eight minutes maybe nine maximum. And let's also see if we can keep the jury questions to 10 to 15 seconds max so that the teams actually get a little more time to maybe answer the question more comprehensively hope that's okay. I mean we all love these discussions but time is a constraint right so let's just try to keep that in mind. All right, hope that's okay. Yeah, thanks. So our next team is securing and validating sensitive data and credentials. Do we have folks here? Yes, yes, a very good evening to everyone. So our main solution was like the problem statement is securing and validating sensitive data or credentials through the use of DLT or blockchain authority. So, yes, so we're basically a team of four members, we're from, we're studying in the university, we're in our third year, and yes, so this is why we pick this problem statement. So basically a lot of transactions have become online and it actually has made our day to day lives much easier than going to a store and making transactions like going to the bank, giving information about the other person that we have to send money and doing all of that has become very easier through online payment. So we no longer need to venture outside and pay in cash and risks also like the risk increases when the amounts of transaction stored in a separate database that is, if it's stored in a centralized database. So it increases because there's loads and loads of data and it needs much like management. So our main objective is to reduce the risk of potential like loss of data through hacking or any other forms of data loss like corruption data corruption or something like that. And it's also to enhance storage options and make it affordable and easily available to customers. How we do this, we will use DLT to securely store assets to credentials like we provide a key like encryption we encrypt the data so basically how we do that is we break down all the data that they like for for instance, if someone is storing bank information. So we basically encrypt the data, we break it into chunks we encrypt the data so only you are able to access it, and we provide a key so and distribute the files across the network so this is how basically blockchain works and So yeah, so it's a decentralized technology meaning that your data is not stored in one database in one company. So suppose any database is attacked, like if a company has its data breached, so you don't need to worry about losing that particular data. And this is the architecture of hyper ledger like why we chose hyper ledger is because it has consensus algorithm. So this this is our main objective where people have to see what what you're storing like And everything that involves like we took person to person protocol and distributed ledger that just storage in all of this. And these are all the participants in the blockchain. So first we have the user to perform transactions, then we have the certificate authority, which basically looks through all of all of the certain questions required like whether they are, they have licenses and all of that. Then we use a traditional database to access like to store the data, then we use the processing platform, like from where they access the data and everything. And then it's on a blockchain development network and the creator like the developer makes the blockchain, and then there's a network regulator like he takes care of all the back end processes basically. And the benefits to this is it's it's a decentralized like blockchain is a decentralized solution where transparency is there. But it also maintains concentration like confidential data it doesn't give out data like that and it also improves security and denies like, you know malicious attacks and everything. And you don't have to worry about anyone else having access to any of your data because you have the encryption key and it's your data at the end of the day. And if acts and the data is accessed, like you can access the data from anywhere. It doesn't need to be from your home system, you can also access it anywhere from anywhere. So yes, that is it. So so where are you in your the development process or testing or adoption at this point in time please. Yes, so we haven't built a working model. So we were we were trying to research into like because blockchain and like decentralized storage is a very new concept we're trying to learn more about it. And we're very like you know honored to be here because this is such a big platform and it gives us very much exposure towards this. And hopefully we will we will try to build it like right now we're still at the learning stage. So yeah. No, but wonderful and have you said oftentimes a lot of these programs that we start to work on. If you if you have an early adopter working with us hand in hand that would be great do you have this in mind whom you would be approaching as you start to build or you want to build and then go approach your potential customers. I think if we had like a prototype that would help the customers understand what we are trying to do. And we would actually build the product first and then approach the customer. Okay, yes, what level you have done the market research for the project. Yes, so there are solutions for this like decentralized storage that is available but I've seen I've researched more and more like solutions based on this. But I'm what I'm trying to do is is making it open source like having a business model that properly fits an everyday customer instead of aiming for large companies like multinational companies. So thank you very much. I sincerely appreciate sharing your view and how you are attempting to build this capability which is definitely required best wishes to you. Thank you. So our next presenter is teams so near I hope I'm pronouncing that right distributed charity platform. Yeah, we can hear you. Yeah, we can hear you. Not someone. Thank you. Good evening. It's an honor to give us the opportunity of this presentation. I'm going to talk about distributed charity platform that is sunny out. Actually, this is our team numbers or team courses as we don't see the problem. We're not able to see your screen if you're sharing it. Can I hear me? Yeah, you're audible and visible. Sorry, what's the problem? We cannot see your screen if you're sharing it. You can click on share screen on zoom. Yeah. Is it okay? Is it okay? Okay, our problem statement based on statistics in 2021 Ministry of Labor and social affairs of Iran say that about 70% of people in Iran are under the power to rate. That means on the one side we have a lot of needy in Iran. On the other side, there are a lot of donors in central charities. So why these donors and these needy people are not connected to each other? The problem is about centralized charities. To say about the problems offered distribution are one of them. Secondly, lack of possibility to evaluate NGOs, lack of defining a unique identity for the needy in NGOs. Lack of coordination in providing assistance for privacy and the last but not least lack of transparency and money laundering. Our proper solution is eventually we have designed a distributed ecosystem called Sanyal, which means distributed plant is by a production platform based on hyperledger fabric. Sanyal is a distributed settlement platform which can be used by charity for managing donation process. We have three phase, three phase here. POSI phase is developing an open platform for charities. MVP phase is designed and developed distributed platform for selling unique needy people and recording transparent and trackable transaction. We are, we develop most of these phase and the future phase is develop a tokenization process for making competition into digital assets for tracking them in the process. The proposed model aims to build a consensus between charities based on five main process that consists of here. Firstly, that's resuscitation needy. Secondly, recording of benevolent projects or plants, recording of aiding to the needy of any charity, recording of aid between charities and the last one distributed settlement. Here is our diagram. That's three section. Our donors are connected to our system by a website needy actually identified by any charity and registration their information. And organization that are charities actually appear to appear to organization or charity. The network membership they introduce and identify the needy cover, for example, for example, settle assistant with the needy cover settle. Within the network. About market opportunity, actually signing a project is not defined to be a profit. It's a nonprofit project or target or the knowledge gained in the field of DRT and development of distributed settlement. The signing a project can be effective in financial and banking markets. I mean markets are all market, especially the Iranian banking market. We have five use cases here. I will explain more in the next slides. Our novelty is today about Iranian banking has taken a step toward transformation in the field of banking using distributed leisure technology or blockchain, but it is still new in this field. Our distributed settlement in the near future can create a competitive advantage for banking in Iran and perhaps other countries in the region. Small use cases post trade security clearing and settlement, for example, is probably expensive or by our solution, it can be reduced from 50% up to 90% of trade processing and settlement can be automated. About another use case cross border payments is a slow settlement time or solution can make it possible for individuals and corporations to try more directly making payments simpler, faster and more secure with settlement of cross border payments. Another one is inter-bank PVP settlement. It's about its problem is control issue by our solution banks can net in an efficient manner choose what time to settle in which currency I'm with you. Let me show you a video. I'm going to play a video is a real situation of our transaction among blockchain network. Here we have 87 blocks and 87 transaction is pure to be actually right. In organization to organization to we have 16 transaction. We are going to actually like in our website is from organization to this website is one charity, for example. Here we are going to registration and needy. We put some information about a needy here. In this. When we, when we want to save this transaction, it will go to the blockchain network into a fabric into a hypervisor fabric on the left top. The operation was come back to our transaction here is 88 plus one plug and one transaction includes an organization to increase to 17 transaction. Another smart counter another is defining a plan. We are going to define a plan information is added here. And after the same. We see that the operation was successful. Another transaction increase increase and organization to increase to 18. 18 transaction. In the video we had actually let me hear. Our transaction. You can see IP in here. And community has our goals are to develop infrastructure improved system. We have we need a mentor and a special consultant in the field of DLT and also some conferences. Thank you. Thanks. I finished. I finished my. Thank you. Judy, if you have any questions. Thank you and thank you to your team. Can you reflect on where you are with the product because I saw something working right it's a prototype that's working. So can you elaborate the readiness towards having customers using this. Are you very close or your halfway through. Can you elaborate that please. Actually, I say that it's not. It's a nonprofit ecosystem for us. We are related to. Bankmark banking markets. Okay, we simulated a settlement distributed settlement in our projects and we are some other use cases in banking in settlement for developing settlement in realistic. Banking markets in our banking projects. But we negotiated with some organization some charities to deploy this ecosystem and hopefully they are trying to work with us. Wonderful. Thank you. Thank you very much. Thank you. Okay, okay, and you can practically implement the consensus in the system. To what? Practically implement the consensus in the system. What do you think are the challenges for implementing the consensus. Sorry, I couldn't understand. Yeah, you have to go for some consensus between various parties over here right. Okay, we use a draft. Okay, can you can you can consensus. Yeah. Implementation is possible. To what level it's implementation is possible between these kinds of parties. In market and business you mean. Yes, yes, of course, he's not asking what consensus technically. He's asking how do you onboard banks, yeah, how do you convince banks to put those transactions here. Okay, because you're talking cross board, yeah, cross border payments and all right. And that is a CBC use case and we need not bring that we can't really bring that kind of thing into a charity scenarios right. Yeah. Actually, since the reality, I believe this reality. Yeah, I believe that it, it can be in reality because we have some solar use cases here and we can implement this ecosystem in other projects. I think that's why it's really important and is distributed. It's really useful in other projects. Okay. Thank you. Are there any other questions. I think we can go ahead with the next presentation. Thank you. Thank you for your time. Well, our project is transparency interoperability national electronic toll network this business. And this business for for the Mexican government is the national electronic toll network. Thank you for your time. Well, our project is transparency interoperability national electronic toll network this business. And this business for for the Mexican government is very important because the incomes, the incomes every month every week or every day are so so so high. So by these reasons, but so by this reason the problem is timing right now we have is because there are a lot a lot a lot of operator, a lot of operator around that around that but this operator when you cross when you cross the toll when you cross the call the toll. You get the ETC message this kind of ETC message is received by the toll for example the toll a we have, we have operator a operator B. But in this case, for example, the tag owner, the tag owner toll, the tag owner toll pass across the operator B, but the owner is operator eight. In this case, for example, this, you need to put this information into the FTP server. But right now, as you know this protocol right now the FTP server is all is insecure right now. So by this reason, in this part of this part of face. We need to resolve three aspects very important. So in this case we need to resolve integrity, traceability, traceability and payment in this case, for example. But right now. Okay, the proposed solution we have right now is the first step is to take out the FTP server. In this case we propose we propose to propose to have the solution. We have the block chain, the block chain right now, using the hyper layer, and the hyper layer public process, okay, like a blockchain or private blockchain, and to have right now the we have the need to use the new protocol. We thought to use the Ethereum protocol but as you know, the Ethereum protocol is suspensive the first, and it's so slow right now because they are using the proof of the proof of work. So the protocol is using right now the proof of the stake by this reason, why was this reason behind that to use the protocol proof of the stake. So, the other the other kind the solution is to have in this case we need to, we need to that we need to bring this information to authority government up to now the government does not have this information when the give the give them this kind of information to make a invoice in disguise in this case in the invoice is so difficult to make as a concealed because the government authority does not have this kind of information. By this reason is very important to have is very important to have in this case the hyper layer fabric behind that because as you know. The private blockchain is very important to this kind of business in disguise and the government is very jealous with the information and by this reason is very important to have the hyper layer and bring them, bring them this this kind of administration, because as you know, well, this kind of administration, because as up to now they don't have the guy they don't have this information to make a concealed between the operator to operator two or three or four. They just only receive the incomes and the seed but after that they don't have to make a audit with any information any information they they have right now it's only the it's only the operator 123 or whatever any kind of operator have right now. So, this architecture right now is the the acts of the currently process, we are making the we are, we are running right now into the into the, the talk about the it is a message is a proposed to be proposed this architecture, as to, as you can see, in this case, for example, we have the, we have received the it is a message about the dog eight, for example, in this case it is a message you go into the blockchain first and to go into the database and after the gateway, this one that we're going to we're going to send the it is a message into the queue, the queue server, like a rabbit in queue in this case, and after we're going to send this information to the blockchain near or near blockchain, because as you know, at the end of the month, we need to send this information. So, some of the information about this kind of this kind of EDC measures, a pass across the each tall, a different owner. So, the solution architecture is to make is to make is to put this in this architecture into the AWS right now. I think we have easy to I will like to I will like to put in this guy in this case, three kindness or not easy to right now to make a to make a conceal to make a simulate operator, and after to simulate the send the message like a EDC tall. So the solution architecture like a private blockchain fabric is this case is the architecture. I was, I was, we was thinking to, we were thinking to have operator five, for example, or operator two in this case to receive the message. Okay, up to now we don't have any from, we don't have any from and just only we have the, we have the backend on the ground process using the Python right now, and we send information across this kind of sketching. And then we, we send this information across the, the same call. So, as you can see in green the authority authority admin is going to be the government. In this case, the government is going to be the owner, all the information after the operator send the invoice to receive the incomes. So the architecture message queue rabbit thank you is this is this is this kind of architecture, we have a triad we have a tree operator, for example, is going to be going to receive the message, because as you know, the gateway, this kind of process the gateway is going to receive every message and the gateway is going to think, okay, I received this message but you know, you are not the owner, you are not the owner, I'm going to sense, I'm going to send this, this process is a message to the correctly owner right now. In this case, the process is to receive the message, go to the exchange right now. DHL, for example, the message queue, and after you're going to send the property, the property, the property or the owner, in this case operator one operator two operator three in this case in the into the interoperability. We have the kind, we have different operators. So this kind of operator has, for example, posters is SQL, I don't know, both in this, this simulate all this demo we want to use a poster SQL. As you can see, we are using right now the posters SQL. We are going to use, it's going to be into the AWS as cloud from easy to call the build, for example, and database and postgres and web engine. We are thinking about the, we are the web page, or M we're using the SQLize and backend. In this case, the type of script and front end BGS and CNC front end and GitHub, and code files, private blockchain, we're going to use the hyper layer, the public blockchain we're going to use there, the near and after we're going to use the Q message server we're going to use the rabbit in queue. The most important benefit about this are behind the solution is the benefit of solution and so several and the most important are the transparency and internet information collecting from the cost operator. And if they're, for example, if they're in a loose communication, we're going to use the MQ server, but what he using the MQ server, we can, as you know, we are using the tolerance fail or fail tolerance. And the, the interoperability type delivery is, it's going to send the correct message to the correct owner, in this case. So, okay, let me show you the demo. Okay, you can see my, my screen right. We're still on the solution benefits like, and we have around 15 seconds left for before we open up for you. In this case, we are running right now the boxers behind that in this case this process is sending the information the Q information to the gateway right now. Okay. I want to send the queue. So, in this case, we have the different server the shield dish out is going to be going to receive the gateway for the information and the Q server and the API gateway and my name there. Db and after the web page. Okay, this is under construct. Let me show you the process is running right now. So, I'm going to start to receive the message right now. I'm running right now the gateway. The process is running right now and sending right now sending information to the blockchain hyperlayer and we are we are in this process is sending right now the the MTC message into the near protocol. So, let me show you the application web or the web application. We're running out of time with in mind wrapping it up. Yeah, it's okay we can understand the stakeholders and nothing much on the up to now we are receiving right now the the message from near and near receive the message as you can see right now we have in here the MTC message into the blockchain and local and local host right now because I would like to use the public blockchain but I'm using the just only the local host to make a demo and you can see I received the this kind of message. Well, I would like to show you the promise those to check the how hot hot hot when I add the information into the hyperlayer fabric. So, as you can see right now we have the web page of rabbit in Q a rabbit in Q is receiving right now the all the message. You can see is receiving all the measures and here we have the wallet near a local house and the fabric is receiving right now they all the message into the blockchain the private blockchain. Excuse me for my for my laptop is so slow, but okay. I'm really sorry but I need to stop here at this point so that we can get at least one jury question in we have about a minute or two left. So, any questions please. I just have one question. Can you elaborate the importance of hyperlegion fabric here. So a lot of the things you have explained this is being built right so there's some differentiation, if you can share your view to the team that would be fantastic. Well, the, the important to use the hyperlayer fabric behind that is to because as you know, well, we are using like a to resolve the transparency immutability and the after the payment, but in this case and in Mexico government is very yellows or yellows with information or he's in the information. And in this case hyperlayer fabric is going to is going to be good for us to share this kind of information and to be secure, to be secure, because we thought to use, for example, whatever engine or a call or whatever the one you think, but hyperlayer is going to is going to be in the information it is a message is going to be safe to receive every invoice and to conceal information the different authority government best because it was the idea behind that. All right, are there any other questions. I'd like to know why he has also have a combative statements with the other platforms like Ethereum for implementation. Consensus regarding the proof of stake and making plans TPS etc. Can you have a combative statement with other platforms. Well, well, I took up exactly the answer to the TPS. Right. So well, we thought to use, we thought to use the near protocol because we are just I don't yes I different different kind of protocol, different levels of protocol to one three. In this case we're going to use the level one in this case the proof of the state because it's going to be more faster than more faster than Ethereum. And the other, the other, the other idea behind that is to use the, because as you know the cost, the cost of the cost of transaction with a terrible is more expensive than a new protocol right now. As you know, Ethereum is thinking to make it to move into the proof of the state right now, but it's missing a lot a lot of time I don't know. But in this case it's more faster as you know, a way in this case the government, the government wants to resolve the micro payment. In this case, okay, in this demo, I cannot show you the micro payment right now because it's not implemented, but near protocol is going to is going to support or it's going to help you to make this this to load the cost. Thank you. Concludes our presentations for the day we saw a lot of really awesome presentations. Thank you to the members of the jury for spending the time with us and helping us evaluate and judging all the wonderful presentations thanks to all the teams for taking the time, you know, all these months to develop new things awesome things and presenting it here as well. And then tomorrow, I think the invites have already gone out for it starts at 1130am IST. It may be in various different time zones for the rest of you would love to see you there again.