This content originally appeared on HackerNoon and was authored by Ishan Pandey
Why do 22% of US adults own Bitcoin, and roughly 1.1% actually spend it?
\ This is the structural puzzle on-chain finance has been unable to solve for seventeen years. The Bitcoin whitepaper described "a peer-to-peer electronic cash system." What got built instead, by every measure of actual usage, is a peer-to-peer store-of-value system. The asset is held in cold storage, traded on centralized exchanges, and increasingly held in tokenized treasury structures. It is not spent at merchants. Not in any volume that matters.
\ GoMining launched GoBTC Pay on June 19, is a bet that the gap between holding and spending is not a Bitcoin problem. It is an infrastructure problem, and one that the existing rails, including Lightning, BitPay, and Strike, have only partially solved.
\ The pitch is simple enough to fit in one line: 0.2% merchant fee, on-chain settlement on Bitcoin Layer 1, non-custodial by design, zero fees for users, and any wallet provider can integrate. The deeper claim is more interesting: that the company best positioned to fix Bitcoin payments is not a payments company, but a mining company that already runs the infrastructure to prioritize the blocks.
\
What is GoBTC Pay?
GoBTC Pay is an open Bitcoin payment protocol launched by GoMining, a top-10 Bitcoin miner with 5 million users. The protocol delivers instant authorization at the point of sale, with final on-chain settlement targeted at 12 hours by end-2026. Merchants pay 0.2%, users pay nothing, and the fee is split between GoMining's dedicated mining pool (0.1% to miners) and the wallets that route the payment (0.1%). The system is 2-of-3 multi-signature: user, GoMining, and an independent recovery custodian. Public launch was June 19, 2026, with a live demo at Consensus Miami 2026 in May.
\
The fee economics
Almost every payments story buries the fee comparison because it is rude to the incumbents. The chart belongs at the top.'
Visa and Mastercard interchange in the US currently runs around 1.5% to 2.5% for small merchants on consumer credit cards, with premium card products like Visa Infinite reaching 2.18% plus $0.10 per transaction at the small-merchant tier. PayPal and Stripe charge merchants around 2.9% plus fixed per-transaction fees. BitPay sits around 1%. Lightning Network operators have driven fees to approximately 0.3%.
\ GoBTC Pay charges 0.2%.
\ That is not a 10% improvement. That is an order of magnitude. For a US merchant doing $1 million in annual sales at Visa's average rate, switching to GoBTC Pay would mean roughly $2,000 in fees instead of $2,200. Not life-changing. But a 1,000-store coffee chain doing $500 million in sales is looking at the difference between $11 million and $1 million per year on payment processing alone.
\ The Visa/Mastercard settlement filed in late 2025, which promises to reduce interchange by an average of 0.10 percentage points over five years, gives a useful frame. Even after card networks fully implement their court-mandated reduction, the gap to GoBTC Pay's 0.2% remains roughly the same order of magnitude.
\ The breakdown of where the fee actually goes is the more interesting story.
\
In the card model, the issuer bank captures the largest single slice, the network gets a sliver, and the processor takes a markup. PayPal's 2.9% goes almost entirely to PayPal itself. In GoBTC Pay's model, the entire 0.2% is split 50/50 between the GoMining pool that confirms the transaction and the wallet that routed the payment. The economic result is that miners and wallet providers are aligned with payment volume in a structural way that has no parallel in the card networks.
\
Lightning got there first, and it is still small
Any analysis of Bitcoin payments has to start with Lightning. The Lightning Network has been the consensus answer to Bitcoin's payment problem for nearly a decade, and it works. The numbers prove it works.
\
Lightning crossed $1 billion in monthly transaction volume in January 2026, a 300% increase over the previous year. Network capacity stabilized at roughly 4,132 BTC across 16,294 nodes. Square enabled Lightning payments for 4 million merchants with fee waivers running through 2027. The average Lightning transaction is now around $223.
\ These numbers are real. They also represent, in aggregate, a fraction of what Visa processes in an average hour.
\ The honest reading is that Lightning solved the technical problem of fast, cheap Bitcoin payments at small denominations, and ran into a different problem: the user experience of channel management, liquidity routing, and the trust assumptions involved in custodial Lightning services. Every successful Lightning payment company has, in practice, made tradeoffs on the non-custodial property to make the user experience work. That is a defensible engineering choice. It is also why the holder-to-spender gap remains.
\ GoBTC Pay's contrarian bet is that the right place to fix Bitcoin payments is not in a new layer above the base chain, but in the way Bitcoin's existing Layer 1 is operated. Specifically, in who runs the mining pool that confirms the transactions.
\
What GoBTC Pay actually does
The mechanics are simpler than the architectural debate suggests.
\ When a user pays with GoBTC Pay, the protocol generates a signed transaction using a 2-of-3 multi-signature wallet that includes the user, GoMining, and an independent recovery custodian. The transaction is submitted directly to GoMining's dedicated mining pool. Because GoMining mines its own blocks rather than outsourcing to a public pool, it can prioritize GoBTC Pay transactions for inclusion in the next block it finds.
\ The merchant gets instant authorization, similar to a card "auth" message. The transaction settles on-chain over Bitcoin's normal block timing. GoMining is targeting a 12-hour final settlement guarantee by end-2026, which is slower than Lightning's seconds-to-finality but is fully on-chain and inherits Bitcoin's native security model.
\ The 2-of-3 multi-sig design means no single party can move user funds unilaterally. The user retains custody. GoMining cannot seize funds. The independent recovery custodian exists for the unhappy-path case where the user loses access. This is non-custodial in the technical sense, with explicit recovery rails.
\ The protocol is open. Any wallet provider, from Ledger to Trust Wallet to MetaMask, can integrate against the GoBTC Pay SDK. GoMining operates the reference implementation, but the standard is not proprietary to GoMining.
\
Why the cost-latency map matters
The most useful way to position GoBTC Pay against the alternatives is to plot every payment system in the cost-by-latency plane. Once you do that, the strategic positioning becomes clear.
The target zone, sub-second confirmation at sub-percent cost, is empty for traditional financial rails. Cards confirm fast but cost 2 to 3%. ACH and SWIFT cost less but settle in days. Raw on-chain Bitcoin transactions cost almost nothing but take ten minutes to an hour for first confirmation and longer for finality. BitPay and Strike sit in the middle. Lightning has occupied the target zone, but only for users who can navigate its UX.
\ GoBTC Pay's bet is that the target zone is winnable by a non-Lightning solution if you control the mining pool. That is a real architectural argument.
\
The vertical integration argument
The single most underappreciated detail in the GoBTC Pay design is that GoMining is launching its own mining pool to confirm the transactions.
\ This is qualitatively different from how Lightning, BitPay, Strike, or any other Bitcoin payment system operates. Every existing payment company depends on public mining pools to confirm their transactions, which means they are price-takers for block space and have no guarantee of timely inclusion. GoMining is its own pool. The protocol's settlement guarantee is backed by mining capacity that the company directly controls.
\ This matters more than it sounds. Bitcoin's payment problem has never been the protocol itself. It has been the queueing dynamics of a system where every payment competes for the same scarce block space against every other Bitcoin transaction in the world. A merchant accepting Bitcoin payments through a payment processor has no way to guarantee their transaction will be confirmed in a predictable window, because the processor has no influence over which pool mines the block.
\ GoMining does. The trade is centralization of mining for predictability of settlement. Whether that is a price the Bitcoin community is willing to pay is a question that will play out over the next eighteen months.
\ The mining pool also creates the economic engine for the flywheel. A portion of every transaction fee flows back to the miners who own tokenized hashrate through GoMining's app. GoMining's "digital miner" users get BTC yield not just from new issuance and block fees, but from payment processing revenue. That is a meaningful structural improvement to the economics of running mining infrastructure in a post-halving world where block subsidy revenue is permanently declining.
\
The merchant adoption problem is real and addressable
The reason this all matters is that merchant adoption of Bitcoin payments has been stuck at the protocol layer, not at the demand layer. The constraint is not whether merchants want lower fees. The constraint is whether the integration overhead, the volatility, and the settlement uncertainty are worth the savings.
\
The three barriers cited by the largest share of merchants are price volatility, settlement time uncertainty, and integration complexity. GoBTC Pay's architecture targets all three directly. Settlement happens within a known window. Integration is via SDK to existing wallets, not a separate POS system. And while volatility is a property of Bitcoin itself rather than the payment protocol, the instant-authorization model gives merchants a clear price-at-time-of-sale, which is what they actually need for accounting purposes.
\ The realized US merchant adoption curve has gone from roughly 1,200 directly-accepting merchants in 2022 to about 7,000 in 2026. Speed.app projects 82% growth over 2024-2026 in US merchants accepting crypto, and the trajectory of the next two years will be decided primarily by what happens at the protocol layer.
\
The bull case is that a single protocol that meaningfully reduces volatility exposure and integration cost can shift the curve by a factor of two or more. The bear case is that merchants are simply not motivated by 0.2% versus 2% fees at the small-merchant scale, and that the curve grows on its existing slope regardless of protocol-layer improvements. Both readings are defensible.
\
Bitcoin's spending problem is global, not American
The US data understates the opportunity. The same paradox shows up in every major economy, and in some places, it is the dominant payment story rather than the marginal one.
\
El Salvador is the obvious outlier on the spending axis, where Bitcoin's legal-tender status has created a ratio of holding to spending that is structurally different from any other country. Argentina, Vietnam, Nigeria, and the Philippines all show meaningfully higher spending-to-holding ratios than the US, UK, Germany, or Japan, driven by local currency instability, remittance corridors, and informal-economy adoption.
\ The interesting strategic question is whether GoBTC Pay's economics work better in emerging markets, where the alternative to Bitcoin payments is often a 6-8% remittance fee or a depreciating fiat currency, than in developed markets, where the alternative is a 2% credit card fee. The fee math favors the emerging market case. The merchant infrastructure does not, yet.
\
The design-space view
Stepping back further, the cleanest way to read the GoBTC Pay positioning is on the decentralization-versus-throughput map.
\
Bitcoin Layer 1 sits at the maximally decentralized, minimally throughput corner. Visa is its mirror image: high throughput, almost no decentralization. Lightning achieved both decentralization and throughput at the cost of UX and operational complexity. GoBTC Pay is making the explicit tradeoff of slightly less decentralization than raw Layer 1, in exchange for the predictability and throughput that come from a dedicated mining pool.
\ The capability matrix, applied to the headline features merchants actually evaluate, makes the strategic argument tighter.
\ There is no system that scores well on all five of sub-second confirmation, on-chain final settlement, sub-1% merchant fee, non-custodial design, and open wallet integration. Cards fail on fees and custody. Strike fails on settlement and custody. BitPay is decent but proprietary. Lightning gets close but trips on UX. GoBTC Pay is the first protocol to claim all five, though "claim" is doing real work in that sentence until the production data is in.
\
The starting paradox
Step back from the architecture and the fee comparisons and ask the question the chart at the top of the piece is built to answer.
\
Twenty percentage points of US adults have moved into Bitcoin ownership over the last eight years. The share of those holders who actually spend Bitcoin at merchants has stayed essentially flat, around 1.1%. This is not because the Bitcoin community failed to build payment infrastructure. Lightning exists. BitPay exists. Strike exists. The infrastructure was built, and the spending behavior did not follow.
\ The implication is that the infrastructure that was built was not the infrastructure the market needed. Either the fees were too high, the user experience was too complex, the settlement guarantees were too weak, or the wallet integration was too narrow. GoBTC Pay is making the bet that solving all four of these simultaneously, in a single open protocol, is enough to move the spending curve.
\
What could go wrong
A few risks worth flagging plainly:
The 12-hour settlement window may be too slow for merchant acceptance. Card networks settle to merchants in T+1 to T+2 days, but the merchant trusts the auth immediately because of chargeback infrastructure. GoBTC Pay offers instant authorization but the final on-chain settlement window is longer than some merchants will tolerate without a hedging layer. The protocol may need to add explicit settlement insurance to bridge the gap.
\ Mining pool centralization is a real Bitcoin-community concern. Concentrating GoBTC Pay transactions in one mining pool is structurally similar to centralized custody in its political optics, even if the economic mechanism is different. The Bitcoin community has historically pushed back hard on pool concentration. Whether the convenience tradeoff is accepted will depend on adoption pace and visible centralization metrics over the next year.
\ Wallet provider integration is the actual distribution bottleneck. The 0.1% fee share to wallets is meaningful, but wallets have spent years building their own payment integrations and may not see GoBTC Pay as a strategic priority. If Ledger, Trust Wallet, MetaMask, and Phantom do not integrate, the SDK becomes academic.
\ Volatility risk for merchants is unaddressed. Bitcoin's price can move 5-10% in a day. A merchant who accepts $1 million in Bitcoin Tuesday and converts Wednesday is exposed in a way that they are not on cards. GoBTC Pay does not directly solve this, and the existing infrastructure for instant BTC-to-fiat conversion is dominated by competitors.
\ The "independent recovery custodian" needs to be named and audited. The 2-of-3 multi-sig design depends on the third signer being genuinely independent and operationally sound. The protocol whitepaper will need to spell out who this is, how they are credentialed, and what their failure modes are. This is the single most important detail that has not been publicly disclosed.
\ None of these are dealbreakers. They are the cost of operating a new protocol in a market with mature alternatives.
\
The bottom line
GoBTC Pay is making an architectural argument that the Bitcoin community has been talking around for years: that the right fix for Bitcoin payments is not a higher abstraction layer, but ownership of the mining infrastructure that confirms the transactions. The economics work because owning the pool lets you guarantee block space, and guaranteeing block space lets you guarantee settlement, and guaranteeing settlement lets you offer merchants a fee that no card network can match.
\ Whether this becomes the standard for everyday Bitcoin payments is a question of distribution and wallet integration over the next eighteen months. The fee math is unambiguous. The user experience tradeoffs are honest. The vertical integration is a real strategic moat that incumbent Bitcoin payment companies cannot easily replicate.
\ What sits underneath all of this is the harder, older question: whether Bitcoin actually wants to be a payment system, or whether the spending-to-holding ratio has stayed flat for seventeen years because the asset itself functions better as a store of value than a medium of exchange. GoBTC Pay is the cleanest test of that proposition that anyone has built. The result will be visible in the on-chain merchant payment numbers, twelve months from now.
That is worth watching.
\ Don't forget to like and share the story!
:::tip Vested Interest Disclosure: HackerNoon has reviewed the report for quality, but the claims herein belong to the author. #DYOR.
:::
\
This content originally appeared on HackerNoon and was authored by Ishan Pandey
Ishan Pandey | Sciencx (2026-06-22T11:05:53+00:00) GoBTC Pay Wants to Make Bitcoin Spendable Again. The Fee Math Says It Might.. Retrieved from https://www.scien.cx/2026/06/22/gobtc-pay-wants-to-make-bitcoin-spendable-again-the-fee-math-says-it-might/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.