Russia's 1% Crypto Cap Is Actually a Shield for Bank Customers
The Bank of Russia's Sept. 18 draft sets a brutal 1% capital cap on crypto. But the fine print carves out client custody assets, and that distinction is what actually protects depositors. Here's the mechanic everyone on CT missed.
I've been staring at the Bank of Russia's Sept. 18 draft for two days now. And honestly? The headline number, that brutal 1% cap, isn't the story. The story is what it doesn't count.
The chain doesn't lie, and neither does a capital ratio. Everyone on CT read "1% crypto cap" and panicked. Anon, let me explain why that panic is backwards.
What N31 and N32 Actually Do
Here's the thing. The proposal creates two new ratios. N31 for individual credit institutions. N32 for banking groups, measured on a consolidated basis. Both compare what the central bank calls covered exposure against a bank's own capital.
Not its total assets. Its capital. That distinction matters way more than the 1% figure.
Covered exposure includes the bank's own crypto holdings. It also sweeps in crypto-linked instruments, which is the wide net. Think derivatives, tokenized products, anything whose value tracks a digital asset. If the bank is holding that risk on its own book, it eats into the 1% ceiling.
But here's the carve-out. Client custody positions sit outside the calculation, conditionally. So if a bank is just safekeeping crypto for customers, not trading it with house money, that exposure doesn't torch its capital ratio.
Read that again. The cap targets the bank's balance sheet, not yours.
So what happens when a bank's own crypto exposure blows past 1% of capital? It has to shed it. Fast. No slow bleed, no hoping the market recovers. The ratio forces the decision.
Why This Is Better Than It Looks
Russia has been weirdly hostile to crypto for years. A blanket ban floated in 2022. Then a hands-off stance that mostly meant "don't touch it." Now we get a 1% number that sounds like a stranglehold.
It's not. It's a firewall.
A bank with its own crypto bags can only push so much risk into that 1% bucket. That limits how much house money gets exposed to a 40% drawdown. Meanwhile, customer assets, held in custody, keep their own lane. The bank isn't incentivized to gamble with your coins because your coins aren't what's testing the ratio.
Is 1% harsh? Absolutely. Compare it to Basel's treatment in the EU, where banks got a 1,250% risk weight on crypto but with more nuance baked into the exposure classes. Russia just went straight to the ceiling. No ladder, no phase-in, just a hard lid.
But harsh and protective aren't opposites. Real talk: a tight cap forces banks to keep crypto risk small. That's the whole point. The folks screaming about this are reading the number and skipping the mechanism.
My Take and What to Watch
Should you care if you're not in Moscow? Yeah. This is bigger than people realize.
Capital rules travel. When one major regulator designs a clean separation between bank proprietary risk and customer custody, other watchdogs copy the blueprint. The conditional client-asset exemption is the template. That's the signal. I've been saying this for weeks about the broader trend, and Russia just handed everyone a case study.
Here's what I'm watching next. First, whether that "conditional" exclusion holds once the final draft drops. Conditions are where regulators hide the teeth. Second, whether banking groups use N32's consolidated basis to shuffle exposure between subsidiaries. Third, the comment window closing on Sept. 18. Watch the revisions.
My honest read: this protects depositors more than it punishes crypto. A bank that can't hide client coins inside a capital ratio is a bank that can't quietly liquidate them when things get ugly.
Don't aping headlines. Read the ratio.