Registering a new Blockchain

Before proceeding, we recommend having these items on hand:

  • Certificates (Public and Private keys) for the Identity that you have created for our agent
  • Peer host names and ports
  • Permissions you wish to grant BlocWatch
  • Channels that you want to monitored
  1. Open the navigation menu and select Blockchains.

  2. If this is your first time you will see "Register a new blockchain". Otherwise, you will see your blockchains listed.

  3. Choosing the Blockchain type.

    • If you only want to see a demo, you can click on either option under Demos.
    • If you want to integrate your own network, choose one of the three options under Custom.

Ethereum or Quorum

  1. Enter a Peer URL.

    • Using Geth or another on-premise solutions, this is a URL you would use to connect to the Web3 JSON RPC service (e.g., https://host:8545).
    • In Azure Blockchain Service, this is an HTTPS connection string. To acquire this information, see our Azure Blockchain Service documentation.
  2. If available, enter a Prometheus metrics URL from which BlocWatch can collect metrics.

    • Using Geth, prometheus metrics must be enabled via command-line flags. Metrics are then exposed via a new endpoint (e.g., https://host:6060/debug/metrics/prometheus).
    • In Azure Blockchain Service, this field should be left blank.

Hyperledger Fabric Blockchain

  1. Enter the name of the channel you want monitored (ex. mychannel).

  2. Enter a Membership Service Provider ID (ex. Org1MSP).

  3. Enter an identity name (ex. Admin@org1.example.com, User@org1.example.com, etc…).

    • BlocWatch recommends that you create a separate identity for us to use to connect to your network. This ensures that you grant our agent the minimum required access to your system.
  4. Obtain the identity certificate and private key: Copy everything in the files including the BEGIN and END tags.

    • When you enroll using the Fabric CA client, you can obtain a membership certificate from the client or the MSP folder on your file system under the name of the BlocWatch identity you created:

      • Identity certificate is in the signcerts folder
      • Private key is in the keystore folder
    • If using a demo blockchain that utilized crypto-config, you can find the certificates in a file path similar to the one below:

      crypto-config/peer-organizations/org1.example.com/users/Admin@org1.example.com/msp/signcerts

      crypto-config/peer-organizations/org1.example.com/users/Admin@org1.example.com/msp/keystore

  5. Enter the peer host (ex. peer0.org1.example.com, peer1.org1.example.com, etc…).

    • The peerhost name must be resolvable by the BlocWatch agent. For demonstration purposes, it may be started locally to the fabric peer in which case localhost may be used however that is not recommended for production environments.
  6. Finally, enter the port of one of the valid peers (ex. 30051, 7053, 7051, 8080, etc…). a. The port is used by the fabric peer to handle Remote Procedure Call (RPC) requests. It is important that the ports you choose are open and can be accessible.

  7. If the blockchain utilizes Transport Layer Security (TLS) (e.g. IBM Blockchain Platform), continue to the section below. Otherwise, hit "Continue" and decide what you want to see on the following pages. Once the blockchain is created, skip to the Obtaining your blockchain reference ID section.

Utilizing Transport Layer Security (TLS) on your Blockchain

  1. Enable TLS on the blockchain you are adding (shown below).

  2. Enter the Server TLS CA certificate (If the TLS CA cert is in base64, you will need to convert it to .pem and then remove line breaks):

    • The server TLS CA cert is what the agent needs to connect to the peer (the peer is the server from the perspective of the agent). For IBM's platform, you can find the TLS certificates in your credentials profile.
  3. If TLS is only enabled on the server and not on a component to component basis, you can click through to the next page without filling in the Client TLS Certificate and Client TLS Private key. Otherwise, you will need to gather those and fill them in accordingly.

  4. Decide what information you want to monitor on the following pages. Once your blockchain is created, proceed to Obtaining your blockchain reference ID.

Obtaining the blockchain's reference ID

  1. Once the chain has been created on the BlocWatch app, navigate to the Blockchains tab.

  2. Click on the name of the blockchain you created.

  3. The navigation menu will expand to include new sections for that specific blockchain. Select Settings under the blockchain (shown below).

    Side Note: It is okay if the dashboard does not look the same as it does below.

  4. The reference ID that you need for the Docker and Kubernetes command is shown below.

Navigate to Creating an Agent to continue the setup process.