testenvironment is meant for local development. Application developers can use the
TestAbacusDeployobject 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.
sdkare artificial chains
test3which are all deployed on the same hardhat-network node, either in unit tests setup by
hardhator a dedicated node that is run via
hardhat node. Local end-to-end tests should be run in the
testenvironment as well. Developers can use the
@abacus-network/deployto construct a
MultiProviderthat works for the
testnet2environment is where developers should expect to make integration tests of their app. Analogous to traditional software engineering practices,
testnetis 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.
testnet2Hyperlane core deployment by calling
optimismkovan. You can find the contract addresses under the Contract Addresses section.
mainnetenvironment 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.
kovan. You can find the contract addresses under the Contract Addresses section.