Chains Quickstart

This docs section provides the list of all chains available on the Web3 API platform (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.

Allora

Allora API is available on Web3 API platform (opens in a new tab).

The Allora Network is an advanced protocol that leverages decentralized AI and machine learning (ML) to generate and share predictions among its participants. It provides a structured way for users to access on-chain AI predictions and pay the AI/ML node operators who produce these insights.

Allora acts as a bridge between various parties — data owners, processors, AI/ML predictors, market analysts, and end-users — allowing them to utilize and act on these predictions. AI/ML agents on the network use their data and algorithms to broadcast predictions across a peer-to-peer network. They also evaluate predictions from other agents.

The network’s consensus mechanism then combines these predictions and assessments, rewarding agents based on the quality of their contributions. This incentive system helps Allora continuously learn and adapt to changing market conditions.

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

Networks

• Testnet:
  • Tendermint RPC API (HTTPS and WSS)
  • Tendermint REST API (HTTPS)
  • Cosmos REST API (HTTPS)

API methods

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

Unsupported

Tendermint (both for REST and JSON-RPC):

/health, /genesis, /broadcast_evidence, /dial_seeds, /dial_peers,

Cosmos:

/cosmos/auth/v1beta1/address_by_id/{id}, /cosmos/auth/v1beta1/module_accounts, /cosmos/auth/v1beta1/bech32, /cosmos/auth/v1beta1/bech32/{address_bytes}, /cosmos/auth/v1beta1/bech32/{address_string}, /cosmos/bank/v1beta1/supply/{denom}, /cosmos/bank/v1beta1/denom_owners/{denom}, /cosmos/bank/v1beta1/send_enabled, /cosmos/base/reflection/v1beta1/interfaces, /cosmos/base/reflection/v1beta1/interfaces/:interface_name/implementations, /cosmos/base/reflection/v1beta1/app_descriptor/authn, /cosmos/base/reflection/v1beta1/app_descriptor/chain, /cosmos/base/reflection/v1beta1/app_descriptor/codec, /cosmos/base/reflection/v1beta1/app_descriptor/configuration, /cosmos/base/reflection/v1beta1/app_descriptor/query_services, /cosmos/base/reflection/v1beta1/app_descriptor/tx_descriptor, /cosmos/base/tendermint/v1beta1/abci_query, /cosmos/feegrant/v1beta1/issued/{granter}, /cosmos/gov/v1/proposals/{proposal_id}, /cosmos/gov/v1/proposals, /cosmos/gov/v1/proposals/{proposal_id}/votes/{voter}, /cosmos/gov/v1/proposals/{proposal_id}/votes, /cosmos/gov/v1/params/{params_type}, /cosmos/gov/v1/proposals/{proposal_id}/deposits/{depositor}, /cosmos/gov/v1/proposals/{proposal_id}/deposits, /cosmos/gov/v1/proposals/{proposal_id}/tally, /cosmos/group/v1/group_info/{group_id}, /cosmos/group/v1/group_policy_info/{address}, /cosmos/group/v1/group_members/{group_id}, /cosmos/group/v1/groups_by_admin/{admin}, /cosmos/group/v1/group_policies_by_group/{group_id}, /cosmos/group/v1/group_policies_by_admin/{admin}, /cosmos/group/v1/proposal/{proposal_id}, /cosmos/group/v1/proposals_by_group_policy/{address}, /cosmos/group/v1/vote_by_proposal_voter/{proposal_id}/{voter}, /cosmos/group/v1/votes_by_proposal/{proposal_id}, /cosmos/group/v1/votes_by_voter/{voter}, /cosmos/group/v1/groups_by_member/{address}, /cosmos/group/v1/proposals/{proposal_id}/tally, /cosmos/nft/v1beta1/balance/{owner}/{class_id}, /cosmos/nft/v1beta1/owner/{class_id}/{id}, /cosmos/nft/v1beta1/supply/{class_id}, /cosmos/nft/v1beta1/nfts, /cosmos/nft/v1beta1/nfts/{class_id}/{id}, /cosmos/nft/v1beta1/classes/{class_id}, /cosmos/nft/v1beta1/classes, /cosmos/params/v1beta1/subspaces, /cosmos/upgrade/v1beta1/module_versions, /cosmos/upgrade/v1beta1/authority, /cosmos/base/tendermint/v1beta1/node_info, /cosmos/base/tendermint/v1beta1/syncing, /cosmos/params/v1beta1/params,

/syncing, /blocks/latest, /blocks/{height}, /validatorsets/latest, /validatorsets/{height}, /wasm/code, /wasm/code/{codeID}, /wasm/code/{codeID}/contracts, /wasm/contract/{contractAddress}, /wasm/contract/{contractAddress}/code-hash, /wasm/contract/{contractAddress}/query/{query}, /wasm/code/{codeID}/hash, /reg/consensus-io-exch-pubkey

API querying

Request example

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

Response example

{
    "jsonrpc": "2.0",
    "id": -1,
    "result": {
        "block_id": {
            "hash": "663789D1BAA0354453A5BB1474C46C9F74E6140B247153482BBE84893C029600",
            "parts": {
                "total": 1,
                "hash": "BFCC2C78C439E367ABEEA996FD9A120EAA70DC44572B8BFDCA032908BA4B439B"
            }
        },
        "block": {
            "header": {
                "version": {
                    "block": "11"
                },
                "chain_id": "allora-testnet-1",
                "height": "761001",
                "time": "2024-08-21T21:33:36.088780054Z",
                "last_block_id": {
                    "hash": "AD51186842A63CB515A4946C558DF1DA71D384DF646EC5522ECD5008E3FAEDA0",
                    "parts": {
                        "total": 1,
                        "hash": "16A9CCD523F2E593E66F46CBD20FCC03B5849ACE5325951E50BC53B6D7D2F893"
                    }
                },
                "last_commit_hash": "77BE45E09B5A5F40FA1F10BF430C2E14371445B9E2DF89952478E84A98DFA081",
                "data_hash": "78F2AF9D01AC871045FB53CB383AA50EF4C0094E9563428BFF8BA59071801050",
                "validators_hash": "CB957FF7AB192A9F9321F0E471C7BAE5A9AA82573FF8D509F8ACF7CA3A450A42",
                "next_validators_hash": "CB957FF7AB192A9F9321F0E471C7BAE5A9AA82573FF8D509F8ACF7CA3A450A42",
                "consensus_hash": "048091BC7DDC283F77BFBF91D73C44DA58C3DF8A9CBC867405D8B7F3DAADA22F",
                "app_hash": "72AEC5979CEA9EE65275B77DA8F31676C7E52DA57B991D86C4870237E3D40127",
                "last_results_hash": "455FD6D9D1888EBE5B8602E20E84EEACA30020B717A5B5298890E7236CAB84AD",
                "evidence_hash": "E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855",
                "proposer_address": "01458B61F0D7DE6E90798FE8C370413D718EB34C"
            },
            "data": {
                "txs": [
                    "CuECCt4CCiQvZW1pc3Npb25zLnYyLk1zZ0luc2VydFdvcmtlclBheWxvYWQStQIKK2FsbG8xYWhhcGE2ZHpkOG0yNjc0MHp5N2gyd3pnamx1ZnM4NjRmeDR1eHcShQIKK2FsbG8xYWhhcGE2ZHpkOG0yNjc0MHp5N2gyd3pnamx1ZnM4NjRmeDR1eHcSBAiRuS4YBSJICkYIBRCRuS4aK2FsbG8xYWhhcGE2ZHpkOG0yNjc0MHp5N2gyd3pnamx1ZnM4NjRmeDR1eHciETE0NS42NTg1MDk2NjIzMjkzKkBkgCxd7XHQh+Debe/yvS+c8BBoKguydI/J/YNqRaYpBDpnwQo+4/LPouiYF04JXDBa4qxTfJFlpdSJ9EgoX+TAMkIwMmQ4MjYzOTFiYWI4ZjYzNWYzNDhkYmQxNDQ1ZGUxZmQ0YjgzZjNiNGJiZjFkY2EzY2Q4YWFjM2FlMWMyYmY5ODcSWApQCkYKHy9jb3Ntb3MuY3J5cHRvLnNlY3AyNTZrMS5QdWJLZXkSIwohAtgmORurj2NfNI29FEXeH9S4PztLvx3KPNiqw64cK/mHEgQKAggBGCkSBBDAhD0aQN1AnyLR2Kz/KMZ5yr+Sz4wo+4Tp8OnyDqSlr98oCNQVPtF69bWneamHvTEq7r5WUGuwQfWSD+sybXlUgnDlmIw=",
                    "CuECCt4CCiQvZW1pc3Npb25zLnYyLk1zZ0luc2VydFdvcmtlclBheWxvYWQStQIKK2FsbG8xcmZweng2MGR6MDc5dWhuZXRxdHNkdTJ1ZTM0dmdyMnJ3ZGFrd2cShQIKK2FsbG8xcmZweng2MGR6MDc5dWhuZXRxdHNkdTJ1ZTM0dmdyMnJ3ZGFrd2cSBAiTuS4YAyJICkYIAxCTuS4aK2FsbG8xcmZweng2MGR6MDc5dWhuZXRxdHNkdTJ1ZTM0dmdyMnJ3ZGFrd2ciETYxMzI3LjIzMTM5NzQ3MTg1KkA2b71NaRNK8PFRv+nLbaTfB53wu/AqI4cGoFYED/4U/3c8JOYW+Q2moUdlX35tKF0U2gneVA2jQy0vmem8uIz6MkIwMzA5Zjg2ZWY3YzNlM2IyZjUzMzg3OGZiNjY2Mjk1NjljNjFkYTNhMzg2OTkyNjNmMWM4MDhlMTcxMTQzOWYxMmMSWQpRCkYKHy9jb3Ntb3MuY3J5cHRvLnNlY3AyNTZrMS5QdWJLZXkSIwohAwn4bvfD47L1M4ePtmYpVpxh2jo4aZJj8cgI4XEUOfEsEgQKAggBGLJKEgQQwIQ9GkAYepebNx4qruj3/XCxlmVQ3XDbhfsXZlZyM+yeqUs7d263LfRxugRgQH3aiV/ROiC/gVH0bID6GA00y5QMWM+B"
                ]
            },
            "evidence": {
                "evidence": []
            },
            "last_commit": {
                "height": "761000",
                "round": 0,
                "block_id": {
                    "hash": "AD51186842A63CB515A4946C558DF1DA71D384DF646EC5522ECD5008E3FAEDA0",
                    "parts": {
                        "total": 1,
                        "hash": "16A9CCD523F2E593E66F46CBD20FCC03B5849ACE5325951E50BC53B6D7D2F893"
                    }
                },
                "signatures": [
                    {
                        "block_id_flag": 1,
                        "validator_address": "",
                        "timestamp": "0001-01-01T00:00:00Z",
                        "signature": null
                    },
                    {
                        "block_id_flag": 2,
                        "validator_address": "2D5A6E69CDFBE8FF7C0C2DAFF752387AC73B9AB1",
                        "timestamp": "2024-08-21T21:33:36.07519025Z",
                        "signature": "LvyV25u8kxAivi7rHuAZlXtawVBMYyOJflcr4al44TWVLmYnztqycSgGyi1S9GkUGoeA4nG+wRM/4pqk4YIKDQ=="
                    }
                ]
            }
        }
    }
}

Aptos

Aptos API is available on Web3 API platform (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 Web3 API platform (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 Web3 API platform (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"
}

Avail

Avail API is available on Web3 API platform (opens in a new tab).

Avail is a Web3 infrastructure layer that allows modular execution layers to scale and interoperate in a trust minimized way.

A foundational Data Availability (DA) layer, Nexus interoperability layer, and Fusion Security network layer come together to form the Unification Layer.

• The DA layer is a highly optimized, low-level layer, specifically constructed for data availability. This is the deepest blockchain layer, with the minimal functionality required to build cross-ecosystem interoperability on top.
• Nexus acts as a light but powerful proof aggregation and sequencer selection ZK rollup on top of Avail, allowing for cross-rollup and cross-ecosystem settlement.
• Fusion Security enables a basket of tokens to pool their crypto-economic security to serve and secure the Avail network.

Avail's mission is to streamline the rollup experience, offering a unified, efficient platform for both users and developers from any ecosystem. This vertically integrated stack aims to dissolve the growing pains and user fragmentation experienced today, enabling Rollups to seamlessly access users and liquidity across the entire blockchain landscape.

The Turing Testnet is live and marks Avail's final and definitive pre-Mainnet testing environment, aimed at vetting Mainnet deployments, executing extensive stress tests, and assessing network topologies for scalability and resilience.

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

Networks

• Turing Testnet (HTTPS and WSS)

API methods

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

Unsupported

state_getMetadata, state_getPairs, state_traceBlock, state_trieMigrationStatus, state_subscribeStorage, state_unsubscribeStorage, state_queryStorage, sync_state_genSyncSpec, system_accountNextIndex, system_addLogFilter, system_addReservedPeer, system_health, system_localListenAddresses, system_localPeerId, system_name, system_nodeRoles, system_peers, system_properties, system_removeReservedPeer, system_reservedPeers, system_resetLogFilter, system_syncState, system_unstable_networkState, system_version,

account_*, babe_*, mmr_*, dev_*, offchain_*, author_*

API querying

Request example

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

Response example

{
    "jsonrpc": "2.0",
    "result": {
        "block": {
            "header": {
                "parentHash": "0x32d67a9e5843dd8527bf0e2ec1f4c6d2f8642ef264348ef7d610575619a5b6e8",
                "number": "0x49993",
                "stateRoot": "0x7d0860d48e20e42886aeac479dd339d1f75387d3be844a490ca1734efd430213",
                "extrinsicsRoot": "0x07d2cb3154a4bc3ff485d0101bb1cba8045bf1bd74a34a977cc2672a41e76596",
                "digest": {
                    "logs": [
                        "0x0642414245b5010359000000757a1e0500000000841bf8fb61a548ec94caba8ddedcf85e02de0110990ffe3c4216277ee0b9734a9b966b69d9025691e82043d9a647ce917871b1b2d2082afc3ce3b195c96e1c039b2e312d9028cf976284d61c41f1069b1df154b5e6b6bef9ad4455dd24ea160d",
                        "0x05424142450101c2be2a753a256b1261e00d5d31a20befa735767d5debe27edfff52149e4ce53398135479d97a0e594a2160cf78b3743ca42899138b0c5b58334bc7c4d0217080"
                    ]
                },
                "extension": {
                    "V3": {
                        "appLookup": {
                            "size": 114,
                            "index": [
                                {
                                    "appId": 36,
                                    "start": 0
                                }
                            ]
                        },
                        "commitment": {
                            "rows": 1,
                            "cols": 128,
                            "commitment": [
                                128,
                                27,
                                216,
                                161
                            ],
                            "dataRoot": "0x67e432157400275ba4e6e7c9d61312afa5cbbea68d8b718fa8be3038980a9970"
                        }
                    }
                }
            },
            "extrinsics": [
                "0x280403000ba0f41eed8f01",
                "0xc90384007ce8ccf46bbdf7561f0d1419857dab91bfbda9866d564c2c5cfe43210a75db310122850737c933478016ee92ddcbd1eda470ead30b6a7938adba396b9e51922949b1bba1bf56ca8bd67f2241b1240fa1f2bd18f07b42111fe70f9f386b78f66f87040162760100000001020c0603004e558a63713b227cb661a5cb639c5bea499bd00039d7dabe16cb891e8fc2025213000064a7b3b6e00d06030006aa84733a1b39c3cc83586e589fd6bb82228321e1f75d4e2bc3af8d4957785213000064a7b3b6e00d0603003a1e5289c81ff9dfd53cf55e64aaaee9aeb31e5ae43c9679de15a841b406521d13000064a7b3b6e00d"
            ]
        },
        "justifications": null
    },
    "id": 1
}

Avalanche

Avalanche API is available on Web3 API platform (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 Web3 API platform's or MetaMask's UI.

Via Web3 API platform

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
}

B2 Network

B² Network API is available on Web3 API platform (opens in a new tab).

The B² Network is an advanced Layer-2 solution designed to enhance transaction speed, reduce costs, and broaden application diversity without compromising security. It is notable for being the first zero-knowledge proof verification commitment rollup on Bitcoin.

Key Features:

• Zero-Knowledge Proof Verification: Utilizes zero-knowledge proof technology to ensure transactional privacy and security, allowing for the verification of transactions without revealing the underlying data.

• Rollup Technology: Processes multiple off-chain transactions and rolls them into a single on-chain transaction, significantly increasing efficiency and reducing costs.

• Turing-Complete Smart Contracts: Supports Turing-complete smart contracts, enabling complex computations and a wide range of decentralized applications (dApps) to run off-chain with enhanced performance.

• Gate Commitment and Challenge-Response Mechanism: Integrates gate commitment and challenge-response mechanisms, leveraging Taproot on Bitcoin to ensure secure and private transaction confirmations.

• EVM-Compatibility: The B² Network is compatible with the Ethereum Virtual Machine (EVM), allowing it to run Ethereum-based smart contracts and dApps. This compatibility enables developers to use existing Ethereum tools, libraries, and standards while benefiting from the B² Network's enhanced features.

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 B² Network, 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/b2 \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc":"2.0",
      "method":"eth_blockNumber",
      "params": [],
      "id":1
    }'

Response example

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

Bahamut

Bahamut API is available on Web3 API platform (opens in a new tab).

Bahamut is an EVM-based, Layer 1 public blockchain designed to improve block reward distribution by incorporating validator activity into the consensus algorithm.

Key Features:

• EVM-Compatible: Fully compatible with Ethereum smart contracts.
• Layer 1 Blockchain: Operates independently with its own infrastructure.
• Consensus Mechanism: Proof of Stake and Activity (PoSA)

Bahamut introduces a unique Proof of Stake and Activity (PoSA) consensus mechanism, combining traditional PoS with an activity parameter based on the gas used by a validator's smart contracts.

• Proof of Stake (PoS): Validators are selected based on their stake in the network.
• Activity Parameter: Measures and rewards validators based on their smart contract activity, influencing their chances of proposing new blocks.

Benefits:

• Encourages Active Participation: Rewards validators for both stake and activity.
• Fair Reward Distribution: Ensures a more equitable distribution of block rewards.
• Improved Efficiency: Promotes faster transaction processing and smart contract execution.

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 Bahamut, 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/bahamut \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc": "2.0",
      "method": "eth_blockNumber",
      "params": [],
      "id": 1
    }'

Response example

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

Base

Base API is available on Web3 API platform (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)
• Testnet:
  • Sepolia (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"
}

Berachain

Berachain API is available on Web3 API platform (opens in a new tab).

Berachain is a high-performance EVM-compatible blockchain built on Proof-of-Liquidity consensus. Proof-of-Liquidity is a novel consensus mechanism that aims to align network incentives, creating strong synergy between Berachain validators and the ecosystem of projects. Berachain's technology is built on Polaris, a high-performance blockchain framework for building EVM-compatible chains on-top of the CometBFT consensus engine.

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

Networks

• Testnet (HTTPS and WSS)

API methods

For Berachain, 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/berachain_testnet \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc": "2.0",
      "method": "eth_blockNumber",
      "params": [],
      "id": 1
    }'

