What is the BOB RPC URL?

The BOB Mainnet RPC URL with BoltRPC is https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/bob. Replace YOUR_API_KEY with your API key from dashboard.boltrpc.io. The chain ID is 60808.

How do I add BOB to MetaMask?

Open MetaMask, go to Settings, then Networks, then Add Network, and enter: Network Name: BoltRPC BOB, RPC URL: https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/bob, Chain ID: 60808, Currency Symbol: ETH, Block Explorer: https://explorer.gobob.xyz.

Is BOB EVM compatible?

Yes. BOB is built on the OP Stack and is EVM equivalent. Solidity contracts deploy without modification and standard Ethereum tooling works out of the box. Only the RPC URL and Chain ID (60808) change.

What is BOB and who is it for?

BOB stands for Build on Bitcoin. It is a hybrid Layer 2 that combines EVM smart contracts with Bitcoin's asset base: wrapped BTC, Bitcoin liquid staking tokens and BTC-denominated DeFi are its core ecosystem.

What gas token does BOB use?

BOB uses ETH for gas, like other OP Stack chains. BTC and Bitcoin-derived assets circulate on the network as tokens, but transaction fees are paid in ETH.

Why do public BOB RPCs fail in production?

Public BOB endpoints are shared infrastructure serving many applications simultaneously. Under load they rate-limit requests, return stale block data, and drop WebSocket connections. Production applications need a dedicated provider.

Does BoltRPC support WebSocket for BOB?

Yes. BoltRPC provides WebSocket endpoints for BOB at wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/bob. Use WebSocket for real-time event streaming: new blocks, pending transactions, contract event logs.

BOB RPC Endpoint

BOB (Build on Bitcoin) brings Bitcoin liquidity into an EVM rollup. A dedicated endpoint keeps your BTC DeFi protocol in sync, with debug methods included.

chain id · 60808JSON-RPC 2.0WebSocketDebug

Start free trial Contact sales

LIVE LATENCY

29ms

LIVE

gateway round-trip · sampled every second

IN PRODUCTION AT Chainlink

Your endpoint, ready in one line.

Drop this URL into your RPC client, HTTP library or wallet config. No SDK install required.

HTTPS

https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/bob

WEBSOCKET

wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/bob

Replace YOUR_API_KEY with your API key. Get a free key →

Pick your stack.

Copy-paste examples for the libraries you already use. Swap the API key, hit run.

import { ethers } from "ethers";

const provider = new ethers.JsonRpcProvider(
  "https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/bob"
);

const blockNumber = await provider.getBlockNumber();
console.log("Latest block:", blockNumber);

import { createPublicClient, http } from "viem";
import { bob } from "viem/chains";

const client = createPublicClient({
  chain: bob,
  transport: http("https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/bob"),
});

curl https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/bob \
  -X POST \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

Connect your dApp, bot, or protocol to BOB Mainnet with BoltRPC. BOB (“Build on Bitcoin”) is a hybrid Layer 2 that pairs EVM smart contracts with Bitcoin’s asset base, and predictable request-unit pricing keeps your RPC costs flat while BTC liquidity flows through your contracts.

Chain at a Glance


Chain ID	60808
Protocol	Optimistic rollup on the OP Stack, Bitcoin-focused
Block time	~2 seconds
Gas token	ETH
Settlement	Ethereum mainnet
EVM compatible	Yes (EVM equivalent)

What BOB is Built For

BOB exists to make Bitcoin productive. It is an EVM rollup built on the OP Stack that treats BTC as its first-class asset: wrapped Bitcoin variants, Bitcoin liquid staking tokens and BTC-denominated lending markets are the core of its DeFi ecosystem, and the network integrates Bitcoin staking infrastructure to anchor its security roadmap to Bitcoin itself. For developers this is the practical bridge between the two largest ecosystems in crypto, Solidity contracts, Ethereum tooling and OP Stack infrastructure on one side, Bitcoin liquidity on the other. Contracts deploy unchanged with ethers.js, viem, Foundry and Hardhat, but BTC DeFi workloads, vault accounting, collateral monitoring, bridge watchers, generate sustained RPC load that public endpoints throttle.

