Chains Quickstart

This docs section provides the list of all chains available on RPC Service (opens in a new tab). Each chain in the list has the following information structure:

Overview —— Networks —— Adding to MetaMask —— Methods —— API Querying

• Overview — chain description based on official docs with quicklinks to chain's website, docs, and GitHub.
• Networks — networks (Mainnet/Testnet) and protocols (HTTPS/WSS) we support for each chain.
• Adding to MetaMask — using Ankr as the blockchain provider for MetaMask.
• Methods — supported (link to the chain's API Reference) and unsupported methods.
• API Querying — code snippets with basic requests in various languages and the corresponding JSON responses.

Chains supported

Find the chain you require and go to its docs section by clicking it.

Aptos

Aptos API is available on RPC Service (opens in a new tab).

The Aptos blockchain, designed with scalability, safety, reliability, and upgradability as key principles, to address blockchain challenges, such as frequent outages, high costs, low throughput limits, and security concerns. The Aptos blockchain has been developed over the past three years by over 350+ developers across the globe. It offers new and novel innovations in consensus, smart contract design, system security, performance, and decentralization. The combination of these technologies will provide a fundamental building block to bring web3 to the masses.

Official quick links: Website (opens in a new tab), Docs (opens in a new tab), GitHub (opens in a new tab)

Networks

• Mainnet (HTTPS)
• Testnet (HTTPS)

API methods

For Aptos, we support blockchain interaction via all the applicable methods except for those listed as unsupported.

Unsupported

/v1/spec, /v1/-/healthy

API querying

Request example

curl -X GET https://rpc.ankr.com/http/aptos/v1/ \
-H 'Content-Type: application/json'

Response example

{
  "chain_id": 0,
  "epoch": "32425224034",
  "ledger_version": "32425224034",
  "oldest_ledger_version": "32425224034",
  "ledger_timestamp": "32425224034",
  "node_role": "validator",
  "oldest_block_height": "32425224034",
  "block_height": "32425224034",
  "git_hash": "string"
}

Arbitrum

Arbitrum API is available on RPC Service (opens in a new tab).

Arbitrum is a side chain that runs parallel to Ethereum Mainnet. Also known as a Layer 2 (L2) scaling solution, Arbitrum improves transaction speeds and cost compared to the mainnet, making it an excellent solution for Ethereum developers.

By the Arbitrum we mean Arbitrum One which is the flagship Arbitrum mainnet chain; it is an Optimistic Rollup chain running on top of Ethereum Mainnet, and is open to all users. In an upgrade on 8/31, the Arbitrum One chain was upgraded to use the Nitro (opens in a new tab) tech stack, maintaining the same state.

Official quick links:

• Website (opens in a new tab), Docs (opens in a new tab), GitHub (opens in a new tab)
• Community treasury address (opens in a new tab) (0x8C316E77c4D4aBc461a074cf68c04DD666c57b42)

Networks

• Mainnet (HTTPS and WSS)

API methods

For Arbitrum, we support blockchain interaction via all the applicable methods except for those listed as unsupported.

Unsupported

HTTPS:

eth_newFilter, eth_getFilterChanges, eth_coinbase, eth_hashrate, eth_mining, eth_getWork,eth_submitWork, eth_submitHashrate, net_peerCount, eth_newBlockFilter, eth_newPendingTransactionFilter, eth_uninstallFilter, eth_getFilterLogs,

debug_*, personal_*, admin_*, clique_*, les_*, miner_*, engine_*, parity_*

WSS:

txpool_content, txpool_inspect, txpool_status, txpool_contentFrom

API querying

Request example

curl -X POST https://rpc.ankr.com/arbitrum \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc":"2.0",
      "method":"eth_blockNumber",
      "params": [],
      "id":1
    }'

Response example

{
  "jsonrpc":"2.0",
  "id":1,
  "result":"0x2484729"
}

Arbitrum Nova

Arbitrum Nova API is available on RPC Service (opens in a new tab).

Arbitrum Nova offers an ultra-low transaction costs with high security. Nova powers dapps with high transaction volumes that seek to drive costs even lower.

Official quick links: Website (opens in a new tab), Docs (opens in a new tab), GitHub (opens in a new tab)

Networks

• Mainnet (HTTPS and WSS)

API methods

For Arbitrum Nova, we support blockchain interaction via all the applicable methods except for those listed as unsupported.

Unsupported

HTTPS:

eth_newFilter, eth_getFilterChanges, eth_coinbase, eth_hashrate, eth_mining, eth_getWork,eth_submitWork, eth_submitHashrate, net_peerCount, eth_newBlockFilter, eth_newPendingTransactionFilter, eth_uninstallFilter, eth_getFilterLogs,

debug_*, personal_*, admin_*, clique_*, les_*, miner_*, engine_*, parity_*

WSS:

txpool_content, txpool_inspect, txpool_status, txpool_contentFrom

API querying

Request example

curl -X POST https://rpc.ankr.com/arbitrumnova \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc":"2.0",
      "method":"eth_blockNumber",
      "params": [],
      "id":1
    }'

Response example

{
    "jsonrpc": "2.0",
    "id": 1,
    "result": "0x257932"
}

Avalanche

Avalanche API is available on RPC Service (opens in a new tab).