Response example

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

Bitcoin

Bitcoin API is available on Web3 API platform (opens in a new tab).

Bitcoin API provides the means for communication with the Bitcoin’s public ledger.

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

Networks

• Mainnet (HTTPS)
• Signet Testnet (HTTPS)

API methods

For Bitcoin, we support blockchain interaction via the following interfaces:

• Bitcoin API native methods
• Blockbook API methods

Unsupported

Bitcoin's HTTPS:

savemempool, verifychain, getmemoryinfo, getrpcinfo, gettransaction, help, logging, stop, uptime, getblocktemplate, getmininginfo, getnetworkhashps, pruneblockchain, generateblock, generatetoaddress, generatetodescriptor, prioritisetransaction, submitblock, submitheader, addnode, clearbanned, disconnectnode, getaddednodeinfo, getconnectioncount, getnettotals, getnetworkinfo, getnodeaddresses, getpeerinfo, listbanned, ping, setban, setnetworkactive, signrawtransactionwithkey, createmultisig, getdescriptorinfo, signmessagewithprivkey, abandontransaction, abortrescan, addmultisigaddress, backupwallet, bumpfee, createwallet, dumpprivkey, dumpwallet, encryptwallet, getaddressesbylabel, getbalance, getbalances, getnewaddress, getrawchangeaddress, getreceivedbyaddress, getreceivedbylabel, getunconfirmedbalance, getwalletinfo, importaddress, importdescriptors, importmulti, importprivkey, importprunedfunds, importpubkey, importwallet, keypoolrefill, listaddressgroupings, listlabels, listlockunspent, listreceivedbyaddress, listreceivedbylabel, listtransactions, listsinceblock, listunspent, listwalletdir, listwallets, loadwallet, lockunspent, psbtbumpfee, removeprunedfunds, rescanblockchain, send, sendmany, sendtoaddress, sethdseed, setlabel, setwalletflag, signmessage, settxfee, signrawtransactionwithwallet, unloadwallet, upgradewallet, walletcreatefundedpsbt, walletlock, walletpassphrase, walletpassphrasechange, walletprocesspsbt, deriveaddresses, fundrawtransaction, scantxoutset, preciousblock, gettxoutsetinfo

