---
title: "How to choose a reliable Bitcoin RPC endpoint"
description: "A 10-point checklist for choosing a Bitcoin RPC endpoint, a sourced comparison of seven providers, and a script that tests correctness and freshness before you commit."
datePublished: "2026-11-20"
dateModified: "2026-11-20"
---

# How to choose a reliable Bitcoin RPC endpoint

<ImageBlock
  src="https://media.alchemy.com/bitcoin-rpc-endpoint-overview-2026-11-20.webp"
  alt="How to choose a reliable Bitcoin RPC endpoint title card"
  width={2000}
  height={1125}
  priority
/>

Every deposit your app credits, every withdrawal it broadcasts and every balance it shows passes through a Bitcoin RPC endpoint first. When that endpoint falls behind the chain or drops a request, your users see a missing deposit or a stuck payout.

A Bitcoin RPC endpoint is a URL that takes JSON-RPC requests, such as "what's the latest block?" or "broadcast this transaction," and passes them to a Bitcoin node. A reliable one returns data that matches the chain, stays up under load, supports the methods your app calls, and tells you why a request failed.

A reliable endpoint agrees with the chain, every time.

**At a glance**

- Judge providers on [ten criteria](#the-bitcoin-rpc-reliability-checklist). Correct data and uptime come first.
- Test before you commit: run the [script below](#how-do-you-test-a-bitcoin-rpc-endpoint-before-you-commit) against the endpoint and a second source for an hour.
- Compare providers on chain coverage, indexed data, streaming and SOC 2, using each provider's own pages.
- Alchemy puts Bitcoin, Litecoin, Dogecoin and Bitcoin Cash on the same API key and dashboard as 100+ other chains, and the free plan includes Bitcoin JSON-RPC.

## The Bitcoin RPC reliability checklist

Ten criteria cover the ways a Bitcoin endpoint fails in production, and you can test each one yourself. Correct data and uptime come first. A fast endpoint that serves a stale block still credits deposits late.

<EmbeddedTable
  table={{
    columns: [
      { key: "c0", title: "#", dataType: "object" },
      { key: "c1", title: "Criterion", dataType: "object" },
      { key: "c2", title: "What good looks like", dataType: "object" },
      { key: "c3", title: "How to test it", dataType: "object" },
      { key: "c4", title: "Matters most for", dataType: "object" },
    ],
    data: [
      {
        c0: { title: "<p>1</p>", tooltip: "", icon: "" },
        c1: { title: "<p>Correct chain data</p>", tooltip: "", icon: "" },
        c2: { title: "<p>Same blocks and hashes as the network, even after a reorg (the chain swapping out its newest blocks)</p>", tooltip: "", icon: "" },
        c3: { title: "<p>Compare <code>getblockhash</code> with a second source, 6 blocks below the tip</p>", tooltip: "", icon: "" },
        c4: { title: "<p>Custody, payments, reconciliation</p>", tooltip: "", icon: "" },
        id: 0,
      },
      {
        c0: { title: "<p>2</p>", tooltip: "", icon: "" },
        c1: { title: "<p>Availability</p>", tooltip: "", icon: "" },
        c2: { title: "<p>Keeps answering when a node behind it fails</p>", tooltip: "", icon: "" },
        c3: { title: "<p>Over an hour, count failures, timeouts and blocks behind. Read the status page history</p>", tooltip: "", icon: "" },
        c4: { title: "<p>Exchanges</p>", tooltip: "", icon: "" },
        id: 1,
      },
      {
        c0: { title: "<p>3</p>", tooltip: "", icon: "" },
        c1: { title: "<p>Method and node support</p>", tooltip: "", icon: "" },
        c2: { title: "<p>Every method you call, on unpruned nodes with a full transaction index (<code>txindex</code>)</p>", tooltip: "", icon: "" },
        c3: { title: "<p>Call each method. Fetch an old transaction by its ID alone</p>", tooltip: "", icon: "" },
        c4: { title: "<p>Custody, reconciliation, analytics</p>", tooltip: "", icon: "" },
        id: 2,
      },
      {
        c0: { title: "<p>4</p>", tooltip: "", icon: "" },
        c1: { title: "<p>Rate limits</p>", tooltip: "", icon: "" },
        c2: { title: "<p>Handles your peak without HTTP 429 (too many requests) errors</p>", tooltip: "", icon: "" },
        c3: { title: "<p>Send peak traffic and count 429s separately</p>", tooltip: "", icon: "" },
        c4: { title: "<p>Exchanges, analytics</p>", tooltip: "", icon: "" },
        id: 3,
      },
      {
        c0: { title: "<p>5</p>", tooltip: "", icon: "" },
        c1: { title: "<p>Latency from your region</p>", tooltip: "", icon: "" },
        c2: { title: "<p>Fast enough from your own servers</p>", tooltip: "", icon: "" },
        c3: { title: "<p>Time successful calls only. Count timeouts as failures</p>", tooltip: "", icon: "" },
        c4: { title: "<p>Trading</p>", tooltip: "", icon: "" },
        id: 4,
      },
      {
        c0: { title: "<p>6</p>", tooltip: "", icon: "" },
        c1: { title: "<p>Broadcast reliability</p>", tooltip: "", icon: "" },
        c2: { title: "<p>Your transactions reach other nodes' mempools (their queues of unconfirmed transactions)</p>", tooltip: "", icon: "" },
        c3: { title: "<p>Run <code>testmempoolaccept</code> on mainnet, then a small send on testnet4</p>", tooltip: "", icon: "" },
        c4: { title: "<p>Payments</p>", tooltip: "", icon: "" },
        id: 5,
      },
      {
        c0: { title: "<p>7</p>", tooltip: "", icon: "" },
        c1: { title: "<p>Debuggability</p>", tooltip: "", icon: "" },
        c2: { title: "<p>Clear errors, request logs, Bitcoin on the status page</p>", tooltip: "", icon: "" },
        c3: { title: "<p>Send a bad request and read the error</p>", tooltip: "", icon: "" },
        c4: { title: "<p>Every team</p>", tooltip: "", icon: "" },
        id: 6,
      },
      {
        c0: { title: "<p>8</p>", tooltip: "", icon: "" },
        c1: { title: "<p>Security</p>", tooltip: "", icon: "" },
        c2: { title: "<p>A SOC 2 Type II report</p>", tooltip: "", icon: "" },
        c3: { title: "<p>Ask for the report and check the trust page</p>", tooltip: "", icon: "" },
        c4: { title: "<p>Regulated teams</p>", tooltip: "", icon: "" },
        id: 7,
      },
      {
        c0: { title: "<p>9</p>", tooltip: "", icon: "" },
        c1: { title: "<p>Support</p>", tooltip: "", icon: "" },
        c2: { title: "<p>A real person who answers fast</p>", tooltip: "", icon: "" },
        c3: { title: "<p>Send a technical question before you buy. Ask about a signed SLA</p>", tooltip: "", icon: "" },
        c4: { title: "<p>Every team</p>", tooltip: "", icon: "" },
        id: 8,
      },
      {
        c0: { title: "<p>10</p>", tooltip: "", icon: "" },
        c1: { title: "<p>Exit cost</p>", tooltip: "", icon: "" },
        c2: { title: "<p>Standard methods, with equivalents for any indexed calls</p>", tooltip: "", icon: "" },
        c3: { title: "<p>List your non-standard calls and check the new provider</p>", tooltip: "", icon: "" },
        c4: { title: "<p>Every team</p>", tooltip: "", icon: "" },
        id: 9,
      },
    ],
  }}
/>

## How do Bitcoin RPC providers compare?

The table compares providers on chain coverage, indexed data, streaming and compliance, using each provider's own pages. It doesn't rank performance. "Not stated" means we couldn't confirm the item on the provider's pages.

<EmbeddedTable
  table={{
    columns: [
      { key: "c0", title: "Provider", dataType: "object" },
      { key: "c1", title: "UTXO chains", dataType: "object" },
      { key: "c2", title: "Bitcoin node and data", dataType: "object" },
      { key: "c3", title: "Streaming", dataType: "object" },
      { key: "c4", title: "Free tier with Bitcoin", dataType: "object" },
      { key: "c5", title: "Dedicated Bitcoin option", dataType: "object" },
      { key: "c6", title: "SOC 2", dataType: "object" },
      { key: "c7", title: "Status page lists Bitcoin", dataType: "object" },
    ],
    data: [
      {
        c0: { title: "<p>Alchemy</p>", tooltip: "", icon: "" },
        c1: { title: "<p>BTC, BCH, LTC, DOGE</p>", tooltip: "", icon: "" },
        c2: { title: "<p>Unpruned full nodes with txindex; indexed UTXO API</p>", tooltip: "", icon: "" },
        c3: { title: "<p>WebSocket</p>", tooltip: "", icon: "" },
        c4: { title: "<p>Yes (JSON-RPC)</p>", tooltip: "", icon: "" },
        c5: { title: "<p>Yes</p>", tooltip: "", icon: "" },
        c6: { title: "<p>Type II</p>", tooltip: "", icon: "" },
        c7: { title: "<p>Yes</p>", tooltip: "", icon: "" },
        id: 0,
      },
      {
        c0: { title: "<p>Blockdaemon</p>", tooltip: "", icon: "" },
        c1: { title: "<p>BTC, BCH, LTC, DOGE</p>", tooltip: "", icon: "" },
        c2: { title: "<p>UTXO data via custom RPC methods and REST</p>", tooltip: "", icon: "" },
        c3: { title: "<p>Event streaming</p>", tooltip: "", icon: "" },
        c4: { title: "<p>Not stated</p>", tooltip: "", icon: "" },
        c5: { title: "<p>Yes</p>", tooltip: "", icon: "" },
        c6: { title: "<p>Type II</p>", tooltip: "", icon: "" },
        c7: { title: "<p>Yes</p>", tooltip: "", icon: "" },
        id: 1,
      },
      {
        c0: { title: "<p>Blockstream</p>", tooltip: "", icon: "" },
        c1: { title: "<p>BTC, Liquid</p>", tooltip: "", icon: "" },
        c2: { title: "<p>Indexed Esplora REST and Electrum; Bitcoin Core JSON-RPC not stated</p>", tooltip: "", icon: "" },
        c3: { title: "<p>Not stated</p>", tooltip: "", icon: "" },
        c4: { title: "<p>Yes</p>", tooltip: "", icon: "" },
        c5: { title: "<p>Yes</p>", tooltip: "", icon: "" },
        c6: { title: "<p>Not stated</p>", tooltip: "", icon: "" },
        c7: { title: "<p>Yes</p>", tooltip: "", icon: "" },
        id: 2,
      },
      {
        c0: { title: "<p>Chainstack</p>", tooltip: "", icon: "" },
        c1: { title: "<p>BTC; LTC and DOGE on dedicated nodes</p>", tooltip: "", icon: "" },
        c2: { title: "<p>Unpruned with txindex</p>", tooltip: "", icon: "" },
        c3: { title: "<p>Not stated</p>", tooltip: "", icon: "" },
        c4: { title: "<p>Yes</p>", tooltip: "", icon: "" },
        c5: { title: "<p>Yes</p>", tooltip: "", icon: "" },
        c6: { title: "<p>Type II</p>", tooltip: "", icon: "" },
        c7: { title: "<p>Yes</p>", tooltip: "", icon: "" },
        id: 3,
      },
      {
        c0: { title: "<p>GetBlock</p>", tooltip: "", icon: "" },
        c1: { title: "<p>BTC, BCH, LTC, DOGE</p>", tooltip: "", icon: "" },
        c2: { title: "<p>Full node; indexed Blockbook API</p>", tooltip: "", icon: "" },
        c3: { title: "<p>WebSocket via Blockbook (paid plans)</p>", tooltip: "", icon: "" },
        c4: { title: "<p>Yes</p>", tooltip: "", icon: "" },
        c5: { title: "<p>Yes</p>", tooltip: "", icon: "" },
        c6: { title: "<p>Type II</p>", tooltip: "", icon: "" },
        c7: { title: "<p>Not stated</p>", tooltip: "", icon: "" },
        id: 4,
      },
      {
        c0: { title: "<p>NOWNodes</p>", tooltip: "", icon: "" },
        c1: { title: "<p>BTC, BCH, LTC, DOGE</p>", tooltip: "", icon: "" },
        c2: { title: "<p>Full node; indexed Blockbook API</p>", tooltip: "", icon: "" },
        c3: { title: "<p>WebSocket on paid plans</p>", tooltip: "", icon: "" },
        c4: { title: "<p>Yes (trial)</p>", tooltip: "", icon: "" },
        c5: { title: "<p>Yes</p>", tooltip: "", icon: "" },
        c6: { title: "<p>Not stated</p>", tooltip: "", icon: "" },
        c7: { title: "<p>Not stated</p>", tooltip: "", icon: "" },
        id: 5,
      },
      {
        c0: { title: "<p>QuickNode</p>", tooltip: "", icon: "" },
        c1: { title: "<p>BTC, BCH; LTC and DOGE as paid add-ons</p>", tooltip: "", icon: "" },
        c2: { title: "<p>Pruning disabled; Blockbook add-on</p>", tooltip: "", icon: "" },
        c3: { title: "<p>Streams (block data only)</p>", tooltip: "", icon: "" },
        c4: { title: "<p>Yes (trial)</p>", tooltip: "", icon: "" },
        c5: { title: "<p>Yes (Enterprise)</p>", tooltip: "", icon: "" },
        c6: { title: "<p>Type II</p>", tooltip: "", icon: "" },
        c7: { title: "<p>Yes</p>", tooltip: "", icon: "" },
        id: 6,
      },
    ],
  }}
/>

Sources: each provider's own docs, pricing, security and status pages, checked November 19, 2026. Start with [Alchemy](https://www.alchemy.com/docs/bitcoin/bitcoin-api-overview), [Blockdaemon](https://docs.blockdaemon.com/reference/rpc-api-overview), [Blockstream](https://help.blockstream.com/blockstream-explorer-api), [Chainstack](https://chainstack.com/build-better-with-bitcoin/), [GetBlock](https://getblock.io/nodes/btc/), [NOWNodes](https://nownodes.io/nodes/bitcoin-btc) and [QuickNode](https://www.quicknode.com/docs/bitcoin).

If you need balances and address history, start with the node and data column, because Bitcoin Core keeps no address index. If you need real-time updates, check streaming. In a regulated industry, start with SOC 2.

## How do you test a Bitcoin RPC endpoint before you commit?

Run the script below against the endpoint and a second source for an hour, then compare. Think of the second source like a second clock in a server room: one clock can't tell you it's wrong, but two clocks that disagree tell you to look.

Your second source can be your own Bitcoin Core node or another provider. Over an hour (about six new blocks), the script counts failures by type, times successful calls, tracks how far the endpoint trails, and checks that both sources agree on the block hash six blocks below the tip. At about one request per second it isn't a load test, so test peak throughput separately.

<CodeSnippet
  language="javascript"
  code={"// test-endpoint.mjs: check a Bitcoin RPC endpoint against a second source. Node 18+, no dependencies.\n// PRIMARY_URL=https://bitcoin-mainnet.g.alchemy.com/v2/YOUR_KEY REFERENCE_URL=http://user:pass@127.0.0.1:8332 node test-endpoint.mjs\nconst env = process.env;\nconst DURATION_S = Number(env.DURATION_S ?? 3600); // an hour sees ~6 new blocks\nconst INTERVAL_MS = Number(env.INTERVAL_MS ?? 2000);\nconst TIMEOUT_MS = Number(env.TIMEOUT_MS ?? 5000); // slower than this counts as a timeout\nconst DEPTH = 6; // compare hashes 6 blocks below the tip, past normal reorgs\n// A 200 response only counts if the result has the right shape.\nconst VALID = { getblockcount: Number.isInteger, getblockhash: (h) => /^[0-9a-f]{64}$/.test(h) };\nif (!env.PRIMARY_URL || !env.REFERENCE_URL) throw new Error(\"Set PRIMARY_URL and REFERENCE_URL.\");\n\n// fetch() rejects user:pass in URLs, so move credentials into a header.\nfunction target(raw) {\n  const url = new URL(raw);\n  const headers = { \"content-type\": \"application/json\" };\n  if (url.username) {\n    const creds = `${decodeURIComponent(url.username)}:${decodeURIComponent(url.password)}`;\n    headers.authorization = \"Basic \" + Buffer.from(creds).toString(\"base64\");\n    url.username = url.password = \"\";\n  }\n  return { url: url.toString(), headers };\n}\n\nasync function rpc({ url, headers }, method, params = []) {\n  const started = performance.now();\n  try {\n    const res = await fetch(url, { method: \"POST\", headers, signal: AbortSignal.timeout(TIMEOUT_MS),\n      body: JSON.stringify({ jsonrpc: \"2.0\", id: 1, method, params }) });\n    const text = await res.text();\n    const ms = performance.now() - started;\n    let body;\n    try { body = JSON.parse(text); } catch { return { kind: res.ok ? \"bad_response\" : `http_${res.status}` }; }\n    if (body?.error) return { kind: `rpc_${body.error.code}` }; // Bitcoin Core before v28 sends these as HTTP 500\n    if (!res.ok) return { kind: `http_${res.status}` };\n    if (!VALID[method](body?.result)) return { kind: \"bad_response\" };\n    return { ok: true, result: body.result, ms };\n  } catch (err) {\n    return { kind: err.name === \"TimeoutError\" || err.name === \"AbortError\" ? \"timeout\" : \"network\" };\n  }\n}\n\nconst P = target(env.PRIMARY_URL), R = target(env.REFERENCE_URL);\nconst latencies = [], errors = {}, referenceErrors = {}, checked = new Set(), mismatches = new Set();\nlet calls = 0, maxBehind = 0, behindSince = null, longestBehindMs = 0;\nconst tally = (bag, r) => r.ok || (bag[r.kind] = (bag[r.kind] ?? 0) + 1);\n\n// Call both endpoints at once. Returns [primary, reference] results, or null if either failed.\nasync function both(method, params) {\n  const [p, r] = await Promise.all([rpc(P, method, params), rpc(R, method, params)]);\n  calls++;\n  tally(errors, p);\n  tally(referenceErrors, r);\n  if (p.ok) latencies.push(p.ms);\n  return p.ok && r.ok ? [p.result, r.result] : null;\n}\n\nconsole.log(`Testing for ${DURATION_S}s...`);\nfor (const end = Date.now() + DURATION_S * 1000; Date.now() < end; await new Promise((r) => setTimeout(r, INTERVAL_MS))) {\n  const heights = await both(\"getblockcount\"); // does the primary keep up?\n  if (!heights) continue;\n  const behind = heights[1] - heights[0];\n  maxBehind = Math.max(maxBehind, behind);\n  behindSince = behind > 0 ? behindSince ?? Date.now() : null;\n  if (behindSince) longestBehindMs = Math.max(longestBehindMs, Date.now() - behindSince);\n  const height = Math.min(...heights) - DEPTH;\n  const hashes = await both(\"getblockhash\", [height]); // do both agree on a settled block?\n  if (!hashes) continue;\n  checked.add(height);\n  if (hashes[0] !== hashes[1]) mismatches.add(height);\n}\n\nconst sorted = latencies.sort((a, b) => a - b);\nconst pct = (q) => (sorted.length ? Math.round(sorted[Math.min(sorted.length - 1, Math.floor(q * sorted.length))]) : null);\nconst failed = Object.values(errors).reduce((a, b) => a + b, 0);\nconsole.log({\n  primaryCalls: calls,\n  failures: errors,\n  failureRate: `${((100 * failed) / Math.max(calls, 1)).toFixed(2)}%`,\n  latencyMsOnSuccess: { p50: pct(0.5), p95: pct(0.95), p99: pct(0.99) },\n  maxBlocksBehindReference: maxBehind,\n  longestSecondsBehind: Math.round(longestBehindMs / 1000),\n  blockHeightsChecked: checked.size,\n  hashMismatchesAtHeights: [...mismatches],\n  referenceFailures: referenceErrors, // if this is high, pick a better second source\n});\n"}
/>

Run it with your own endpoint URLs:

<CodeSnippet
  language="bash"
  code={"PRIMARY_URL=https://bitcoin-mainnet.g.alchemy.com/v2/YOUR_KEY \\\nREFERENCE_URL=https://your-second-source.example \\\nDURATION_S=3600 node test-endpoint.mjs\n"}
/>

If your second source is your own Bitcoin Core node, put its RPC username and password in the URL, such as `http://user:pass@127.0.0.1:8332`. The script moves them into an authorization header.

Here's how to read the output:

<EmbeddedTable
  table={{
    columns: [
      { key: "c0", title: "Field", dataType: "object" },
      { key: "c1", title: "Healthy", dataType: "object" },
      { key: "c2", title: "If not", dataType: "object" },
    ],
    data: [
      {
        c0: { title: "<p><code>failureRate</code></p>", tooltip: "", icon: "" },
        c1: { title: "<p>Close to 0%</p>", tooltip: "", icon: "" },
        c2: { title: "<p><code>http_429</code>: you're at your plan's rate limit. <code>rpc_</code>: the node returned an error. <code>bad_response</code>: no usable answer, such as a gateway error page or an empty result</p>", tooltip: "", icon: "" },
        id: 0,
      },
      {
        c0: { title: "<p><code>maxBlocksBehindReference</code></p>", tooltip: "", icon: "" },
        c1: { title: "<p>0 or 1</p>", tooltip: "", icon: "" },
        c2: { title: "<p>Each block behind is about 10 minutes of missing transactions</p>", tooltip: "", icon: "" },
        id: 1,
      },
      {
        c0: { title: "<p><code>longestSecondsBehind</code></p>", tooltip: "", icon: "" },
        c1: { title: "<p>A few seconds</p>", tooltip: "", icon: "" },
        c2: { title: "<p>Minutes behind means stale data, even at one block</p>", tooltip: "", icon: "" },
        id: 2,
      },
      {
        c0: { title: "<p><code>blockHeightsChecked</code></p>", tooltip: "", icon: "" },
        c1: { title: "<p>More than 2</p>", tooltip: "", icon: "" },
        c2: { title: "<p>Run the test longer</p>", tooltip: "", icon: "" },
        id: 3,
      },
      {
        c0: { title: "<p><code>hashMismatchesAtHeights</code></p>", tooltip: "", icon: "" },
        c1: { title: "<p>Empty</p>", tooltip: "", icon: "" },
        c2: { title: "<p>One source is almost certainly on the wrong chain</p>", tooltip: "", icon: "" },
        id: 4,
      },
      {
        c0: { title: "<p><code>referenceFailures</code></p>", tooltip: "", icon: "" },
        c1: { title: "<p>Low</p>", tooltip: "", icon: "" },
        c2: { title: "<p>Your second source is the problem. Pick another and rerun</p>", tooltip: "", icon: "" },
        id: 5,
      },
    ],
  }}
/>

Run the test at your busiest time of day, from the region where your servers run. The same rules we follow for our public [RPC benchmarks](https://www.alchemy.com/benchmarks) apply: send every provider the same requests at the same time, and report failures next to latency.

## When is Alchemy the right Bitcoin RPC provider?

Alchemy is a good fit if you want Bitcoin, Litecoin, Dogecoin and Bitcoin Cash on the same [RPC platform](https://www.alchemy.com/rpc-api) you already use for [Ethereum](https://www.alchemy.com/overviews/best-ethereum-rpc-providers), [Solana](https://www.alchemy.com/overviews/solana-rpc) and 100+ other chains: one API key, one dashboard, one bill.

Choose Alchemy if:

- **You already run EVM or Solana on Alchemy.** Bitcoin becomes one more network on your app, with no new vendor or security review.
- **You need balances, UTXOs and address history.** Our indexed UTXO API answers those over REST, including lookups by xpub (an extended public key that derives all of a wallet's addresses) and output descriptor.
- **You need real-time updates.** Our Bitcoin WebSockets stream new blocks and activity on the addresses you watch. Address activity webhooks for Bitcoin and Dogecoin are in beta.
- **You're migrating from another UTXO API.** Our [UTXO migration guide](https://www.alchemy.com/docs/bitcoin/utxo-migration-guide) maps QuickNode, BlockCypher and Blockdaemon calls to Alchemy.
- **Your security review requires SOC 2 Type II.** We're certified, and our [trust center](https://trust.alchemy.com) has the details.

Supported node methods work the same as on your own Bitcoin Core node. Check the [method list](https://www.alchemy.com/docs/bitcoin/bitcoin-api-overview) for the ones you call. Wallet methods like `getbalance` and `listunspent` aren't available on our endpoints, so use the indexed UTXO API for balances.

## What about Litecoin, Dogecoin and Bitcoin Cash?

All three come from Bitcoin's codebase, so they share its UTXO model, most of its JSON-RPC methods and the same checklist.

<EmbeddedTable
  table={{
    columns: [
      { key: "c0", title: "Chain", dataType: "object" },
      { key: "c1", title: "Block time", dataType: "object" },
      { key: "c2", title: "What's different", dataType: "object" },
      { key: "c3", title: "Networks we support", dataType: "object" },
    ],
    data: [
      {
        c0: { title: "<p>Litecoin</p>", tooltip: "", icon: "" },
        c1: { title: "<p>About 2.5 minutes</p>", tooltip: "", icon: "" },
        c2: { title: "<p>\"Two blocks behind\" is a smaller gap than on Bitcoin</p>", tooltip: "", icon: "" },
        c3: { title: "<p>Mainnet, testnet</p>", tooltip: "", icon: "" },
        id: 0,
      },
      {
        c0: { title: "<p>Dogecoin</p>", tooltip: "", icon: "" },
        c1: { title: "<p>About 1 minute</p>", tooltip: "", icon: "" },
        c2: { title: "<p>Blocks arrive about ten times as often as on Bitcoin</p>", tooltip: "", icon: "" },
        c3: { title: "<p>Mainnet</p>", tooltip: "", icon: "" },
        id: 1,
      },
      {
        c0: { title: "<p>Bitcoin Cash</p>", tooltip: "", icon: "" },
        c1: { title: "<p>About 10 minutes</p>", tooltip: "", icon: "" },
        c2: { title: "<p>Uses <code>estimatefee</code> instead of <code>estimatesmartfee</code></p>", tooltip: "", icon: "" },
        c3: { title: "<p>Mainnet, testnet</p>", tooltip: "", icon: "" },
        id: 2,
      },
    ],
  }}
/>

The [UTXO chains guide](https://www.alchemy.com/blog/how-to-build-on-utxo-chains) explains how all four differ from account-based chains like Ethereum.

## How do you get a Bitcoin RPC endpoint on Alchemy?

Create an app, enable Bitcoin, and send a request.

1. Sign in to the [Alchemy dashboard](https://dashboard.alchemy.com/) and create an app.
2. Enable Bitcoin Mainnet.
3. Copy the endpoint URL. It looks like `https://bitcoin-mainnet.g.alchemy.com/v2/YOUR_KEY`.
4. Send a request:

<CodeSnippet
  language="bash"
  code={"curl -X POST https://bitcoin-mainnet.g.alchemy.com/v2/YOUR_KEY \\\n  -H \"Content-Type: application/json\" \\\n  -d '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"getblockcount\",\"params\":[]}'\n"}
/>

The response is the current block height. The [Bitcoin API reference](https://www.alchemy.com/docs/bitcoin/bitcoin-api-overview) lists every supported method.

The [indexed UTXO API](https://www.alchemy.com/docs/chains/bitcoin/utxo-api-endpoints/utxo-api-endpoints/get-utxo) (balances, UTXOs, address and xpub history) is a paid add-on. On pay-as-you-go plans you buy it per chain from the dashboard, and [Enterprise plans](https://www.alchemy.com/enterprise) include it along with a signed SLA. For capacity reserved for your team alone, see [Dedicated Clusters](https://www.alchemy.com/dedicated-clusters) or [talk to our team](https://www.alchemy.com/contact-sales).

<CalloutBlock>

Ready to see for yourself? [Create a free Bitcoin endpoint](https://dashboard.alchemy.com/signup/?a=overviews%2Fbitcoin-rpc-endpoint) and run the test script against it. No sales call, no contract. For Enterprise plans or Dedicated Clusters, [talk to our team](https://www.alchemy.com/contact-sales).

</CalloutBlock>

## Frequently asked questions

### How do I choose a reliable Bitcoin RPC endpoint?

Compare providers on ten criteria: correctness, availability, method and node support, rate limits, latency from your region, broadcast reliability, debuggability, security, support and exit cost. Then test your shortlist against a second source for an hour. Count failures, timeouts, blocks behind and block-hash mismatches, and time successful calls only.

### What is a Bitcoin RPC provider?

A Bitcoin RPC provider runs Bitcoin nodes for you and gives you an endpoint URL for JSON-RPC requests. The provider handles syncing, upgrades and disk growth. Many providers also offer indexed APIs for balances and address history, which Bitcoin Core doesn't provide on its own.

### Should I run my own Bitcoin node or use a provider?

Run your own node for local development, or if you need full control of its configuration. Use a provider in production if you'd rather not run syncing, upgrades, monitoring and an address indexer yourself. Many teams do both, and use their own node as the second source when they test a provider.

### Which Bitcoin RPC methods should my provider support?

At a minimum: `getblockcount`, `getblockhash`, `getblock`, `getrawtransaction`, `sendrawtransaction`, `estimatesmartfee`, `getblockchaininfo` and mempool methods such as `getrawmempool`. Check that `getrawtransaction` finds old transactions by ID alone, which requires txindex. Wallets and custody apps also need balance, UTXO and xpub lookups from an indexed API.

### Does Alchemy support Bitcoin, Litecoin, Dogecoin and Bitcoin Cash?

Yes. Alchemy supports JSON-RPC on Bitcoin, Litecoin, Dogecoin and Bitcoin Cash, plus an indexed UTXO API for balances, UTXOs and address history on all four. The indexed API is a per-chain add-on on pay-as-you-go plans and is included on Enterprise. All four share one dashboard and API key with 100+ other chains.

### Does Alchemy offer an archive Bitcoin node?

Yes, in the sense Bitcoin teams usually mean. Alchemy's Bitcoin endpoints run on unpruned full nodes with a full transaction index (txindex), so you can fetch any block and any confirmed transaction by its ID. For address balances and history, use the indexed UTXO API, because Bitcoin Core keeps no address index.

### What happens during a chain reorg?

A reorg happens when the network replaces its newest block, or several, with a competing branch. Transactions in the replaced blocks, other than miners' rewards, go back to the mempool, and most confirm again later. One can drop out if a conflicting transaction confirmed on the new branch, so wait for enough confirmations before crediting deposits, and be ready to reverse.

### Is there a free Bitcoin RPC endpoint?

Yes. Several providers include Bitcoin JSON-RPC on a free plan, including Alchemy, and free public endpoints exist for testing. Free plans have lower rate limits, and public endpoints have no uptime commitment, so use them for development. On Alchemy, the indexed UTXO API isn't available on the free plan.
