Bitcoin

The Bitcoin Gateway provides Bitcoin Core-style JSON-RPC over HTTP for chain, block, and transaction data. Its native asset is BTC.

Supported networks

Bitcoin does not use an EVM Chain ID. Copy the complete Access Point from the dashboard.

Endpoint-free calls

On an Accelerator hit, getblockchaininfo, getblockhash([height]), and getblock([hash, 3]) work without an Endpoint. See Accelerator for exact parameter forms and cache limitations.

Configure complete method access

Provider sync does not currently cover Bitcoin:

1. Create a Gateway for the target Bitcoin network.
2. Manually add a JSON-RPC Bitcoin Endpoint on the same network and configure upstream credentials on the Endpoint.
3. Add the Endpoint to the default JSON-RPC route and complete its health check.
4. Call getblockchaininfo and inspect chain to verify the network.

curl '<bitcoin_access_point>' \
  -H 'Authorization: Bearer <app_api_key>' \
  -H 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"getblockchaininfo","params":[]}'

chain should be main on Mainnet and is normally test on Testnet.

Accelerator may answer getblockchaininfo. To verify your own Endpoint, also inspect its health check and route state.

Current limits

• Single Bitcoin JSON-RPC calls over HTTP are supported; batch, WebSocket, ZMQ, and public gRPC are not.
• Esplora, Electrum, and vendor-specific REST endpoints are not exposed.
• Wallet methods, indexes, pruning, and historical data depend on upstream configuration.
• The Gateway does not manage node wallets or fail over between Mainnet and Testnet.

See JSON-RPC and Errors and troubleshooting for shared behavior.