## TL:DR

This batched proposal is to Accept/Open an HRMP channel with Calamari and to register the KMA token

## Summary

We propose to open a bi-directional channel between Moonriver and Calamari. Initially, the main use case will be to transfer MOVR and KMA between the two chains, but it can be further expanded to other use cases. The proposal also includes the KMA asset registration as xcKMA, with the following details:

 - Multilocation: *{ "parents": 1, "interior": {"X1": { "Parachain": 2084 }}}*
 - Decimals: *12*
 - Name: *Calamari*
 - Symbol: *xcKMA*

xcKMA will have the following asset ID and XC-20 address:
 - Asset ID: 213357169630950964874127107356898319277
 - XC-20 address: 0xFFffFffFA083189f870640b141ae1E882c2b5bad

## Proposal

Proposal #90 with the following hash: *0xece4cd77f5d06a976d10df9634903ed13b3b3c67a55b91e42fb7ce6726f9f02e*

## Technical details:

The procedure for opening the channels is as follows:

 - Calamari: already proposed to open an HRMP channel to Moonriver
 - Moonriver: democracy batched proposal:
    - Open Moonriver to Calamari HRMP channel
    - Accept Calamari to Moonriver HRMP channel
    - Register KMA asset as an XC-20 
    - Calamari: democracy proposal to accept Moonriver to Calamari HRMP channel

Once the HRMP channels are ready, XCM based cross-chain transfer will be possible. The extrinsics that need to be executed on the relay chain, are:

 - To open the HRMP channel from Moonriver: hrmp.hrmpInitOpenChannel(recipient: *2084*, proposedMaxCapacity: 1000, proposedMaxMessageSize: 102400), which its hex-encoded call data is *0x3c0024080000e803000000900100*
 - To accept this HRMP channel: hrmp.hrmpAcceptOpenChannel(sender: 2023) , which hex-encoded call data is *0x3c0124080000*

The *proposedMaxCapacity *and *proposedMaxMessageSize *are set to the values of Kusama’s *configuration.activeConfig.hrmpChannelMaxCapacity* and *configuration.activeConfig.hrmpChannelMaxMessageSize* values, respectively.

These extrinsics need to be called from the parachain’s sovereign account as origin, via a democracy proposal. The proposal will use *polkadotXcm* pallet to send XCM message to the Relay Chain with the following items:

 - Withdraw asset: take funds out of the Sovereign Account of the origin parachain (in the relay chain) to a holding state
 - Buy execution: buys execution time from the relay chain, to execute the XCM message
 - Transact: provides the call data to be executed
 - Deposit asset (optional): refunds the leftover funds after the execution. If this is not provided, no refunds will be carried out

The asset will be registered with the metadata described in the summary. The *setAssetUnitsPerSecond* was calculated using the value for KMA value on April May 16th 2022, targeting a XCM transaction cost of 0.02$.

If you are interested, the hex-encoded call data for this proposal in [Moonriver](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fwss.api.moonriver.moonbeam.network#/extrinsics/decode) is:

0x1e020c670001010002100004000000000700e876481713000000000700e8764817010700f2052a01060002286bee183c01240800000d0100040001010070617261e7070000000000000000000000000000000000000000000000000000670001010002100004000000000700e876481713000000000700e8764817010700f2052a01060002286bee383c0024080000e8030000009001000d0100040001010070617261e70700000000000000000000000000000000000000000000000000001e020c69000001010091202043616c616d6172691478634b4d410c0001000000000000000000000000000000016901000101009120aba8cdcf29b9670000000000000000001300000000050411011da53b775b270400e7e61ed5cbc5a146ea70f53d5a3306ce02aaf97049cf181a9663dacd60a0781792df8466393c1106ffffffffa083189f870640b141ae1e882c2b5bad181460006000fd

As a prerequisite, the parachain’s sovereign account 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.

The proposal by LimeChain aims to develop Gosemble, a framework for building Substrate-compatible runtimes in Go. Phase 2 aims to modularize the codebase, develop additional modules, and create comprehensive documentation. The project involves tasks such as improving Wasm compatibility, enhancing benchmarking, and establishing developer relations.

Link multisig.

Proxy Support.

Additional network support(SDK & App).

Custom Call data transactions.

Create extrinsic and sign as multi.

Address category and additional info.

Transaction Tags and additional metadata.

Notification bots.

Multi-currency support.

Shared Address Book.

Extend SDK support for all new features like custom transactions, call data signing, batch transactions and more.

Transaction Batching(Bulk payouts).

Apps.

Polkassembly app.

Videos for tutorials.

SDK Docs.

2FA login.

Next.js migration.

Send a batch of dispatch calls and atomically execute them.
The whole transaction will rollback and fail if any of the calls failed.

May be called from any origin.

- `calls`: The calls to be dispatched from the same origin. The number of call must not
  exceed the constant: `batched_calls_limit` (available in constant metadata).

If origin is root then call are dispatch without checking origin filter. (This includes
bypassing `frame_system::Config::BaseCallFilter`).

# <weight>
- Complexity: O(C) where C is the number of calls to be batched.
# </weight>

- The proposal is to open a channel between Moonriver and Calamari.
- They want to transfer MOVR and KMA between the two chains.
- They also want to register the KMA asset as xcKMA.
- They have a proposal number and a hash for the proposal.
- They need to execute some technical steps to open the channel and register the asset.

Open/Accept HRMP channel to/from Calamari and Register KMA Asset

Democracy

#90 Open/Accept HRMP channel to/from Calamari and Register KMA Asset

No Active Proposals