 Hello, everyone. I'm Tatsuya Sato from Hitachi. In this session, I introduce the operations smart contract of SC, which is a smart product-based system operation tool for Hyperlegio Public Based Systems. This of SC got registered as a Hyperlegio Lab of Project in this February. First, I'd like to talk about what is of SC. As a background, a single blockchain-based system is built across multiple organizations, and each organization has a separate kick-admins rating. Our goal is establishing decentralized system operations across multiple organizations for blockchain-based systems. The primary idea is to define a system operational workflow as a smart contract, like this. And each organization operates their own nodes according to the... like this. As a result, J-operations are unified over multiple organizations. We assume that the value of our OSSC is inter-organizational operation, which can be performed without relying on decisions by a specific organization with unified uniform procedure, conformity parameters, effects. Let's move on to the Hyperlegio specific topics. In the current fabric, individual operational tasks, like peer commands, have been refined. And single point of trust is eliminated. For example, with the introduction of new chain code life cycle from version 2.0. However, as a remaining issue, there is room for improvement in end-to-end operational workflows using individual tasks. To improve this issue, J-OxSC for public version 2.0.x aims to enhance negotiation and automation capabilities. J-OxSC has negotiated conformity parameters for operations and executes operations to nodes automatically and decentralized. This scenario... sorry, this slide shows the job view of the current implementation. The implementation consists of three components, OXSC chain code, API server, and agent. Chain code provides functions to manage operational workflows and issue chain code events, including the operational interactions. API server provides less API for each OX admin to interact with the OXSC chain code. Agent for each organization addresses operations based on the chain code event to all nodes for the organization. In the typical use case, later for an organization, first for an operation and then administrators for other organizations, both for the proposal. If a majority of both is collected by each organization, agent for each organization addresses operations to all nodes for the organization based on the chain code event. Currently, the implementation provides a proper specific OXSC which is essential for managing the public network for operating chain code and channels. At the first phase, this slide presents the OXSC for operating chain code. From version 2.0, new chain code life cycle was introduced. The new step for uploading chain code definition from each organization was added. It can eliminate centralized process in deploying chain codes. However, as a remaining issue, it increases operations which are executed by each organization and must use the same parameters. Also, the admins who need to negotiate the source code and parameter with other organizations in the typical case. So, the OXSC is streamlined end-to-end chain code deployment. An organization creates a proposal with chain code source code and definition. As an OXSC, both for the proposal shared on the OXSC. When the majority of both is collected, an automatically deployed chain code is on the proposal with downloading, installing, uploading and committing the chain code. This slide presents OXSC for operating channels. The left part shows process for channel update across multiple organizations. Like adding an organization. In the process, an organization first creates a config.tx to update the channel. And then, as a result, sign the config.tx. So, they need to share the config.tx with the organization. So, the OXSC is streamlined such a channel update across multiple organizations. The sequence is same as the ones for operating channels. And now, I give a demonstration using customized test network in public samples. Just a moment, I'm delivering the demonstration. Okay, the first scenario is adding a chain code. This is the portal screen with interacting OXSC. In this scenario, three organizations of one to three are ready. Each organization admin uses a separated portal for each organization. Now, OV1 create and submit a new proposal to deploy a new chain code via the OXSC. And then, the information is shared on the OXSC chain code. As a next step, OV2 will upload a proposal like this. When the majority of our blue bar is collected, the agent for each organization deploy the chain code to nodes based on the OXSC event. Now, the chain code is installed on the OQs. And now, the chain code is deployed over nodes for all organizations. In summary, OXSC enables decentralized coordination of operational information across multiple organizations. It enables automated and unified chain code deployment. The second scenario is adding a new organization OV4. And as an initial state, the three organizations of one to three are ready. To add OV4, first, OV4 issue key and certificate for their nodes by using their share outside of OXSC. Then, OV4 send MSP information including certificate to OV1. Next, OV1 will create a proposal to add OV4 to system channel by using MSP information for OV4. Now, OV1 is creating the proposal and now OV1 submit it. Next, OV2 upload it. So now, agent update the channel state. Now, the organization are repeating for other application channels. Let me skip the steps. After that, OV1 fetch the system content block and send it to OV4. And OV4 launches their nodes using the content block. Now, OV4 is ready on the portal. Also, you can see existing channels are deployed on OV4 peer by the OXSC. Let's go back to the slide. Okay, here is the roadmap for OXSC as a kind of time. We have planned to include the quality of existing features and also to develop new features for general purpose operations. Which enables to execute arbitrary command via OXSC chain code. Also, we aimed to get the part of functionality of OXSC merged in Hyperlink public in the future. Now, OXSC is available on this report. And we welcome your feedback and contribution. Please feel free to contact us on the RocketChap channel or email. And as a related presentation, Toto from Oracle will be giving a presentation with this title. If you are interested, please check also his presentation. And finally, let me check the question from the audience. Okay, there are no questions so far. Okay, that's all my presentation. Thank you for coming.