BOB Alpha Map

01 / What changed

BOB is no longer just a Bitcoin L2 pitch deck. The interesting surface is now operational: a token sale, a DAO, a Gateway product, BTC swaps, a BitVM testnet, Uniswap/Oku liquidity, institutional custody integrations, and a growing list of BTC yield assets.

That does not make it safe. It makes it inspectable.

The report angle should be simple: BOB is trying to become the Bank of Bitcoin, and the public artifacts now give us enough seams to hunt for alpha instead of repeating the slogan.

02 / Gateway is the wedge

Gateway is the strongest product surface. BOB describes it as a Bitcoin intents system for native BTC swaps, stablecoin exits, wBTC routes, and direct deployment into DeFi positions with a single Bitcoin transaction.

The live and near-live hooks matter:

The quiet line worth tracking: Gateway mentions future agent integration, limit orders, DCA, instant settlement, and composable DeFi actions. That is not enough to publish an agent report. It is enough to keep Gateway on the watchlist for machine-executable Bitcoin flows.

03 / Token, DAO, delegation

The BOB token moved from abstract future incentive to public artifact. The Community Sale page lists a fixed 10 billion supply, up to 4% of supply reserved for sale, $165M community-member FDV, $230M public FDV, and 50% unlock at TGE followed by three-month linear vesting.

Tokenlist data now shows BOB token entries, including BOB chain address 0xB0BD54846a92b214C04A63B26AD7Dc5e19A60808. That gives the market a concrete object to track.

Governance also exists, with delegates and an initial mission-charter proposal. The Hybrid Nodes page says BOB token delegation goes live at TGE. The immediate question is not “is there a token?” It is “where does delegation, staking, node trust, and Gateway priority create reflexive demand?”

04 / Liquidity is not imaginary

The Uniswap proposal is the cleanest third-party proof that BOB has real liquidity ambition. Proposal 84, brought through Uniswap governance, describes BOB as an official Uniswap V3 deployment and requests a $375k Uniswap onboarding package while BOB commits $500k over six months.

The proposal cites BOB at roughly $247M TVL in late March 2025 and about $43M in UniV3 pools, ranking fifth among UniV3 deployments at that point. Treat those numbers as dated, but not meaningless. They show BOB was not just asking for attention; it had enough liquidity to negotiate from a position.

The pools to watch are not random:

The alpha is not “farm every pool.” The alpha is to watch which BTC assets BOB keeps incentivizing after the obvious launch campaign fades.

05 / BitVM clock

BitVM is the long-dated catalyst. BOB docs describe a BitVM bridge testnet, Q4 2025 mainnet target, and a 1-of-n security model where a single honest challenger can prevent fraudulent withdrawals.

The testnet partner list is strong enough to matter: P2P.org, Lombard, Solv, Amber Group, Ankr, RockawayX, Fiamma, UTXO Management, Luganodes, and SatLayer.

But this is also where the report needs discipline. Some roadmap pages and blog posts carry stale or conflicting dates. If BitVM mainnet timing slipped, that is not a footnote; it is the core risk. The right stance is to treat BitVM as the institutional-security clock, not as delivered mainnet fact.

06 / Partner map

BOB’s ecosystem page lists more than 120 projects. The names worth tracking are the ones tied to live user action or institutional access:

This is enough for a report. It is also enough to avoid the lazy version of the report. The lazy version says BOB has partners. The useful version says which partner changes user behavior, liquidity routing, or token demand.

07 / What to do now

The current watchlist:

1. Track Gateway route expansion: native BTC to stables, ETH, wBTC, gold, and any direct DeFi action.
2. Track BOB token transferability, delegation, staking, and Hybrid Node economics around TGE.
3. Track whether Uniswap/Oku remains the canonical DEX after incentives normalize.
4. Track BTC LST liquidity: LBTC, SolvBTC, pumpBTC, tBTC, HybridBTC.pendle, BTC+.
5. Track BitVM mainnet status against docs and partner announcements.
6. Track institutional access announcements from Fireblocks, Anchorage, and custody-adjacent partners.
7. Track scam domains and fake BOB airdrop pages. gobob.live already surfaced as noise, not signal.

The first practical user action is not buying anything blind. It is building a dashboard of routes, incentives, and token flows that answers: where is native BTC entering, what does it become, and who is paying for that conversion?

08 / What could break

• Roadmap drift. BitVM dates and finality milestones must be re-verified before any public claim.
• Mercenary incentives. TVL can leave when campaigns end.
• Token unlock pressure. The community sale has favorable vesting compared to private/team rounds, but unlocks still matter.
• Gateway centralization. Solver quality, compliance screening, and route control are the real trust surface.
• Bitcoin culture mismatch. Bitcoin users may hate the abstraction until it saves them money or time.
• Scam noise. Generic BOB terms are polluted. Use gobob, Build on Bitcoin, BOB Gateway, HybridBTC, BitVM bridge, and official URLs.

Appendix / Agent NFT scout note

The earlier BOB agent-NFT idea should stay private for now. BOB already has NFT collections, so “first NFT on BOB” is false. A stronger agent thesis may exist later: Bitcoin-native operator identities, bridge sentries, BTC yield scouts, onchain archivists, or Gateway-linked agents.

For now, the public evidence is thin. No strong BOB-native ERC-8004 or Adapter8004 deployment surfaced in the checks, and social search did not show a clean BOB agent-NFT pocket. The only direct bridge back into agents is Gateway’s future agent-integration language.

Keep the agent angle as a scout note. Lead with the Bank of Bitcoin stack.