Skip to main content

Add a transaction node to your Quorum Blockchain Service member

Quorum Blockchain Service (QBS) allows you to add additional transaction nodes to your blockchain member. Adding transaction nodes can be useful for load balancing or if you want to have separate private nodes in your network.

Add a new transaction node

You can use the QBS management API to add additional transaction nodes to your QBS member. Select Authorize on the API website to authorize running the APIs.

Authorize API

Once you authorize the API, select the PUT request for Adds a transaction node under the TransactionNodes section, and select Try it out.

Try it out

In the fields for the API request, fill out the following using your QBS member information:

  • subscriptionID - Your subscription ID, in the Overview tab for your QBS member, under the Essentials section.

  • resourceGroupName - The resource group to which your QBS member is deployed. Note this is NOT the Managed Application resource group.

  • blockchainMemberName - The name of your QBS member, also known as the name of your Managed Application, located in the upper-left corner of the Overview tab.

  • transactionNodeName - The name to give your new transaction node.

  • isArchiveNode - True or False. True indicates the new transaction node will have a full archive of the ledger history.

Overview Page

Verify your transaction node has been provisioned

After adding the new transaction node using the API, QBS provisions a new VM with the information provided. This can take up to five minutes to complete.

To verify your transaction node was successfully provisioned, select the GET request for Get the details of the transaction node under the TransactionNodes section, and select Try it out.

Get transaction node

View the Response body of the output of the API.

Example JSON result
"id": "/subscriptions/<YOUR SUBSCRIPTION ID>/resourceGroups/devtool-testing/providers/Microsoft.Solutions/applications/consensys/transactionNodes/mytransactionnode",
"location": "eastus",
"name": "mytransactionnode",
"type": "ConsenSys.Blockchain/blockchainMembers/transactionNodes",
"properties": {
"dns": "",
"firewallRules": [],
"provisioningState": "Updating",
"publicKey": null

If the provisioningState is Updating, your transaction node is still in the process of provisioning. Once it changes to Succeeded, your transaction node is ready to use.

You can get the connection string of your new transaction node to connect to it with MetaMask, Truffle, or your dapp.