Overview
In a single-collateral HWR, tokens are locked on one source chain. Example:- Lock 100 USDC on Ethereum
- Mint 100 USDC on NewChain
- Lock 50 USDC on Base
- Lock 50 USDC on Arbitrum
- Mint 100 USDC on NewChain
Native Rebalancing
If more funds flow in one direction, one of the chains in the route can run out of collateral, creating imbalanced flow that prevents withdrawals. To maintain a smooth user experience, collateral must be balanced across chains. HWR 2.0 addresses this with native rebalancing - collateral is automatically moved between chains to resolve imbalances via the rebalancer. To learn more about Native Rebalancing, head over to: HWR 2.0 : Native RebalancingHigh-level Flowchart
Supported Tokens and Protocols
Native rebalancing is possible when the required conditions are met for a given token on each participating chain in the HWR 2.0.USDC
- Chains: Arbitrum, Base, Ethereum, OP Mainnet, Polygon PoS, Unichain, Avalanche
- Support for additional chains which are supported by Circle CCTP v1/v2 and Everclear will roll out incrementally.
ETH
- 🚧 Native rebalancing support is currently planned
USDT
- 🚧 Native rebalancing support is currently planned
Chain support for native rebalancing depends on protocol availability and
token bridging infrastructure. Read more about the requirements for native
rebalancing
Guides
- To deploy Hyperlane Warp Routes 2.0 head over to Deploy a Hyperlane Warp Route 2.0