TL;DR
We propose to open HRMP communication between Astar Network and HydraDX. This will require actions on both chains.
Summary
We propose to open a bi-directional channel between Astar Network and HydraDX. The primary use cases will be:
- $ASTR can be transferred to HydraDX and used as liquidity in the protocol and its unique Omnipool. That enables tradability with all the other listed assets, single-sided LPing, Liquidity Mining, DCAs and other advanced methods of value accrual for ASTR holders.
- $HDX can be transferred to Astar to be used in the ecosystem of Astar Network and the protocols build on top of the network.
Proposal
The integration has been tested on the Rococo network.
An HRMP channel has been already requested from the HydraDX side. This post acts as a proposal to accept and request opening the opposite direction HRMP channel from the Astar network.
Technical details
The procedure for opening the channels is as follows:
- Astar Network proposes to accept the HydraDX to Astar Network HRMP channel and open a Astar Network to HydraDX HRMP channel via [Astar MuliSig Governance Batch call].
- Wait until the proposal on step 1 gets approved & enacted.
- HydraDX accepts the Astar Network to HydraDX HRMP channel and lists ASTR to the Omnipool.
- Wait for another session on Polkadot for the change to be effective.
These extrinsics need to be called with the parachain’s sovereign account as the origin. To achieve this, on the HydraDX side we will use polkadot-xcm pallet to send XCM message to the relay chain, by executing the following extrinsic from the parachain. Astar Network should make an open request call and an accept request call with its pallet.
As a prerequisite, the parachain’s sovereign account must contain at least 20 DOT to be locked as collateral (10 for each channel direction), plus some DOT to pay for XCM execution fees.
