 I'm Koush Ikegawa from Hitachi Research and Development Group at Japan. This is my first time to participate in HyperAger Global Forum. Today, I would like to talk about trust data sharing and utilization infrastructure for sensitive data using HyperAger Avalon. This is the table of contents for this presentation. Introduction. Demand for trust data sharing and utilization is increasing around the world. The concept of data-free flow with trust called DFFT was proposed at the World Economic Forum 2019. One of the focus points of DFFT is cross-border data flows such as across countries or across industries. Blockchain is required to realize cross-border data flows. There are many types of data to share such as many types of open data and many types of sensitive data. Our focus point is healthcare data. Background. We introduced our use case. We created an infrastructure to manage and utilize genome data in multiple organizations and have confirmed proof of consent. In this use case, multiple organizations are participating in a blockchain network for genome data sharing. A focus point, low genome data must not be passed on to other organizations because the data is sensitive data. Therefore, analyze the data on the processor of the data owner organization and pass only the result of the organization. This figure is an overview of the proof of concept we conducted. First, patients agree to use data and provides the data. Organization BDoctor stores genome data in genome data storage. Organization ADoctor requests utilization of genome data owned by Organization B. Organization B's data processor rules specified genome data and return results. Our motivation is to realize trust data sharing and utilization infrastructure for sensitive data. To realize the infrastructure, personal information such as genome data must be handled with particular care in accordance with the law. We focus on the following three points of trust. One, trust encryption. Two, trust processing. Three, trust data load. Here, we decided to use Hyperlature Avalon. Hyperlature Avalon can enable to trust encryption and trust processing. Oh, sorry. Can you see my screen? Yes, we see. I can. Okay, thank you. Okay, next. We will give a brief introduction to what Hyperlature Avalon is. Avalon is a Hyperlature project to realize off-chain trusted computing. In contrast to calling the smart contracts and data on the blockchain, the on-chain. We lead the area outside the blockchain at the off-chain. Avalon guarantees a trust execution of a program in the protected area by a CPU-native secure function called trusted execution environment. We will give a brief introduction to what a trusted execution environment is. A trusted execution environment is a CPU security function that guarantees a protected area in memory and loads programs and data into the memory. Enabling programs to be executed while protecting sensitive data. This technology provided by CPU vendors such as Intel, ARM, and AMD. In Hyperlature Avalon, Intel SGX is for implementation. This is the focus point of this presentation. We enable a trust infrastructure by enabling trust data loads. This design and approach. To enable trust data loads, we should solve this issue. That is the infrastructure enabled to verify the correctness of data on genome data storage. When the doctor in organization A requests organization B to analyze the genome data, organization A doctor cannot know if the specified genome data is loaded correctly. To solve this issue, the data when it is loaded into an area protected by Avalon. First, organization B doctor stores genome data. At the same time, the doctor writes genome metadata to the blockchain. The metadata here includes the name of the data, ownership information, and the hash value of the genome data. Organization A doctor refers to the genome metadata and research for data that he wants to utilize. If the doctor finds that if the doctor finds that the doctor wants to utilize, the doctor writes a request to the data owner in the blockchain for access rights. Organization B doctor is a request for access rights, and if the doctor approves the doctor writes the information to the blockchain. If organization A doctor gets the access rights, the doctor requests organization B to analyze the genome data. Once the analysis is requested, check to see if the requester has access rights to that genome data in the chain code. If the requester's access rights are confirmed, write the past information of the request to the ledger. The written request is read and start processing within Avalon project area of organization B. The processor loads the specified genome data from the genome data storage. The next step is to calculate the hash value of the loaded genome data. The next step is to obtain the hash value from the metadata that has been written to the blockchain ledger in advance. The processor compares the computed hash value with the hash value maintained in the metadata ledger and performs verification. The processor performs the verification and if the hash value varies much, it performs the passing process and writes the results to the blockchain. By using Avalon and implementing our approach, we can realize a trustworthy data utilization infrastructure. We introduce our work in progress. We think we can further improve our infrastructure. In the current implementation, only task management using Avalon is encrypted, but metadata management and access rights management is not encrypted. Metadata is not needed for encrypting because the data is shared information, but access management data should be encrypted. We think about who requested access should be kept confidential. We are trying to use Hyperlature Fabric Private Chain Code. Hyperlature Fabric Private Chain Code enables the execution of chain codes using trusted execution environment. We think that the combination of Avalon and Hyperlature Fabric Private Chain Code can make both on chain and off chain more trustworthy. We have started trying to use the Fabric Private Chain Code and contact FPC community and contribute to FPC summary. We introduce one of implementation to realize a trusted infrastructure for sharing and utilization sensitive data. With Avalon and our approach, we have made the following three points into a trust. We are trying to use Hyperlature Fabric Private Chain Code to make both on chain and off chain more trustworthy. Thank you for listening. This is end of presentation. Thank you. Okay. Check. Q&A. Hi, Mark Assan. Thank you for your question. First question. Is there some access control for the GNOME data also enforced by the blockchain or the Avalon worker? Now implementation. Wait, this right. Now implementation, GNOME data access rights control is used only by train fabric, train hyperlature fabric. This is answer that we don't use access control. We don't use Avalon for access control. Mark Assan's second question is the process to agree on the GNOME analysis code that is executed with Avalon. Okay. Okay. Firstly, access control, organization BDoctor approved access rights for organization A is done. Next, organization ADoctor request analyze task. For this request, use Avalon. Doctor A request and share task information all of its Avalon protected area query this task information. Next, load data and validate hash value. Analyze its automatic query. Is that answer. If you want to more detail answer, I will answer. Rocket chat. Thank you, Mark Assan. Our next question. Oliver Assan's question is, I did not get the part how you securely transfer GNOME data from B to A. Okay. In this implementation, organization B do not share low GNOME data. Organization B share only analysis result data. Because organization B want not share low GNOME data use case in this use case. Any other question? Oliver Assan, thank you. So is then the intention demand from Doctor A. Okay. Doctor A want to analyze GNOME data. Doctor A want only analyze analysis results. For example, in GNOME domain, Doctor A want. For example, cancer GNOME in use case, cancer GNOME analysis. In cancer GNOME analysis use case. Doctor A want to know only GNOME chromosome of GNOME. Where is chromosome of GNOME? So Doctor A want, don't want to allow GNOME data. Okay. Oliver Assan, thank you. Any other question? Any other question? Okay. Okay. I will finish this session. I'm sorry, my mistake. It's all not good. Thank you very much for share my presentation. Thank you.