Connecting to BEVM: Networks, RPC Endpoints & APIs

BEVM provides multiple network environments for developers to build and deploy decentralized applications. These include the BEVM Mainnet, Testnet, and Canary Network, each with its own RPC endpoints, WebSocket connections, and explorers.

• BEVM Mainnet (Chain-ID: 11501) is the primary network for production use, with BTC as the native asset. It supports multiple RPC endpoints (rpc-mainnet-1.bevm.io, rpc-mainnet-2.bevm.io) and a WebSocket (wss://rpc-mainnet-1.bevm.io/ws).
• BEVM Testnet (Chain-ID: 11503) is used for development and testing, accessible via https://testnet.bevm.io and its WebSocket endpoint.
• BEVM Canary Network (Chain-ID: 1501) serves as a preliminary mainnet, offering RPC (rpc-canary-1.bevm.io, rpc-canary-2.bevm.io) and WebSocket (wss://rpc-canary-1.bevm.io/ws) connections.

The highest supported Solidity version is 0.8.13, and developers can integrate BEVM networks via Chainlist for quick configuration.

Running a BEVM Node and Setting Up Your Own RPC Server

For developers working with BEVM, managing a dedicated RPC server ensures better reliability, decentralization, and security compared to relying on public endpoints. Running your own node minimizes risks like centralization and maintenance issues, reducing potential points of failure.

To set up a BEVM RPC server, you need to configure an archive node with a config.json file specifying key parameters:

{
  "chain": "testnet",
  "unsafe-rpc-external": true,
  "rpc-methods": "unsafe",
  "rpc-port": 8087,
  "rpc-cors": "all"
}

This configuration launches a BEVM archive node on the testnet, exposing a WebSocket (WS) and HTTP endpoint on port 8087. Running a private RPC server allows projects to interact efficiently with BEVM while maintaining greater control over their infrastructure.