Blockbook API:

• All WebSocket methods
• All socket.io methods

API querying

Request example

curl -X POST https://rpc.ankr.com/btc \
-d '{
      "id": "hmm",
      "method": "getindexinfo",
      "params": []
}'

Response example

{
    "result": {
        "txindex": {
            "synced": true,
            "best_block_height": 843277
        },
        "basic block filter index": {
            "synced": true,
            "best_block_height": 843277
        }
    },
    "error": null,
    "id": "hmm"
}

Bitlayer

Bitlayer API is available on Web3 API platform (opens in a new tab).

Bitlayer is the first Bitcoin security-equivalent layer 2 based on BitVM. It consists of an EVM compatible chain/sequencer that can map BTC ecological assets and facilitate the entry of BTC users.

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 Bitlayer, 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/bitlayer \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc": "2.0",
      "method": "eth_blockNumber",
      "params": [],
      "id": 1
    }'

Response example

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

BitTorrent Chain

BitTorrent Chain API is available on Web3 API platform (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 Web3 API platform's or MetaMask's UI.

Via Web3 API platform

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"
}

Blast

Blast API is available on Web3 API platform (opens in a new tab).

Blast is the only Ethereum L2 with native yield for ETH and stablecoins.

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

Networks

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

API methods

For Blast, 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/blast_testnet_sepolia \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc":"2.0",
      "method":"eth_blockNumber",
      "params": [],
      "id":1
    }'

