Introduction Endorsement policy controls the approval of a proposal to be executed at various granular levels. In other words, this is the primary entity which is validated before a transaction is committed. Endorsement policy can operate at two different granularities: Namespace level: They can be set for the whole namespace. This is the default approach in which endorsement policies are specified in the chaincode definition, which is agreed to by channel members and then committed to a channel Individual key level: They can be set for individual state keys called private data collections. You can also specify an endorsement policy at the private data collection level, which would override the chaincode level endorsement policy for any keys in the private data collection. This would further restrict which organizations can write to a private data collection. Problem Statement This becomes complex to handle when operating at scale. Some use cases 1. Complex endorsement policy resolving for namespace level ones 2. Tracking Endorsement policies on large quantity Private data collections each having different endorsement policies 3. Resolving policy for a given object combining namespace level with overriding individual key-level ones.
No project history available for this organization.
Counts are based on projects listed in the Contribo catalog.
Showing 1 of 1 projects. Click any project card for scope, mentors, and proposal studio.
Introduction Endorsement policy controls the approval of a proposal to be executed at various granular levels. In other words, this is the primary entity which is validated before a transaction is committed. Endorsement policy can operate at two different granularities: Namespace level: They can be set for the whole namespace. This is the default approach in which endorsement policies are specified in the chaincode definition, which is agreed to by channel members and then committed to a channel Individual key level: They can be set for individual state keys called private data collections. You can also specify an endorsement policy at the private data collection level, which would override the chaincode level endorsement policy for any keys in the private data collection. This would further restrict which organizations can write to a private data collection. Problem Statement This becomes complex to handle when operating at scale. Some use cases 1. Complex endorsement policy resolving for namespace level ones 2. Tracking Endorsement policies on large quantity Private data collections each having different endorsement policies 3. Resolving policy for a given object combining namespace level with overriding individual key-level ones.