Registry Interaction via Kaleido Console

Registry Interaction via the Kaleido Console

The On-Chain Registry service dashboard is split into a few different sections, which are each described below.

Dashboard Header 

The header contains the following general information for the consortium and this service.

• # Memberships: total number of memberships in your consortium.
• # On-Chain Members: number of memberships within your consortium that have already been registered on-chain.
• # Members Owned: number of memberships in this consortium owned by your organization
• Contract Address: address of the Directory smart contract deployed when this service was provisioned. This is the address to target when making transactions to register memberships on-chain.

Available Off-Chain Memberships

This is a list of all memberships in your consortium that have not yet been added to the on-chain Directory. This section is divided into two sub-categories.

• Owned Memberships: These memberships are owned by your organization, which means that you are able to take action and add them to the on-chain Directory. Each membership has a field indicating which type of identity proof (a valid x509 certificate) is attached to it. The three possible types are:
  • Self-Signed: these certificates have been created by Kaleido, and Kaleido stores an encrypted version of the private key. Highlighting one of the memberships in this category will reveal a button labeled Establish Identity. Clicking that button will create an Ethereum account and store it inside the service pod. This account’s private key is managed by Kaleido and will then be used to make a transaction against the Directory contract to establish the membership’s identity on-chain.
  • Externally Signed: these certificates have been created outside of Kaleido, and the user maintains the private key without any help from Kaleido. Selecting a membership in this category reveals instructions about how to use the Kaleido CLI to establish an on-chain identity.
  • None: this means that the membership does not have an identity proof attached to it yet. Selecting the membership allows you to either attach a self-signed certificate by clicking on the Confirm Identity button, or attach an externally-signed certificate by clicking the link and following the instructions there.
• Other Memberships: These memberships are owned by other organizations, which means that you do not have the ability to add them to 0n-chain Directory. Members of the owning organization are the only ones that can take action.

On-Chain Memberships

These memberships have already been added to the on-chain Directory. You can navigate through these memberships using the nested-tree view on the left side of the web-page to view details of the membership. Details include the identity proof used to register the membership and the Ethereum account address owned by that membership.

If the on-chain membership used a self-signed x509 identity proof, thereby creating a Kaleido-managed Ethereum account, there is an option to store additional on-chain information using the Add Profile Key button. Clicking that button allows you to input a key-value pair to store on-chain information you would like to share with the other members of the consortium. The information is added to the Profile contract by creating a transaction signed by the Kaleido-managed Ethereum account.