Response example

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

BNB Smart Chain

BNB Smart Chain API is available on Web3 API platform (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 Web3 API platform's or MetaMask's UI.

Via Web3 API platform

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"
}

Celo

Celo API is available on Web3 API platform (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 Web3 API platform's or MetaMask's UI.

Via Web3 API platform

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 Web3 API platform (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"
}

Core

Core API is available on Web3 API platform (opens in a new tab).

Core is a layer 1 blockchain built around a unique consensus mechanism called "Satoshi Plus" (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)

API methods

For Core, 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/core \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc": "2.0",
      "method": "eth_blockNumber",
      "params": [],
      "id": 1
    }'

Response example

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

Electroneum

Electroneum API is available on Web3 API platform (opens in a new tab).

Electroneum is an IBFT-based blockchain that operates with known validators, ensuring a high level of trust and security. Compatible with the Ethereum Virtual Machine (EVM), Electroneum allows developers to easily deploy and interact with smart contracts. The blockchain offers impressive 5-second transaction speeds, facilitated by its unique proprietary instant blockchain finality system.

The finality system ensures that transactions are quickly and irreversibly confirmed, eliminating the need for multiple confirmations and enabling rapid and efficient transactions. Combined with ultra low-cost smart contract fees, Electroneum provides an attractive platform for developers and users alike.

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

