How to add Flare network to MetaMask? (RPC settings)

Flare Network Overview

1. Flare Network is a Turing-complete smart contract platform that operates as a Layer-1 blockchain, designed to bring interoperability and decentralized finance capabilities to assets from non-smart-contract blockchains like XRP Ledger and Litecoin.

2. It introduces the concept of state connectivity, enabling trustless retrieval of data from external systems without relying on centralized oracles.

3. The native utility token, FLR, is used for staking, governance, and transaction fees across the network.

4. Flare’s architecture includes the Songbird testnet as a canary deployment environment before mainnet upgrades, allowing developers to validate integrations in advance.

5. Its consensus mechanism combines Federated Byzantine Agreement with a modified version of Avalanche, ensuring high throughput and finality within seconds.

MetaMask Compatibility Requirements

1. MetaMask must be updated to version 10.22.0 or higher to support custom EVM-compatible chains with proper chain ID validation and asset detection.

2. Users need to disable “Privacy Mode” in MetaMask Settings → Security & Privacy if they wish to see accurate token balances and transaction history on Flare explorers.

3. Hardware wallet support via MetaMask is limited to Ledger devices; Trezor does not yet expose Flare-specific derivation paths through MetaMask’s interface.

4. Custom RPC endpoints must include correct chain ID, block explorer URL, and currency symbol — deviations will cause failed transactions or balance mismatches.

5. MetaMask mobile app supports Flare only on iOS 16+ and Android 12+, with WebView restrictions preventing certain dApp interactions unless “Advanced” mode is enabled.

RPC Configuration Steps

1. Open MetaMask and click the network selector dropdown located at the top of the interface.

2. Select “Add Network” and then choose “Add a network manually”.

3. Enter Network Name: Flare Mainnet.

4. Input New RPC URL: https://flare-api.flare.network/ext/C/rpc.

5. Set Chain ID: 14, which is the official EVM-compatible identifier assigned by Flare Foundation.

6. Specify Currency Symbol: FLR and Block Explorer URL: https://flare-explorer.flare.network.

7. Confirm submission — MetaMask will verify endpoint responsiveness and display “Flare Mainnet” in the network list upon success.

Token Integration and Asset Management

1. FLR tokens held natively on Flare do not auto-appear in MetaMask; users must manually add the token contract address: 0x12Cd132F98F9bBf149E10c2A13C0e3d61435096a.

2. Wrapped assets such as WFLR or sFLR require separate contract addresses and may not be recognized unless imported individually using the “Import Tokens” function.

3. Cross-chain bridges like Flare’s Songbird Bridge or third-party services like Multichain generate unique deposit addresses per user session — reusing old addresses risks irreversible loss.

4. MetaMask’s “Activity” tab displays Flare transactions only after confirmation on-chain; pending status may persist longer than Ethereum due to different finality thresholds.

5. Gas estimation for Flare transactions defaults to 21000 units for simple transfers but jumps significantly for contract calls — users should review gas price (in FLR/Gwei) before confirming.

Frequently Asked Questions

Q: Why does MetaMask show “Invalid RPC URL” when I paste https://flare-api.flare.network/ext/C/rpc?A: This occurs if the trailing slash is omitted or if an extra space exists before or after the URL. Ensure exact syntax and clear browser cache before retrying.

Q: Can I use the same seed phrase for Flare and Ethereum without conflicts?A: Yes — Flare uses standard BIP-39 derivation with m/44'/60'/0'/0, identical to Ethereum, so no additional backup is required.

Q: Is it safe to interact with Flare dApps through MetaMask if they request signature requests with arbitrary messages?A: No — Flare dApps should never ask for signatures on unverified payloads. Always cross-check message content against official documentation or verified contracts.

Q: Why does my FLR balance remain zero after bridging from Songbird?A: Bridging requires two confirmations — one on Songbird and one on Flare. Wait for both to finalize and refresh MetaMask’s token list manually via “Edit Token” → “Reset Balance”.