Avalanche is an open-source platform for launching decentralized applications and enterprise blockchain deployments in one interoperable, highly scalable ecosystem. Avalanche is the first decentralized smart contracts platform built for the scale of global finance, with near-instant transaction finality. Ethereum developers can quickly build on Avalanche as Solidity works out-of-the-box.

Avalanche is an ecosystem that features three built-in blockchains: Exchange Chain (X-Chain) (opens in a new tab), Platform Chain (P-Chain) (opens in a new tab), and Contract Chain (C-Chain) (opens in a new tab).

Official quick links: Website (opens in a new tab), Docs (opens in a new tab), GitHub (opens in a new tab)

Networks

• Mainnet / Fuji Testnet:
  • Standard EVM API (HTTPS and WSS)
  • X-Chain (HTTPS)
  • P-Chain (HTTPS)
  • C-Chain (HTTPS)

Add networks to MetaMask

Using Ankr as the blockchain provider for MetaMask makes user interaction on Web3 not just easy and slick but also PRIVATE. We DON'T collect users' blockchain addresses — end of the story. Feel free to check our terms (opens in a new tab) and privacy policy (opens in a new tab) to be sure.

For MetaMask to interact with Avalanche through Ankr's infrastructure, add a required Avalanche network either via RPC Service's or MetaMask's UI.

Via RPC Service

To be added soon.

Via MetaMask

To add Avalanche Mainnet, follow these steps:

1. In MetaMask extension, click Networks (drop-down menu) > Add network to open Settings.

2. In the Add a network pane, click Add a network manually, then enter the network details and click Save:

   • Network name: Avalanche Mainnet by Ankr RPC.
   • New RPC URL: https://rpc.ankr.com/avalanche/.
   • Chain ID: 43114.
   • Currency symbol: AVAX.
   • Block explorer URL: https://snowtrace.io/.

Congrats — you've just added Ankr as the blockchain provider for MetaMask to interact with Avalanche Mainnet.

To add Avalanche Fuji Testnet, follow these steps:

1. In MetaMask extension, click Networks (drop-down menu) > Add network to open Settings.

2. In the Add a network pane, click Add a network manually, then enter the network details and click Save:

   • Network name: Avalanche Fuji Testnet by Ankr RPC.
   • New RPC URL: https://rpc.ankr.com/avalanche_fuji/.
   • Chain ID: 43113.
   • Currency symbol: AVAX.
   • Block explorer URL: https://testnet.snowtrace.io/.

Congrats — you've just added Ankr as the blockchain provider for MetaMask to interact with Avalanche Fuji Testnet.

API methods

For Avalanche, we support blockchain interaction via the following methods:

• Standard EVM methods
• P-Chain methods
• C-Chain methods
• X-Chain methods

Unsupported

HTTPS:

eth_newFilter, eth_getFilterChanges, eth_coinbase, eth_hashrate, eth_mining, eth_getWork, eth_submitWork, eth_submitHashrate, net_peerCount,

debug_*, personal_*, admin_*, clique_*, les_*, miner_*, engine_*, parity_*,

avm.createAddress, avm.exportKey, avm.importKey, avm.export, avm.import, avm.mint, avm.createFixedCapAsset, avm.createVariableCapAsset, avm.createNFTAsset, avm.mintNFT, avm.listAddresses, avm.send, avm.sendMultiple, avm.sendNFT, wallet.send, wallet.sendMultiple, wallet.issueTx, avax.export, avax.exportAVAX, avax.exportKey, avax.import, avax.importAVAX, avax.importKey,

platform.addDelegator, platform.addValidator, platform.addSubnetValidator, platform.createAddress, platform.createBlockchain, platform.createSubnet, platform.exportAVAX, platform.exportKey, platform.importAVAX, platform.importKey, platform.listAddresses

WSS:

txpool_content, txpool_inspect, txpool_status, txpool_contentFrom

API querying

Request example (Standard EVM)

curl -X POST https://rpc.ankr.com/avalanche \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc":"2.0",
      "method":"eth_blockNumber",
      "params": [],
      "id":1
    }'

Response example (Standard EVM)

{
  "jsonrpc":"2.0",
  "result":"0x155ea63",
  "id":1
}

Request example (P-Chain)

curl -X POST 'https://rpc.ankr.com/avalanche-p' \
-H 'Content-Type: application/json' \
-d '{
    "jsonrpc":"2.0",
    "id"     :1,
    "method" :"platform.getBalance",
    "params" :{
      "address":"P-custom18jma8ppw3nhx5r4ap8clazz0dps7rv5u9xde7p"
    }
}'

Response example (P-Chain)

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "txID": "NUPLwbt2hsYxpQg4H2o451hmTWQ4JZx2zMzM4SinwtHgAdX1JLPHXvWSXEnpecStLj"
  }
}

Request example (C-Chain)

curl -X POST 'https://rpc.ankr.com/avalanche-c' \
-H 'Content-Type: application/json' \
-d '{
    "jsonrpc":"2.0",
    "id"     :1,
    "method" :"avax.getAtomicTx",
    "params" : {
        "txID":"2GD5SRYJQr2kw5jE73trBFiAgVQyrCaeg223TaTyJFYXf2kPty",
        "encoding": "hex"
    }
}'

