# Overview

Crypto Chief RPC provides production-ready node access to 79 blockchain networks from a single platform. One API key unlocks every chain — EVM L1s and rollups, Bitcoin, Solana, SUI, TON, Polkadot, NEAR, and more — through their native RPC protocols, with no proprietary wrappers or SDK lock-in.

{% hint style="info" %}
**Endpoint pattern:** `https://rpc.crypto-chief.com/{network}/{YOUR_API_KEY}`

Get your API key at [crypto-chief.com/rpc](https://crypto-chief.com/rpc/).
{% endhint %}

***

## What You Get

* **79 networks** across every major ecosystem — EVM chains (L1 + L2), Bitcoin and UTXO forks, Solana, Move VMs, TON, Substrate, and emerging protocols
* **Native interfaces** — Ethereum JSON-RPC 2.0 for EVM, Bitcoin Core RPC for UTXO, Solana JSON-RPC, Substrate RPC, REST, GraphQL, gRPC, and WebSocket as each network dictates
* **Standard library compatibility** — works out of the box with `ethers.js`, `viem`, `web3.py`, `@solana/web3.js`, Polkadot.js, and any other client that speaks the native protocol
* **Archival nodes** on select networks for full historical state queries
* **Premium tiers** with higher rate limits, dedicated throughput, and SLA guarantees

***

## Supported Networks

### Ethereum & EVM Layer 1

All EVM-compatible L1 chains implement the [Ethereum JSON-RPC 2.0](https://ethereum.org/en/developers/docs/apis/json-rpc/) specification. Methods are identical across networks — `eth_blockNumber`, `eth_getBalance`, `eth_call`, `eth_sendRawTransaction` — so a single integration pattern works on every chain listed here.

[Ethereum](/chains/ethereum.md) · [Ethereum Beacon](/chains/ethereum-beacon.md) · [BNB Smart Chain](/chains/bnb-smart-chain.md) · [Avalanche](/chains/avalanche.md) · [Polygon](/chains/polygon.md) · [Fantom](/chains/fantom.md) · [Kava](/chains/kava.md) · [Celo](/chains/celo.md) · [Harmony](/chains/harmony.md) · [Moonbeam](/chains/moonbeam.md) · [Telos](/chains/telos.md) · [IoTeX](/chains/iotex.md) · [Flare](/chains/flare.md) · [Kaia](/chains/kaia.md) · [Gnosis](/chains/gnosis.md) · [Gnosis Beacon](/chains/gnosis-beacon.md) · [Bahamut](/chains/bahamut.md) · [Chiliz](/chains/chiliz.md) · [Core](/chains/core.md) · [Electroneum](/chains/electroneum.md) · [Filecoin](/chains/filecoin.md) · [Gravity](/chains/gravity.md) · [Horizen EON](/chains/horizen-eon.md) · [Neura](/chains/neura.md) · [Tenet](/chains/tenet.md) · [XDC](/chains/xdc.md) · [Xphere](/chains/xphere.md) · [Sei](/chains/sei.md)

### EVM Layer 2 & Rollups

Optimistic rollups, ZK rollups, and Ethereum-anchored sidechains. Every network here exposes the same Ethereum JSON-RPC interface — switching from mainnet to any L2 requires only a new endpoint URL.

[Arbitrum](/chains/arbitrum.md) · [Arbitrum Nova](/chains/arbitrum-nova.md) · [Base](/chains/base.md) · [Optimism](/chains/optimism.md) · [zkSync Era](/chains/zksync-era.md) · [Scroll](/chains/scroll.md) · [Linea](/chains/linea.md) · [Blast](/chains/blast.md) · [Mantle](/chains/mantle.md) · [Taiko](/chains/taiko.md) · [Etherlink](/chains/etherlink.md) · [X Layer](/chains/x-layer.md) · [Swell](/chains/swell.md) · [Corn](/chains/corn.md) · [Rollux](/chains/rollux.md) · [Metis](/chains/metis.md) · [Xai](/chains/xai.md) · [Matchain](/chains/matchain.md) · [GOAT](/chains/goat.md) · [Movement](/chains/movement.md) · [Story](/chains/story.md) · [TAC](/chains/tac.md) · [IOTA EVM](/chains/iota-evm.md)

### Bitcoin & UTXO Networks

Bitcoin and its forks use the UTXO accounting model and the Bitcoin Core RPC interface. Bitlayer, B2 Network, and Botanix extend Bitcoin with EVM smart-contract execution anchored to Bitcoin's proof-of-work security.

| Network                                 | Description                               |
| --------------------------------------- | ----------------------------------------- |
| [Bitcoin](/chains/bitcoin.md)           | Original proof-of-work chain              |
| [Bitcoin Cash](/chains/bitcoin-cash.md) | UTXO fork with a larger block size        |
| [Dogecoin](/chains/dogecoin.md)         | Scrypt PoW · merged-mined with Litecoin   |
| [Litecoin](/chains/litecoin.md)         | Scrypt PoW · faster 2.5-minute block time |
| [Bitlayer](/chains/bitlayer.md)         | Bitcoin L2 · BitVM-based EVM execution    |
| [B2 Network](/chains/b2-network.md)     | Bitcoin L2 · ZK-rollup                    |
| [Botanix](/chains/botanix.md)           | Bitcoin L2 · Spiderchain EVM              |

### Solana & SVM

[Solana](/chains/solana.md) · [Sonic](/chains/sonic.md)

Solana's native JSON-RPC interface is distinct from EVM. Sonic is an SVM-based Layer 2.

### Move-Based Networks

Move is a resource-typed smart-contract language with linear-type safety designed for secure asset management. SUI and Aptos are independent Move L1s; SUI supports three protocol interfaces simultaneously.

| Network                   | Interfaces                                                                                                        |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| [SUI](/chains/sui.md)     | [JSON-RPC](/chains/sui/sui-json-rpc.md) · [gRPC](/chains/sui/sui-grpc.md) · [GraphQL](/chains/sui/sui-graphql.md) |
| [Aptos](/chains/aptos.md) | REST API                                                                                                          |

### TON

[TON](/chains/ton.md) (The Open Network) is a sharded proof-of-stake chain with a masterchain/workchain architecture and Bag of Cells binary encoding. Two REST interfaces are available:

| Interface                             | Best suited for                                                                   |
| ------------------------------------- | --------------------------------------------------------------------------------- |
| [TonCenter v2](/chains/ton/ton-v2.md) | Real-time queries, balance lookups, contract execution, broadcasting transactions |
| [TonCenter v3](/chains/ton/ton-v3.md) | Historical data, Jetton and NFT metadata, analytics, indexed lookups              |

### Polkadot Ecosystem

Substrate-based chains implementing the Polkadot JSON-RPC interface.

[Polkadot](/chains/polkadot.md) · [Kusama](/chains/kusama.md) · [Avail](/chains/avail.md)

### Other Alternative Layer 1s

Non-EVM chains each exposing their native RPC protocol.

| Network                       | Interface                   |
| ----------------------------- | --------------------------- |
| [NEAR](/chains/near.md)       | JSON-RPC                    |
| [XRP](/chains/xrp.md)         | Ripple JSON-RPC / WebSocket |
| [Stellar](/chains/stellar.md) | Horizon REST API            |
| [TRON](/chains/tron.md)       | HTTP API + JSON-RPC         |
| [IOTA](/chains/iota.md)       | REST API                    |
| [Nervos](/chains/nervos.md)   | CKB JSON-RPC                |
| [Fuel](/chains/fuel.md)       | FuelVM · GraphQL            |

### Emerging Networks

[0G](/chains/0g.md) · [Allora](/chains/allora.md) · [Atleta](/chains/atleta.md) · [Midnight](/chains/midnight.md) · [Monad](/chains/monad.md) · [Somnia](/chains/somnia.md)

***

## Quick Start

Every EVM endpoint accepts standard HTTP POST with a JSON-RPC 2.0 body. The example below queries the latest block number — replace the endpoint URL with any other chain from the sections above.

{% tabs %}
{% tab title="cURL" %}

```bash
curl https://rpc.crypto-chief.com/{network}/{YOUR_API_KEY} \
  -X POST \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'
```

{% endtab %}

{% tab title="JavaScript" %}

```javascript
const response = await fetch("https://rpc.crypto-chief.com/{network}/{YOUR_API_KEY}", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    jsonrpc: "2.0",
    method: "eth_blockNumber",
    params: [],
    id: 1
  })
});
const data = await response.json();
console.log(data);
```

{% endtab %}

{% tab title="Python" %}

```python
import requests

response = requests.post(
    "https://rpc.crypto-chief.com/{network}/{YOUR_API_KEY}",
    json={
        "jsonrpc": "2.0",
        "method": "eth_blockNumber",
        "params": [],
        "id": 1
    }
)
print(response.json())
```

{% endtab %}

{% tab title="ethers.js" %}

```javascript
import { ethers } from "ethers";

const provider = new ethers.JsonRpcProvider(
  "https://rpc.crypto-chief.com/{network}/{YOUR_API_KEY}"
);
const blockNumber = await provider.getBlockNumber();
console.log(blockNumber);
```

{% endtab %}
{% endtabs %}

Each chain's documentation page lists its exact endpoint URL, supported methods, and request/response examples.

***

{% hint style="success" %}
**Ready to connect?** Sign up at [crypto-chief.com/rpc](https://crypto-chief.com/rpc/) — free tier included, no credit card required.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs-rpc.crypto-chief.com/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.