Hi community,

[referendum 93](https://moonbeam.polkassembly.network/referendum/93) aimed to accept and open an HRMP channel with HydraDX and register xcHDX as asset.

However, the council proposed the [Runtime Upgrade to v2302 in Ref94](https://moonbeam.polkassembly.network/referendum/94) due to performance degradation, which was fast-tracked.

Referendum 93 was prepared for the old runtime with XCMv2 and cannot be executed now on v2302.
The referendum has strong support and will pass but the underlaying calls won't be executed.

This is why we had to re-propose it with adjustments for XCMv3 and compatibility with the new runtime.

The [forum post](https://forum.moonbeam.foundation/t/proposal-93-hydradx-proposal-open-accept-hrmp-channel-and-register-asset-xchdx/794/7) has been commented accordingly by AlbertoV19.

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 referendum called 93 that wanted to open a channel with HydraDX and register xcHDX as an asset.
- However, there was a performance issue, so a new referendum called 94 was proposed to upgrade the system.
- Referendum 93 cannot be executed now because of the upgrade.
- They had to make adjustments to referendum 93 to make it compatible with the new system.
- AlbertoV19 commented on the forum post about this.

#95 Re-Propose Ref93 / Opening HRMP Channel WIth HydraDX