Response example (C-Chain)

{
  "jsonrpc": "2.0",
  "result": {
    "tx": "0x000000000000000030399d0775f450604bd2fbc49ce0c5c1c6dfeb2dc2acb8c92c26eeae6e6df4502b19d891ad56056d9c01f18f43f58b5c784ad07a4a49cf3d1f11623804b5cba2c6bf000000018212d6807a0ec9c1b26321418fe7a548180b5be728ce53fe7e98ab5755ed316100000001dbcf890f77f49b96857648b72b77f9f82937f28a68704af05da0dc12ba53f2db00000005000003a352a382400000000100000000000000018db97c7cece249c2b98bdc0226cc4c2a57bf52fc000003a3529edd17dbcf890f77f49b96857648b72b77f9f82937f28a68704af05da0dc12ba53f2db000000010000000900000001ead19377f015422fbb8731204fcf6d6879dd05146c2d5b5594e2fea2cb420b2f40bd457b71e279e547790b28fe5482f278c76cf39b2dce5c2e6c53352fe6827d002cc7d20d",
    "encoding": "hex",
    "blockHeight": "1"
  },
  "id": 1
}

Request example (X-Chain)

curl -X POST 'https://rpc.ankr.com/avalanche-x' \
-H 'Content-Type: application/json' \
-d '{
    "jsonrpc":"2.0",
    "id"     :1,
    "method" :"avm.getAddressTxs",
    "params" : {
      "address":"X-avax1dp6707ka34puejwg7ntnenxry98h37yvsqsm7f",
      "assetID":"AVAX",
      "pageSize":20
    }
}'

Response example (X-Chain)

{
  "jsonrpc": "2.0",
  "result": {
    "txIDs": ["SsJF7KKwxiUJkczygwmgLqo3XVRotmpKP8rMp74cpLuNLfwf6"],
    "cursor": "1"
  },
  "id": 1
}

Base

Base API is available on RPC Service (opens in a new tab).

Base is a secure, low-cost, developer-friendly Ethereum L2 built to bring the next billion users to web3.

Base is built on the Bedrock (opens in a new tab) release of the OP Stack (opens in a new tab), which is designed from the ground up to be as close to Ethereum as possible. Because of this, there are very little differences when it comes to building on Base and Ethereum.

However, there are still some minor discrepancies between the behavior of Base and Ethereum that you should be aware of when building apps on top of Base.

These minor differences include:

• Opcodes (opens in a new tab)
• Blocks (opens in a new tab)
• Network specifications (opens in a new tab)
• Transaction costs (opens in a new tab)

Official quick links: Website (opens in a new tab), Docs (opens in a new tab), GitHub (opens in a new tab)

Networks

• Mainnet (HTTPS and WSS)
• Goerli Testnet (HTTPS and WSS)

API methods

For Base, we support blockchain interaction via all the applicable methods except for those listed as unsupported.

Unsupported

HTTPS:

eth_newFilter, eth_getFilterChanges, eth_coinbase, eth_hashrate, eth_mining, eth_getWork,eth_submitWork, eth_submitHashrate, net_peerCount, eth_newBlockFilter, eth_newPendingTransactionFilter, eth_uninstallFilter, eth_getFilterLogs,

debug_*, personal_*, admin_*, clique_*, les_*, miner_*, engine_*, parity_*

WSS:

txpool_content, txpool_inspect, txpool_status, txpool_contentFrom

API querying

Request example

curl -X POST https://rpc.ankr.com/base \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc":"2.0",
      "method":"eth_blockNumber",
      "params": [],
      "id":1
    }'

Response example

{
    "jsonrpc": "2.0",
    "id": 1,
    "result": "0x459996"
}

BNB Smart Chain

BNB Smart Chain API is available on RPC Service (opens in a new tab).

BNB Smart Chain (BSC) (previously Binance Smart Chain) is an innovative solution to bring programmability and interoperability to Beacon Chain. BNB Smart Chain relies on a system of 21 active validators with Proof of Staked Authority (PoSA) consensus that can support short block time and lower fees. The most bonded validator candidates of staking will become validators and produce blocks. The double-sign detection and other slashing logic guarantee security, stability, and chain finality.

To the EVM compatibility that permits support for Ethereum tools and DApps, BNB Smart Chain adds smart contract functionality to the chain. The dual-chain architecture alongside Binance Chain enables sending and receiving of BNB and BEP2 tokens cross-chain.

Official quick links: Website (opens in a new tab), Docs (opens in a new tab), GitHub (opens in a new tab)

Networks

• Mainnet (HTTPS and WSS)
• Chapel Testnet (HTTPS and WSS)

Add networks to MetaMask

Using Ankr as the blockchain provider for MetaMask makes user interaction on Web3 not just easy and slick but also PRIVATE. We DON'T collect users' blockchain addresses — end of the story. Feel free to check our terms (opens in a new tab) and privacy policy (opens in a new tab) to be sure.

For MetaMask to interact with BNB Smart Chain through Ankr's infrastructure, add a required BNB Smart Chain network either via RPC Service's or MetaMask's UI.

Via RPC Service

To be added soon.

Via MetaMask

To add BNB Smart Chain Mainnet, follow these steps:

