Hyperledger Foundation Hyperledger Global Forum 2022, 6 Oct 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Toward Fully-Decentralized System With Hyperledger Fabric... - Tatsya Sato

Description

Toward Fully-Decentralized System With Hyperledger Fabric - Requirement Analysis of Decentralized System Configuration/Operations and Potential Use of a Decentralized Operations Tool “OpsSC” - Tatsuya Sato, Hitachi, Ltd.

A system using Hyperledger Fabric (Hyperledger Fabric-based system) provides the value of executing transactions inter multiple organizations in a decentralized manner. To maximize this value, it is essential to maintain decentralization not only in the execution system but also in the entire system, including system configuration and management. On the other hand, Hyperledger Fabric is still in the process of maturing and full-decentralization is still difficult to achieve (e.g., ops with a single centralized script as a bad practice). The lack of clarity on how to achieve this may be a disincentive for production uses of Hyperledger Fabric. So, Tatsuya tries to analyze comprehensive basic requirements for realizing fully-decentralized Hyperledger Fabric-based systems and design a reference architecture to satisfy the requirements. In addition, he also lists various types of system management workflows (e.g., BC network ops) to which the requirements would potentially apply, and then demonstrates the applicability of "OpsSC" which is a decentralized system operation tool for Hyperledger Fabric and is registered as a Labs project (https://github.com/hyperledger-labs/fabric-opssc).

Sessions Details & Slides (if available): https://sched.co/14H4o
Access All Sessions: https://events.linuxfoundation.org/hyperledger-global-forum/program/schedule/
----
Hyperledger – Open Source Blockchain Technologies

Hyperledger is an open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments.
It serves as a neutral home for various distributed ledger frameworks including Hyperledger Besu, Fabric, Sawtooth, Indy, as well as tools like Hyperledger Avalon, Cactus and libraries like Hyperledger Aries, Ursa. Learn more about Hyperledger projects: https://www.hyperledger.org/use

Discord: https://discord.gg/rVCn4j7UFd
Case Studies: https://www.hyperledger.org/learn/case-studies
Training & Certification: https://www.hyperledger.org/learn/training
Tutorials: https://www.hyperledger.org/use/tutorials
Webinars: https://www.hyperledger.org/learn/webinars
Events: https://www.hyperledger.org/events
Vendor Directory: https://www.hyperledger.org/use/vendor-directory

Subscribe to the Hyperledger Newsletter: https://www.hyperledger.org/newsletter

Follow-us on Twitter @Hyperledger

Learn about Hyperledger Membership: https://www.hyperledger.org/about/join

#Hyperledger #Blockchain
License
Creative Commons Attribution license (reuse allowed)

A

Hello: everyone hirachi today I'd like to talk about 12, free decentralized system with hyperledger fabric requirement, analysis of decentralized system configuration and operation and potential use of a decentralized system. Operation. 2 of C here is an introduction to this presentation.

A

This presentation Target system using hypology fabric here after we call hyperledger fabric just fabric and also we call a system using public habit-based system.

A

Okay fabric basic system provides the value of executing across multiple organization in a decentralized manner, to maximize the value. It is essential to decentralization not only in the execution system, but also the entire system, including system configuration and management.

A

However, there are gaps between them and it may be at this incentive for production use so in this presentation to add three decentralized fabric basis system. First, we try to analyze comprehensive basic requirement for realizing foreign public Business Systems and design a reference architecture to satisfy the requirement.

A

And then we will demonstrate the applicability of obsession which is a decentralized system, operation 2 throughout achieving some of the requirements on management perspective.

A

Okay: first, let's briefly review a public-based systems.

A

This slide explains the execution system of public based system, and here is an overview of a fabric based system.

A

So each organization from a plus domain in fabric, in other words organization, is unit with participant Independence, also of long version. 1 fabric introduces Execute Order, valid architecture which enables conduction across multiple organization, with increasing scalability in this architecture fabric separate the trust model into two parts. The first one is ordering service and second one is transaction validation, so trust model for ordering depends on communication. Protocol and Trust model for transaction variation depends on endorsement policy.

A

Next: let's explain about management, side of fabric based system, our fabric managers chain code, which are fabric smart contract and razor for each Channel, which is fabric subnetwork.

A

This video shows an example of a fabric based system with a small management part, and it's only in the figure in public can update the configuration by the combination of public Cris subcommand executed by each organization, and it needs to coordinate across multiple organization with config parameters like chain code definition, internally, public issues or special transactions and store the configuration on chain.

A

So typical steps to update the config here.

A

Okay, then, let's discuss about plus model design in public based systems.

A

So the level of decentralization required for fabric based systems depends on assumed, plus model and configuration in the past. The main focus on having a known enduring decentralization in execution system. Mainly this part, but in secret rust model decentralization in the management system becomes also important. Guess what now? Let's consider about some trust model, as example.

A

First first case of Consortium is here in this Consortium transaction participant and not trust trustable, each other. This is better to be achieved and the Consortium has a single console, Channel owner, which will have their Consortium in this case. If the owner does not participate in the transactions as a participants can trust the owner, because owner has no interest on transactions in this case centralized to management by owner like this, who do not be problem, then, because owner has no interest on transaction.

A

The second second case. On the other hand, the the Consortium owner also participate in the transactions in this case, as a participants does don't fully class Chic owner in this case, for management side. If uh centralized management by owner is executed, the owner can control the blockchain network to its advantage.

A

So such centralized management would not be acceptable in this case, so in stick up a trust model. One of the challenges is that uh cannot be completely decentralized, including management.

A

Okay, next topic is related work.

A

To find some activities that focus on certain aspects of based, blockchain based system and mentioned, enduring decentralization.

A

However, there are no lack systematically organized requirement to achieve decentralized or permissioned blockchain or fabric, so our motivation is to know comprehensive requirement for realizing fully decentralized public based system.

A

In this part, we try to consider a basically comment and reference architecture of fully decentralized fabric-based systems.

A

We extracted the four basic requirement for decentralized fabric based systems based on both related work and our experiences findings. We categorized statement and important description in related work and Consolidated them as a basic requirement.

A

The perspectives of database predicament are following. I will explain the perspective one by one in subsequence right.

A

A

The perspective perspective is a ye identity, that is, uh ideas to identify participant and node in the blockchain network, and method of managing them require requirement. For the perspective is that unit of stakeholder business individual should have an independent little Trust.

A

And our left part shows typical case of Intel companies so and fabric Shear Acts. This is one important point and F0 is a conflict of interest regarding transaction. The CL should be separated between companies like this.

A

And people right shows another case that stakeholders are individual and a single owner of the Consortium at the back practice. If the owner issue, ideas for all users see endorsement on the Consortium main makes no sense, because the endorsement is a executed by Shin Guru organization.

A

So, as with process, each user should be considered an organization and has its own Shia.

A

Second perspective is a transaction execution, and that is execution and management method over the blockchain network.

A

A requirement for the perspective is that all transaction should be processed by achieving a current number of organization with identical result in each organization.

A

So, as shown in a figure fabric based system should have proper endorsement policy settings uh and chain code design, including private editor and ordering communication protocol with avoiding single point of glass parts.

A

Okay status management and governance, that is, management of the blockchain network and our governance of Consortium.

A

The requirement for the this aspect is that the management and operation related to the Consortium should be decided performed by multiple organization and the processes and the operational history should be transparent.

A

Shows but practice so, as shown in the figure, intelonization or operation is decided performed by shingle organization of one in a centralized manner with centralized script so as good practice into organizational operations should be performed by each organization's. Admin and configure parameters should be coordinated among organization also. It needs to endure transparency of coordination process, coordination process and operational history.

A

So the last perspective is system configuration that is configuration of the blockchain network and blockchain based system.

A

So a requirement for the first effective is that on the configuration must be such that bigger on The Ledger cannot be changed without the agreement. Multiple organization to do this, or the configuration must be considered on ownership and management setting to mitigate and authorized data modification, for example like this, and also the system, must be verifiable and detectable in case of unauthorized data modification, for example, always comparing a ledger.

A

Next, oh, we try to consider a different architecture.

A

The goal here is to elaborate on a specific architecture of 3D decentralized public based system. However, the basic requirement to abstract to consider reference architecture directory.

A

So first we try to specify the requirement from the architecture perspective and then we design a refinance architecture with specified requirements.

A

This is a list of specific requirements.

A

So each specific requirement corresponds to basically requirement and public components and uh so specific requirement. I'll take it with oh geez labels, the public means or special functionality. That fabric should have a blockchain platform and uh rub your mission. Is mechanism currently Mission from official release, functions.

A

This is the overview of a reference architecture to satisfy specific requirements, so she can just write her explain on the specific requirement, part by part.

A

This right explain the baseball of transaction execution system, ID and system configuration and during decentralization of the execution system required to provide system design and configuration spot single point of the last on the transaction. Processing must be emanated so.

A

So to do GS offense each oath has its own independent, shear and also the blockchain network has a PFT ordering service.

A

We will discuss about the requirement rate again and furthermore, each chain could have the endorsement policy setting including private data, to get agreement from enough organizations peers for bfdancing for tutorial, and each organization should have its own API server to submit transaction to fabric Network by examples.

A

For system configuration it must be, this must avoid a single organization or administrator becoming single point of trust. To do this, each component especially feels on others here, is not owned or managed by a single organization.

A

Yes, right shows and accomplished requirement with Associated Community activities. Mechanisms for achieving some requirements are missing, but some are being proposed developed in the community and will enable them to be achieved in this in the future.

A

The first one is for BFD ordering in the Consortium with low Mutual Trust ordering should also have Beauty, but it's not supported as a version 2.5. So this is uh the next release version of public.

A

uh Of course, Consortium has recognized the realization of bft order as a top priority for version 3, Series and specific feature proposal and development in progress.

A

A

As another requirement, the system should be able to verify the depth data cloud. That fabric itself does not take a detect data cloud, so the system needs to check data Integrity of blocks transaction State. Later the following. Two tools can be used to achieve this.

A

First one is blockchain verifier, which is a project in hypology levels, and this is a tool to verify the Integrity of blocks and transactions and the blockchain verifier already supported fabric.

A

Laser utility is a fabric command to identify potential Divergent transaction among snapshot. It will be available from version 2.5.

A

Okay, yes, right, discuss the perspective of management and governance.

A

As a requirement system should have a mechanism mechanism, we have a complete values: config changes for the Consortium at determined by multiple organization, as shown in previous slide.

A

Config values on the blockchain network, especially Channel chain code, can be managed on chain without, depending on a specific organization by using public GLI. So the mechanism is in place and needs to be used properly.

A

We need to remember that other configs on the construction are handled offline and as a as another requirement, the system has a mechanism of cross-organizational operations management workflow.

A

It should should have a capability of across organizational coordination and execution, and it should have transparency of operational process and operational history, but the fabric does not support such and to the end operational workflow, so coordination and execution must be done offline and it is difficult to endure transparency process history of chain, so management tool to streamline them would be required to have satisfying the above requirements. We are expecting the possibility use of obsession.

A

From here, I'd like to discuss about potential use of of CSG, yes, sir I want to talk about what is oxusg of CSG is Operation smart contract, which we proposed, and the goal is to establish a decentralized system management across multiple organization, and the primary idea is to define a system operational workflow as a smart contract like this and each organization, a domain or agent program, something like that operates their own nodes according to the slot contract.

A

As a result, G operations are unified over multiple organization.

A

The value of obsession is that inter-organization operation can be performed without designing known decision by a specific organization with uniform procedure, configure parameters efficiently.

A

We have implemented an obsession for hyperledger fabric version, 2.x and G implementation is registered as a hypology levels project in 2020..

A

The purpose is to streamline and to end operations workflow using the individual tasks like Fabric or Cris subcommand, and the first phase as a fast phase. The implementation provides oxygi for managing the public network, especially for operating chain code and channels.

A

And you have to shows a typical blockchain operation in fabric version 2. in version 2, only individual tasks can be executed in decentralized manner.

A

So the perspective of endo2 and operations organization organizations needed to share, adjust, configure parameters of chain, and then each organization executes the command with adjusted parameter manually.

A

On the other hand, obviously in office G and to end operations can be executed in a decentralized manner, so uh organizations can share, adjust the config parameters on chain, especially on obsession changles, and then each organization's agent automatically execute the command based on the proposal on.

A

Chain called sorry officiency chain code.

A

Just write presents accessg for breaking chain code.

A

New j-code rice cycle is introduced in fabric version 2.. The new step for uploading chain code definition by each organization is addict and it can eliminate centralized process in deploying chain code. However, as a remaining issue, it increases operations which are executed by each organization and must be not to use the same parameters also.

A

It needs to share and negotiate a source code of a chain called source code and config parameters like chain code definition with other organization in typical case Obsession for operating with chain code, streamline such endo2 and change of deployment in ethical use case. An organization create a proposal with a chain called source code and chain code definition, and then other organizations fought for the proposal shared on the offset sheet.

A

When the majority of bodies collected each agent automatically deploying the chain code based on the proposal, always downloading installing approving and committing chain code.

A

And of the sheet this slide shows official operating Channel in the left shows processes for channel update across multiple organization like adding an organization.

A

In this physical process of one, an organization create a configure PX to update config EX.

A

Then an organization sent to the compute ex to node to update the channel channel confuse so as shown in the figure as a remaining issue, it needs to share computer ex with each other organization.

A

General update across much organization, the chickens is the same as plants for operating chain code.

A

Okay, now I give a demonstration using a customized test Network in for fabric samples.

A

A

This is a scenario for deploying a new chain code, and their ideas is a portal screen is interlocking of the sheet, and in this case there are three organization of one two. Three and each OS admin uses separates photo executed by ah sorry uh separated photo for each organization.

A

A

No! No! No! No! No! No! No! No! No! No! No! No! No! No! No! No! No! No! No! No! No! No.

A

Okay, now again created and submit the proposal to deploy new chain code, and then the proposal is shared on Obsession chain code and then the chain code notifies the information to other organization.

A

Next, the OG 2 uploads The Proposal, when the majority of approval is collected or each agent for each organization deploys to the proposal chain code to all nodes for each organization based on the offset sheet now on. Each agent for each organization is deploying the chain code and now chain code is deployed over all nodes for all organization.

A

So, in summary, Obsession enables, in this case decentralized uh coordination of operational information across organizations, and it enables automated unified or change of deployment. Okay, let's go back to the slide.

A

Oh okay, uh current implementation of obviously only focuses on a channel chain, coil management, but we expect that the accessory concept of defining operational workflow as a smart contract has potential for application to other management processes. I think this is our future work.

A

Okay, uh let's summarize my presentation to add, through a decentralized um hyperledger fabric, piece of systems, not only execution system, but also management and system configuration.

A

We try to analyze, uh comprehensive for basically comment and design or refinance architecture to satisfy the requirement uh FP of the ordering order is implemented in version 3 Series. We, it will be ready as a blockchain platform to satisfy the requirement and we will demo, we demonstrated the applicability of of the C.

A

The goal is to establish decentralized system operations across multiple organizations, and the primary idea is to define a system operation as a smart contract in the current implementation, support, endo2 and operational workflow on a chain code and channel management and I'm going to expand the scope of a type of management in the future. Okay, that's all my presentation. Thank you.

B

What you are trying to do is to streamline the out-of-bound communication yeah like exchanging Channel configuration, yeah use the pre-existing fabric infrastructure that yes, different organizations change this information that currently is done out of ground. So consequently, you only need to bootstrap yourself at once in the network and then being part of the channel where the operate operations chain code is installed, and then you blockchain itself for communicating the of course yeah right.

A

Yes, that's right so endo2 and uh uh Intel organizational and the two and uh workflow is our scope.

A

C

Do you support the current features that exists in 2.4, whereby you don't have to use the system channel so.

A

C

Work with that capability.

A

Currently, uh the implementation support version 2.4, but uh with system system tunnel. So but we are going to implement uh without version without system channels.

C

You should simplify things right.

A

Yes, yeah it's our older or OSN admin. This is one of uh nearest to future work. Yeah sounds good. Thank you.

B

How long do you think.

A

I'm, sorry I'm not sure it's just watching the how's, your event activity on the community in the outside of yeah.

A

It depends on decision of community.

C

And how ready is the Ops see as far as like? Can we start using it for production deployments, or is it still in development or what's the status? How would you rate it in terms of production, Readiness.

A

uh Actually, I'm not sure, of course, I try to apply the production, uh but uh not yet, and this implementation is open sourced and somewhere eventually use all this in production, but I'm not sure and the production use is our one of future work.

B

I mean I would assume that the general workflow of the hyper electric Foundation would apply so right now it's in love. We have.

C

To go through incubation and then become the same official being.

C

Yeah, thank you.

A

Anything here: okay, okay, thank you very much.