Moonriver Network

Moonriver Network was an Ethereum-compatible smart contract parachain on the Kusama network that served as a permanently incentivized canary network for Moonbeam on Polkadot, launched in 2021 on Kusama as part of the Moonbeam ecosystem supported by the Moonbeam Foundation. New code was deployed and tested on Moonriver under real economic conditions before being shipped to Moonbeam.^[8]​^[9] The network’s native utility token, MOVR, powered gas fees, staking incentives for collators, on-chain governance, and other transaction fees on Moonriver.^[8]​^[9] As part of a planned transition, MOVR migrated from the Moonriver parachain to an ERC‑20 token on Base via a 1:1 bridge that operated until July 31, 2026, after which Moonriver entered maintenance mode on August 1, 2026.^[14]​^[2]​

Overview

Moonriver was an Ethereum Virtual Machine (EVM)-compatible, developer-focused parachain built on Kusama that mirrored Moonbeam’s functionality in a higher-velocity, experimental environment.^[8]​^[9] It provided a canary network where new runtime upgrades, features, and smart contracts were deployed first and exercised under real economic conditions before being rolled out to Moonbeam on Polkadot.^[8]​^[9] To support this role, Moonriver offered a full EVM implementation, Web3-compatible RPC endpoints, and bridges to Ethereum networks, which allowed Solidity-based decentralized applications (DApps) and tooling such as MetaMask, Hardhat, and Remix to be used with minimal changes.^[8]​^[9]​

The MOVR token underpinned Moonriver’s economic and governance model by metering gas for smart contract execution, incentivizing collators that produced blocks, paying transaction and transfer fees, and enabling on-chain governance participation, including proposing referenda and voting.^[8]​^[9] In a strategic shift, the Moonbeam Foundation announced a migration of MOVR from its native form on Moonriver to a Base ERC‑20 token via a custom bridge with a fixed 1:1 conversion rate, which was followed by Moonriver and Moonbeam entering maintenance-mode wind-down on August 1, 2026.^[14]​

History

Moonriver secured the second parachain slot on Kusama through a community-focused crowdloan that concluded on June 29, 2021, raising 205,935.0111 KSM from contributors in exchange for future MOVR rewards tied to the initial lease period.^[1][10][13] The crowdloan structure followed the standard Kusama and Polkadot model, where contributors locked KSM to back Moonriver’s slot bid and received MOVR rewards, with the locked KSM returned after the parachain lease expired.^[10][12] In total, 30% of MOVR’s network tokens were allocated to reward crowdloan participants, aligning Moonriver’s early token distribution with the community that funded its deployment.^[11]

Following the slot acquisition, the network’s launch process on Kusama proceeded as a multi-phase rollout that began with the minting of the genesis block on June 29, 2021 and culminated in the full launch and activation of EVM smart contract functionality, staking, and unrestricted token transfers on August 26, 2021.^[1][6] Throughout these phases, control of the network transitioned from a team-managed sudo key to MOVR token holders via on-chain governance, establishing Moonriver as a community-governed canary network for Moonbeam.^[5][4]

In a later strategic update, the Moonbeam Foundation announced that MOVR would migrate off the Moonriver parachain to Base as an ERC‑20 token using a dedicated migration bridge.^[14] The migration bridge offered a 1:1 conversion from native MOVR to Base MOVR and was available until July 31, 2026, after which users who had not bridged may be unable to move remaining tokens.^[14] As part of the same transition, Moonriver and Moonbeam entered maintenance mode at 00:00 UTC on August 1, 2026, at which point user-initiated transactions, including transfers and cross-chain messages, were no longer processed while block production continued for a limited wind‑down period.^[14][2]

Phase 0

Phase 0 began on June 29, 2021, when the genesis block was minted and the Moonriver network operated in a centralized configuration.^[1] During this initial phase, the Moonbeam team controlled governance and infrastructure while the network’s core functionality and stability were validated.^[1]

Phase 1

Phase 1 began on July 9, 2021, starting the decentralization process.^[3] In this phase, the team added third-party collators from outside of the Moonbeam organization to expand the collator set.^[3] The goal was to ensure that a decentralized group of collators could reliably produce blocks and interact correctly with the Kusama Relay Chain validators while maintaining network stability.^[3]

Phase 2

Phase 2 began on July 23, 2021, and focused on enabling and testing Moonriver’s on-chain governance.^[4] During this phase, token holders gained the ability to participate directly in governing the network, allowing the community-led governance model to be exercised under live conditions.^[4] The phase ensured that all governance systems, including referenda and council mechanics, worked as expected before the network transitioned to full community control.^[4]

Phase 3

Phase 3 started on August 5, 2021, when the sudo (superuser) key was removed and control of the Moonriver network was handed over to MOVR token holders.^[5] During this phase, crowdloan rewards functionality was introduced, performance improvements were applied, and bug fixes were implemented as the network transitioned fully to community governance.^[5]

Phase 4

Phase 4 marked the full launch of the Moonriver network on the Kusama relay chain and was announced on August 26, 2021.^[6][7] During this phase, MOVR token transfers and reward claiming were enabled, staking services for MOVR were activated, and full EVM functionality and smart contract deployment were opened to users, making Moonriver the first fully functioning EVM deployment on Kusama.^[6] Crowdloan rewards were distributed to participants, and the chain moved to being governed by token holders through its on-chain governance system.^[6]