1. In MetaMask extension, click Networks (drop-down menu) > Add network to open Settings.

2. In the Add a network pane, click Add a network manually, then enter the network details and click Save:

   • Network name: BNB Smart Chain Mainnet by Ankr RPC.
   • New RPC URL: https://rpc.ankr.com/bsc/.
   • Chain ID: 56.
   • Currency symbol: BNB.
   • Block explorer URL: https://bscscan.com/.

Congrats — you've just added Ankr as the blockchain provider for MetaMask to interact with BNB Smart Chain Mainnet.

To add BNB Smart Chain Testnet, follow these steps:

1. In MetaMask extension, click Networks (drop-down menu) > Add network to open Settings.

2. In the Add a network pane, click Add a network manually, then enter the network details and click Save:

   • Network name: BNB Smart Chain Chapel Testnet by Ankr RPC.
   • New RPC URL: https://rpc.ankr.com/bsc_testnet_chapel/.
   • Chain ID: 97.
   • Currency symbol: BNB.
   • Block explorer URL: https://testnet.bscscan.com/.

Congrats — you've just added Ankr as the blockchain provider for MetaMask to interact with BNB Smart Chain Chapel Testnet.

API methods

For BNB Smart Chain, we support blockchain interaction via all the applicable methods except for those listed as unsupported.

Unsupported

HTTPS:

eth_newFilter, eth_getFilterChanges, eth_coinbase, eth_hashrate, eth_mining, eth_getWork,eth_submitWork, eth_submitHashrate, net_peerCount, eth_newBlockFilter, eth_newPendingTransactionFilter, eth_uninstallFilter, eth_getFilterLogs,

debug_*, personal_*, admin_*, clique_*, les_*, miner_*, engine_*, parity_*

WSS:

txpool_content, txpool_inspect, txpool_status, txpool_contentFrom

API querying

Request example

curl -X POST https://rpc.ankr.com/bsc \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc":"2.0",
      "method":"eth_blockNumber",
      "params": [],
      "id":1
    }'

Response example

{
  "jsonrpc":"2.0",
  "id":1,
  "result":"0x1601d3a"
}

BitTorrent Chain

BitTorrent Chain API is available on RPC Service (opens in a new tab).

BitTorrent Chain (BTTC) is a layer 2 scaling solution, BTTC strives to solve scalability and usability issues without compromising decentralization, and can make full use of the existing Ethereum developer community and ecosystem. BTTC is fully compatible with Ethereum, and existing applications on Ethereum can be easily migrated to this BTTC. In addition to the same experience as Ethereum, users can also enjoy ultra-high throughput and extremely low fees.

Users can conduct fast, low-cost, and safe transactions on BTTC, and assets on BTTC can be easily transferred between Ethereum, TRON, and BNB Smart Chain.

Official quick links: Website (opens in a new tab), Docs (opens in a new tab), GitHub (opens in a new tab)

Networks

• Mainnet (HTTPS and WSS)

Add networks to MetaMask

Using Ankr as the blockchain provider for MetaMask makes user interaction on Web3 not just easy and slick but also PRIVATE. We DON'T collect users' blockchain addresses — end of the story. Feel free to check our terms (opens in a new tab) and privacy policy (opens in a new tab) to be sure.

For MetaMask to interact with BitTorrent Chain through Ankr's infrastructure, add a required BitTorrent Chain network either via RPC Service's or MetaMask's UI.

Via RPC Service

To be added soon.

Via MetaMask

To add BitTorrent Chain Mainnet, follow these steps:

1. In MetaMask extension, click Networks (drop-down menu) > Add network to open Settings.

2. In the Add a network pane, click Add a network manually, then enter the network details and click Save:

   • Network name: BitTorrent Chain Mainnet by Ankr RPC.
   • New RPC URL: https://rpc.ankr.com/bttc/.
   • Chain ID: 199.
   • Currency symbol: BTT.
   • Block explorer URL: https://scan.bt.io/.

Congrats — you've just added Ankr as the blockchain provider for MetaMask to interact with BitTorrent Chain Mainnet.

API methods

For BitTorrent Chain, we support blockchain interaction via all the applicable methods except for those listed as unsupported.

Unsupported

HTTPS:

eth_newFilter, eth_getFilterChanges, eth_coinbase, eth_hashrate, eth_mining, eth_getWork,eth_submitWork, eth_submitHashrate, net_peerCount, eth_newBlockFilter, eth_newPendingTransactionFilter, eth_uninstallFilter, eth_getFilterLogs,

debug_*, personal_*, admin_*, clique_*, les_*, miner_*, engine_*, parity_*

WSS:

txpool_content, txpool_inspect, txpool_status, txpool_contentFrom

API querying

Request example

curl -X POST https://rpc.ankr.com/bttc \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc":"2.0",
      "method":"eth_blockNumber",
      "params": [],
      "id":1
    }'

Response example

{
  "jsonrpc":"2.0",
  "id":1,
  "result":"0xd91939"
}

Celo

Celo API is available on RPC Service (opens in a new tab).

Celo is a mobile-first blockchain designed to make decentralized financial (DeFi) tools and services accessible to anyone with a mobile phone.