Networks

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

API methods

For Electroneum, 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/electroneum \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc": "2.0",
      "method": "eth_blockNumber",
      "params": [],
      "id": 1
    }'

Response example

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

Ethereum

Ethereum API is available on Web3 API platform (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:
  • Holesky (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 Web3 API platform's or MetaMask's UI.

Via Web3 API platform

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 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

Ethereum Beacon API is available on Web3 API platform (opens in a new tab) upon switching on the Beacon toggle.

The Ethereum 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:
  • Holesky (HTTPS)
  • Sepolia (HTTPS)

API methods

For the Ethereum 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 Web3 API platform (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 Web3 API platform's or MetaMask's UI.

Via Web3 API platform

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 Web3 API platform (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 Web3 API platform (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 Flare, 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/flare \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc":"2.0",
      "method":"eth_blockNumber",
      "params": [],
      "id":1
    }'

Response example (Standard EVM)

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

Gnosis

Gnosis API is available on Web3 API platform (opens in a new tab).

Gnosis Chain (formerly xDai Chain) provides stability, scalability and an extendable beacon chain framework.

Development on Gnosis Chain is straightforward for Ethereum developers as it is an EVM compatible chain. Smart contracts can be written and deployed in the same way as for Ethereum just by setting a different RPC endpoint.

Any contract that works on the Ethereum mainnet can be redeployed to the Gnosis chain. Transaction costs are minimized, and all fees and transactions are paid with a single token (xDai). Many tools supporting Ethereum development are compatible with Gnosis 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)
• 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 Gnosis Chain through Ankr's infrastructure, add a required Gnosis Chain network either via Web3 API platform's or MetaMask's UI.

Via Web3 API platform

To be added soon.

Via MetaMask

To add Gnosis 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: Gnosis Chain Mainnet by Ankr RPC.
   • New RPC URL: https://rpc.ankr.com/gnosis/.
   • Chain ID: 100.
   • Currency symbol: xDai.
   • Block explorer URL: https://blockscout.com/xdai/mainnet/.

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

API methods

For Gnosis, 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
}

Gnosis Beacon

Gonsis Beacon API is available on Web3 API platform (opens in a new tab) upon switching on the Beacon toggle.

The Gnosis Beacon Chain is a consensus layer that introduced a proof-of-stake (opens in a new tab) to Ethereum. The Gnosis 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 Gnosis 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)

Networks

• Mainnet (HTTPS)
• Testnet (HTTPS)

API methods

For the Gnosis 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/gnosis_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"
    }
}