Design and Mechanism

Moonriver was built on Substrate as a parachain connected to the Kusama relay chain, inheriting shared security and consensus from Kusama while focusing on Ethereum compatibility and smart contract execution.^[9] Its design included a full Ethereum Virtual Machine implementation and a Web3-compatible API, which enabled developers to deploy existing Solidity contracts and DApp frontends with minimal changes and to use familiar Ethereum tooling such as MetaMask, Remix, Hardhat, Truffle, and web3.js.^[9][8] Bridges connected Moonriver to Ethereum and other networks, allowing assets and liquidity to move between ecosystems and supporting use cases in DeFi, NFTs, and other application categories.^[9]

Block production on Moonriver was performed by collators, which gathered transactions and produced blocks that were finalized by Kusama’s validators as part of the parachain architecture.^[9] MOVR was used to incentivize these collators, aligning their economic interests with network performance and availability.^[8] The network used an on-chain governance system in which MOVR holders participated directly in protocol upgrades and parameter changes, with referenda and council elections executed through the chain’s governance modules.^[9] This combination of Kusama’s shared security, a collator-based parachain architecture, and Ethereum-compatible execution was intended to provide a practical environment for experimenting with features that might later be promoted to Moonbeam.

Tokenomics and Distribution

MOVR is the native utility token of the Moonriver network and was used to support gas metering for smart contract execution, pay transaction and transfer fees, incentivize collators that maintained the network’s block production, and power Moonriver’s on-chain governance processes such as proposing referenda, electing council members, and voting.^[8][9] Moonriver’s economic model was designed around an initial total supply of 10 million MOVR and a target annual inflation rate of 5% to support ongoing network incentives.^[9] Over time, this inflation has increased the circulating and total supply beyond the initial 10 million MOVR.^[2]

A significant portion of MOVR was allocated to community participants through a Kusama crowdloan that supported Moonriver’s initial parachain slot lease, with those contributors receiving rewards in MOVR for locking KSM during the lease period.^[10][11] Additional allocations were made to the treasury and the Moonbeam ecosystem to fund development, grants, and long-term ecosystem growth.^[8] MOVR’s role was evolving as the token migrated from the Moonriver parachain to Base via a 1:1 bridge, after which the ERC‑20 MOVR on Base became the primary representation managed by foundation-controlled smart contracts.^[14]

Governance

Moonriver used an on-chain governance system in which MOVR token holders played a central role in managing the network.^[9] Holders could propose referenda, vote on protocol changes, and participate in electing council members, giving the community direct influence over upgrades and key parameters.^[8][9] The removal of the sudo key during the launch process completed the transition from a team-controlled network to one governed by MOVR holders through these on-chain mechanisms.^[5]

As part of the announced wind‑down, Moonriver entered maintenance mode on August 1, 2026, after which user-initiated transactions, including governance extrinsics, were no longer processed while block production continued in a limited, read‑only state.^[14][2] Governance of MOVR’s future utility and integrations is expected to shift primarily to the ERC‑20 representation on Base, managed through foundation-controlled contracts and any governance processes defined for that environment.^[14]

Partnerships

Moonriver integrated with a broad set of Ethereum developer tools, including MetaMask, Remix, Truffle, web3.js, and ethers.js, to provide a familiar environment for developers moving applications from Ethereum.^[9] It supported oracle providers such as Chainlink, Band Protocol, Razor, and DIA, as well as infrastructure and analytics services like OnFinality and Covalent.^[9] In addition, Moonriver interacted with other parachains and projects in the Polkadot and Kusama ecosystems, including networks focused on DeFi and asset issuance, and offered bridges via third-party protocols such as ChainBridge, Ren, Interlay, Snowfork, and Axelar to connect with external chains.^[9] These integrations supported a range of applications, including automated market makers, lending platforms, and NFT marketplaces, that leveraged Moonriver’s EVM compatibility and Kusama connectivity.^[9]

Network Wind-Down and Maintenance Mode

Moonbeam and Moonriver entered maintenance mode at 00:00 UTC on August 1, 2026, as part of the planned wind-down of the Moonriver parachain.^[14][2] From that time, user-initiated transactions on Moonriver, including transfers, staking operations, cross-chain XCM messages, governance actions, and other extrinsics, were no longer processed, while block production continued to preserve read-only access during the final operational wind-down.^[14][2] The duration of this maintenance period is described as dependent on technical and operational considerations and subject to future updates.^[14]

In parallel with the network wind-down, the MOVR token migrated from its native representation on the Moonriver parachain to an ERC‑20 MOVR token on the Base network via an official 1:1 migration bridge operated by the Moonbeam Foundation.^[14] The migration bridge operated through July 31, 2026, after which the Moonriver chain entered maintenance mode the following day.^[14] The Moonbeam Foundation’s strategic update warns that funds left in on-chain protocols on Moonriver during the wind-down, including liquidity positions, lending markets, staking contracts, and other DeFi applications, may become permanently inaccessible once maintenance mode begins.^[14] The Moonriver team later communicated that the migration period would officially end on September 30, 2026, and that valid claims submitted within the migration window would continue to be processed.^[15]