## Batch

This Referendum is composed of 2 actions, combined inside a `Batch`:
  * Cancel referendum for `runtime 1801 upgrade`
  * Authorize `runtime 1802 upgrade` 

## Runtime upgrade

The Moonbeam Council proposes to upgrade the Moonbeam's runtime to version **version 1802**. This upgrade will include the Runtime 1800 change proposal along with the below fixes.

### Runtime 1800 release note :
[https://github.com/PureStake/moonbeam/releases/tag/runtime-1800](https://github.com/PureStake/moonbeam/releases/tag/runtime-1800)

Fixes :
* [https://github.com/PureStake/moonbeam/releases/tag/runtime-1801](https://github.com/PureStake/moonbeam/releases/tag/runtime-1801)
* 1802 fix includes recent changes required for the relaychain (details to be communicated soon)

### Important updates:
* Add proxy precompile : ([#1705](https://github.com/PureStake/moonbeam/pull/1705))
A smart contract is now able to proxy a real account and effectively make substrate calls on its behalf.

* New collective to accept and reject treasury spending proposal ([#1723](https://github.com/PureStake/moonbeam/pull/1723))  
Add a new TreasuryCouncilCollective pallet to manage the treasury. It will only replaces the normal Council for treasury management.

* Add CallPermit precompile ([#1706](https://github.com/PureStake/moonbeam/pull/1706))  
Allows a user to sign an EIP712 (signed type message) permit for any EVM call, which can then be dispatched by anyone else on their behalf.

### Verification
Blake2_256 Hash: `0xea1f71080c18febe27c197756ef4c1b4ed951f91d5af643077b8cd57a0fa48e3` 

If you want to apply the best practices and verify the hash of the proposal, we advise you to use srtool

This project's goal is to create a new metadata protocol friendly to offline devices and implement it in the most critical tools available: Ledger and Kampela, as well as create tools to port it to other wallets and key management devices, including Polkadot Vault. This will involve changing the runtime code to support a new method of transaction signing that would include a proof of metadata used for transaction rendering to the user.

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.

- `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 call are dispatch 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 is a referendum with two actions: canceling an upgrade and authorizing a new upgrade.
- The Moonbeam Council wants to upgrade the Moonbeam's runtime to version 1802.
- The upgrade includes fixes and improvements.
- There are important updates like adding a proxy precompile and a new collective for treasury management.
- You can verify the proposal using a hash code.

#62 Runtime 1802 Upgrade

No Active Proposals