toggle quoted messageShow quoted text
Thank you for your explanation. I now understand it clearly.
But this would cost huge efforts to maintain private data collections in production environment if there are hundreds of private data collections.
How about pre-define a regulator or auditor, the private data collection will include this pre-defined regulator or auditor in the collection configuration period. So we don’t need to define every private data collection to include it. It will
be automatically included in every private data collection. That would be more simple and useful for massive private data collection configuration in production environment.
On Feb 4, 2020, at 1:54 PM, David Enyeart <enyeart@...
A regulator or auditor would be modeled as any other organization.
Example: Channel includes four organizations: 'Org1', 'Org2', 'Org3', 'regulator'.
Create Org1Collection that includes (Org1, regulator) in the private data distribution "policy" and "endorsementPolicy".
Create Org2Collection that includes (Org2, regulator) in the private data distribution "policy" and "endorsementPolcy".
Create Org3Collection that includes (Org3, regulator) in the private data distribution "policy" and "endorsementPolcy".
Org1Collection would have properties as:
"policy": "OR('Org1.peer', 'regulator.peer')"
"signaturePolicy": "AND('Org1.peer', 'regulator.peer')"
This implies that any private data written to Org1Collection requires endorsement from a 'Org1' peer AND a 'regulator' peer. And the private data will get distributed to any peer belonging to 'Org1' OR 'regulator'.
See collection definition doc at
<graycol.gif>"胡 银松" ---02/03/2020 11:55:26 PM---Hi All, The fabric doc said: “Fabric v2.0 also enables new patterns for working with and sharing
From: "胡 银松" <huyinsong@...>
To: "fabric@..." <fabric@...>
Date: 02/03/2020 11:55 PM
Subject: [EXTERNAL] [Hyperledger Fabric] How to set regulator or auditor in private data collection
Sent by: fabric@...
The fabric doc said: “Fabric v2.0 also enables new patterns for working with and sharing private data, without the requirement of creating private data collections for all combinations of channel members
that may want to transact. Specifically, instead of sharing private data within a collection of multiple members, you may want to share private data across collections, where each collection may include a single organization, or perhaps a single organization
along with a regulator or auditor
I wonder how to set regulator or auditor along with a single organization when using private data in Fabric 2.0?
Is there any sample to tell how to do this?