 Again, good morning, good afternoon, and good evening, everyone. We have, welcome to the second round of Hyperledger Challenge, which is Prototype Phase, and we are excited to look for, look, have all your presentations, all your prototypes built for this challenge. We could not be more proud of what outcome has come in for this event. And on this call, we have three of our esteemed jury panelists. We have Professor Ali, he's based in Australia. He is a professor at Queensland University of Technology. And he also recently started community activity for, it has been a long time community member at Hyperledger, and also he currently has started a chapter for Australia, and he's leading the chapter. And then we have Kamlesh, who is CTO at Snapper Future Tech. I believe most of you might have already seen him or heard about him. So he is also, along with his job, a long time community member at Hyperledger, he's at CNTSC, as well as his co-leader of Hyperledger India Chapter. And then we have Radirik. Most of you may have heard about settlement already. So Radirik is co-founder and CTO at Settlement. And he's joining us from Europe. I believe it is from Germany, if I'm not wrong. And... Well, yeah, but close enough. Right. Sorry. So you might have heard about, hired from many other members from Settlement who have been helping us in different events that we have in Hyperledger. So we are delighted to have three of you on the call. And we are looking forward to your final results evaluating these proposals. Now over to the team. The first team would be Anosolok. Okay. Yeah. My name is Ramazun. I will present our project, I don't know if it's social looking. It's a short Anosolok without the N in the end. Yeah. And the pitch presentation for the Hyperledger challenge 2022. Yeah. I'm not alone. So we are on the team. It's me, Ramazun, Misha, Salih, Thomas, Epler, Manuel, Foster, we are based in Switzerland. And what we are currently doing is we enable transparency, control, and simplicity for social looking users. So what does it mean? If you look on the social login, like looking with Google button, you have on the light side, these are convenient for users to register and look into web applications. But on the dark side, you have the user behaviors tracked in the services, making the user product of social identity providers. On the another thing on the dark side is the data related needs of users are not addressed and users still have a lot of places to remember. What we did, we did an analysis of jobs to be done in this process, the outcomes and then make an own user research and then posters on Twitter, LinkedIn, and all the platforms to find what are the underserved needs of the web users for this process. And we found out that by our user research that the top needs identified transparency, control, and simplicity. So first, user want to know what personal data they share with which organization and who else the data is shared with. Then users want to decide and control who can see and use their personal registration data and behavioral data. And users want simple, convenient logins without having to pay their personal data, the granting of user rights and behavioral tracking. So and if you look on these needs, we defined our new approach and our approaches. Okay. First, people have full transparency on the data, granted user rights and behavioral tracking. Second, people can decide and control who can see and use their data. And the next point is in our approach, people can simply and conveniently log into web application without paying with personal data, the granting of usage rights and behavioral tracking. So in short, we want our approach is look in without Google button. So we want by using Anasolock, people can simply and conveniently look into web application without paying with personal data, the granting of usage rights and behavioral tracking and have full control of the personal data and the use of this. And if you look on the technical basics, we want to go with self sour identity concept to solve this. And therefore we use hyper ledger areas project to implement this. So first we use the self sour identity concept to bring ownership to the user social login back to the user. Then we want to provide an issue, which is provided by trusted partner like Linus Foundation. And that's the issue that outputs the data from a social login as a verifier credential. And we want to make a verifier that can be easily integrated into existing web application using of my disconnect or summer to enable registration with this issue to verify credential. And this will be the open source project. And we want to offer an additional support on time material basis or as a service for the integration. So there are two components. The first component is the issue. And here we just transformed the open ID connect connectors from the social login to the verifier credential through did come using the areas cloud wallet. And on the verifier side, we do the same but other way around. So you verify the verifier credentials through the areas cloud wallet and create a token using the standard protocol some of it only see to integrate this in the applications. So by our solution is unique, we seriously focus on the true user needs. And we want to do the constant research on those needs and know the needs. And we are driven by the urge to create something meaningful to the world. This strong focus on true user needs will ensure that users will trust in our solution and love the way we give them transparency control and simplicity. So as I said, the central identity provider cannot track any user behavior. Users can immediately see in the NSO lock wallet where they have locked in with all the accounts and where which usage rights they accepted and they can rework rent rights to use. The real user needs in focus instead of monetization of user behavior. So and let's look on the demo. Here we start to see the platform. So you look in with the look in with Google button. And here's Michel's already looking and what we did after creating and getting the data from Google, you give this data as a verifier credential into the wallet of the user. So in the wallet, the data is stored. It's belonging to the user. And if the user will show this credential somewhere else through the small wallet, Google will never get this information. So it can be tracked anymore. So if we go to another platform and want to look in without Google, but with the Google data and this is the key point. So we have a look in without Google button, for example, on the Linux foundation, this redirects us to the OpenID Connect login page, which is now with a QR code. So just to grab the data from your social login. After showing the data, you're looking and voila, you are on the page. Yeah, so our roadmap is we now the next point is we want to take more time for this project. We want to make more market research and also make something that we want to integrate in the real web application providers. The next step will be for the next year, where we have to scale up. So all the preparations for the team, for the community, another market research again for overseeing needs and pitfalls and of course refactoring of the solution for scalability. And our vision in 2024, we are the global registration and look in meta-service provider of choice for all relevant websites and web applications that focus on the true needs of the internet users. And this is a transparency control and simplicity. And this provides through user sovereignty and ownership of identity data and tribes. And the question now is why now? And if we look under especially in Europe, where we are based, the regulators are also in the meaning that the personal data belongs to the person. And this means and the behavior is also personal data. So if you look on the A, this proposal 2.0, the Swiss government, the data protection laws, especially in Europe or California, you will see that this is the way to go if you think about the identity providing. The next thing is after the major data protection scandals, the awareness of the personal data by the web users has increased enormously. Then we did our own research where we just clearly shows that transparency control simplicity are now the three most important and underserved needs when it comes to look in user choice and behavior tracking. And do not forget that psychological motivators behind the crypto and web three also clearly indicate a strong trend that ownership of the troll of identity and data will come back to the user. So away from central solutions, now it's goes more decent room. And also if you look on another studies belongs to digital identities. Here's one done by check D. This is also showing and supporting our hypothesis. So and everything, every sign shows that now is the time for the sort of approach. Thank you. Any questions? Yeah, hi Roman Kamlesh here. So I think this is a unique idea. So did you any market research like what is the customer looking for this kind of solution or just only the what is available in the media about the data privacy and data security issues? And on the basis of this thing, we are proposing this solution. So if you if you look on the current, current, we lost your voice, Roman. Yeah, I think we lost. Do you hear me? Hello. Yeah, we can hear you. OK, sorry, sorry for the interruption. Yeah, so the current market solutions are basically everything is central way. And because the collection of the data, data of people is an asset for the companies. And we think that if we go through hyper legend links foundation, we have the chance that to show that the true needs of the personal data providing should be by the person itself. And we want to make this from this way. Yeah. And the last question, like, what are the different competitors in this space who are working in the single SSI based authentication and the competitors are basically there are some people who are doing self-serve identity, but they are focused more on the B2B level and not on the user level. If you if you look what are the current solutions from the Hyperledge areas based on Hyperledge areas, you will find a lot of projects there. But they never tackle the needs of the person. But basically, if you look on self-serve identity concept, it's user centric and all the projects are tackling the B2B market. But without the user, self-serve identity will not survive. So I think this is the difference because we are really trying to go to the to tackle the real needs. And I think this is the way to bring self-serve identity also to the market. OK, thanks. Where are the verifiable credentials stored in your application? Is it in the mobile app or is that all? Yeah, so basically it should be in the mobile app because the personal data belongs to the person. And if you so the the Hyperledge areas store the verifiable credentials also in the in the wallet itself. So it should not be the way that we share the data somewhere else or on the storage provider, because in here, in a solid approach, we want to look only on pretty low level of assurance logins. So here we want to tackle the needs of the typical web user and all the processes in the logins that he is doing every day. And not like the electronic idea where you I don't know. I don't know how often you need this in the year. But here we really want to say that people should use self-serve identity to look in in the everyday life. And the level of assurance is not the highest one. And even in disaster recovery, there are some backup approaches. So I think this is the way to go to store the data really by the person and to give them more trust. Because he control everything there. And if you compare it to approaches, for example, I know the Belgian government or at least the Flemish one, they are experimenting with Tim Berners-Lee's new new identity and data storage mechanism. How do you compare to those? So we if you use the self-serve identity without this infrastructure, Berners-Lee, you have less cost for the infrastructure because on the so the NSLK issue is basically it's a public key infrastructure. So and the only thing you store on infrastructure is the public key. Everything else is transferred through peer to peer. Yeah, just transferred through peer to peer connections and the infrastructure. How to say costs are really low. So and I think for such a way, we should go for a solution which have really low infrastructure costs and because all the costs should go to the mobile devices in the end. So this is the way to go. I think if you go this in a really scared way. And maybe one last question, if I have still time, if you're looking towards the future, wouldn't it make sense to build already so that you can support electronic IDs and medical data and all kinds of very sensitive stuff? So if I can just say my analysis about the ADES and so all the proposals for the EID, they will it looks like they will based on the Hyperledge Areas project may be so. And I think what we could really think of or we should really it's an interoperability with the wallets for the EID. For example, for maybe for onboarding or for two-factor authentication. So the interoperability with the regulatory IDs should be implemented. Right. Thanks. Thank you. Awesome. So if there are no more questions. Thank you, Anu Salog. I think we are on time as well. Yeah, so what was the project ID for this team? Project ID is seven. You can fill in for the team one session within that sheet that was shared. OK, so you can go by team one, team two, I'll fill in project ID. OK, OK. And I think as per the evolution, I think they want to open source this to the Leipzig labs or not? Or you can fill out that later. Yeah, so we will do the verifier as a lab. The problem now is to find the time because now we get this email like a couple of days ago and we will do this in parallel to the launch phase. The verifier will be a hyperledger on the hyperledger lab. The issue or not because the issue is something we should provide with a trusted provider where people really with supporting by a trusted provider or trusted partner like Linux Foundation or Hyperledger, so the community trust in this, the verifier instead is more integratable and this is something we will give out and really have to look how to integrate in all the web applications. So the verifier part will be on the hyperledger lab. The issue part is maybe less interesting for the implementation is more or less the interesting part is the governance about this and the trust. And here, I think with the Linux Foundation support, this is the way to go. OK, thank you. Now we'll go with the next team now and the next team is I shall reviews. So team, if you are on, please present your screen. All the best. OK, is my screen visible? Yes. Hello. Yes, it's visible. Please call. Am I audible? Yeah, it's visible. Hello, everyone. I am Priyanka Manda, a software development engineer at Geo platforms. I will be presenting a submission, a cell reviews, revolutionizing online reviews for this hyperledger challenge 2022. Our team members are Nidhi, Meenakshi, Saurabh, Rishabh, Tarul and myself. So starting with the problem statement, online reviews play a major role in today's digital world. Nearly nine out of 10 consumers worldwide read reviews before using any service or buying any product. Consumers have no knowledge about the reviews getting altered. Taking advantage of this situation, many parties generate fake biased reviews on their platforms, thus credibility of reviews gets questionable. Agreeing systems are centralized. No transparency is provided as reviews cannot be tracked or traced. Also, also reviewers are not getting any incentives for reviewing. Hence, they don't feel motivated enough to provide a review. These are some of the facts which you can see for yourself. So our rescue plan here is a cell reviews, a blockchain plus AI based solution. And a motto here is trust more buy more. So coming to propose solution, being a blockchain based solution, it is a decentralized platform that provides transparency, trust, a platform where the opinions of every customer are valued and noticed. We will be using AI to filter out low quality fake reviews and make honest reviews eligible for rewards. Thus, we do have a reward system in which we will be providing incentives to customers for their honest reviews. These are some of the major benefits that a cell review provides. Talking about novelty, as we already know, ours is a blockchain based solution, thus it is a decentralized. That is, there's no a single part of authority here. Also, transparency as well as data integrity is maintained. We are using Hyperledger Fabric as it is a modular, scalable, more performant compared to the rest frameworks available. We are using artificial intelligence to identify fake reviews. This is a solution architecture diagram and tools and technologies. Both of these will be covered in the demo. So now my friend, Nidhi will proceed with the demo part. Thank you, Prayanga. So as we have already guessed by now, our cell reviews has huge potential in various domains such as healthcare, supply chain, lifestyle and others. As customers have as reviews play an integral part in everyone's life. So for the demo purpose, we would be targeting for the tourism industry. So there are basically two types of users. The first one is the guest user for which no login is required. As you can see, the guest user has the privilege of checking out the dashboard where all the reviews are there and the guest can also get detailed view of the reviews. So this is how the details we would look like. And there is also a wide page that could be visible to the guest user. The second type of user that we have is the reviewer. For being a reviewer, the user needs to log in into the cell reviews. So from here, a account can be created. We will start the demo by logging in with existing credentials. So yeah, being a reviewer, the reviewer can write a review. So let's get going with the create review page. So this is what review page looks like. User can enter details and submit a review. And yes, for eliminating fake reviews, we have two strategies. The first is we would be having a group of moderators, which would be performing certain checks and identifying fake reviews. Moderators would be nothing, but they would be like reviewers who have performed good on our platform. We would be promoting them, promoting them to the moderator role. The other way through which we can identify and eliminate fake reviews is using artificial intelligence and artificial intelligence would also be used for what I say, creating the credibility scores of the reviewers. And yeah, so the details have been filled. Now we will go and submit the review. So a review ID would be generated in this case. Now the reviewer also has the option to check my reviews, the reviews which the user has created himself. So on this page, we can see the review that was just being created. And being a reviewer, there's also a facility for upvoting a review. So let's get back to dashboard. And now if the reviewer finds a review is in alignment with what the person thinks, he or she can upvote that review. So this is about that. And coming to the tech stack, the front end is built in Angular. The back end is written in Node and for Hyperlegia, Hyperlegia Fabric is being used as blockchain. Now we can verify the reviews that we created by using Couch TV. So in this case, we are using State Database as Couch TV. We can go into that review collection and check for the product that we created sometime back. So entry would be present in the Couch as well. And we are also using MongoDB as an off-chain DB for storing the database. So yeah, as we can see, the entry is there in the Couch TV. We can verify the details from here. Other than that, we have integrated Hyperlegia Explorer as well. So it's basically for getting an overview about the blockchain, network, blogs and transactions. So as we can see, there are 85 blogs which are committed. The last block was 58 seconds ago. That's the one that we incorporated just now. And we can also explore the transactions. Let's check that almost transaction. So yeah, here we can see even the payload in the right side. So this is the same payload that was being passed from the front end. It's getting reflected in the Hyperlegia Explorer. So that's about this part. And if we talk about our strategy for market adoption, what we are planning to do is we are thinking of attracting the consumers first by providing them incentives. And once we have the enough consumer base, what we can do is we can picture our idea to the major online platforms in the market today and they can come with us and integrate with our system since we would be having a consumer base, which would be having reviews related to their brand as well. So that's how the adoption strategy looks like. And yeah, we can continue the presentation. So this is the code repository. It is publicly available on GitHub. So feel free to check it out and contribute to it. And now let's talk about the next steps. So we are also planning to implement or create an off-chain DB, which would be basically used for analytics and reporting purpose. We would be populating the off-chain DB by we would populating the off-chain DB by some batch processing. And then we can perform rich queries on it. And in the next phase, we would be also trying to implement artificial intelligence for identifying the fake reviews. We would be doing data modeling there. And once the product is ready, we will launch it out. Beta testing would be done. And after that, after beta testing is done, we would be pitching our idea to different service providers in India. Firstly, we would be targeting tourism industry to start with. And that's how the roadmap for launch phase looks like. Yeah, so I think that's bring that brings us to the end of the presentation. Thank you so much. So thanks for the presentation. From the blockchain perspective, from the blockchain survey, I believe you're using blockchain as a point for integrity to make sure that the integrity is there. But the other stuff like saying identifying fake reviews and things like that, they will go ahead with AI, not the blockchain part of it. And also, when you do identify a fake review with whatever methodology that you have, what is what is your approach? Like, how would you deal with the person that is writing that or that comment itself? I didn't get the last part. Can you repeat that thing? When you when you identify a fake review, then how would you deal with it? Like, what would you do to the comment itself to that review itself? And what would you do to that person who wrote that review? OK, OK, so for identification part, what we have thought is we would be injecting all the reviews to the blockchain for the sake of transparency so that everything is visible and there would be certain checker in the blockchain. It's like, let's call it a flag. So that flag would be marked on we could know that review is fake. And in that case, it's like transparency is there. But for the person who is doing the fake review, we won't be doing anything for a certain amount of time. But it's like if that person is indulging in such sort of activities for long, we will try to restrict his or her access to the platform. Does that answer your question? Yeah, cool. Thanks. Could you maybe elaborate a little bit on the economics behind it? Because you're saying you're going to give out incentives. Where are they coming from? Who is paying for them? Because traditionally in these review worlds, it is the websites that show the reviews, the ones that have the economic incentive to do something with them, that both have the money and not necessarily the will to remove fake good reviews. So how are you funding these incentives to build up that customer base? OK, so for that, of course, we would be providing some sort of rewards, but that thing is not yet finalized. We were thinking about implementing some forms of fungible focus for that. For that, we would require help from sponsors as in if we could get a sponsor for this project, it would be really great. So yeah, that's what we are targeting for now. Yeah, thank you, Nidhi. It's nice presentation. I'm thinking about the blockchain network perspective. So how we can justify like what are the different district holder in this blockchain network? OK, coming to start, since we already know that there are major players which are there in the market, right? We can't attract them saying that this is a platform come to us. So that's the reason we are targeting consumers first. For now, we would be just having one node, right? And once we expand our network, we onboard different service providers. We will have nodes for them, making the system truly decentralized. So that's what we are targeting. I mean, to start with it, it would single node cluster. Yeah, okay. I mean, like when when you offer this platform, I mean, sort of Flipkart or Amazon, they are in the same same blockchain network in the in the background, right? Yeah, yeah, we will. We will integrate with them as in we can expose our APIs to them. They can integrate with us or we can provide our platform as a service sort of thing and then they can have a node in our blockchain network, let's say we're taking an Amazon node, so they will have a node and the other companies, they will also have their individual nodes in the network. OK, all right. If there are no more questions, maybe we could go to next presentation. Jury, any more questions? We still have about one and a half minutes left. OK, is it possible to to ask also not for jury members? Mm, let's let's keep that on the chart. Let's not make it on this record. But I appreciate Roman, your question. That's a valid question. How are you planning to integrate the review process with existing websites? As you said, you want to build a customer base first. Are you going with some kind of a browser plugin or how do you connect? Verified reviews to websites that not necessarily are part of your as partners. So that we are thinking of exposing APIs to them as we can have some API set. So as as soon as a customer posts a review, so that it would be like an API, so the entry would be created into blockchain corresponding to that review, which the customer is posting on their website. That's what we are planning to do. Would be like a generic API, which would be exposed to different platforms out there. Or if required, if required, yeah, yeah, yeah. Might be a stupid question, but why would I take booking dot com with all the all the fake reviews and seven people booked these three seconds before you stuff? What would their incentive be to spend time and money on developers to put to integrate that API? OK, that's not a stupid question. That's a very good question, I would say. So in this case, what's happening is that's the reason we are talking consumer based first. If we have enough consumer based on our platform, saying that this is a platform which we trust and rely on the online platforms would want to join a platform in that case, right? They will want to be part of a cell reviews. So that's the reason we are targeting consumer based first. It's all about the consumer basis to if you go to booking dot com and you don't find anybody anybody posting reviews there. So you know how it is right? So I think we are targeting consumers for that reason. And that's how we would be planning to do it. Once we have consumer, we are good to go. So and it's also like the consumer post reviews for different brands, right? So there is a section for brand. So let's say if you're a consumer and you post review for Amazon, right? So we can build some reporting sort of thing and we can pitch our idea to them saying that these many reviews have come for Amazon on our website, right? So in that way, we would have exact numbers and we can pitch them our solution to them so they would join it. No, I think what you could do, I think a browser plugin that overlays across these websites without their interaction. And then you can add buttons to reviews. You can add just like an overview of, OK, look, these ones were reviewed by us. I think that would make sense because then you don't need the cooperation of the bad actors to make it work. Yeah, the point taken, we will explore that part as well in the next round. Thanks for the solution. Thank you, team. We will have to wrap up because over time we'll go to our next team. OK, thank you, Julie. Thank you, everyone. Thank you. The next team would be Electrodo, Climate Related Risk and Sustainable Asset Management. And I hope the team is ready and if you can stop presenting. Yeah, yeah, I'm ready. Thank you. Now I... Yeah, Tim, whenever you're on the screen. Yeah, do you see my screen? Yes, we see it. Yeah. Hello, colleagues. My name is Roman Krautschenko, I'm CEO for A2 Solutions. And today we present our product to Electrodo. So in post-industrial world, we need to re-sync and rebuild our financial system from a traditional profit-oriented approach to sustainability-oriented approach. So that's why we created Electrodo as software service that converts climate-related risks and carbon-related assets into new financial outcomes, into a new sustainable value. Briefly about our company, we are a software engineering provider and specializing in industrial blockchain-based solutions in energy and fintech domain, primarily in the great solutions for green finance domain. We have a headquarter in Ukraine, we are from Ukraine, and we have a representative international office in Singapore. And in Singapore, we participate in the National Singaporean Centre of Innovation for Energy Collapse, partnering with Singapore Institute of Technology. And in Europe, we are partnering with Energy Web Foundation, a great open source blockchain-based platform for energy companies. And we have also a partnership in Ukraine. This is our team who are involved in building Electrodo. And we have a great team of engineering guys and guys who are focusing on entrepreneurship and business development. And what is the problem statement that we try to solve? First of all, companies don't understand what are climate-related risks and how climate-related risks impact on assets and financial outcomes. And that's why companies can transform carbon climate-related risks into opportunities and new financial growth. So our proposition is Electrodo. So this software service for climate-related assets and risk management to increase enterprise market value, based on providing sustainable business models. So our solution is a platform for easy data and context management. Also for gathering data and processing data and generated sustainability, easy reporting. And this data will be verified by using blockchain technology from Hydroledger Fabric. And finally, we are building like Green Finance and Giant for working with carbon-related assets and provide carbon-related asset management services for managing different types of assets like carbon credits, green bonds, etc. This is our general solution or system design. And we use Hydroledger Fabric for building the centralized autonomous organization inside our platform. We use open source context broker FIVARE for gathering processing data about about ESG data and provide this data for consumers like financial institutions. And on the prototype stage, we are building blockchain-based and IPFS-based data management system. And we want to show the principles of gathering processing data and verifying data using blockchain so we can trust this data, ESG data, and can share this data for financial institutions, for example, for insurance companies, for banks or institutional investors who can assess this data and assess climate-related risk for companies. By using Electrode, companies can attract green investors for funding because investors can assess ESG risk inside these assets. Companies can avoid carbon taxes, for example, C-bomb in European Union and get lower insurance costs and, as a result, increase in enterprise market value. We name our novelty as green financing giant and Electrode brings together industrial enterprises and institutional investors, different financial institutions and convert carbon-related assets by gathering and collection and processing ESG data into new liquidity for green finance market. So our goal to tokenize ESG data and tokenize carbon-related assets. With our project, we won Euro grant call and now we are partnering with our Singaporean partners. In Singapore, we are building our pilot platform for sustainable living in public housing in Singapore and we provide Electrode as blockchain-enabled decentralized layer for clean energy asset management and payment optimization. So our platform motivates for consumer clean energy and we provide clean energy traceability and asset management for this fund. Our short roadmap, now we are focusing on creating extended ESG data and context management system and our next step to develop decentralized autonomous organization for voluntary ecological market and we are our solution based on one of the standard for tokenization for voluntary ecological market. We want to extend integration with FIWAR context broker and improve reporting based on the CFD recommendations. And in this year, we want to participate in IFA trust open call and provide our solutions to contribute in FIWAR open source development. Also, we participate thanks to this hyper-logic challenge. We start to participate in this climate action and accounting interest, special interest group and together with Sherwood Moore and Saichien. And now we are involved in working with this group. And finally, at the end of this year, we seek to pilot a project in Singapore for our solution for ESG data management. And now we can provide a short demo for our solution. Yeah, please stop sharing the screen. Perhaps if we have more time. OK, so our solution is already working and we are when we are started tackling with big companies, it's very challenging for them to create this automated system based on FIWAR. So the first version of Electroda, it's Electroda talk and it's working to manually. So you need just to imagine that the company wants to show their reports, show the information about governance strategy, race manager, metrics and targets, and they're just giving this data to the people. So in the company, there is a few roles. It could be like a manager who collecting this data and just upload it. It's like an input folder. And the second manager who is working with this data, who calculating all the influence in the world with carbon information. He calculated this data and applies the second document in here. This calculated information and that's all helped them to create a standard balance open to everyone, this information and the documents. So our solution just could create different folders right now, give access to different folders sent to different persons and new people, just like its test user. If you have only input data folder where you can just upload some information. Just like this, I'm going to show you. I will open this doc just a second. It's like I'm uploading here and the second user just see this input data. He could just download it and basically the data he calculate all the emissions. And one of the interesting features we have ability to upload energy to the certificates right here. So the user just could upload this data if the company is from the energy sector and create a certificate to verify it with another role, like verify all the system who could just check all the information about energy generation and create this IREC, this is like renewable energy certificate where they just store it or just sell it or just transfer it to another user. Well, something like this. Do we have more time to show more functionalities now? But as I see in the chat, we need to go forward with that. Thank you, Roman. So are you going to repeat the question? Are you willing to look at this product open source in Hyperledger Labs or not? Yeah, now we are applying on Hyperledger Labs and share our source code with community. So this demo just demonstrates the principles of this data from data gathering to converting this data into sustainability reports. And we can trust this data because this data verified by DLT and blockchain. So each participation platform can trust this data because this is one of the cornstone of lunch in the green finance market. Nobody has verified data. So we don't know about real liquidity of green finance assets in this case. And we seek to solve this problem of providing reliable and trustful data for green finance market. Yeah, and I already created a full request with our ElectroDoc software, but we just need a little more time to pass all the checks from the Hyperledger Labs community. But you need one more minute left. Please ask Rob your questions soon. From the demo, I didn't quite get how uploading and sharing documents died into the presentation we had just before. How can you make this a financial tool? Yeah, you can present one of the examples of assets. This IRX, this one of the type of renewable energy credits, renewable energy certificates. This is one of the examples of green finance assets. So this tradable assets and we provide our platform for storing these IRX certificates. So we can store data about renewable energy generation. We can create a certificate. We can send a certificate for verification from a authorized verification body. And we can share and transfer this certificate to another entity. So we can sell and buy this certificate. It's just one of the examples because we can use a similar approach to managing carbon credits. For example, one of the types of carbon verified units. We can use a similar approach for this case. And finally, we have not enough time. These solutions provide the ability to gather data and convert the data into sustainability reports. In this report, verified by blockchain. Storing based on IPFS protocol. All right, thank you. Thank you, team. And hope your own. Thank you. Up next, we have the team leap. So team leap, if you're on, please start with your presentations. Thank you. Can you go full screen? Yeah, sure. Hello, everyone. So we are team leap. And you can move to the next slide. So we're just going to do a quick introduction of our team. This is our team. We are all based out of India. And the area that we are working on is basically a loyalty exchange program. You can move to the next slide. So one of the problems that we've seen, especially in the travel domain is that as a traveler, you know, there are many, there are too many loyalty programs with travel agencies and headlines. And many of them are not interoperable. The other problem is that because of so many different programs today, if I'm flying from India to UK, and I have a layover of two separate airlines, the rules of the loyalty points being earned that I can redeem with each of the airlines are very different and they're not very interoperable. So another problem with the partners is, for example, with the airlines themselves, is that the rate of redemption from these loyalty programs by these travelers is very low. And it's a very tedious onboarding process for being such a simple loyalty program to earn points by flying. It is actually a very tedious and expensive program for airlines to implement. So as a result for the solution, we want to build a common platform which will become an ecosystem offering where we are basically trying to level the playing field for all airlines to come on to one single platform. And with that one platform, we have a central cryptocurrency through which travelers can earn points and use their points to redeem with any airline or travel agency. The long term view that we have is that we also want to onboard other vendors like the different airports, the food ports within those airports, and then expand the platform to have all sorts of service providers on to there. We can move to the next slide. So the platform actually has two sides to it. One is for the consumer, which is like a traveler for people like you and me who can use the application through a mobile application. And the application will be connected to this platform and because we will have points in our wallet which can be earned through flying with any airline or any travel agency, it can be redeemed also with any other airline or travel agency. And from the partner's perspective, this helps because it becomes very easy for airlines, hotels, travel agencies to be onboarded to such a platform. And they also get the benefit of getting customers from other service providers, other airlines, other hotels. So blockchain actually provides this sort of safe, decentralized, immutable solution which airlines and travel agencies have been looking for for quite some time. I had it over to Nikhil now, we can maybe demo you the product. So you can see the solution architecture that we have been proposing over here. So talking about more on it, like this is the consumer and then it will be basically be and these are the customer profiles, point database, business rule engine, reward leaderboard which will be showcasing the who is actually leading the leaderboard, like who is the most frequent traveler and who is having the maximum point. So we will be showcasing it on reward leaderboard. Then e-commerce site so that we can get some kind of advertisements or some kind of promotions on a platform which will help us to earn more money through it. And we will be storing all the points in a database which we have named it as a point database and all the checks and all which goes is been shown by these all lines over here. So talking more about our solution model. So this is the lead point generator that we have been which will be based on the amount spent on booking like let's say someone is booking for say $10,000 let's say $1,000 and someone is booking for $2,000. So the one who is booking for $2,000 will get an advantage over the one booking for the $1,000 and then there will be a validator who will be checking on the amount that is being spent on the booking. And then finally we'll be updating the wallet balance based on this on the booking amount and this balance could be basically be used at two places. First is flight booking where we can be used for the future flight booking like let's suppose you booked it today and you took up next flight let's say 15 days later. So you can use that point there to get some kind of discount or you can even use it for the hotel booking like let's say you booked the flight right now and you were planning to book a hotel simultaneously. So that points can be used in that hotel booking or in any future hotel booking. So what are the basic benefits of our solution so the most important benefit is that it is the minimum viable product which would be providing the traveler the ability for creation of a traveler digital wallet to hold the points like today we don't have such kind of scheme in travel domain like we don't find something of a sort of travel like let's say frequent travel traveler don't get any advantage over non frequent traveler. So having a digital wallet that will store the travel points will give an advantage to the frequent flyers and also it will promote travel. And it and it will earn airline NFT view that in the wallet like you can also buy the airline NFT and you can also view that in the wallet that we are creating another from the partner side what we are providing is there the ability for airline to register as a partner into the platform and create NFT for the loyalty reward like let's say we can have different airline partners with our leap project. Which can be working like let's say we have Indigo flights and we have SpiceJet so Indigo can be one of the partner and SpiceJet can be another partner. So there can be interchange of the travelers like let's say Indigo someone booked a flight on Indigo and the next time they booked a flight on SpiceJet so they don't get any reward recently like right now but using our product they can get some kind of benefits in their booking and they can get some kind of discount. So what is the basic uniqueness and novelty over here so the most uniqueness is that these are the reasons for the existence that the existing solutions are inadequate like currently there is no travel wallet as such. But we are proposing a travel wallet and every transaction is based on blockchain which will be providing the extra edge of security and everything else considered that the blockchain provides. Another thing is that there is no open source transfer the real time reconciliation process and also there is no integrated platform that travelers can use to consolidate the travel loyalty point. Like the same point like currently there is no integrated platform like if you are booking from one airline and if you go to another airline or even if you book in the same airline so you don't get any kind of advantage. So using these kind of travel loyalty points the loyal travelers can get advantage over the non frequent travelers so now I will be showing you the demo of a project. The cost 1 to airline 1 will do a transaction like contract. We will select a return pass yes for a buyer request but we will remove the coin that the customer has so the customer can actually have 100 coin so all of them will take the airline balance to have been deducted. Since these are not in the bank customer balance which we will use after that they will be going back to the site because the customer will take the cash back and check the account balance. Customer wants account balance that's there. Customer has size coins and get coin size expected. So this is our project and definitely I will do more. So you recently saw that what we have been proposing like a loyalty program wallet. So you saw that when the customer was booking the airline so he was redeeming his lead points and when the transaction was successful the points were basically going to the airline again and the entire thing was based on hyper ledger Iroha and we have used hyper ledger Iroha for implementing this entire project. So talking about that what are our next plans and what we have thought ahead so the growth roadmap which we have targeted for the next month July 2022 that we will be defining a prospective customer list and demo. Explore the partnership opportunities for funding the growth stage and the target for September 2022 is that giving the lead point not only to travel booking but also on other purchase to promote travel like you can be you. Purchasing some kind of food items at the airport or some or you can be using some kind of facilities at the hotel which you have booked so over there we can also use the leap point. Also we will be making an expiry date in the wallet balance like if you are not using let's say like if you are not using the leap point for three months then your wallet will balance will be restored to zero points and you will be persuaded to travel within the three months and we will be giving the more points to people who will be using our wallet frequently so as a promotion to incentivize travel. So with this we come to an end and we are open for any kind of questions thank you. Have you done any market research with travel with. Airplane airplane with airplane agencies that's the wrong words airlines. To see if they're interested in such a global scheme. Yes, so we have done a little bit of research with some of the airlines, some of the major airlines. So today how it works is many airlines form alliances. When it comes to loyalty programs, there is one word alliance that is star alliance. But then again, the redemption levels of these alliances are still low. Considering these airlines are all from different regions. It's not very, you know, homogeneous in terms of the market that they are targeting, which is why we want to level the playing field and have all the alliances all the airlines on just one platform, which can benefit almost all partners as well as travelers. I think that sort of was my question as well in the sense that you are considering the consumer side of it, which is good for the consumer right, but from the service providers side of it like the airline and other service providers. It might be a bit tricky because sometimes they don't like partner with others because they want to have like to encourage people to come to their airline or service providers. That's probably another reason. And also from technical side of it. I didn't catch quite what is stored in the blockchain what when you're doing a transaction say I'm booking a hotel in somewhere what part of this information is stored in the blockchain because there is a privacy concern here also. I don't know all this information in a public network or or even permission network so I know that we are out of time but it's just maybe if you can just quickly in a short and just answer these two questions. Okay, Michael, can you maybe take the technical question. Whenever we are booking any flight or travel or the travel plan or hotel booking so we can collect that data will not be collecting the personal data but just the amount spent on that data will be collected. And that will be stored you in the leave and we will be providing the lead points based on it will not be storing any kind of personal data, so there will be no kind of issue of privacy or any kind of the cyber security lapses which will be there. So talking about the point that you have raised like where the airlines will be ready to accept it or not. So sooner or later they will have to accept our scheme like they, it's not like we are stealing the consumer from it, we are actually promoting travel in a way, like if someone was traveling have planned to travel from other airlines and then he will plan do so, but he will get advantage of using the previous flight so using that we will be creating somewhat of a global space in this airline domain we are not basically stealing the consumer from any airline and giving it because the lead points are based on the amount that is being spent. It is not being we are not giving the facilities like the one flight, one airline will be giving more lead points and the other will be giving less lead points. So I think that I have answered both of your questions. How do you reconcile between airlines or alliances that say I fly Lufthansa constantly and I redeem my flight, I redeem my lead points at American Airlines. How do you reconcile between those? Do you record where the points are from? As I said that whenever you are making a booking, you are getting some kind of points in your own wallet. So we are keeping a track of the amount that is being spent on your travel and so when we are redeeming it, we are redeeming it using the lead points. We are not redeeming it using any other kind of currency and we are using cryptocurrency for redeeming and getting the discount. So we will be talking with airlines to accept our plans and so there will be kind of a global harmony amongst airlines and those airlines which accepts our point, we will be going forward with that. Okay. Thank you. Thank you. Okay. Up next we have the final team for the day, Project Gino Moneta. So, hey, good morning. Good afternoon and good evening for everybody. This is Daniel and Adam. We are Project Gino Moneta. And then Adam should take actually the lead from here. And then I change back to the technical presentation. All right. Hi. Good morning, everybody. I hope you can hear me. Welcome to Hypergeo Challenge 2022. This is Project Gino Moneta. Let's briefly introduce you what our project is about. Let's jump to the next slide. So our project is an open source wholesale cross-border CBDC platform. What does that mean? It's an international interbank central bank digital currency platform, which has the capability to revolutionize international bio transfers and therefore serve hundreds of millions of people around the globe. Let me introduce you to our team. This is Balash Haider, Daniel Sego, Matip Rezovsky and me, Adam Redkesh. So, why is Project Gino Moneta necessary? What is the reason for it? On the next slide and you can see the problems of the current cross-border payment system. So people and both individuals and companies spend hundreds of billions of dollars each year for transactional fees, which can add up to five percent in case of an individual person's transaction. And they happen in a very limited, un-transparent way with very limited operating hours along the high interbank fees and they are running on legacy infrastructure. And what is our solution for that? Project Gino Moneta is a wholesale cross-border CBDC platform which can enable more efficient interbank central banks. And we use typical central bank digital currency use cases, which Daniel will elaborate on later just to mention a few CBDC token insurance and burning balance query and cross-border payment. All right, let's jump to the next slide. So, Project Gino Moneta's solution can execute real near-time cross-border payments with a 50 to 80% reduction in transaction costs in a 24-7 operating manner directly so without any intermediaries from one bank to the other. And it can help to eliminate data fragmentation problems in contrast to the current cross-border payment system. Next slide. Project Gino Moneta is an open source project, so let me tell you why it is better than the current payment marketing infrastructure provided solutions because it is adjustable for every monetary authority's jurisdiction of needs. And this project is backed by both the Ethereum platform and the community and both the hyperledger community through hyperledger-based business to utilize. And at the end, it will be a supervised payment system built on distributed ledger technologies, which is one of the paths to develop transactional technologies on the planet. All right, and let me pass the word to Daniel to introduce you the technical parts and have a short demonstration of our project. So, what we have from a technical side is a simple demonstration that was prepared for this challenge. What we have practically is a four-institute setup. We got like two central banks in our setup and two commercial banks. The two central banks are the Hungarian central bank called Moderna Mzatibong, and the Chinese one that's the People Bank of China, and the two commercial banks are OTP, that's the Hungarian bank, and Alibaba, which is actually not a commercial bank, but as far as I know, having some commercial bank activities as well. So, we got basically a setup. It's for Bezu, Hyperledger, Bezu node running at the institute, and we got basically many use cases. For the first run, we're going to show a very simple cross-border CBDC setup. So, from a user interface perspective, what we have basically is a complete setup for the organizations. So, as you see, basically, we got like administration user interfaces for like central banks that's like for the Hungarian central bank and the People Bank of China. Having a lot of stuff that you can set, basically, most of them are for governance stuff. So, you can basically allow or disallow wireless or backlist each and every account and each and every activity. So, what you got? You got some user interface for the commercial bank side. Here again, we got like a lot of setups, mostly for wireless listing or blacklisting, every kind of activities, which is must in this sector, I would say. And basically, at the end, we got something which is a CBDC balance. So, this is like a CBDC balance, the Hungarian commercial bank OTP having like 7000 CBDC and then basically commercial bank Alibaba having like 3000 CBDC. So, if you need like more CBDC, what you can do basically, let me just change to another account. This is like basically the Hungarian commercial bank side. So, basically, what you have to do for the first one, you have to require CBDC from your central bank. It is carried out with the connection basically of RTGS payment system and as soon as you require some CBDC then basically the central bank can mean to some CBDC. So, that's the use case. I won't show every steps here because of our time limit. But basically, I mean, if you require some CBDC and having some CBDC on your account, then basically what you can do is transfer the CBDC. So, I will show just one transfer. We got like 7000 CBDC on the Hungarian commercial bank side and 3000 on the Alibaba side. So, let me just transfer basically some of it. It looks that way. We use Bezu and basically this demonstration is set up with Metamask, which is certainly a know-how in an institutional environment. So, what we will do basically, we will set up institutional wallet in the next phase. But at the moment for the sake of demonstration, it's running basically just with Metamask. So, theoretically, the transaction is confirmed. So, what we basically should see that we get like 1000 CBDC less on our Hungarian commercial bank side and we got like 1000 CBDC more on the Chinese commercial bank side. So, that was the demo. It's again, it's way more complicated. So, we could like demo one hour as well, having all the functionalities. Just from a technical perspective, again, it's a distributed ledger-based solution. It's built up with Hyperledger Bezu. It's a modular design, fully open source, but not just one use case, but several other use cases as well, including not just CBDC, but like digitized commercial bank money, payment versus payment, payment versus delivery and stuff like that. So, on the roadmap, we set up our first demonstration and during this challenge, we will extend this with further prototype things. So, further prototype use cases like with atomic cross-chain swaps, payment versus delivery, and some foreign exchange functionalities as well. And then basically we plan to have an evaluation phase at the end of the year. We got two tough things from a technical perspective. One is basically privacy and the second one is speed, is efficiency. And privacy going to be the biggest problem, but we have some ideas how we can reconstruct our code that even in the, in terms of privacy requirements, it will be manageable and acceptable as well. And for the next year, we plan some integration phase. It means mostly like integrating with the ISO 2022 standards. So that was actually our presentation and our demo. And yeah, we are happy to take any questions, any comments, any ideas. And as basically this is a fully open source project, we are happy to take any contribution as well. So, given the violence and sort of cryptocurrencies were the first applications of blockchain, where blockchain been introduced by those. And this area has been like lots of works done in this area. So how would you compare your solution with the already existing solutions for the same problem. And what do you think would make yours different from those solutions. It's quite easy if you compare the cryptocurrency solutions to a central bank digital currency solution the it's it's written in the definition the central bank digital currency is a currency, which is governed by a central bank. Cryptocurrencies are governed by a central bank. So they are very good and supervised solutions for international bio transfers, but not, but there aren't a 7 billion people who trust in who have enough trust in cryptocurrency transactions on an international scale. They use commercial bank money and they use central bank money in form of cash and in form of account money. So what we wanted to do is to leapfrog from cash usage from international commercial bank money, the central bank digital currencies. And it's a it's a safer manner to conduct international bio transfers. How would you handle sanctions and anti-bondy laundering rules in your system? Money laundering is conducted by the commercial banks who have nodes in these systems. So, like when you when you initiate an international bio transfer now in the current system, your commercial bank will check if all the necessary AMR or QIC proceedings have been made. So it will be the same commercial bank anti-bondy laundering and the commercial bank and all your pastima processes will happen. And on the other side, the sanctions, you cannot truly avoid sanctions in this system because payment system sanctions are written in decrees shared and written or published by the central banks or the monetary authorities. These systems are governed by monetary authorities. So they will be part of the sanctions themselves. So it's a monetary policy tool as well. And the geopolitical tool. Yeah, but what I mean is, let's take a current example. The central bank of Russia is part of the system. Suddenly, everyone decides that they are no longer allowed to participate, but they do have these tokens that you've created. If you build in a system that there is some kind of a consensus smart contract thingy that determines that they can no longer spend their tokens, did you build that into the token itself or is that something that you are planning for the future? Yeah, so let me answer this question. So, so one of the idea actually is that, yeah, so the token is 100% controlled by the, by the central bank. The central bank is basically so you can, you can buy this and that is each and every account, each and every activity in the token by the central banks authorities. So practically it means, you know, if, if one, one central bank decides that that kind of an activity is not possible, then they can deny deny every and each and every activities practically. So it's totally in the central banks control what they do with the token, who can transact with the token, and, and where can this token be transferred. So it's, I mean the leisure is decentralized, but the logic is, is far from being decentralized. Governance is basically a big issue here. Governance can be pretty complicated and governance exactly describe such such situations that who can control which activity of the network and then so we got we got pretty strong governance policies again each and every activity can be controlled practically by by by by central banks and by monetary authorities. And then yeah, so what is the current history of the project is already piloted with some central banks or it does the right paper. So we don't have actual central bank contribution at the moment. It's it's open source and we are participating in this in this challenge. Yeah, so we will, we will look for partnerships, we will look for partnerships in the next phase as you can see in our roadmap. The, the, the next phase will be in the next phase it will be very important to fight both commercial banks and central bank partners for our project. Just in addition, so actually we get one more use case, which is called digitized commercial bank money, which is a direct contribution between banks basically. So we might not need for that use case actually central banks as well. So one way of, of doing business is like, so like evaluating use cases such use case in then taking a look with which use case can we do, can we do I mean, you know real business first. Any other questions. The last question, it's open source and planning to contribute to the hyper labs. Yeah, absolutely. So it's open source at the moment in my account, but we are planning to, to set up a hyper ledger lab with that and it will be fully I mean it's already fully available but it will be fully available as hyper ledger lab for the whole community. Thanks team, and that concludes our presentations for the day. And I know. Thank you again to all the teams for participating and thank you also all the jury members for evaluating the proposals. We may take one or two more days to accumulate results from all the jury members and select the top teams will be moving to the next round. And for the next round, which is launch phase. So we will also inform additional instructions and in an email. So that concludes the prototype challenge evaluations. Thank you again. Thank you all.