Haven1

Add Haven1 to Your Wallet — MetaMask, OKX, Rabby, Trust Wallet

Chain ID: 8811·Symbol: H1·TVL:

Haven1 is an EVM-compatible blockchain with Chain ID 8811 and native token H1. This page lets you add Haven1 to MetaMask, Rabby Wallet, OKX Wallet or Trust Wallet in one click — no manual Chain ID or RPC entry required.

RPC Endpoints
https://rpc.haven1.org

Block Explorer

What is Haven1?

Haven1 is an EVM (Ethereum Virtual Machine) compatible blockchain network. Any EVM wallet — MetaMask, Rabby, OKX Wallet, Trust Wallet, Coinbase Wallet — can connect and transact on Haven1 once you add the network configuration.

Why do you need to add Haven1 to your wallet?

MetaMask and most wallets only come pre-configured with Ethereum Mainnet. To transact, swap tokens, or use dApps on Haven1, you need to add the network first. Entering an incorrect Chain ID or RPC can put your assets at risk. Use the "Add to wallet" button above — data sourced directly from chainid.network, the canonical Ethereum chain registry.

How to add Haven1 to your wallet

  1. 1

    Click Add to wallet

    Press the "Add to wallet" button above. MetaMask, OKX Wallet, Rabby Wallet or Trust Wallet will show a popup asking you to confirm adding the Haven1 network.

  2. 2

    Confirm in your wallet

    Your wallet shows the Haven1 network details: Chain ID 8811, native token H1. Verify the Chain ID is correct, then click "Approve" or "Add Network".

  3. 3

    Switch to the new network

    After confirming, your wallet automatically switches to Haven1. You can start transacting right away — you will need H1 to pay gas fees.

Haven1 network technical details

To add manually, go to Settings → Networks → Add Network in MetaMask (or your wallet's equivalent) and enter the details below:

NameHaven1
Chain ID8811
Native tokenH1
Decimals18
RPC Endpointhttps://rpc.haven1.org
Block Explorerhttps://explorer.haven1.org

Important notice

  • Always verify Chain ID 8811 before confirming — attackers sometimes create fake networks with similar names but different Chain IDs
  • You need H1 tokens in your wallet to pay gas fees for transactions on Haven1
  • Data on this page is sourced from chainid.network — the community-verified Ethereum chain registry
  • If the "Add to wallet" button doesn't work, your wallet may not support wallet_addEthereumChain — add the network manually using the details below

Frequently asked questions

Is it safe to add Haven1 to MetaMask?
Yes, if you use the "Add to wallet" button on this page. Data is sourced from chainid.network — the community-audited Ethereum registry. Adding a network does not expose your private key or grant any permissions to the dApp.
What is Haven1 Chain ID?
The Chain ID of Haven1 is 8811. This unique number identifies the network and prevents MetaMask and other EVM wallets from mixing up transactions across different chains.
Do I need H1 tokens to use Haven1?
Yes. Every transaction on Haven1 requires H1 to pay gas fees. You can purchase H1 on exchanges and bridge it to Haven1, or use a faucet if this is a testnet.
What is the Haven1 RPC endpoint?
An RPC endpoint is the server address your wallet uses to communicate with the Haven1 blockchain — sending transactions, reading balances, and checking state. One popular Haven1 RPC is https://rpc.haven1.org. This page shows live latency for each RPC so you can pick the fastest one.
My wallet says Haven1 already exists when I click Add — what do I do?
That's completely normal. If Haven1 is already in your wallet, it will simply switch to that network instead of adding a duplicate — no error or conflict.
I added Haven1 but the network won't load — what's wrong?
The most common cause is a broken or overloaded RPC endpoint. Your wallet uses RPC to connect to the blockchain — if the RPC is down, the network won't load even if it was added correctly. Fix: copy a different RPC from the list above (prefer green low-latency ones), then go to Settings → Networks in your wallet and replace the old RPC with the new one. Watch the tutorial video above for step-by-step instructions on updating your RPC.