BOB (Build on Bitcoin)

BOB is a hybrid Bitcoin Layer 2 that brings Ethereum-compatible smart contracts to Bitcoin. It allows developers to build dapps that settle to Bitcoin while using familiar EVM tooling.

Start indexing

See BOB (Build on Bitcoin) datasets →

Goldsky powers the web3 products you use

How to index BOB (Build on Bitcoin) data with Goldsky

Turbo Pipelines

Stream BOB (Build on Bitcoin) data with the latest blockchain data streaming engine. Vectorized processing, instant deployment, and live data inspection without needing an enterprise team.

Ideal for:

Instant deployment – pipelines spin up in seconds; index BOB (Build on Bitcoin) instantly
Live data previews – inspect what every part of your pipelines produce in real-time
TypeScript transforms – execute custom logic with WebAssembly
Dynamic tables – unlimted filtering on addresses & contracts without redeploying
Local debugging – iterate on BOB (Build on Bitcoin) data on your machine

Mirror

Stream BOB (Build on Bitcoin) data directly into your own database for maximum control. Designed for scaling ambitious projects and unlocking full ownership of your data.

Ideal for:

Teams building on BOB (Build on Bitcoin) who need full control over data storage, infrastructure, and processing
Combining on-chain BOB (Build on Bitcoin) data with off-chain data
Ultra-low latency for the most demanding apps
Multi-chain projects expanding into BOB (Build on Bitcoin) or building cross-chain functionality
High traffic and throughput scenarios

Subgraphs

Query BOB (Build on Bitcoin) data with an instant GraphQL API. Perfect for familiarity, fast setups, on-chain data queries, and getting to market quickly.

Ideal for:

Teams building on BOB (Build on Bitcoin) who want quick setup & minimal infrastructure overhead
Production-ready BOB (Build on Bitcoin) API endpoints
Moderate traffic and throughput scenarios
Predefined data models and standard query patterns
On-chain data from EVM-compatible chains

Website

gobob.xyz

EVM Compatible

Yes

Products

Mirror Subgraphs Turbo Compose

Supported Networks

Mainnet, Testnet

Goldsky Docs

docs.goldsky.com/chains/build-on-bitcoin

Get BOB (Build on Bitcoin) data indexing by --:--

Creating an account is free. No credit card needed.

Get started for free

BOB (Build on Bitcoin) data: frequently asked questions

What is BOB (Build on Bitcoin)?

BOB (Build on Bitcoin) is a blockchain network supported by Goldsky for real-time data indexing and streaming. Goldsky makes it easy to access BOB (Build on Bitcoin) data through subgraphs, data pipelines, and RPC endpoints, so your team spends less time on infrastructure and more time building your product.

How do I start indexing BOB (Build on Bitcoin) data with Goldsky?

Sign up for a free Goldsky account, then deploy a subgraph or pipeline against BOB (Build on Bitcoin) in minutes. Goldsky handles node infrastructure, reorg detection, and data freshness automatically. See the BOB (Build on Bitcoin) docs to get started.

Can I run a subgraph on BOB (Build on Bitcoin)?

Yes. Goldsky Subgraphs run on BOB (Build on Bitcoin) and are fully compatible with The Graph protocol, so you can migrate existing subgraphs with a single CLI command. Queries are served via a standard GraphQL API with sub-second indexing latency.

How do I stream BOB (Build on Bitcoin) data to my database or data warehouse?

Goldsky Mirror streams BOB (Build on Bitcoin) blockchain data in real time to destinations like PostgreSQL, BigQuery, S3, Kafka, and more. You define a pipeline in a YAML config and Goldsky handles delivery, reorgs, and schema management. No custom ETL code required.

How much does it cost to index BOB (Build on Bitcoin) data with Goldsky?

Goldsky offers a free plan with generous limits so you can start building right away. Paid plans scale with usage. Creating an account is free and no credit card is required to get started.

How fresh is the BOB (Build on Bitcoin) data available through Goldsky?

Goldsky indexes BOB (Build on Bitcoin) blocks as they land on-chain, typically delivering data with sub-second latency after confirmation. Reorgs are handled automatically, so your application always reflects the current canonical chain state.