[Forum Post](https://forum.moonbeam.network/t/proposal-124-close-xcm-channel-with-subsocial/2227)

**Abstract**



Our XCM monitor noticed that Subsocial was no longer producing blocks.

Due to this, I’m proposing closing the XCM channel between Moonbeam \<> Subsocial.

**Details**


The proposal will call the XCM Transactor pallet with `hrmpManage` extrinsic with the `close` option to shut down the 2004 → 2101 XCM channel (and 2101 → 2004).

Tested with Chopsticks with preimage hash `0x47bd1fbbe15ec1e0a06192202d9818a045be3bedf99ba1bdb343124ec6666b38`

This proposal aims to develop Magnet, a smart contract platform operating on the Polkadot network. Divided into three milestones, the plan covers key aspects such as gas consumption analysis, DOT-based governance, blockspace ordering, profit distribution, collator incentives, and XCM functionality. The team, with members experienced in various blockchain projects, will ensure thorough testing and deployment after every milestone and will provide detailed reports for each

Maintananing and running Giant Squids for Polkadot & Kusama for Q3 2023.

Maintananing and running Archives for Polkadot & Kusama for Q3 2023.

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.

#124 Closing XCM Channel with Subsocial

No Active Proposals