Using Quorum Blockchain Service (QBS), you can create consortiums (private blockchain networks), where the blockchain network is limited to specific network participants. Only participants in the consortium can view and interact with the blockchain.
QBS consortiums are governed through roles that are assigned to members. There are two roles associated with consortium management in QBS: Owner and Member. A QBS network can have more than one member with the Owner role.
|List members of a consortium||X||X|
|List consortiums in an Azure subscription||X||X|
|Validate an invite code||X||X|
|Invite a member to join a consortium||X|
|Remove a member from a consortium||X|
|Revoke an invitation||X|
|List invitation status||X|
Join or create a consortium
When you invite others to join your consortium, QBS securely peers consortium members together and provides the governance necessary to administer the consortium.
Parties can join or create a consortium using the QBS management API. Invited parties provision a QBS member in Azure using an invitation code, which connects the new member to the existing network.
When a new member joins an existing consortium, an Azure Virtual Network (VNet) peering is created between the new and existing members of the consortium. Nodes in your private member network run and communicate among each other using the VNet.
Leave a consortium
When a member leaves or is removed from a consortium, the Azure VNet connecting the member to other members in the consortium is removed, and the members' metadata is removed from the control plane database in QBS. The member being removed from the consortium doesn't have their member deleted, rather, the QBS resource is still available and has the chain data up until the point the member was removed from the network.