Skip to content


Each environment contains:

  • A firewall isolated network within which all resources run
  • A permissioned blockchain, with its own genesis configuration
  • The full-stack of services that make up your decentralized solution

Configuring the Blockchain

Environment Protocols

The first piece of environment configuration is to choose the enterprise blockchain protocol. The choices are:

  • Enterprise Ethereum
  • Corda

Learn more about protocol providers and consensus algorithms

Multi-region, multi-cloud environments

Environment Regions

The deployment scheme for environments is either cloud-only or hybrid. A cloud-only deployment means that resources (nodes, services, etc.) are all created in a single deployment zone in AWS and Azure. A hybrid deployment model will allow for resources to be created both on-premise and in private cloud VPCs.

  • If your current plan does not support hybrid, please contact us to learn more.
  • Regions must be whitelisted into a consortium before being available in the environments of that consortium.

Protocol Settings

Environment Providers Ethereum

If you have elected for Enterprise Ethereum, you can choose between three-node clients - Geth, Quorum, and Hyperledger Besu - and their supported consensus algorithms.

  • Geth is the hardened Go implementation of the core Ethereum node. Compatible with clique PoA consensus.
  • Quorum is a fork of Geth offering support for private transactions through its "constellation" module. Compatible with Raft and Istanbul BFT.
  • Hyperledger Besu is a modular Java-based client designed specifically for enterprise requirements. Besu also supports private transactions and is compatible with clique PoA and Istanbul BFT.

Environment Providers Corda

If you have elected for Corda, there is only a single choice:

Pausing an Environment

Environments can be manually paused by clicking the Pause button on an environment's dashboard, then selecting Pause again from the sub-menu. The environment's status will temporarily show Pause_pending before changing to Paused.

Environment Status

If you did not make a request to pause your environment and are wondering how it might have reached that state, please read this FAQ article.

Resuming a Paused Environment

To wake an environment in the Paused state, click the Start button on an environment's dashboard, then select Start again from the sub-menu. The environment's status will temporarily show Resume_pending before changing to Live.

Upgrading an Environment

Your environment is eligible for an upgrade to a newer release if you see an orange circular icon with a white up-arrow next to your Release version when viewing the environment web-page. Click on the orange/white arrow icon and follow the pop-up instructions to complete an upgrade to the latest release.

Environment Upgrade

To perform a hard fork upgrade of your environment so that your chain is configured with any newly available EIPs, refer to the steps here.