Skip to content
Last update: July 4, 2022

Supported Quorum Blockchain Service ledger versions

Quorum Blockchain Service (QBS) uses the Ethereum-based GoQuorum ledger designed for the processing of private transactions within a group of known participants, identified as a consortium in QBS.

Manage updates and upgrades

Versioning in GoQuorum is done through calendar versioning with the format YY.M.patch. For example, if the GoQuorum version is 21.4.2, release type would be categorized as follows:

YY (Year) M (Month) Patch
21 (2021) 4 (April) 2

QBS automatically updates patch releases of GoQuorum to existing running members within 30 days of being made available from GoQuorum.

Check ledger version

You can check the GoQuorum version on your QBS member by attaching to your node using the QBS Management API, using geth or viewing diagnostic logs.

Using the QBS Management API

You can use the (QBS management API to view the existing API keys for the transaction nodes of your QBS member. Select Authorize on the API website to authorize running the APIs.

Authorize API

Once you authorize the API, select the GET request Get the details of the transaction node under the TransactionNodes section, and select Try it out.

Try it out

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

  • subscriptionID - Your subscription ID, found 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 isn’t 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 of any transaction node in your QBS Member. You can use the default transaction node name Transaction-1.

Once you’ve entered the fields, select Execute. The Response body of the output of the API lists the quorumVersion and tesseraVersion information.

Example JSON result

{
"id": "/subscriptions/<YOUR SUBSCRIPTION ID>/resourceGroups/my-qbs-rg/providers/Microsoft.Solutions/applications/MyCompany/transactionNodes/transaction-1",
"location": "westus2",
"name": "transaction-1",
"type": "ConsenSys.Blockchain/blockchainMembers/transactionNodes",
"properties": {
    "dns": "transaction-1.mycompany.supplychain-6731.onquorum.net",
    "firewallRules": [],
    "provisioningState": "Succeeded",
    "publicKey": "5hXdvjQ+8ovjKfKYe1RDiC2nTKnMV6VgAohGh8ksiB4=",
    "quorumVersion": "21.4",
    "tesseraVersion": "21.7"
    }
}

Using geth

Attach to your QBS node using geth:

Example

geth attach https://transaction-1.qbsconsortium.onquorum.net:3200/H5xErinMiG21jtiRYbyWeia2

Once your node is connected, geth reports the GoQuorum version:

Example

instance: Geth/v1.9.7-stable-9339be03(quorum-v2.6.0)/linux-amd64/go1.13.12

Using diagnostic logs

If you enable diagnostic logs, the GoQuorum version is reported for transaction nodes:

Example

{"NodeName":"transaction-node","Message":"INFO [06-22|05:31:45.156] Starting peer-to-peer node instance=Geth/v1.9.7-stable-9339be03(quorum-v2.6.0)/linux-amd64/go1.13.12\n"}
{"NodeName":"transaction-node","Message":"[*] Starting Quorum node with QUORUM_VERSION=2.6.0, TESSERA_VERSION=0.10.5 and PRIVATE_CONFIG=/working-dir/c/tm.ipc\n"}
111

Check genesis file content

To check genesis file content of your blockchain node, use the admin_nodeInfo API method.

You can call the API using a geth console or a web3 library.

Back to top