XCM Transactor pallet had an issue in which it crafted an XCM V3 message that could not be converted to XCM V2. Therefore, [Referendum 95](https://moonbeam.polkassembly.network/referendum/95) can't be properly enacted.

As Referendum 95 was already approved, the Council and Tech-Committee has decided to fast-track it via this proposal.


[Forum Post](https://forum.moonbeam.foundation/t/proposal-93-hydradx-proposal-open-accept-hrmp-channel-and-register-asset-xchdx/794/7)

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`).

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

- There was a problem with a pallet called XCM Transactor.
- This problem made it so that a message couldn't be converted properly.
- There is a referendum called Referendum 95 that can't be enacted because of this problem.
- The Council and Tech-Committee want to fast-track the referendum to fix the problem.
- You can read more about it in the forum post.

#98 Fast-Tracked Proposal 95