# MFX Network — Listing & Integration Kit

This document summarizes the key information needed to list or integrate the **MFX Network** (EVM-compatible mainnet) on exchanges, wallets and other services.

All parameters here reflect the current production network.  
For the most up-to-date technical details, please refer to:  
**https://docs.mfx.network/integration.html**

---

## 1. Project overview

- **Name:** MFX Network  
- **Type:** EVM-compatible L1 mainnet  
- **Use cases:** value transfer, on-chain applications, tokenization and DeFi use-cases within the MFX ecosystem.  
- **Consensus / Security:** PoA/validator-based network operated by the MFX team and ecosystem partners.

If you need a short project description for your UI, you can use the following text as a base (and adapt it to your style):

> **MFX Network** is an EVM-compatible mainnet with Chain ID 2064, focused on streamlined integrations and predictable infrastructure for exchanges, wallets and analytics providers.  
> It provides a standard Ethereum JSON-RPC interface, public explorer, health endpoints, and ready-to-use node bootstrap tools for validators and infrastructure partners.

---

## 2. Core network parameters

- **Network name:** MFX Network  
- **Chain ID:** `2064` (`0x810`)  
- **EVM compatibility:** yes (standard Ethereum JSON-RPC)  
- **Native token:** `MFX` (18 decimals)  
- **Public RPC (HTTPS):** `https://rpc.mfx.network/rpc`  
- **Explorer:** `https://explorer.mfx.network`  
- **Docs:** `https://docs.mfx.network`  

For a structured, always up-to-date view of these parameters (including example JSON for wallets), please see:  
**https://docs.mfx.network/integration.html**

---

## 3. RPC & explorer

**Public RPC endpoint**

- Base URL: `https://rpc.mfx.network/rpc`  
- Protocol: Ethereum JSON-RPC over HTTPS  
- Common methods: `eth_blockNumber`, `eth_getBlockByNumber`, `eth_getTransactionByHash`, `eth_call`, `eth_sendRawTransaction`, etc.

**Explorer**

- Web UI: `https://explorer.mfx.network`  
- Example pages:
  - Address: `https://explorer.mfx.network/address/<ADDRESS>`  
  - Transaction: `https://explorer.mfx.network/tx.html?hash=<TX_HASH>`  
  - Block: `https://explorer.mfx.network/block.html?height=<BLOCK_NUMBER>`

---

## 4. Health & monitoring

For basic uptime checks and integration with monitoring systems, the following endpoints are available:

- **API health:** `https://api.mfx.network/health`  
- **Explorer health:** `https://explorer.mfx.network/health`  
- **Wallet health:** `https://wallet.mfx.network/health`  

These endpoints are lightweight and designed to be safe for frequent checks from exchanges, wallets and monitoring providers.

---

## 5. Wallet & dApp integration

For wallets and dApps that support custom EVM chains, the standard configuration is:

```json
{
  "chainId": "0x810",
  "chainName": "MFX Network",
  "nativeCurrency": {
    "name": "MFX",
    "symbol": "MFX",
    "decimals": 18
  },
  "rpcUrls": ["https://rpc.mfx.network/rpc"],
  "blockExplorerUrls": ["https://explorer.mfx.network"]
}
```

For browser wallets (e.g. MetaMask), this JSON can be used as-is when adding a custom network.

---

## 6. Validators & nodes

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

- **Validator onboarding guide (Markdown):** `/MFX_VALIDATOR_ONBOARDING.md` (also served via docs)

- **Node bootstrap repository (GitHub):** https://github.com/mfx-network/mfx-node-bootstrap

These resources describe how to deploy an MFX node from scratch on a Linux server using the official bootstrap scripts and systemd units.

---

## 7. Official integration landing

The canonical, always up-to-date source for integration parameters is:

**Integration & listing info:**  
https://docs.mfx.network/integration.html

When filling in forms (Chainlist, wallet/DEX listing forms, etc.), we recommend linking to this URL as "Official technical integration reference".

---

## 8. Contact & support

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

- **Email (technical / listing):** dev@mfx.network

- **GitHub (issues / PRs):** https://github.com/mfx-network

When reaching out, it is helpful to include:

- Your platform type (CEX, DEX, wallet, explorer, analytics, etc.)
- Expected integration scope (deposits/withdrawals, swaps, portfolio, RPC-read only, etc.)
- Any specific requirements (RPC limits, additional APIs, formal documents, additional endpoints).

---

This document is maintained by the MFX Network team.  
If you notice any outdated parameters, please contact us at dev@mfx.network.