Technical Details and Development
Mbel Finance uses Hyperlane as the foundation for its cross-chain infrastructure. This allows the protocol to deploy and connect new chains such as Etherlink, Arbitrum, and Base into its ecosystem. Hyperlane provides a permissionless and modular interoperability layer, which enables seamless messaging and token transfers across chains. This section explains how the deployment process works from configuration to registration.
Prerequisites
A new, custom, or pre-existing network of your choice, including the following metadata:
A chain name, e.g.
ethereum
A chain ID, e.g.
1
A RPC URL, e.g.
https://eth.llamarpc.com
A deployer wallet/EOA private key or seed phrase
This EOA should be funded on your custom chain and any chain you will be passing messages to & from
1. Registry
Let’s create a custom chain config, run:
hyperlane registry init
Follow the prompts to set up your chain metadata. Setting up block or gas properties is optional.Now, under $HOME/.hyperlane/chains
you will find a new folder named with your custom chain’s name, and a file named metadata.yaml
within that folder.
2. Core
Next, let’s configure, deploy and test your custom chain’s core contracts.
From your local environment, set the private key or seed phrase of your funded deployer address to
HYP_KEY
. For example:export HYP_KEY='<YOUR_PRIVATE_KEY>'
From the same terminal instance, run:
hyperlane core init
Deploy Contracs
To deploy contracts, run:
hyperlane core deploy
Use the arrows and enter to select your custom chain from the bottom of the mainnet list. It will take a few minutes for all contracts to deploy.
Send test message
To send a test message, run:
hyperlane send message --relay
The --relay
flag is optional and will deliver the message to the destination chain.You can also run a relayer in the background with
hyperlane relayer --chains yourchain,sepolia
Note: This documentation may occasionally be out of sync. Please refresh the page before reading to ensure the latest version is displayed.
Last updated