Create a Consensus Policy

The consensus policy allows for customizable consensus rules, where chaincode deployment can be endorsed by a subset of channel members instead of requiring agreement from the entire network. This flexibility enhances performance and scalability, making Spydra platform suitable for various use cases.

Chaincode Consensus

Chaincode consensus policy dictates when chaincode-related activities like deployment and upgrades can occur within a channel.

Default Consensus Policy

In the default consensus policy, all organizations in the channel receive approval requests for chaincode activities such as deployment and upgrade. Consensus is reached when the majority of organizations approve the request.

Once the majority is met, the chain code deployment will continue till its deployed in the channel.

Define Consensus Policy

Users have the flexibility to customize the default chaincode consensus policy. Select which organizations will receive approval requests and define the conditions under which consensus is achieved. To define consensus policy:

• Select organisations which can endorse

  • Any organisation can be have the endorsement rights, be it admin, contributor or reader.

• Select when the consensus is met

  • All the selected organisations should endorse

  • Majority of the selected organisations should endorse

  • At least one of the selected organisation should endorse the request

Accepting Consensus Request

Organizations can also view the summary and status of other endorsement requests. This functionality enables organizations to monitor the progress and approvals of various requests efficiently.

If an organization is an endorsing entity, they will specifically see an option to approve a consensus request. This option will be available on several platforms, including their dashboard, the channel dashboard, and the app dashboard associated with the request. These features collectively streamline the approval process, making it more transparent and easier to manage across multiple channels and networks.

Meeting Consensus:

If consensus is met, the operation will proceed to the next steps, such as deploying the chaincode. At this point, the endorsement requests from other organizations will expire, unless all organizations were required to endorse for consensus. Each time a consensus request is approved, the consensus policy is checked to ensure