Due to a bug in Polkassembly majority of Moonriver community were not able to participate in voting for Runtime Upgrade 2100. 

The Moonriver Council proposes to reconduct the vote proposal to upgrade the Moonriver's runtime to version 2100.

### Runtime 2100 release note :

[https://github.com/PureStake/moonbeam/releases/tag/runtime-2100](https://github.com/PureStake/moonbeam/releases/tag/runtime-2100)

### Important updates:

* OpenGov is being added to Moonriver and introduces new ways for the chain to be managed/administrated. 
It is important for tools, service providers and users to consider this new governance upgrade to ensure correct monitoring and participation in the network important decisions (see [#2041]((https://github.com/PureStake/moonbeam/pull/2041)), [#2044]((https://github.com/PureStake/moonbeam/pull/2044)), [#2028]((https://github.com/PureStake/moonbeam/pull/2028)))
* Staking rewards are now paid 1 block later. Instead of being on the first block of a round, it will start on the 2nd block of that round (see [#1855]((https://github.com/PureStake/moonbeam/pull/1855)))
* EVM/Substrate transactions are now using the new Dynamic fees model in Moonbase Alpha for observation before enacting it on Moonriver.

### Verification

Blake2_256 Hash: `0xfb9f16ba6b3433ba2a273974207260c7ace6aa629992d492bad0ba873b39762d` 

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



-Due a bug on Polkassembly, the majority of Moonriver community were not able to participate in voting for Runtime Upgrade 2100
-The Moonriver Council proposes to reconduct the vote proposal for upgrade to version 2100
-New updates include OpenGov tool for administration of the chain , staking rewards paid one block later, using Dynamic fees model for EVM/Substrate transactions
-You can verify the proposal hash with srtool.

#128 Runtime 2100 Upgrade

No Active Proposals