Gravity

Gravity API is available on Web3 API platform (opens in a new tab).

Gravity is a Layer 1 blockchain designed for mass adoption and an omnichain future. Gravity features the following key points:

• Cross-Chain Transactions: Gravity enables developers to define and settle transactions across multiple blockchains, enhancing efficiency and security.
• Efficient Verification: With cost-efficient ZKP verification, Gravity ensures economical and secure transactions.
• Enhanced User Experience: Gravity introduces cryptographic primitives like the secp256r1 curve through precompiled contracts, allowing for cost-effective passkey authentication for Account Abstraction wallets.
• High-Performance Execution: Gravity integrates the Reth execution layer and the Jolteon consensus algorithm, providing high throughput and near-instant finality.
• Secure and Robust PoS Mechanism: Powered by G token staking and restaking protocols like Babylon and EigenLayer, Gravity's PoS design incentivizes and unites a diverse community to secure the chain.
• EVM-Compatible: Gravity is fully EVM-compatible, enabling seamless deployment and interaction with smart contracts.

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

Networks

• Mainnet (HTTPS and WSS)

API methods

For Gravity, 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/gravity \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc": "2.0",
      "method": "eth_blockNumber",
      "params": [],
      "id": 1
    }'

Response example

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

Linea

Linea API is available on Web3 API platform (opens in a new tab).

