TL:DR
I propose to open bi-directional (request and accept) HRMP channels between Shiden and Turing.
Proposal
The OAK Network requests Astar governance approval to open bi-directional HRMP channels between Shiden and the Turing Network, Kusama’s hub for trustless automation.
OAK Network seeks to enable Turing’s native token (TUR) to be transferred to Shiden and traded with native and foreign tokens.
Cross-consensus messaging (XCM) enables OAK to automate any extrinsic or smart contract function on the Shiden blockchain without taking custody of private keys or crypto. Trustless automation unlocks rich user experiences including scheduled and recurring payments, stable-cost-averaging, and automatically-compounding staking, LP, and money market rewards.
Steps to enact this proposal would be the same as other parachains who have opened HRMP channels with Shiden.
- The extrinsics need to be called with the parachain’s sovereign account as origin.
- Sovereign accounts for both parachains must contain at least 10 KSM to be locked as collateral (5 for each channel direction), plus some KSM to pay for xcm execution fees.
Extrinsics
See also: HRMP channels and you
- Request to open HRMP channel with Turing:
hrmp.hrmpInitOpenChannel(recipient: 2114, proposedMaxCapacity: 1000, proposedMaxMessageSize: 102400)
- Accept the request from Turing to open HRMP channel:
hrmp.hrmpAcceptOpenChannel(sender: 2114)
*Assumption: Turing Network requests to open channel with Shiden
About Turing Network:
As Kusama’s hub for trustless automation, Turing Network (OAK’s canary network) enables multi-chain apps to schedule and automate execution of any transaction or smart contract function. OAK is built for cross-chain automation, allocating 100% of block space to storing and triggering transaction execution on connected blockchains . OAK’s event-driven execution model enables executing blockchain transaction based on time, price, or state change of another chain or smart contract.