The Moonbeam Council proposes to upgrade the Moonbeam's runtime to version **version 1801**. 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)

### 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: `0x51c4ef37f8ae268ac4ddd95dd20a2bcca5e56b79e51e3c73e002e6ce4bb8973f` 

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

- The Moonbeam Council wants to upgrade Moonbeam's runtime to version 1801.
- The upgrade includes fixes and improvements.
- Some important updates include adding a proxy precompile, a new collective for treasury management, and a CallPermit precompile.
- You can verify the upgrade using a hash code.
- If you want to learn more, you can read the full post.

#58 Runtime 1801 Upgrade

No Active Proposals