Moonriver RPC Endpoints & Dedicated Nodes

Moonriver is a companion network to Moonbeam and serves as an incentivized canary network on Kusama. It provides a full Ethereum-like environment, supporting Solidity smart contracts and EVM-compatible tools. New code ships to Moonriver first, where it can be tested under real economic conditions before being deployed to Moonbeam on Polkadot.

Why Use Moonriver RPC?

Developers building on Moonriver need reliable RPC endpoints to interact with the blockchain. Common use cases include:

• dApps and DeFi protocols: Read on-chain data and submit transactions.
• Wallets: Enable users to send MOVR tokens and interact with smart contracts.
• Analytics and indexing: Pull historical data for dashboards and metrics.
• Bots and automation: Monitor events and trigger actions.

Moonriver RPC Endpoints on OnFinality

OnFinality provides managed Moonriver RPC endpoints that are production-ready. Key features include:

• HTTP and WebSocket support: Both transport protocols are available.
• Archive and trace data: Access full historical state and trace APIs for debugging.
• Global regions: Endpoints are available in N. Virginia and Hong Kong.
• Scalable plans: From shared API endpoints to dedicated nodes for high-throughput workloads.

Dedicated Moonriver Nodes

For teams that need more predictable resource planning, OnFinality offers dedicated Moonriver nodes. Benefits include:

• Isolated resources: No sharing with other users.
• Custom configuration: Tune node parameters to your needs.
• Full control: Access to debug and trace APIs.
• Observability: Monitor node health and performance metrics.

How to Connect to Moonriver

1. Create or sign in to your OnFinality account.
2. Select Moonriver from the supported networks list.
3. Create an API endpoint or deploy a dedicated node.
4. Test the endpoint using the example method chain_getBlock.
5. Monitor request usage, errors, and limits before moving critical traffic.

Public vs. Private Moonriver RPC

Public endpoints are suitable for lightweight testing, but for production workloads, authenticated endpoints offer better reliability, clearer limits, and request analytics.

Moonriver RPC and developer resources

A useful Moonriver RPC page should make the connection path, supported capabilities, and production planning trade-offs clear before a developer opens the dashboard.

Best fit: mainnet production workflows for ecosystem apps, validators, and infra teams.

What builders usually check first:

• Read blocks, storage, events, and governance or staking data from Substrate-based chains.
• Support wallets, indexers, parachain apps, collators, validators, and analytics services.
• Plan node infrastructure when the workload needs isolated resources or chain-specific operations.

Supported capability notes:

• Authenticated Moonriver RPC/API access for ecosystem apps, validators, and infra teams.
• Flexible HTTP and WebSocket access for app, backend, and integration workflows.
• Archive-capable workflows when the product needs older chain state.
• Trace-ready workflows for teams that need to inspect execution paths.
• Managed node options for workloads that outgrow shared endpoint access.

Decision notes:

• Environment: mainnet. Protocol family: Substrate JSON-RPC.
• Flexible HTTP and WebSocket access is listed for supported app and backend workflows.
• Archive support is available for historical state or older chain-data queries.
• Trace support is available for transaction debugging and execution analysis.
• Dedicated node options are available when the workload needs isolated resources or more operational control.

A quick connection check usually starts with chain_getBlock, then moves into the exact methods your wallet, dashboard, bot, indexer, or backend service needs.

Planning the next step:

• Shared RPC is usually enough for early integration, prototypes, and moderate app traffic.
• Consider dedicated nodes when traffic becomes sustained, workloads are latency-sensitive, or isolation and monitoring become operational requirements.

Next steps:

• Create or manage RPC endpoints
• Review RPC pricing
• Explore dedicated nodes
• Read the RPC provider selection guide