MFX Network · Mainnet

MFX Network — Integration & Listing Guide

This page summarizes the technical parameters of the MFX Network mainnet for exchanges, wallets, explorers and other integrators. All values below refer to the current production network.

AT A GLANCE

Core network parameters

EVM-compatible mainnet with a single canonical RPC endpoint and explorer.

Network name MFX Network
Type EVM-compatible mainnet
Chain ID 2064 (0x810)
Native token MFX (18 decimals)
RPC endpoint https://rpc.mfx.network/rpc
Block explorer https://explorer.mfx.network
Docs https://docs.mfx.network
Wallet https://wallet.mfx.network
GitHub github.com/mfx-network

FOR WALLETS

Standard EVM chain params

This is the configuration most wallets and dapps expect.

MetaMask / EVM chain addNetwork params
{
  "chainId": "0x810",              // 2064
  "chainName": "MFX Network",
  "nativeCurrency": {
    "name": "MFX",
    "symbol": "MFX",
    "decimals": 18
  },
  "rpcUrls": [
    "https://rpc.mfx.network/rpc"
  ],
  "blockExplorerUrls": [
    "https://explorer.mfx.network"
  ]
}

For chainlist.org or similar registries you can use the same values. If you need a signed JSON file or official confirmation, please contact us via email.

RPC & EXPLORER

Public RPC

The MFX Network exposes a single public RPC endpoint for integrators:

The endpoint follows the Ethereum JSON-RPC specification for standard methods (e.g. eth_getBlockByNumber, eth_call, eth_getLogs, etc.).

Block explorer

HEALTH & MONITORING

Public health endpoints are available for basic uptime checks and integration with monitoring systems:

These endpoints are lightweight and suitable for periodic checks from exchanges or wallets that want to monitor connectivity to MFX infrastructure.

VALIDATORS & NODES

If you need to run your own full node or validator for deeper integration, please see:

CONTACT & SUPPORT

For listing, integration support or technical questions, please contact:

When reaching out, it is helpful to include:

ADDITIONAL RESOURCES