Celo is a layer 1 protocol and blockchain platform. The Celo Mainnet is entirely separate from the Ethereum network. The Celo client originated as a fork of Ethereum Go language client, go-ethereum (opens in a new tab) (or geth). Celo has several significant differences, including a Proof-of-Stake-based Practical Byzantine Fault Tolerance (PBFT) consensus mechanism.

All the crypto assets on Celo have ERC-20 compliant interfaces, meaning that while they are not ERC-20 tokens on the Ethereum Mainnet, all familiar tooling and code that support ERC-20 tokens can be easily adapted for Celo assets, including Celo Native Asset (CELO) and Celo Dollar (cUSD).

Official quick links: Website (opens in a new tab), Docs (opens in a new tab), GitHub (opens in a new tab)

Networks

• Mainnet (HTTPS and WSS)

Add networks to MetaMask

Using Ankr as the blockchain provider for MetaMask makes user interaction on Web3 not just easy and slick but also PRIVATE. We DON'T collect users' blockchain addresses — end of the story. Feel free to check our terms (opens in a new tab) and privacy policy (opens in a new tab) to be sure.

For MetaMask to interact with Celo through Ankr's infrastructure, add a required Celo network either via RPC Service's or MetaMask's UI.

Via RPC Service

To be added soon.

Via MetaMask

To add Celo Mainnet, follow these steps:

1. In MetaMask extension, click Networks (drop-down menu) > Add network to open Settings.

2. In the Add a network pane, click Add a network manually, then enter the network details and click Save:

   • Network name: Celo Mainnet by Ankr RPC.
   • New RPC URL: https://rpc.ankr.com/celo/.
   • Chain ID: 42220.
   • Currency symbol: CELO.
   • Block explorer URL: https://explorer.celo.org/.

Congrats — you've just added Ankr as the blockchain provider for MetaMask to interact with Celo Mainnet.

API methods

For Celo, we support blockchain interaction via all the applicable methods except for those listed as unsupported.

Unsupported

HTTPS:

eth_newFilter, eth_getFilterChanges, eth_coinbase, eth_hashrate, eth_mining, eth_getWork,eth_submitWork, eth_submitHashrate, net_peerCount, eth_newBlockFilter, eth_newPendingTransactionFilter, eth_uninstallFilter, eth_getFilterLogs,

debug_*, personal_*, admin_*, clique_*, les_*, miner_*, engine_*, parity_*

WSS:

txpool_content, txpool_inspect, txpool_status, txpool_contentFrom

API querying

Request example

curl -X POST https://rpc.ankr.com/celo \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc":"2.0",
      "method":"eth_blockNumber",
      "params": [],
      "id":1
    }'

Response example

{
  "jsonrpc":"2.0",
  "id":1,
  "result":"0xf6b842"
}

Chiliz

Chiliz API is available on RPC Service (opens in a new tab).

Chiliz is an EVM-compatible Layer-1 blockchain built to serve as the foundation for an ever-growing ecosystem of enterprise-level sports and entertainment stakeholders developing blockchain-based user/fan experiences and B2B/B2C tools within their respective industries.

Official quick links: Website (opens in a new tab), Docs (opens in a new tab), GitHub (opens in a new tab)

Networks

• Mainnet (HTTPS and WSS)

API methods

For Chiliz, we support blockchain interaction via all the applicable methods except for those listed as unsupported.

Unsupported

HTTPS:

eth_newFilter, eth_getFilterChanges, eth_coinbase, eth_hashrate, eth_mining, eth_getWork,eth_submitWork, eth_submitHashrate, net_peerCount, eth_newBlockFilter, eth_newPendingTransactionFilter, eth_uninstallFilter, eth_getFilterLogs,

debug_*, personal_*, admin_*, clique_*, les_*, miner_*, engine_*, parity_*

WSS:

txpool_content, txpool_inspect, txpool_status, txpool_contentFrom

API querying

Request example

curl -X POST https://rpc.ankr.com/chiliz \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc": "2.0",
      "method": "eth_blockNumber",
      "params": [],
      "id": 1
    }'

Response example

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": "0x2a35d7"
}

Ethereum

Ethereum API is available on RPC Service (opens in a new tab).

Ethereum is a blockchain with a computer embedded in it. It is the foundation for building apps and organizations in a decentralized, permissionless, censorship-resistant way. Ethereum uses a proof-of-stake-based consensus mechanism (opens in a new tab).

Official quick links: Website (opens in a new tab), Docs (opens in a new tab), GitHub (opens in a new tab)

Networks

• Mainnet (HTTPS and WSS)
• Testnet:
  • Goerli (HTTPS and WSS)
  • Sepolia (HTTPS and WSS)

Add networks to MetaMask

Using Ankr as the blockchain provider for MetaMask makes user interaction on Web3 not just easy and slick but also PRIVATE. We DON'T collect users' blockchain addresses — end of the story. Feel free to check our terms (opens in a new tab) and privacy policy (opens in a new tab) to be sure.

For MetaMask to interact with Ethereum through Ankr's infrastructure, add a required Ethereum network either via RPC Service's or MetaMask's UI.

Via RPC Service

To be added soon.

Via MetaMask

To add Ethereum Mainnet, follow these steps:

1. In MetaMask extension, click Networks (drop-down menu) > Add network to open Settings.

