 So let's start and greetings to all of you and welcome to Hyperledger Global Forum. I am Pratipa Muthi, a software engineer working with Intel for the past 9 years. And I have my colleague Manjunath and he is also working for the past 10 years. We have been working towards applying blockchain on enterprises for the last 3 years. So today we are here to present Hyperledger Evlon. Hyperledger Evlon was solely developed by Intel and Intel was the primary maintainer of Evlon. But in the recent quarter, the leading global company BitPro has been made as the maintainer of Evlon. So Manjunath will take over to the rest of the slides. Over to you Manjunath. Thank you, Kartika. Can you, yes. Okay, let's look at what is Hyperledger Evlon. I guess if you are a newcomer or newbie to Evlon, let's just see what is Evlon and how it started. So initially, all the blockchain frameworks, when they execute a computationally intensive transactions or workloads, they have to process the transaction. This was leading to a lot of resource crunch and it was impacting on the performance a lot. And also there was a privacy concern issues when there are multiple parties participating in the consortium. So to address this main issue, Enterprise Ethereum Alliance initially started to develop a spec to solve these issues. Initially it was only the Ethereum was in mind and then later the spec got evolved and it was made generic so that even the solution can be adopted to even non-ledger solutions as well. So that is how Hyperledger Evlon got started and its ledger independent implementation of the trusted compute spec developed by Enterprise Ethereum Alliance. And currently in Evlon we have integrated Hyperledger Fabric and Hyperledger... So the main goal of Evlon would be the data security while performing computation of data. So Evlon offloads the transaction to a centralized entity called trusted compute. So we enable input, throughput and scalability. And I would also like to mention that Evlon provides a tested auditors, tested reports of the data generated outside of the property. So this way we trust that the trust is definite between known clients and our users. So the sponsors, so talking about the sponsors we have Intel, IBM, Microsoft, Alibaba, Baidu. And we have already published the open source and told before that Vipro is the current maintenance of the Evlon. Let us talk about a small business case which is using have-none for providing the data security. So now consider a small-scale business which is interested in a medical insurance coverage for its employees and want to protect the confidential health data of the employees involved. An insurance company can provide a required code but it depends upon the hospitals for the user data which in turn is encrypted as the hospital policy. So the hospital, insurance company and a small-scale business cannot be trusted in each other with the data security. So this is where Hyperledger is known as basic hero, providing a secure channel for a small-scale business to meet the requirement in an unrestrained environment. Manju, you want to talk about the use case? I mean I have just given an overview about the use case. Manju, I think it is still not good. So the hospital encrypts the data. So initially the hospital encrypts the data which can be encrypted only inside the exchange. So such an encrypted data is only passed to the insurance company on request and in agreement with the enterprises. So you can see in this way the data influence data health data which is considered to be very confidential. It still stays confidential because it can be decrypted only within an input. And such data is passed to the insurance company. An insurance company also tries to apply its algorithm over it but all this execution happens within another Intel SGX on click. So what we see is as an outsider the data is never disclosed because the data is always encrypted for an outsider and the insurance company can also give a quote about the health details or anything as per the enterprises asked. So this way we find that the hospital insurance company and the business are trusting each other. Basically I mean trust based execution is established. So going forward to the next slide. So this is a demo of the hard case valuation. It is something like the insurance company itself. And Manju you are online now can you hear? Yes I can hear you. You can continue with this demo. Okay let us look at the business use case of Avalon here. As you can see there are three entities. One is a business. It could be a corporate company and insurance company and the hospital. Manju I think I have covered that. Maybe we have to talk about the demo of the hard risk valuation. Sure. Can you move to that particular slide? Yeah I am already pointing to that. Okay I am seeing the use case demo. Just go back and come back again. Hi there. You can see from the point of which slide are you seeing? Is it the demo slide or the use case slide? Okay no issues. I can talk about it one second. Yes okay so as Kartika was giving the introduction about the business use case. This demo is a hard disease evaluation example that is provided as a reference implementation in the Avalon code. What you see in the left hand corner is a UI client at the client side where you can input all your employee health data like your age or blood sugar it could be cholesterol. All those parameters could be entered in the UI client. When you submit all the data all the patient's data is encrypted and it will be sent to the Avalon framework. Only in the place where you deploy the Avalon the trusted execution environment implemented using Intel SGX it will be able to decrypt the result and the algorithm which will basically apply some logic on these parameters and it can come up with evaluation what is the probability of getting a hard disease from this patient data. At the top right corner you can also see that in the response all the data is also again encrypted and the client will have the corresponding encryption key. It can use the encryption key and it could decrypt the result and at the end it can view the result. You can see you have 45% risk of hard diseases. This demonstrates the end-to-end confidentiality from the moment the client submits a request till it gets the response the whole cycle the request and response are encrypted and it is only authorized entities can view the results. Can you move to the next slide please? Coming up is what are the latest developments that we have done? From the past few quarters what we have done is we have segregated the key management responsibility and the work order processing logic into a two separate processes. We call it as a key management enclave and the work order processing enclave. This will enable us to achieve greater scalability so that we can intake multiple requests at a time and all this will be processed by a set of work order processing enclaves. We are also coming up with key management enclave replication technologies. It is in the pipeline and recently we have integrated graphene library OS to the Avalon. What graphene does is in the traditional Avalon it only supports C++ based workloads to be integrated with the TE but what if we want to run the existing already developed existing applications inside the trusted execution element and graphene provides the support and we have provided the integration of graphene and also we have provided a support for receipt handling in the direct mode and till now we used to support only Docker based deployments and right now we are supporting Kubernetes based deployment is also available and also we have support for engine X based load balancer for basically handling multiple requests coming in from the different different clients. It will be correspondingly it will be redirected to different listeners and correspondingly it gets processed. So these are the some of the key highlights of recent developments that we have done and moving on or is it more. So we can see some of the references to Avalon here. Basically the open source repository is available in the GitHub and all the contributions to open source is accepted. Take a look at the source code and if you would like to contribute we welcome you to contribute and we can also see the project proposal here and we have a good number of blogs and the in the previous slide I evaluation demo a screenshot and this is the YouTube video which will demonstrate any demonstration of heart disease evaluation and we have a wiki for Avalon as well and we conduct a monthly once developer forum please feel free to join and that brings us to the end of the project demo. So if you have any questions please let us know. Also you could contact us if you have questions maybe we can you know take those questions offline as well and so currently Avalon implements trusted execution environment using interless checks hardware technology. There are other alternatives to it. One is it the same spec can be implemented using AMD based trust zone or you can you you can completely use a software based trusted execution environment like I know zero knowledge pro for multi-party compute the spec is open for all this flexibility. No questions. Thank you everyone. Thank you everyone for joining the session. It was pleasure having this pleasure presenting the session at High Collegial Global Forum. Thank you. Bye.