Skip to content



In June 2021, Moonriver first launched as a parachain on the Kusama network. Moonriver is a sister network of Moonbeam, and provides an environment to test new code under real economic conditions. Developers now have access to start experimenting and building on an incentivized canary network connected to Kusama.

In order to collect as much feedback as possible and provide fast issue resolution, you can check out the dedicated Moonriver section on Discord.

Initial Configurations

Currently, Moonriver has the following configurations:

  • Runs as a parachain connected to the Kusama relay chain
  • Has an active set of 72 collators
  • Has infrastructure providers that provide API endpoints to connect to the network. Projects can also run their own node to have access to their own private endpoints

Moonriver Diagram

Some important variables/configurations to note include:

Variable Value
Minimum gas price 1.25 Gwei*
Target block time 6 seconds
Block gas limit 60,000,000
Transaction gas limit 52,000,000
Variable Value
Minimum delegation stake 5 MOVR
Maximum delegators per candidates 300
Maximum delegations per account 100
Round 600 blocks (2 hours)
Bond duration delegation takes effect in the next round (funds are withdrawn immediately)
Unbond duration 24 rounds

*Read more about token denominations


As of runtime 3000, asynchronous backing has been enabled on all Moonbeam networks. As a result, the target block time was reduced from 12 seconds to 6 seconds, which may break some timing-based assumptions.

Additionally, the block and transaction gas limits increased by 4x on Moonriver.

Network Endpoints

Moonriver has two types of endpoints available for users to connect to: one for HTTPS and one for WSS.

If you're looking for your own endpoints suitable for production use, you can check out the Endpoint Providers section of our documentation. Otherwise, to get started quickly you can use one of the following public HTTPS or WSS endpoints:

Provider RPC URL Limits
80 req/sec
20 req/sec
40 req/sec
32 req/sec
Provider RPC URL Limits
80 req/sec
20 req/sec
40 req/sec
32 req/sec

Quick Start

Before getting started, make sure you've retrieved your own endpoint and API key from one of the custom Endpoint Providers. Then for the Web3.js library, you can create a local Web3 instance and set the provider to connect to Moonriver (both HTTP and WS are supported):

const { Web3 } = require('web3'); // Load Web3 library
// Create local Web3 instance - set Moonriver as provider
const web3 = new Web3('INSERT_RPC_API_ENDPOINT'); // Insert your RPC URL here

For the Ethers.js library, define the provider by using ethers.JsonRpcProvider(providerURL, {object}) and setting the provider URL to Moonriver:

const ethers = require('ethers'); // Load Ethers library

const providerURL = 'INSERT_RPC_API_ENDPOINT'; // Insert your RPC URL here

// Define provider
const provider = new ethers.JsonRpcProvider(providerURL, {
    chainId: 1285,
    name: 'moonriver'

Any Ethereum wallet should be able to generate a valid address for Moonbeam (for example, MetaMask).

Chain ID

Moonriver chain ID is: 1285, or 0x505 in hex.


You can see current Moonriver telemetry information by visiting Polkadot's Telemetry dashboard.


The tokens on Moonriver will also be called Moonriver (MOVR). Check out the Moonbeam Foundation site for more information on the Moonriver token.

Token Denominations

The smallest unit of Moonriver, similarly to Ethereum, is a Wei. It takes 10^18 Wei to make one Moonriver. The denominations are as follows:

Unit Moonriver (MOVR) Wei
Wei 0.000000000000000001 1
Kilowei 0.000000000000001 1,000
Megawei 0.000000000001 1,000,000
Gigawei 0.000000001 1,000,000,000
Micromoonriver 0.000001 1,000,000,000,000
Millimoonriver 0.001 1,000,000,000,000,000
Moonriver 1 1,000,000,000,000,000,000
Kilomoonriver 1,000 1,000,000,000,000,000,000,000

Proof of Stake

The Moonriver network is a fully decentralized Delegated Proof of Stake network where users of the network can delegate collator candidates to produce blocks and earn rewards. It uses the Nimbus framework framework for parachain consensus. The number of candidates in the active set will be subject to governance. The active set will consist of the top candidates by stake, including delegations.


Some precompiles are yet to be included. You can check a list of supported precompiles on the Canonical Contract page. However, all built-in functions are available.

Last update: June 24, 2024
| Created: June 30, 2021