Common Use Cases on BOB

BTC lending and collateral monitoring Lending markets built on Bitcoin assets track collateral health continuously. Their backends call eth_call against price oracles and positions on every block to keep health factors current and liquidations timely.

Bridge and mint watchers Assets enter BOB through bridges, and the services that credit deposits watch bridge contracts around the clock. A reliable eth_getLogs pipeline with WebSocket confirmation is the difference between crediting a deposit in seconds and crediting it late.

Liquidation and arbitrage bots BTC-denominated DeFi has the same MEV dynamics as any lending ecosystem. Liquidation bots poll positions at high frequency and need a provider that sustains concurrent request load without throttling.

Indexers and analytics Dashboards tracking BTC liquidity on BOB backfill history and follow the chain head. Fixed per-method request-unit pricing keeps a continuous indexing workload affordable and predictable.

Built for teams that ship on BOB.

Built for BTC DeFi workloads

Lending markets and vaults denominated in Bitcoin assets live on fresh collateral state. Their backends run eth_call against oracles and positions continuously; a dedicated endpoint keeps those reads fast when the market moves and everyone else is reading too.

Debug methods included

BoltRPC serves debug_* methods on BOB, so you can trace failing transactions and inspect execution without maintaining your own archive-grade node. Method availability is measured live against our own infrastructure and shown on this page.

EVM equivalence, zero migration friction

BOB is built on the OP Stack and is EVM equivalent. Contracts, scripts and infrastructure written for Ethereum or any OP Stack chain work unchanged: switch the RPC URL, set Chain ID 60808, and you are live.

WebSocket streaming included

Subscribe to new blocks, pending transactions and contract events over WebSocket at no extra charge. Bridge watchers and liquidation bots react to events the moment they land instead of polling for them.

Bitcoin and Ethereum from one provider

BoltRPC serves BOB alongside Bitcoin Core JSON-RPC, Ethereum and 20+ other networks behind one dashboard and one key pattern. A BTC-to-BOB bridge watcher talks to both chains through the same provider.

Full JSON-RPC coverage.

Every standard BOB method you would expect. Archive-only methods are available on request for qualifying plans.

STANDARD5

eth_calleth_getLogseth_sendRawTransactioneth_getTransactionReceiptdebug_traceTransaction

BOB, explained.

Common questions about connecting to BOB over BoltRPC.

Ask a question →Read the docs

: The BOB Mainnet RPC URL with BoltRPC is https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/bob. Replace YOUR_API_KEY with your API key from dashboard.boltrpc.io. The chain ID is 60808.
: Open MetaMask, go to Settings, then Networks, then Add Network, and enter: Network Name: BoltRPC BOB, RPC URL: https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/bob, Chain ID: 60808, Currency Symbol: ETH, Block Explorer: https://explorer.gobob.xyz.
: Yes. BOB is built on the OP Stack and is EVM equivalent. Solidity contracts deploy without modification, and standard Ethereum tooling, ethers.js, viem, Foundry, Hardhat, MetaMask, works out of the box. Only the RPC URL and Chain ID (60808) change.
: BOB stands for "Build on Bitcoin". It is a hybrid Layer 2 that combines EVM smart contracts with Bitcoin's asset base: wrapped BTC, Bitcoin liquid staking tokens and BTC-denominated DeFi are its core ecosystem. It is aimed at teams that want Bitcoin liquidity with Ethereum developer tooling.
: BOB uses ETH for gas, like other OP Stack chains. BTC and Bitcoin-derived assets circulate on the network as tokens, but transaction fees are paid in ETH.
: Public BOB endpoints are shared infrastructure serving many applications simultaneously. Under load they rate-limit requests, return stale block data, and drop WebSocket connections. Production applications need a dedicated provider with consistent response times.
: Yes. BoltRPC provides WebSocket endpoints for BOB at wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/bob. Use WebSocket when you need real-time event streaming: new blocks, pending transactions, contract event logs.

Ship on BOB this week.

An API key in under 60 seconds, BOB plus 34 other chains, and a team that answers when you write.

Start free trial View pricing