Linea is a network that scales the experience of Ethereum. Its out-of-the-box compatibility with the Ethereum Virtual Machine enables the deployment of already-existing applications, as well as the creation of new ones that would be too costly on Mainnet. It also enables the community to use those dapps, at a fraction of the cost, and at multiples the speed of Mainnet.

It does this by leveraging quantum-resistant lattice-based cryptography to create zero-knowledge proofs that include every transaction performed on the network, and rolling them up to Mainnet. This ensures that every transaction is recorded to the Ethereum ledger while dividing the cost of that security by magnitudes.

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

Networks

• Mainnet (HTTPS and WSS)

API methods

For Linea, 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/linea/{your_token} \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc": "2.0",
      "method": "eth_blockNumber",
      "params": [],
      "id": 1
    }'

Response example

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

Harmony

Harmony API is available on Web3 API platform (opens in a new tab).

Harmony is a fast and secure blockchain for decentralized applications. Production mainnet is expected to support 4 shards of 1000 nodes, producing blocks in 2 seconds with finality.

An Effective Proof-of-Stake (EPoS) reduces centralization while supporting stake delegation, reward compounding and double-sign slashing.

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 Harmony through Ankr's infrastructure, add a required Harmony network either via Web3 API platform's or MetaMask's UI.

Via Web3 API platform

To be added soon.

Via MetaMask

To add Harmony 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: Harmony Mainnet by Ankr RPC.
   • New RPC URL: https://rpc.ankr.com/harmony/.
   • Chain ID: 1666600000.
   • Currency symbol: ONE.
   • Block explorer URL: https://explorer.harmony.one/.

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

API methods

For Harmony, 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_*,

