<a href="https://forum.moonbeam.network/t/proposal-73-close-xcm-channel-with-parallel-finance/1890">Forum Post</a>
 Abstract
Our XCM monitor noticed a mismatch of GLMR between Parallel's Sovereign account on Moonbeam and the amount of <code>xcGLMR</code> in Parallel FInance chain.
Due to this, I'm proposing closing the XCM channel between Moonbeam &lt;&gt; Parallel.
Details The proposal will call the XCM Transactor pallet with <code>hrmpManage</code> extrinsic with the <code>close</code> option to shut down the 2004 -&gt; 2012 XCM channel.
The balance mismatch at the time of writing is:
<pre><code>GLMR on Parallel: 156269.426033674418712475
GLMR on MB Parallel Sovereign: 156123.586758753852442111

Difference: 145.83 GLMR
</code></pre>

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:** Mismatch of GLMR between Parallel's Sovereign account on Moonbeam and xcGLMR in Parallel Finance chain.
- **Significance:** Ensuring accurate balance reconciliation and preventing discrepancies.
- **Proposed Solution:** Close the XCM channel between Moonbeam and Parallel using the XCM Transactor pallet with hrmpManage extrinsic.
- **Expected Outcomes:** Resolving the balance mismatch and maintaining consistency in GLMR values.

#73 [Proposal: 73] Close XCM Channel with Parallel Finance

No Active Proposals