2. In the Add a network pane, click Add a network manually, then enter the network details and click Save:

   • Network name: Ethereum Mainnet by Ankr RPC.
   • New RPC URL: https://rpc.ankr.com/eth/.
   • Chain ID: 1.
   • Currency symbol: ETH.
   • Block explorer URL: https://etherscan.io/.

Congrats — you've just added Ankr as the blockchain provider for MetaMask to interact with Ethereum Mainnet.

To add Ethereum Goerli Testnet, follow these steps:

1. In MetaMask extension, click Networks (drop-down menu) > Add network to open Settings.

2. In the Add a network pane, click Add a network manually, then enter the network details and click Save:

   • Network name: Ethereum Goerli Testnet by Ankr RPC.
   • New RPC URL: https://rpc.ankr.com/eth_goerli/.
   • Chain ID: 5.
   • Currency symbol: ETH.
   • Block explorer URL: https://goerli.etherscan.io/.

Congrats — you've just added Ankr as the blockchain provider for MetaMask to interact with Ethereum Goerli Testnet.

To add Ethereum Sepolia Testnet, follow these steps:

1. In MetaMask extension, click Networks (drop-down menu) > Add network to open Settings.

2. In the Add a network pane, click Add a network manually, then enter the network details and click Save:

   • Network name: Ethereum Sepolia Testnet by Ankr RPC.
   • New RPC URL: https://rpc.ankr.com/eth_sepolia/.
   • Chain ID: 11155111.
   • Currency symbol: ETH.
   • Block explorer URL: https://sepolia.etherscan.io/.

Congrats — you've just added Ankr as the blockchain provider for MetaMask to interact with Ethereum Sepolia Testnet.

API methods

For Ethereum, we support blockchain interaction via all the applicable methods except for those listed as unsupported.

Unsupported

HTTPS:

eth_newFilter, eth_getFilterChanges, eth_coinbase, eth_hashrate, eth_mining, eth_getWork,eth_submitWork, eth_submitHashrate, net_peerCount, eth_newBlockFilter, eth_newPendingTransactionFilter, eth_uninstallFilter, eth_getFilterLogs,

debug_*, personal_*, admin_*, clique_*, les_*, miner_*, engine_*, parity_*

WSS:

txpool_content, txpool_inspect, txpool_status, txpool_contentFrom

API querying

Request example

curl -X POST https://rpc.ankr.com/eth \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc": "2.0",
      "method": "eth_blockNumber",
      "params": [],
      "id": 1
    }'

Response example

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": "0xf3c34b"
}

Ethereum Beacon

Beacon API is available on RPC Service (opens in a new tab) upon switching on the Beacon toggle.

The Beacon Chain is a consensus layer that introduced a proof-of-stake (opens in a new tab) to Ethereum. The Beacon Chain mechanism is responsible for creating new blocks, making sure those new blocks are valid, and rewarding validators with ETH for keeping the network secure.

The Beacon Chain has several clients to choose from, serving the same purpose but built with slightly different focus in mind:

• Prysm (opens in a new tab) — focuses on usability, security, and reliability. Prysm is developed by Prysmatic Labs, a company with the sole focus on the development of their client.
• Lighthouse (opens in a new tab) — a client with a heavy focus on speed and security. Built by Sigma Prime, an information security and software engineering firm who have funded Lighthouse along with the Ethereum Foundation, ConsenSys, and private individuals.
• Nimbus (opens in a new tab) — strives to be as lightweight as possible in terms of resources used. This allows it to perform well on embedded systems, resource-restricted devices — including Raspberry Pis — and multi-purpose servers.

Official quick links: Website (opens in a new tab), Docs (opens in a new tab), GitHub (opens in a new tab), Eth Beacon Node API specification (opens in a new tab)

Networks

• Mainnet (HTTPS)
• Testnet:
  • Goerli (HTTPS)
  • Sepolia (HTTPS)

API methods

For the Beacon Chain, we support blockchain interaction via all the applicable methods except for those listed as unsupported.

Unsupported

/eth/v1/node/identity

API querying

Request example

curl -X GET "https://rpc.ankr.com/premium-http/eth_beacon/{your_token}/eth/v1/beacon/genesis" \
-H "Accept: application/json"

Response example

{
    "data": {
        "genesis_time": "1606824023",
        "genesis_validators_root": "0x4b363db94e286120d76eb905340fdd4e54bfe9f06bf33ff6cf5ad27f511bfe95",
        "genesis_fork_version": "0x00000000"
    }
}

Fantom

Fantom API is available on RPC Service (opens in a new tab).

Fantom is a fast, scalable, and secure layer-1 platform built on an aBFT consensus protocol. Fantom is permissionless, decentralized, open-source, and fully compatible with Ethereum.

Lachesis, its revolutionary aBFT consensus mechanism, allows Fantom to be much faster and cheaper than previous technologies, yet extremely secure.

Official quick links: Website (opens in a new tab), Docs (opens in a new tab), GitHub (opens in a new tab)

Networks

• Mainnet (HTTPS and WSS)
• Testnet (HTTPS and WSS)

Add networks to MetaMask

Using Ankr as the blockchain provider for MetaMask makes user interaction on Web3 not just easy and slick but also PRIVATE. We DON'T collect users' blockchain addresses — end of the story. Feel free to check our terms (opens in a new tab) and privacy policy (opens in a new tab) to be sure.