hmyv2_getCurrentBadBlocks, hmyv2_getNodeMetadata, hmy_getFilterLogs, hmy_newFilter, eth_newPendingTransactionFilter, eth_newBlockFilter, hmy_getFilterChanges, hmy_syncing

WSS:

txpool_content, txpool_inspect, txpool_status, txpool_contentFrom

API querying

Request example

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

Response example

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

Huobi ECO Chain

HECO API is available on Web3 API platform (opens in a new tab).

Huobi ECO Chain (HECO) is a decentralized, high-efficiency and energy-saving public chain. It is compatible with smart contracts and supports high- performance transactions. The endogenous token of Heco is HT, and it adopts the HPoS consensus mechanism. Heco will continue to improve the efficiency of Ethereum by Layer2, which will supplement and empower the Ethereum ecosystem.

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 HECO, 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/heco/{your_token} \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc":"2.0",
      "method":"eth_blockNumber",
      "params": [],
      "id":1
    }'

Response example

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

Horizen EON

Horizen EON API is available on Web3 API platform (opens in a new tab).

EON is Horizen's Ethereum VM (Virtual Machine). EON has adopted Ethereum’s account-based transaction model to represent assets as balances within accounts. The account model, in VM capable blockchains, differentiate account types on whether they represent a normal account balance or an account which is bound to some code that has to be executed by the VM.

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)
• Gobi Testnet (HTTPS and WSS)

API methods

For Horizen EON, 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/horizen_eon \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc": "2.0",
      "method": "eth_blockNumber",
      "params": [],
      "id": 1
    }'

Response example

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

IoTeX

IoTeX API is available on Web3 API platform (opens in a new tab).

IoTeX Network is the lightning-fast, ultra-secure, and highly scalable blockchain platform that connects real world data to on-chain Dapps.

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 IoTeX through Ankr's infrastructure, add a required IoTeX network either via Web3 API platform's or MetaMask's UI.

Via Web3 API platform

To be added soon.

Via MetaMask

To add IoTeX 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: IoTeX Mainnet by Ankr RPC.
   • New RPC URL: https://rpc.ankr.com/iotex/.
   • Chain ID: 4689.
   • Currency symbol: IOTX.
   • Block explorer URL: https://iotexscan.io/.

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

API methods

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

Unsupported

HTTPS:

eth_newFilter, eth_getFilterChanges, eth_syncing, eth_coinbase, eth_hashrate, eth_mining, eth_getWork, eth_submitWork, eth_submitHashrate, eth_accounts, eth_getStorageAt, eth_getUncleCountByBlockHash, eth_getUncleCountByBlockNumber, eth_sign, eth_signTransaction, eth_sendTransaction, eth_getUncleByBlockHashAndIndex, eth_getUncleByBlockNumberAndIndex, eth_newBlockFilter, eth_newPendingTransactionFilter, eth_uninstallFilter, eth_getFilterLogs, eth_pendingTransactions,

debug_*, personal_*, admin_*, clique_*, les_*, miner_*, db_*, shh_*

WSS:

txpool_content, txpool_inspect, txpool_status, txpool_contentFrom

API querying

Request example

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

Response example

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

Kava

Kava API is available on Web3 API platform (opens in a new tab).

The Kava Network is the Layer-1 blockchain that combines the speed and scalability of the Cosmos SDK with the developer support of Ethereum. Kava will empower developers to build for Web3 and next-gen blockchain technologies through its unique co-chain architecture. KAVA is the native governance and staking token of the Kava Network, enabling its decentralization and security.

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

Networks

• Mainnet:
  • REST API (HTTPS)
  • EVM JSON-RPC API (HTTPS and WSS)
  • Tendermint REST API (HTTPS)
  • JSON-RPC API (HTTPS and WSS)

API methods

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

Unsupported

EVM JSON-RPC:

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

Tendermint REST:

/health, /broadcast_evidence, /dial_seeds, /dial_peers

API querying (EVM JSON-RPC)

Request example

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

Response example

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

Kinto

Kinto API is available on Web3 API platform (opens in a new tab).

Kinto is a Layer 2 focused on providing safe access to on-chain finance. It's built on top of the Ethereum network using the Arbitrum Nitro Stack (opens in a new tab), and it's non-custodial, transparent, permissionless, and governed by the community.

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

Networks

• Mainnet (HTTPS and WSS)

API methods

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

Unsupported