Block's OCC Trust Charter: A Regulatory Follower in a Crowded Pipeline
0xHasu
September 10. A filing lands at the Office of the Comptroller of the Currency. Block, Inc. submits an application for a non-insured national trust bank charter. The proposed entity: Builders Bank & Trust, N.A. No token launch. No protocol upgrade. No code commit. A regulatory filing.
If the value proposition is "we have a bank charter," and six other firms already have one or are closer to getting one, then the charter is table stakes. Not differentiation. Block is not first. Not second. Somewhere in the middle of a crowded queue.
The OCC's national trust bank charter has become the preferred regulatory wrapper for crypto custody. It provides federal preemption over state money transmitter licensing—a fragmented nightmare of fifty jurisdictions. For Block, a company with Square merchant services and Cash App consumer rails, that fragmentation is a real cost. Every state adds compliance overhead. Every jurisdiction introduces legal ambiguity.
A national trust charter consolidates that. One regulator. One set of fiduciary standards. One examination cycle.
But there's a catch. "Non-insured national trust bank" means exactly what it says. No FDIC insurance. No deposit insurance. No safety net. This is not a retail bank. It does not take deposits in the traditional sense. It holds assets in trust. The fiduciary duty is to the beneficiary, not the depositor.
This distinction is critical. And it will be misunderstood.
The OCC has issued these charters sparingly, but the pipeline has accelerated. Anchorage Digital received one. Paxos. BitGo. These are not consumer-facing brands. They are infrastructure plays. Block's proposed entity follows the same pattern: a trust bank that custodies Bitcoin and stablecoins for institutional clients, not a retail depository that holds your checking account.
Based on the filing, Builders Bank & Trust would provide Bitcoin and stablecoin custody, plus "other trust services." The application notes this would create a federal framework for some of Block's existing custody services. That word "some" is doing a lot of work.
Which services? The filing does not specify. Cash App's Bitcoin product? Square's merchant settlement? The Bitcoin stored on behalf of users? The stablecoin reserves under management? This is hidden information, and the confidence level is medium at best.
Here is the architectural problem. Block has multiple custody surfaces. Cash App holds Bitcoin for millions of retail users. Square processes merchant payments, some of which touch stablecoins. There is also TBD, Block's open-source Bitcoin effort. These are not the same custody model. Retail self-custody via Cash App is not the same as institutional trust custody. The compliance, key management, and audit requirements diverge significantly.
If Builders Bank absorbs even one of these surfaces, it changes the risk profile. A trust bank has fiduciary obligations. It must segregate client assets. It must maintain capital reserves. It must submit to OCC examination. That is not free. That is not fast. That is a structural shift.
The differentiation, if it exists, comes from distribution capability, not technical leadership. Block owns the rails to millions of consumers and merchants. If it can offer regulated custody through a national trust bank, it can onboard institutional partners who demand federal regulatory clarity. The value is in the distribution, not the charter.
Competitive landscape: Coinbase Custody. Paxos Trust. BitGo Trust. Anchorage Digital. These are the incumbents. They have years of operating history, audited controls, institutional relationships. Block is applying now. If approved, it starts from zero in the institutional custody business. It has no track record. It has a brand, but not in this segment.
The custody business is trust-intensive. Institutions do not switch custodians lightly. The switching cost is high because the operational risk is high. A misstep—a lost key, a failed audit, a regulatory finding—destroys the value proposition. Block's consumer brand does not transfer to institutional trust. Different buyer. Different sales cycle. Different due diligence.
Now, the stablecoin angle. The filing mentions stablecoin custody. The OCC has taken an increasingly active stance on stablecoin issuers and custodians. If Builders Bank custodies stablecoin reserves, it becomes a critical node in the stablecoin infrastructure. Circle. Tether. Paxos. These reserves are massive. The custodian matters. The regulatory status of the custodian matters.
Block could position itself as a regulated custodian for stablecoin reserves. That is a real business. But it requires operational excellence. It requires a security posture that withstands institutional scrutiny. The filing does not disclose wallet architecture, private key management, MPC, cold/hot storage, or audit status. These are not minor omissions. They are the entire security story.
Based on my audit experience reverse-engineering custody architectures, the absence of disclosed key management details in a charter application is not unusual, but it is a significant blind spot. Without that information, the charter application is a regulatory signal, not a technical proof. The approval, if it comes, will be conditional. The OCC will impose requirements. The bank will be examined. The real work starts after the charter is granted.
Here is the counterintuitive angle. The "bank" label creates a perception problem that could backfire. The public—and many crypto users—see "bank" and assume deposit insurance. They assume FDIC protection. They assume safety. This is a high-confidence hidden risk: the public may misread "bank" as "deposit insurance."
This is not hypothetical. It is predictable. When Block announces "Builders Bank & Trust, N.A.," the headline will say "Block gets bank charter." The subtext will be "your Bitcoin is now in a bank." That is not what is happening. A non-insured trust bank is a fiduciary structure, not a deposit institution. If the market misunderstands this, the reputational risk is asymmetric. A negative event—even a small operational failure—gets amplified by the false expectation of deposit insurance.
Speed is an illusion if the exit door is locked. Block can move fast on consumer products. But regulatory approval is not a product sprint. It is a marathon with no fixed finish line.
The other contrarian point: Block is late. The OCC pipeline is crowded. Revolut received conditional approval. World Liberty Financial received conditional approval. Coinbase, Paxos, BitGo, Ripple, Circle—these are not newcomers. They have charters, conditional approvals, or applications in advanced stages. Block's application is a catch-up move, not a leadership move. In a sideways market where capital is cautious, being late to a regulatory land grab is not a neutral position. It is a disadvantage.
Watch the OCC's public filing database. Watch whether Block discloses the custody architecture—key management, MPC, audit reports—before or after approval. If those disclosures come only after the charter is granted, the market is buying a regulatory headline without technical substance. The real signal is not the charter. The real signal is the operational infrastructure that sits beneath it. Logic prevails, but bias hides in the edge cases. The edge case here is a bank that is not a bank, custody without FDIC, and a follower pretending to lead.
Regulatory approval is a starting gun, not a finish line.