<p>Polkadex is moving towards a new integration with Hyperbridge for cross-chain interactions, and thus they haven't renewed their parachain slot in Polkadot. This has caused the XCM channels between Moonbeam and Polkadex to become unresponsive, so this proposal is made with the purpose of closing these channels.</p>

Polkadex is moving towards a new integration with Hyperbridge for cross-chain interactions, and thus they haven't renewed their parachain slot in Polkadot. This has caused the XCM channels between Moonbeam and Polkadex to become unresponsive, so this proposal is made with the purpose of closing these channels.

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:** XCM channels between Moonbeam and Polkadex are unresponsive due to Polkadex not renewing its parachain slot in Polkadot.
- **Significance:** Ensuring smooth cross-chain interactions between Polkadex and Moonbeam is crucial for the ecosystem's functionality.
- **Proposed Solution:** Proposal to close the unresponsive XCM channels between Moonbeam and Polkadex.
- **Expected Outcomes:** Improved cross-chain interactions and ecosystem functionality.

#100 Batch proposal to close channels between Moonbeam and Polkadex

No Active Proposals