The Filing That Tells You Almost Nothing
Last week a company called Rain filed paperwork with the Office of the Comptroller of the Currency to stand up a national trust bank built around stablecoins. That is the entire factual payload. Four information points, one of which is a fact, two of which are opinions dressed as reporting, and one of which is a source link I could not independently verify. Everything else in the discourse is projection.
I want to be precise about that, because precision is the only thing separating a charter application from a charter. A filing is an intent. An approval is a capability. A capability is not a business. The distance between those three states is where most crypto narratives go to die, and nobody writing headlines about Rain seems interested in measuring it.
Entropy wins. Always check the fees. And always check whether the thing being announced is a noun or a verb. Rain filed a verb. The market is trading a noun.
Let me walk through what a national trust bank actually is at the mechanical level, because the gap between the public imagination of "bank" and the legal reality of "trust bank" is the entire story here. Then I will show you why the most dangerous part of this filing is not the risk of rejection โ it is the risk of approval.
Context: The OCC, the Trust Charter, and Two Decades of Precedent
To read this filing correctly you need the plumbing. The OCC is the federal regulator that charters and supervises national banks and, relevant here, national trust banks. It operates under a dual banking system โ meaning a firm can be chartered federally by the OCC or at the state level by a state banking department. Federal and state charters carry different powers, different capital regimes, different supervisory expectations. This dual track is not a technicality. It is a competitive lever, and it has been the single most important variable in crypto custody for eight years.
A national trust bank is a specific animal. It is authorized to act as a fiduciary โ to hold and administer assets on behalf of clients under a legal duty to act in their best interest. It is expressly not authorized to take deposits in the ordinary commercial-bank sense and not authorized to make loans. No deposit-taking means no FDIC insurance. No lending means no credit creation. What you get instead is the fiduciary duty, which is a legal obligation that a trustee must subordinate its own interests to the beneficiary's. That obligation is enforceable. It is also, and this is the part people skip, expensive to operationalize.
The crypto industry has walked this path before, and the precedents matter more than the press release. Anchorage Digital obtained a national trust charter in 2021 and became the first federally chartered crypto bank. Paxos held a trust charter and built an infrastructure business around issuance and custody. Circle pursued a trust path as part of its broader compliance architecture before going public. Each of these firms arrived at the same structural insight: the charter is not a product. The charter is a wrapper that lets you sell a product to institutions that cannot legally touch unlicensed counterparties.
Then came 2025. The United States passed federal stablecoin legislation โ the GENIUS Act framework โ and suddenly the question of who is legally permitted to issue a payment stablecoin moved from a gray zone into a rulebook. The OCC became the front door for non-bank issuers seeking federal recognition. Rain's filing sits squarely inside this window. It is a regulatory cycle artifact, not a technological event.
That distinction is load-bearing. If you read this as "Rain invented something," you will misprice it. If you read it as "Rain is trying to buy a license that makes it legible to institutions," you are closer to the truth. The rest of this piece is about why that license may be worth less than the headline implies โ and why the headline may be worth more than the license.
The Mechanical Anatomy of a National Trust Bank
Let me get forensic about the instrument itself, because I have spent the better part of my career reading regulatory structures the way I read Solidity โ line by line, looking for the gap between what the code says and what the market assumes it says.
A trust charter grants fiduciary powers. In practice this means the entity can take custody of client assets, administer them, act as trustee or agent, and hold reserves. It cannot run a fractional reserve book. It cannot issue demand deposits backed by nothing. It cannot extend credit. Every dollar it holds for a client must be held for that client, not lent out against.
The economic consequence is severe and underappreciated: a trust bank has no balance-sheet leverage. A commercial bank earns a spread by borrowing short and lending long. A trust bank earns fees for safekeeping and administration. It does not get to multiply money. It gets to babysit it.
Now layer stablecoins on top. When you hear "a trust bank built around stablecoins," you are almost certainly hearing about one of two structures, or both. Structure one: the trust bank holds the reserve assets backing a stablecoin โ Treasuries, cash, short-duration instruments โ under fiduciary custody. Structure two: the trust bank itself issues or administers the issuance and redemption of the stablecoin, using the trust wrapper to satisfy the reserve-segregation and audit expectations that federal law now imposes on issuers.
Neither of these is technically novel. Both are legal-engineering. There is no new consensus mechanism, no new proof system, no new cryptography. The innovation, such as it is, lives entirely in the structure of obligations and permissions. When someone tells you this "redefines stablecoin trusts," you should ask them what line of code changed. The answer is none. What changed is who is allowed to sign what.
That does not make it worthless. It makes it dependent. And dependent structures are the ones that break when the dependency moves.
What the Charter Actually Authorizes โ and the Gap Nobody Is Checking
Here is the trap I want you to see clearly, because it is the center of this whole analysis.
A trust charter grants fiduciary powers. It does not, by its own force, grant the power to issue a payment stablecoin. Those are two different permissions, governed by two different bodies of law. The trust charter says "you may hold and administer assets for others." The stablecoin statute says "you may issue a token that is redeemable at par and backed by qualifying reserves." A firm can have the first without the second. Conflating them is the most common error in the coverage of this filing.
The source material I have flags, explicitly, that the application "faces legal obstacles." I do not have the specifics, and I refuse to invent them. But I can enumerate the most likely candidates, ranked by how often they appear in comparable proceedings.
First, and most probable: a question of statutory authority. Does a national trust bank chartered under existing OCC rules have the legal power to issue a stablecoin, or does stablecoin issuance require a separate authorization that the trust charter does not confer? This is a pure question of law, and it is exactly the kind of question that stalls an application for a year.
Second: the federal-versus-state conflict. If a state-level money transmission regime imposes obligations that a federal charter does not preempt cleanly, the applicant is caught between two supervisors with different opinions. The dual banking system is a feature until it becomes a vise.
Third: the qualification criteria embedded in the new stablecoin legislation itself. Federal stablecoin law sets conditions on who may issue โ reserve composition, redemption guarantees, disclosure cadence, audit standards. If Rain's proposed structure does not map cleanly onto those conditions, the application is non-conforming regardless of how strong its trust powers are.
I have audited contracts where a single incorrect modifier โ >= instead of > โ created a one-block window for an attacker. Regulatory text is the same species of artifact. A single clause about who qualifies as an issuer can invalidate an entire business model. The most expensive word in this filing is not "trust." It is "issuer."
Until the OCC publishes an acceptance or a rejection, we do not know which body of law governs, and therefore we do not know what Rain owns. Everything downstream โ the reserve economics, the business model, the moat โ is contingent on a determination that has not been made.
The Reserve Asset Engine: Where the Money Actually Is
Strip away the legal wrapper and a stablecoin is a very simple machine. Someone holds a pool of reserve assets. Someone issues a token that promises to redeem against that pool at par. The float โ the interest earned on the reserves โ is the entire economic engine.
I have spent a lot of time on this engine. In August 2021, while the rest of the market was staring at JPEGs, I spent two weeks simulating Ethereum's fee market under EIP-1559, trying to understand how the burn mechanism behaved under different gas-price volatility regimes. The lesson I took from that exercise applies here almost verbatim: in any system where a residual value accumulates at a choke point, the question is never whether the value exists โ it is who controls the valve.
For a stablecoin issuer, the choke point is the reserve pool, and the valve is the right to claim the yield. If Rain's trust bank holds T-bill reserves, the interest on those bills is real, contractual, and paid by the U.S. Treasury. Someone receives it. The distribution of that someone is the entire economic question, and the filing does not disclose it.
There are two canonical models. In the first, the issuer keeps the float. This is the Tether model, and it is extraordinarily profitable because the reserve is large and the cost of servicing a token holder is near zero. In the second, the float is passed through to holders in whole or in part โ the yield-bearing stablecoin model, closer to what USDe and USDY attempt. The two models have radically different unit economics, radically different regulatory exposure, and radically different competitive positioning.
If Rain keeps the float, it is competing on the same axis as the incumbents, with none of their distribution. If Rain passes the float through, it is competing with yield products, which drags it toward securities analysis. Either way, the reserve-yield allocation is the number that matters, and it is the number that is missing.
I want to be blunt about how I read this absence. When a firm files a charter application and the economics are not disclosed, it is not because the economics are boring. It is because disclosure would constrain optionality. Optionality is valuable to the applicant and expensive to everyone trying to price the applicant from the outside.
The Howey Overlay: When a Payment Token Starts Looking Like a Security
Let me run the standard test, because the standard test is where these structures get interesting.
The Howey analysis asks four questions. Is there an investment of money? Is there a common enterprise? Is there an expectation of profit? Does that profit derive from the efforts of others?
A plain payment stablecoin โ a token that redeems at par, earns nothing for its holder, and exists purely as a settlement instrument โ generally fails the "expectation of profit" prong. No profit, no security. This is the reason the whole category has been able to grow.
But the moment you introduce reserve-yield distribution, the analysis shifts. If holders receive a yield that depends on the issuer's management of the reserve pool, you have an expectation of profit deriving from the efforts of a third party. That is not automatically a security โ the analysis is fact-specific and the case law is a mess โ but it is close enough to the line that the structure must be designed around it. My assessment: the base stablecoin is not a security; the yield-bearing variant is a live question, and the reserve-yield pass-through is the mechanism that moves it across the boundary.
This matters for Rain in a specific way. A trust charter is a fiduciary wrapper. Fiduciary wrappers carry their own disclosure and conflict-of-interest obligations. If the trust bank both administers the reserve and controls the yield distribution, you have a self-dealing structure that a regulator will examine closely, because the trustee is on both sides of the trade. That is not a technology problem. It is a governance problem, and governance problems do not get patched. They get litigated.
The Network Effect Wall
The stablecoin market is one of the most concentrated liquid markets in crypto, and concentration is a moat made of habit. Two tokens โ USDT and USDC โ account for the overwhelming majority of supply and, more importantly, of usage. Usage is the part that matters. Supply can be minted. Usage cannot.
I have watched this pattern repeatedly. In 2020, during DeFi Summer, I spent six weeks deriving the impermanent loss curves for Uniswap v2's constant-product formula using stochastic calculus. I produced a twelve-page proof, refused to simplify it, and lost half my potential audience. The thing I learned from that exercise was not about AMMs. It was that liquidity is a coordination equilibrium โ it sits where the other liquidity sits, because that is where the spreads are tightest. The equilibrium is stable and it is hostile to newcomers.
Stablecoins are the same coordination equilibrium, scaled up. A merchant accepts USDT because their counterparty accepts USDT. An exchange lists USDC because its institutional clients demand USDC. A new entrant with identical functionality and no differentiated distribution gets no flow, regardless of how clean its charter is. Impermanent loss is real. Do your math. And do the same math for network effects, because they compound the same way.
So Rain cannot win on the token. The token is a commodity. The only place a new entrant can win is on the infrastructure โ becoming the licensed venue through which other issuers access the regulated rail. That is a fundamentally different business, and it is the business I would bet the filing is actually about.
The B2B Pivot: Selling Shovels in a Gold Rush That Ended
Here is the interpretation I find most plausible, stated as a hypothesis rather than a fact.
Rain is not trying to win the stablecoin market. Rain is trying to become the compliance shell that other stablecoin projects rent. In this reading, the trust charter is a product for B2B consumption: issuance-as-a-service, reserve-custody-as-a-service, regulatory-wrapper-as-a-service. The customer is not the end user. The customer is another token project that wants federal legibility without spending two years and eight figures obtaining its own charter.
The structural dependency graph looks like this. Upstream, the trust bank depends on the U.S. Treasury market for reserve instruments and on correspondent banks for fiat on/off ramps. Midstream, it holds reserves and administers issuance under fiduciary duty. Downstream, it plugs into exchanges, wallets, payment processors, and potentially DeFi protocols that want access to a compliant stablecoin.
Notice what is missing from that graph: any proprietary technology. Every node in the chain is either a regulated counterparty or a commodity service. The moat, to the extent one exists, is the license itself โ the scarcity of federal charters and the cost of obtaining one. That is a real moat. It is also a moat that erodes the moment the OCC starts approving more of them. If a wave of trust-charter applications follows โ and the source material flags this as a watch signal โ the scarcity premium collapses and the business reverts to competing on service quality and price, which is to say, on being a commodity with extra paperwork.
Precedent Autopsy: What Anchorage, Paxos, and Circle Actually Built
I want to run a forensic comparison, because the incumbents in this exact niche have publicly observable trajectories, and trajectories are more informative than press releases.
Anchorage Digital got the first federal crypto trust charter and built an institutional custody and infrastructure business. Its moat is not the charter alone โ it is the charter plus years of integration into institutional workflows. The charter opened the door; the integrations are what keep it closed to competitors.
Paxos ran a trust-chartered infrastructure model and became a multi-issuer shop, running issuance for partners rather than only for itself. This is the clearest template for the B2B hypothesis I described above. Paxos's insight was that the charter is more valuable as a platform than as a single product.
Circle took the compliance-first path all the way to public markets, and its disclosures are instructive. When Circle went public, the market got a rare look at the actual economics of a regulated stablecoin issuer โ and what it saw was that reserve income is the business, and that reserve income is sensitive to interest rates. When rates fall, the float shrinks, and the model compresses. This is the hidden rate exposure in every stablecoin issuer, and it is the exposure that Rain's filing does not address.
Here is the uncomfortable synthesis. Every successful entrant in this niche arrived with either a decade of institutional relationships (Anchorage), a platform strategy (Paxos), or scale and distribution (Circle). Rain's filing tells us it is attempting the same path. It does not tell us it has any of the three preconditions. And a charter without relationships, platform, or distribution is just a very expensive license to do business that no one has agreed to do with you yet.
The Legal Obstacle: Reading the Silence
The source material is explicit that the application faces legal obstacles. I want to reason about what that phrase most likely encodes, while being honest that I am inferring.
The most structurally interesting possibility is the one I flagged earlier: that a national trust bank does not, as a matter of law, have the power to issue a stablecoin at all, because issuance is not a fiduciary activity โ it is a monetary activity, governed by a separate statutory regime. If that is the obstacle, then the fix is not a better lawyer. The fix is a different charter category or a legislative amendment, either of which is measured in years.
A second possibility is federalism friction. Federal trust charters are powerful but not omnipotent, and the interaction between federal preemption and state-level stablecoin or money-transmission regimes is unsettled. A state regulator with an aggressive reading of its own authority can create operational friction even for a federally chartered entity.
A third possibility is capital and reserve qualification. The new federal stablecoin framework imposes reserve and disclosure conditions. If Rain's proposed reserve composition or audit cadence does not conform, the application fails on the merits rather than on the law.
I cannot tell you which of these it is. What I can tell you is the meta-pattern: when a regulatory filing is described as facing "legal obstacles" without specifics, the probability of a clean, fast approval is low. Regulators approve clean filings quietly. They delay, condition, or deny complicated ones loudly. The phrase itself is a signal about the shape of the process, even without its content.
The Name Collision Problem
I have to raise this because it is a genuine analytical hazard and almost no one covers it.
"Rain" is not a unique identifier in this industry. There is at least one well-known crypto exchange operating under that name in the Middle East, and quite possibly other entities besides. The source material I have does not disambiguate which Rain filed with the OCC, and I will not pretend it does. If you are reading secondary coverage that attributes financing, team, or track record to "Rain," you need to verify that the coverage is describing the same Rain that filed the application. Name collisions are how false facts propagate, and they propagate fastest in low-information news cycles exactly like this one.
This is not a trivial caveat. It is the difference between analyzing a company and analyzing a homonym. I have seen this failure mode before. During the FTX collapse I spent four months reverse-engineering the withdrawal engine's internal routing logic, mapping how ledger entries were manipulated to mask insolvency. The single hardest part of that work was not the technical reconstruction. It was entity resolution โ figuring out which legal vehicle held which obligation at which moment. Names lie. Ledgers, if you can get them, do not.
Until the entity is resolved, every claim about Rain's team, funding, or history is unverified. Treat it accordingly.
The Information Asymmetry Is the Real Story
Step back and look at the shape of what we have.
A company filed a regulatory application. The filing is public. The content of the filing โ the business plan, the reserve structure, the ownership, the capital, the intended product โ is not. The market is being asked to form an opinion on the basis of the existence of an application rather than its substance.
This is a recurring pattern in crypto, and it is the pattern I have spent the most time documenting. In late 2017, during the ICO mania, I spent three months dissecting the MakerDAO MKR token's collateralization logic in Solidity 0.4.11, and I found three integer overflow vulnerabilities that the standard audits had missed. The vulnerabilities were not the story. The story was that thousands of people were pricing the token without reading the code that made the token work. The information asymmetry was the market.
We are in the same configuration now, one cycle later. The thing being priced โ the charter, the business, the moat โ is not the thing that is disclosed. What is disclosed is an intent. What is priced is a capability. The gap between them is the entire trade.
2017 vibes. Proceed with skepticism.
Contrarian: The Charter Is a Liability, Not an Asset
Here is where I diverge from every optimistic read of this filing.
The consensus framing treats the trust charter as an asset โ a moat, a license, a competitive advantage. I think that framing is backwards, and the reason is mechanical.
A charter is not a permission you hold. It is a constraint you accept. When Rain obtains a national trust charter, it inherits fiduciary duty, supervisory examination, capital and reserve obligations, disclosure requirements, and the full weight of OCC supervision. It inherits a set of things it may not do โ and among those things are almost certainly some of the highest-margin activities in the sector. A trust bank cannot lend. It cannot run a fractional book. It cannot take the balance-sheet risk that makes commercial banking profitable. It trades optionality for legitimacy.
That trade is worth making if and only if the legitimacy unlocks revenue that optionality could not. For Anchorage and Paxos, it did, because they had institutional demand waiting on the other side of the license. For Rain, we have no evidence that the demand exists yet. And a charter without demand is not a moat. It is a fixed cost with a compliance department attached.
The deeper contrarian point is about the narrative itself. The claim that a single company can "redefine stablecoin trusts" is the kind of claim that gets written when the facts are thin and the ambition is large. You cannot redefine a category by filing an application. You redefine it by shipping something that the category then adopts. Circle did not redefine stablecoins by filing; it redefined them by achieving distribution. Paxos did not redefine trust-chartered infrastructure by filing; it redefined it by running issuance for partners at scale. The filing is not the redefinition. The filing is the application to be allowed to attempt one.
And there is a third-order risk that the coverage ignores entirely: the possibility that this filing is, in part, a fundraising instrument. Regulatory applications are expensive and slow, and the announcement of a regulatory application is free, fast, and generates exactly the kind of institutional-looking headline that helps with capital formation. I am not asserting that this is the motive. I am asserting that the incentive exists, that it is common in this sector, and that a rational reader should discount the narrative accordingly.
What Would Change My Mind
I do not want to be the analyst who is skeptical of everything and therefore useful for nothing. So let me be specific about the evidence that would move me from "structurally unconvinced" to "watching closely."
An OCC acceptance โ not a filing, an acceptance โ would be the first real signal. A conditional approval would be the second, with the caveat that conditional approvals constrain the business more than headlines suggest. Disclosed reserve composition and a disclosed float-allocation model would be the third, because those two numbers determine whether the economics are viable. And a named, verifiable customer โ an exchange, a payment processor, another issuer โ would be the fourth, because a B2B charter business is only as real as its first tenant.
Absent those four signals, the filing remains what it is today: an intent with a legal obstacle and an undisclosed business model, wrapped in a name that might refer to more than one company. That is not nothing. But it is not a redefinition either.
Takeaway: The Vulnerability Forecast
Here is my forward-looking read, offered as a forecast rather than a conclusion.
The most likely path is a long, quiet process. The OCC will neither approve nor reject quickly. It will examine, request supplements, and either grant a conditional approval with meaningful restrictions or let the application sit. During that window, the narrative will run ahead of the facts, because narratives always do.
The structural vulnerability to watch is not technological โ there is no code to break here. It is the collision between three things: a charter that constrains more than it enables, a market that is a coordination equilibrium hostile to newcomers, and a legal regime whose treatment of "trust bank as stablecoin issuer" is not yet settled. Any one of those can sink the business. All three together make a clean outcome unlikely without evidence we do not have.
If you are holding a position โ financial or intellectual โ in the thesis that this filing changes the stablecoin landscape, I would ask you one question before you add to it. What did the filing actually authorize? If you cannot answer that with a specific statute and a specific clause, you are not holding a thesis. You are holding a headline.
Entropy wins. Always check the fees โ and in this case, check whether there are any fees to check yet, because the business that would generate them does not exist until a regulator says it can. Proceed with skepticism. The charter race is real. The winner is not determined by who files first. It is determined by who, after filing, actually holds something.