For MetaMask to interact with Fantom through Ankr's infrastructure, add a required Fantom network either via RPC Service's or MetaMask's UI.

Via RPC Service

To be added soon.

Via MetaMask

To add Fantom Mainnet, follow these steps:

1. In MetaMask extension, click Networks (drop-down menu) > Add network to open Settings.

2. In the Add a network pane, click Add a network manually, then enter the network details and click Save:

   • Network name: Fantom Mainnet by Ankr RPC.
   • New RPC URL: https://rpc.ankr.com/fantom/.
   • Chain ID: 250.
   • Currency symbol: FTM.
   • Block explorer URL: https://ftmscan.com/.

Congrats — you've just added Ankr as the blockchain provider for MetaMask to interact with Fantom Mainnet.

To add Fantom Testnet, follow these steps:

1. In MetaMask extension, click Networks (drop-down menu) > Add network to open Settings.

2. In the Add a network pane, click Add a network manually, then enter the network details and click Save:

   • Network name: Fantom Testnet by Ankr RPC.
   • New RPC URL: https://rpc.ankr.com/fantom_testnet/.
   • Chain ID: 4002.
   • Currency symbol: FTM.
   • Block explorer URL: https://testnet.ftmscan.com/.

Congrats — you've just added Ankr as the blockchain provider for MetaMask to interact with Fantom Testnet.

API methods

For Fantom, we support blockchain interaction via all the applicable methods except for those listed as unsupported.

Unsupported

HTTPS:

eth_newFilter, eth_getFilterChanges, eth_coinbase, eth_hashrate, eth_mining, eth_getWork,eth_submitWork, eth_submitHashrate, net_peerCount, eth_newBlockFilter, eth_newPendingTransactionFilter, eth_uninstallFilter, eth_getFilterLogs,

debug_*, personal_*, admin_*, clique_*, les_*, miner_*, engine_*, parity_*

WSS:

txpool_content, txpool_inspect, txpool_status, txpool_contentFrom

API querying

Request example

curl -X POST https://rpc.ankr.com/gnosis \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc":"2.0",
      "method":"eth_blockNumber",
      "params": [],
      "id":1
    }'

Response example

{
  "jsonrpc":"2.0",
  "result":"0x17d5c3d",
  "id":1
}

Filecoin

Filecoin API is available on RPC Service (opens in a new tab).

Filecoin is a peer-to-peer network that stores files, with built-in economic incentives and cryptography to ensure files are stored reliably over time.

Filecoin is built on top of the same software powering IPFS (opens in a new tab) protocol, which is a peer-to-peer distributed storage network that leverages content addressing (opens in a new tab) to allow permanent references to the data, and avoids relying on specific devices or cloud servers for addressing the content. Filecoin is different from IPFS because it has an incentive layer on top to incentivize contents to be reliably stored and accessed.

Filecoin enables several use cases, from Web3 native NFT and metaverse/game assets storage, incentivized permanent storage, to archiving Web2 datasets as a cheaper alternative to cloud storage.

Official quick links: Website (opens in a new tab), Docs (opens in a new tab), GitHub (opens in a new tab)

Networks

• Mainnet (HTTPS and WSS)
• Testnet (HTTPS and WSS)

API methods

For Filecoin, we support blockchain interaction via the following methods:

• Filecoin EVM methods
• Filecoin native methods

Unsupported

HTTPS EVM methods:

eth_newFilter, eth_getFilterChanges, eth_syncing, eth_coinbase, eth_hashrate, eth_mining, eth_getWork,eth_submitWork, eth_submitHashrate, net_peerCount, eth_newBlockFilter, eth_newPendingTransactionFilter, eth_uninstallFilter, eth_getFilterLogs,

debug_*, personal_*, admin_*, clique_*, les_*, miner_*, engine_*, parity_*

WSS EVM methods:

txpool_content, txpool_inspect, txpool_status, txpool_contentFrom

WSS Filecoin methods:

Filecoin.ChainNotify

API querying

Request example (Standard EVM)

curl -X POST https://rpc.ankr.com/filecoin \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc": "2.0",
      "method": "eth_blockNumber",
      "params": [],
      "id": 1
    }'

Response example (Standard EVM)

{
    "jsonrpc": "2.0",
    "id": 1,
    "result": "0x2910f9"
}

Request example (Filecoin native)

curl -X POST https://rpc.ankr.com/filecoin \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc": "2.0",
      "method": "Filecoin.ChainGetBlock",
      "params": [
                  {
                    "/": "bafy2bzacecbzs3i5qubhgozauss4nvifgty5zvyvf6cy6frnnznojdmfl6phe"
                  }
                ],
      "id": 1
    }'

Response example (Filecoin native)

