Somewhere in a server rack you will never visit, there is a wallet with your name on it—and you have never seen its keys, its recovery phrase, or its address. According to Itai Turbahn, vice president at Fireblocks, you are probably already using it. "You're already using a crypto wallet without knowing it," he told his audience, and the line landed because it is simultaneously true and unsettling.
The claim rests on two numbers: $8 trillion in annual transaction flows pass through Fireblocks' networks, and the company says it carries roughly 15% of all stablecoin volume. Those figures are unaudited, they come from a single interested party, and the definitions are never specified. But they point at something real. A new layer of financial plumbing has been built beneath the apps people actually touch—Cash App, Western Union, Magic Eden, the payroll tool that paid a worker in Argentina in ten seconds—and almost nobody using it knows it exists. We build walls of code to protect hearts of flesh, and then we hide the walls.
Fireblocks began life as an institutional custody provider: a company that sells banks and exchanges the ability to hold crypto without holding keys. Its core technology is multi-party computation, or MPC, a cryptographic method that splits a private key into fragments distributed across servers so that no single machine ever assembles the whole thing. That is the engineering promise, and it is a serious one.
What changed the story is embedded wallets—software that gives a customer a wallet without a seed phrase, without a login, without any awareness of blockchains at all. Fireblocks bought this capability by acquiring Dynamic, a startup whose entire premise was to let developers hand out wallets as casually as they hand out user accounts. The merger turned a custody company into a wallet factory, shipping the invisible infrastructure behind hundreds of consumer products.
Now layer on stablecoin payment rails. When Western Union or SoFi decides to issue its own dollar token, when Circle routes USDC across chains, when Fiserv clears between banks, Fireblocks sits underneath, signing transactions and enforcing approval rules. The pitch is seductive: you do not need to teach the world about private keys. You simply remove the need to know.
That is a genuine technical achievement. It is also a values decision dressed as an engineering convenience. For a decade the industry preached "not your keys, not your coins." The new doctrine is colder and more honest: you never needed to know the keys existed.
Here the analyst has to slow down, because the architecture hides its most important tradeoffs.
MPC, in Fireblocks' implementation, is almost certainly a threshold signature scheme—TSS, built on academic protocols like GG18 or GG20 that anyone can read. The distinguishing property of TSS is that it leaves no on-chain footprint. A threshold wallet looks on the blockchain like a single ordinary signature. Compare that to a classic multisignature contract like Gnosis Safe, whose policies sit publicly visible on-chain, auditable by anyone.
| Dimension | MPC / TSS | Traditional Multisig | |-----------|-----------|----------------------| | On-chain footprint | None (appears as single sig) | Visible contract | | Privacy | High | Low | | Auditability | Low | High | | Regulator friendliness | High | Low |
Read that table slowly. For an institution, "no footprint" is a feature—privacy, compatibility, clean regulatory integration. For an ordinary user, it is a black box. You cannot verify on-chain who controls your wallet, whether the threshold is 2-of-3 or a single party quietly holding everything. The "keyless wallet" is, technically, a wallet whose keys were never yours to begin with. Vault-grade custody has been re-labeled as convenience, and the label stuck because it is pleasant.
The approval logic Turbahn described makes this concrete: a $1 transaction might clear with an email confirmation, while $5 million requires a quorum of multiple parties. That gradient is elegant. It is also a governance policy configured by Fireblocks, not by you. Truth is not consensus, it is verification—and here verification is precisely what the architecture removes.
Then there is the geography of stablecoins, which the interview quietly revealed. South America runs on Tron and USDT; the United States runs on USDC. That is not a technical outcome—it is a regulatory arbitrage outcome. The "10 seconds to Argentina" case sounds like a blockchain triumph, but most of those seconds are spent in fiat on-ramps and compliance checks, not on-chain confirmation. The bottleneck in payments was never the ledger. It was always the fiat gate and the KYC desk.
And follow the money to see who actually captures value. Stablecoin issuers like Circle and Tether earn Treasury interest on reserves—the strongest margin in the entire stack. Wallet infrastructure like Fireblocks earns SaaS subscriptions and per-signature fees. End applications like Cash App and Western Union earn user fees and FX spreads. This is a smile curve, and Fireblocks sits in the uncomfortable trough of it, squeezed upstream by issuers and downstream by anyone who owns the customer relationship. When enterprise clients finish a transfer and immediately route idle balances into Morpho or Aave to chase yield, the signal is unmistakable: capital barely rests inside the vendor's system. Fireblocks collects a toll, not a float.
The strategic threat arrived quietly. Stripe acquired Privy, a direct competitor to Dynamic. Stripe has millions of merchants and does not need a neutral infrastructure vendor—it can own the wallet layer itself. Fireblocks' remaining moat is not cryptography, which is public, but relationships: Fiserv's bank-rail integration, Circle's cross-chain bridge, the years of compliance paperwork that cannot be copied overnight. It is the same logic that drove PayPal to launch PYUSD—become a regulatory partner rather than wait to be regulated. Fireblocks is playing the same game, one layer lower. That is a real moat. It is not an unassailable one.
Here is the blind spot the entire narrative skips past: "you are already using a wallet without knowing it" is presented as market penetration, but read literally it is a disclosure failure.
If a user's assets sit in a white-label wallet operated by Fireblocks and interfaced through an app, and something breaks—a shard goes offline, a signing policy misfires, a migration goes wrong—who is liable? The user never consented to Fireblocks' custody terms. They consented to Cash App's or Western Union's. Under Europe's MiCA, crypto-asset service providers carry explicit disclosure duties; under consumer protection law, "I didn't know I had a wallet" is not a defense for the company—it is a lawsuit waiting for a docket number. The responsibility boundary between the invisible infrastructure and the visible app is unmapped, and nobody in the interview touched it.
Nor did anyone mention performance. $8 trillion in annual flow tells you volume. It tells you nothing about throughput, signing latency, concurrency, or failure rate—the metrics that determine whether that volume is safe to route through a single vendor. Education dissolves fear; but fear is not the same as diligence, and diligence is the only thing that survives a bad quarter.
The future of custody will not be decided by which protocol is cleverest. It will be decided by who is willing to hold the responsibility when the invisible wallet fails. Fireblocks has built a remarkable engine and pointed it at a market that will never look at it. But the ledger remembers what the crowd forgets: every unsuspecting user is a promise, and promises made in private are the hardest to keep in public. The generation now building on these rails will either learn to audit them—or inherit the bill.