BOB Hybrid Bitcoin Layer 2: What Build on Bitcoin Does

BOB, short for Build on Bitcoin, is the hybrid Bitcoin Layer 2 on which the Bitcoin.one app is built. According to the Bitcoin.one whitepaper it uses the OP Stack, lets users bring in native BTC through BOB Gateway, and hosts the app’s wallets and contracts. Bitcoin.one is independent of BOB.

What “hybrid” is meant to convey

In the Bitcoin.one whitepaper, BOB is called a hybrid Bitcoin Layer 2. The paper does not define the word further, so we use it as a descriptive label: the network borrows tooling from the Ethereum world, here the OP Stack, while anchoring value to Bitcoin through deposits. For a general framework to judge any such network, see Bitcoin Layer 2 explained. For exact technical and security claims about BOB, rely on BOB’s own documentation, since a third-party site like ours cannot verify them.

What the OP Stack means for users

The OP Stack is the open-source software framework behind Optimism’s chain, and other teams reuse it to launch their own chains (Optimism documentation). For an app developer it means familiar EVM tooling, Solidity contracts and standard wallets. For a user it mostly means the app behaves like an Ethereum-style app with its own, usually lower, fees. It does not by itself tell you how bridged BTC is secured, which is a separate question.

Where BOB sits in the Bitcoin.one architecture

The paper’s chain table gives each network a role:

Chain	Role in the paper
BOB	App chain: wallets, WBTC, PayRouter, CheckoutRouter, BuybackVault, OneStaking, Oku liquidity
Ethereum	BC1 home chain; 21B minted once; presale and claims
Base	Presale; BC1 OFT mirror
BNB Chain	Presale only
Solana	BC1 OFT mirror; presale program

So BOB is where everyday use happens, while Ethereum is where supply is anchored. The swap from BTC to BC1 happens in one step on Oku, a Uniswap v3 deployment on BOB, according to the paper. The relevant contracts include PayRouter for sends and claim links and CheckoutRouter for shop orders; we examine the latter in buying gift cards with crypto.

The deposit path

1. You deposit native BTC through BOB Gateway.
2. The BTC is held as WBTC on BOB.
3. You can send it, swap it to BC1 or withdraw back to Bitcoin.

The paper does not detail how BOB Gateway secures the BTC, who operates it or what the withdrawal time is. It does list “L2 and WBTC custodial risk” in its risk section, which tells you the authors consider wrapped-BTC custody a real exposure. That is the number one question to answer yourself before using any bridge: if the operator fails or is compromised, what happens to the backing?

Key takeaway: the app’s convenience depends on a stack of third parties: the L2, the gateway, the wrapped asset and the DEX. Each one is a separate failure point.

Independence and third-party dependence

Bitcoin.one’s home page states it is an independent app built on BOB and is not affiliated with or endorsed by BOB. The paper also lists BOB, Oku, Reown, Bitrefill, NOWPayments and Supabase among third-party dependencies that can fail or change terms. That candour is useful, and you should read it as a to-do list: for each dependency, ask what the fallback is.

Testnet versus mainnet

The app is live on BOB Sepolia, a test network using test tokens, and the paper says mainnet launches with the token generation event planned for Q1 2027. The project’s buybacks page is labelled as BOB Sepolia and reports its totals as unavailable, which is what you would expect before mainnet. Anything you try now is a rehearsal, and balances on a testnet carry no real value.

Questions to ask before you bridge value

• Who can pause or upgrade the bridge contracts?
• Is there a published audit, and does it cover the gateway?
• What is the exit time, and is there a forced exit?
• Which assets does the app custody, if any? The paper describes the wallet as non-custodial; see smart wallets without a seed phrase.
• What happens to WBTC balances if BOB stops operating?

Reading the claims fairly

We cannot confirm the details of BOB itself from here, and this article does not rate its security. What we can do is separate what the Bitcoin.one paper states from what it leaves out. For the broader product context, visit the Bitcoin.one app page and the risk disclosure. Nothing here is financial advice.

Putting the contracts in order

It helps to picture a single journey through the app, step by step, using only what the paper lists.

1. You sign up and receive a smart wallet on BOB. See our wallet explainer.
2. You deposit BTC. It enters through BOB Gateway and is held as WBTC on BOB.
3. You swap part of it to BC1 on Oku, a Uniswap v3 deployment on BOB.
4. You send BC1 or BTC through PayRouter, which charges 0 with a hard ceiling of 1%.
5. Or you buy a gift card through CheckoutRouter, which charges a 2% margin with a ceiling of 5%.
6. Fees arrive at BuybackVault, which buys BC1, burns half and sends half to rewards.
7. You may stake BC1 in OneStaking, which uses a dynamic APR.

Every one of those steps happens on BOB, which is why the network’s reliability matters to the whole design. If BOB is paused, congested or compromised, all seven steps are affected.

Why the app uses several chains

BC1’s total supply is minted once on Ethereum, which the paper calls the home chain, and mirrored to Base and Solana through LayerZero’s OFT standard, where tokens are burned on one chain and minted on another. BOB hosts the app. This split gives the token wide reach while keeping day-to-day activity on a cheaper chain, at the price of more dependencies: LayerZero, Chainlink and Pyth are all named in the paper’s risk list.

What would make us more comfortable

None of this is a verdict on BOB. It is a list of public information that would help any reader:

• A published description of how BOB Gateway holds and releases BTC.
• The audit report for the Bitcoin.one contracts, which the paper says is planned before the token launch.
• Mainnet deployment addresses that match those in the paper.
• A clear statement of who operates the keeper and the vault, a point the buybacks page leaves open.

Until then, the honest summary is: the architecture is clearly described, it is running on a test network, and most of the trust questions are still open.