{
    "jsonrpc": "2.0",
    "result": {
        "Miner": "f0427989",
        "Ticket": {
            "VRFProof": "pbmP9mctFpH6BoFFh22uvzv8Ixx0rJq9YanJLFTRsgIWDibuomloU2UTWiN8007KBYAnB5Xj1jw7o81VJzKrUByqHUpZHWZM34CgVkuzcHPoSJpM8XGxs2GQkfNAncK2"
        },
        "ElectionProof": {
            "WinCount": 1,
            "VRFProof": "oLSLThMoFfGX4E8cDIEULGmUteJY/10nCfun3hiRE1PDIpkPOnoBACmto7/SCz1yFixgQaysEcKK6RCx1ImUW2Q9dlrj3MCbjRQtNiumTXviDqAWgoxYU55QSBDpLbel"
        },
        "BeaconEntries": [
            {
                "Round": 2787998,
                "Data": "h+zHzc0DvUFIWFpFzqREiA2f3Uk4sn5NExnJJUtfju3Hlc0/dkNXq31+su9kh/q1CK69TRUy9562jx/eV4XXw1lA4QhDxBBWKoxQL/xR+zoCcfm4nzoD3HximnPCEEQA"
            }
        ],
        "WinPoStProof": [
            {
                "PoStProof": 3,
                "ProofBytes": "pK36Z/ehsV5sqyoX/Gc64tsV2yQOW6X+p8Wy1wH03WC9VA6qyc3ZaTt4d9oI6xVniJdyHiu22yMsXfimEfVSc/UzThf8KrnIBMWZr3sSQsOVusdf1zV5zNfvDr1wccHhCjIExyinkvGRW/irioDZ49Jrm5PUvaBERIuJC4hUp0DijM8UgY7FIYTA16HHp7gbpUzU7mpofBz42tL3c/8LgOmLd7FKOh69fk0xHYaeQU1Oz3cbSSHWL8a/wRf4y3nV"
            }
        ],
        "Parents": [
            {
                "/": "bafy2bzaceaxasycsjnixwqqbx4o3fsspal2zspnhmdjdtyke5xwtjkut7asyw"
            },
            {
                "/": "bafy2bzaceadqtqu4wcecrk2akfb4mw7y3bedihwanwk2l4dxbcu4fonu3x6pe"
            },
            {
                "/": "bafy2bzacecoqk52mag2xpxn2eq3pfmyr6mafvogju4znyagmkah4oo4fjgh5i"
            },
            {
                "/": "bafy2bzaced46b2tewkbg6qfa5jnoecvbpdn5k7loz7qsoon3m5mgeb63de46s"
            }
        ],
        "ParentWeight": "63400884650",
        "Height": 2692153,
        "ParentStateRoot": {
            "/": "bafy2bzacec5o4ffqnp4zmkn44i6h7oajurvtsb5zvstudvgwhha7y25alt3ck"
        },
        "ParentMessageReceipts": {
            "/": "bafy2bzacebvll7rq7wscnsgbvgdc7xeuzsp2quu4hhfx4pjvq3hydhw2auvd6"
        },
        "Messages": {
            "/": "bafy2bzacechrvqknf26ff4pihyatewfx64ae4bawbp4ibtasy72hr63fds4iq"
        },
        "BLSAggregate": {
            "Type": 2,
            "Data": "mQuz4wd292+Qh8oeZmpl+4QX7/90Oz7VDFLgPhRjIGgvYTEj0FYAecHTaxKaH0GGDwt0nqEvoVbFGf6PA6wCNtzwpLTMqQXZrT2cFeSAtC62vOOn7KTSdqtFxJvBwX1a"
        },
        "Timestamp": 1679070990,
        "BlockSig": {
            "Type": 2,
            "Data": "qiMSk+hQ1E9WGMRn2o5dQmCpz1uO8JK4oIoh8NUwybN7GzrLEaSTv1W5IGx5AAnrAIYgE1MA+Y+CQ677iBC6wD3YUpzdSIt0QCv3cbf8SJgeOVusC+x0Vo/29zRGBgU/"
        },
        "ForkSignaling": 0,
        "ParentBaseFee": "403334159"
    },
    "id": 1
}

Flare

Flare API is available on RPC Service (opens in a new tab).

Flare is the blockchain for data. It is a layer 1, EVM smart contract platform designed to expand the utility of blockchain.

Flare has the following native data acquisition protocols at these stages of development:

• The Flare Time-Series Oracle (FTSO) (opens in a new tab) provides continuous estimations of changing data, such as price pairs.
• The State Connector (opens in a new tab) allows querying of verifiable, non-changing data from other chains and the internet.
• Flare LayerCake (opens in a new tab) is being developed by Flare Labs to provide a decentralized, trustless bridging system between smart contract networks.

By giving developers trustless access to the broadest range of data, Flare can advance the development of more blockchain use cases where data is important, such as in DeFi, gaming, NFT, music, and social networks.

Official quick links: Website (opens in a new tab), Docs (opens in a new tab), GitHub (opens in a new tab)

Networks

• Mainnet:
  • Standard EVM API (HTTPS and WSS)
  • C-Chain (HTTPS)
  • P-Chain (HTTPS)
  • X-Chain (HTTPS)

API methods

For Avalanche, we support blockchain interaction via the following methods:

• Standard EVM methods
• P-Chain methods
• C-Chain methods
• X-Chain methods

Unsupported

HTTPS:

eth_newFilter, eth_getFilterChanges, eth_coinbase, eth_hashrate, eth_mining, eth_getWork, eth_submitWork, eth_submitHashrate, net_peerCount,

debug_*, personal_*, admin_*, clique_*, les