Configuring New Chains in the Hyperlane Explorer
Hyperlane can be deployed to any chain by anyone, this open access is called Permissionless Interoperability (PI). However the messages on PI chains cannot be identified by the default Hyperlane Agents. To view details about messages from PI chains, first configure the explorer with metadata about that chain.
Adding Chain Metadata to Hyperlane Explorer
- On the Explorer’s homepage, click either the Origin or Destination button to open the chain selection. This will open the chain selection modal. From there, click the plus icon in the top-right.
-
On the form that appears, enter the chain’s metadata using JSON or YAML conforming to the ChainMetadata schema.
-
If a valid Etherscan-based block explorer config is provided, the Hyperlane Explorer will utilize it to find the desired messages. If not, it will use the RPC URL. Note, Explorers with API keys (even just free-tier keys), perform faster and more reliably.
Chain Metadata Examples
A minimal example in JSON:
A more detailed example in YAML:
If the origin or destination domainId
of chains in your messages doesn’t
match their chainId
then you must include the domainId
field in your chain
config.