Lombard (@Lombard_Finance): The Case for Neutral Bitcoin Infrastructure

The Case for Neutral Bitcoin Infrastructure Why credible neutrality matters when choosing a Bitcoin asset — and why BTC.b is the only asset that has it The wrapped Bitcoin market has a framing problem. Most comparisons between WBTC, cbBTC, and BTC.b are written as feature tables. Fees here, custody model there, liquidity depth somewhere in the middle. It's a useful format, but it misses the question that actually matters for any protocol, chain, or institution deciding which Bitcoin primitive to build with. The question isn't which wrapper has the lowest fees today. It's which one can be adopted by the broadest possible set of participants — including participants who compete with each other — without any of them strengthening a rival. That is the property of credible neutrality. And in the wrapped Bitcoin market, it is the only moat that compounds. The structural problem with aligned wrappers WBTC and cbBTC are both good products in narrow contexts. That's not the argument against them. The argument is structural. cbBTC is a Coinbase product. It is gated to Coinbase customers. Minting requires a Coinbase account, geographic eligibility, and compliance with Coinbase's terms. That's not a bug — it's a deliberate design choice that makes cbBTC work extremely well within the Coinbase ecosystem. The problem is that any protocol integrating cbBTC is, by extension, strengthening Coinbase's distribution and user base. A competing exchange will not adopt cbBTC, which is why we observe many exchanges launching their own. A protocol that wants to remain neutral across the full landscape of institutional partners will have to think carefully before making cbBTC its primary Bitcoin collateral. WBTC's issues are different in character but similar in effect. What was originally positioned as neutral infrastructure became materially less neutral following key custody changes that transferred control to BiT Global, an entity associated with Justin Sun. The western institutional community, in particular, has responded with wariness. When the custodial counterparty becomes a source of reputational and concentration risk, the asset stops functioning as neutral infrastructure. Neither of these outcomes was inevitable. Both were products of the same underlying design decision: building a wrapper that serves a specific platform's interests alongside the broader market's needs. Those two objectives are compatible until they aren't — and when they conflict, it's the neutrality that gives way. Why neutrality is a compounding property Neutrality matters more than almost any other wrapper attribute because it determines the size of the market the asset can serve. A wrapper aligned to a single exchange or custodian is structurally limited to partners who don't compete with that entity. In practice, that's a meaningful constraint. Competing exchanges won't integrate it. Protocols with large institutional user bases will hesitate. Chains that want to attract the broadest possible Bitcoin liquidity will choose the asset their entire ecosystem can adopt without friction. A credibly neutral wrapper, by contrast, can be adopted simultaneously by entities that compete with each other. Every adoption strengthens the network. Liquidity deepens. Integrations compound. The asset becomes more useful to the next adopter precisely because it's already been adopted by many others. This is the dynamic that made WBTC dominant during its early years — not superior technology, but the ability to be adopted by parties who were competitors in every other respect. It's also why cbBTC's growth, while impressive in scale, has been largely concentrated within the Coinbase and Base ecosystems rather than spreading evenly across the market. Aligned assets capture their natural constituency very well. They struggle to grow beyond it. Why BTC.b was built to fill this gap? BTC.b was designed from the ground up as shared infrastructure. The five dimensions where this plays out in practice: Neutrality. BTC.b has no commercial alignment to any exchange, chain, or custodian. Competing businesses can adopt it without strengthening a rival. A centralized exchange, a decentralized protocol, and a neobank can all integrate BTC.b simultaneously, and each adoption makes the asset more useful to the others rather than less. Minting access. Minting BTC.b is fully permissionless. Any BTC holder can mint directly onchain from any wallet, exchange, or custodian — no Coinbase account, no approved merchant relationship, no geographic restriction. The mint fee is capped at approximately 29 satoshis (~$0.02). Redemptions cost 0 satoshis plus ~10,000 satoshis (~$6.50) to cover Bitcoin network costs. The Lombard SDK lets developers embed native BTC deposit flows directly into their own products. For protocols and chains, this matters because it means their users arrive at BTC.b from wherever they hold Bitcoin — not through a specific exchange's onboarding flow. Fees. BTC.b is built as infrastructure, not a profit centre. Users move Bitcoin in and out without a toll. By contrast, WBTC merchant fees vary by intermediary, and cbBTC's zero-fee economics are subsidised by Coinbase's ETF business — an advantage no other organization can replicate structurally. Security model. BTC.b is secured by the Lombard Security Consortium: 15 independent digital asset institutions, including OKX, Kraken, Galaxy, DCG, Wintermute, Amber Group, Figment, P2P, Kiln, Antpool, and F2Pool. The Consortium requires a two-thirds quorum to authorise any mint. No single institution can unilaterally act. No single point of failure exists. This is structurally different from both cbBTC (single custodian: Coinbase) and WBTC (single custodian: BiT Global). Reserve integrity is verified onchain via Chainlink Proof of Reserve in real time. Key management sits with Cubist’s CubeSigner — HSM-backed signing where key material is never exposed to operators. Team and developer support. BTC.b has a full-time dedicated team and the full Lombard SDK: direct Bitcoin deposit flows, customizable user journeys, white-label options, and multi-chain deployment across Ethereum, Avalanche, Solana, and MegaEth. cbBTC is a secondary product within Coinbase's broader offering, with limited dedicated engineering tooling. WBTC's operational structure has become increasingly opaque, with no clear team ownership or developer support infrastructure. The comparison, plainly stated The addressable market argument For protocols and chains deciding which Bitcoin primitive to build on, the neutrality argument has a direct commercial implication. A neutral wrapper has a total addressable market equal to the entire Bitcoin-in-DeFi opportunity. An aligned wrapper's TAM is structurally smaller — limited to the portion of the market that doesn't compete with the aligning entity, or doesn't care about the alignment. This matters less at early stages, when the priority is getting to liquidity quickly and the alignment provides a distribution advantage. It matters enormously at scale, when the question is whether the asset can become the universal Bitcoin primitive across the full DeFi landscape — and when the answer depends on whether every participant in that landscape can adopt it without hesitation. BTC.b is no longer an early-stage asset asking for adoption on the promise of neutrality. It is a scaled asset whose track record demonstrates that neutral infrastructure and institutional-grade security are not in tension. For any protocol or platform with a crypto strategy If you're a DeFi protocol evaluating Bitcoin collateral, the choice between BTC.b, cbBTC, and WBTC is partly a liquidity question and partly a strategic one. The liquidity question has a clear answer: all three have meaningful depth, and BTC.b's onchain liquidity on Ethereum continues to grow following the Aave V3 listing. The strategic question is the one worth spending more time on. Which asset can your entire institutional user base access without geographic restriction or exchange dependency? Which asset will your institutional partners be comfortable with as a counterparty? Which asset can you integrate today and still be comfortable with in three years, regardless of how the competitive landscape among exchanges and custodians evolves? If you're a chain or L2 looking for a canonical Bitcoin asset, the question is similar but larger in scope. The asset you choose becomes the Bitcoin primitive for your entire ecosystem. It needs to be something every project building on your chain can adopt — including projects that compete with each other, and including institutional users who may have views on custodial counterparties that limit their options. Both Katana and MegaEth adopted BTC.b as their canonical BTC asset. If you're an institution or neobank evaluating Bitcoin DeFi exposure, the question is about counterparty concentration. A 15-institution consortium with a two-thirds quorum requirement is a structurally different risk profile from a single regulated custodian or a single offshore entity. That difference compounds as exposure scales. In all three cases, the answer points in the same direction. The case for BTC.b The Bitcoin DeFi market is at an early enough stage that infrastructure choices made today will shape its architecture for years. The wrapper that becomes the default Bitcoin primitive — the asset protocols integrate first, chains adopt as canonical, and institutions treat as the reference — will have compounding advantages that make it progressively harder to displace. The property that determines which asset fills that role is not fees, because fees can be changed. It is not liquidity depth, because liquidity follows adoption. It is not even security track record, though track record matters. It is credible neutrality — the property that allows the asset to be adopted simultaneously by the broadest possible set of participants without any of them creating a problem for the others. WBTC no longer has it. cbBTC was never designed for it. BTC.b was built for nothing else.