<a href="https://forum.moonbeam.network/t/proposal-65-close-xcm-channel-with-litmus/1967">Forum Post</a>
Abstract
Our XCM monitor noticed that Litmus was no longer producing blocks.
Due to this, I'm proposing closing the XCM channel between Moonriver &lt;&gt; Litmus.
Details The proposal will call the XCM Transactor pallet with <code>hrmpManage</code> extrinsic with the <code>close</code> option to shut down the 2023 -&gt; 2106 XCM channel (and 2106 -&gt; 2023).
Tested with Chopsticks with preimage hash <code>0x9bd482a9a1bd059a5e1c75d3c96d01e179d036c6bb779ac10c0109e7470eb4b5</code>

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 except `None`.

- `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 the calls are dispatched without checking origin filter. (This
includes bypassing `frame_system::Config::BaseCallFilter`).

## Complexity
- O(C) where C is the number of calls to be batched.

- Problem Statement: Litmus is no longer producing blocks, prompting the proposal to close the XCM channel between Moonriver and Litmus.
- Significance: Ensuring the functionality of the XCM channel is crucial for the network's operations.
- Proposed Solution: Close the XCM channel between Moonriver and Litmus using the XCM Transactor pallet with the hrmpManage extrinsic.
- Expected Outcomes: Restoring the network's stability and functionality by addressing the issue with Litmus not producing blocks.

#65 [Proposal: 65] Close XCM Channel with Litmus

No Active Proposals