Core App Environments
Predefined Hyperlane environments for test and production use
Note: Abacus is the former name of the Hyperlane protocol. Parts of the codebase will soon be renamed.
Throughout the Hyperlane Code bases exist the concept of environments to facilitate the development and testing of changes, both of the Hyperlane core platform as well as applications building on top of Hyperlane. Environments also encode the set of domains/chains that are supported. This page outlines the purpose of each environment and how developers should think about them.

Environment: "test"

The test environment is meant for local development. Application developers can use the @abacus-network/hardhat plugin's TestAbacusDeploy object to deploy a mocked Hyperlane core platform. By calling processMessages(), developers can simulate the processing of messages across domains without having to run any of the Agents.
The domains that are supported by the sdk are artificial chains test1, test2, and test3 which are all deployed on the same hardhat-network node, either in unit tests setup by hardhat or a dedicated node that is run via hardhat node. Local end-to-end tests should be run in the test environment as well. Developers can use the getMultiProviderFromConfigAndSigner from @abacus-network/deploy to construct a MultiProvider that works for the test environment.

Environment: "testnet2"

The testnet2 environment is where developers should expect to make integration tests of their app. Analogous to traditional software engineering practices, testnet is Hyperlane's staging environment. It's where one can test deployment tooling to real remote networks, as well as UI and SDK integrations. Agents are run as close as possible to mainnet and the relayer will expect Interchain gas payments in order to process messages on the destination chain.
Developers can interact with testnet2 Hyperlane core deployment by calling
import { AbacusCore } from '@abacus-network/sdk';
const core = AbacusCore.fromEnvironment(environment, multiProvider);
The domains that are supported are alfajores, kovan, fuji, mumbai, bsctestnet, arbitrumrinkeby, optimismkovan. You can find the contract addresses under the Contract Addresses section.

Environment: "mainnet"

The mainnet environment is where real value is at stake, a production environment deploying to the full set of Hyperlane supported domains. Where Validator sets will be continuously decentralized and relayers will need to be incentivized to process messages via interchain gas payments.
The domains that are supported are ethereum, polygon, avalanche, bsc, celo, arbitrum and kovan. You can find the contract addresses under the Contract Addresses section.

Contract Addresses

In cases where the core Hyperlane contract addresses are needed (instead of using utilities via Environment names), the artifacts for core deployments can be found in the monorepo here.
Copy link
On this page
Environment: "test"
Environment: "testnet2"
Environment: "mainnet"
Contract Addresses