Observe the timeline. On Wednesday, Ready — the self-custody wallet formerly known as Argent — terminated its card program. The cause was not a smart contract bug, not a chain outage, not a governance exploit. The cause was Kulipa, its card issuer, which wound down its operations with no advance notice. Founder Itamar Lesuisse stated that he received no warning. He learned of the shutdown at the same moment his users did.
That statement should trouble every wallet team in this industry. Not because Lesuisse was careless, but because he was telling the truth.
Ready is not an obscure project. It emerged from Argent, one of the most established smart-contract wallet teams in the Ethereum ecosystem. If a team of this maturity can be blindsided by a critical infrastructure provider, the rest of the sector has no reason to assume better.
This was not an isolated incident. Kulipa served multiple downstream clients. Solflare, the Solana wallet, lost card service the same night. Other card projects went dark in the same wave. One issuer. Many casualties. A coordinated collapse of the fiat off-ramp layer, triggered by a single off-chain entity.
In a bull market, launches get celebrated and dependency stacks get ignored. Weeks like this expose the cost of that instinct.
I have spent years auditing crypto infrastructure — from Tezos's pre-launch contracts in 2017 to EigenLayer's slashing conditions in 2024. The Kulipa shutdown is a different species of failure. No code was exploited. No funds were stolen. The blockchain functioned exactly as designed. And the service died anyway. The cards died anyway.
Let me build the forensic timeline. Phase one: the partnership. Ready selected Kulipa as its issuer, transferring control of the product's fiat exit to an external party. Phase two: the silent accumulation of risk. Inside Kulipa, a process began — a bank partner withdrawing, a compliance finding, a balance-sheet decision. Phase three: the shutdown. Kulipa halted operations. No broadcast. No notice period. No grace window. Phase four: downstream failure. Ready and Solflare suspended card services within days. The user, at the end of the chain, discovered the outage by attempting a transaction that declined.
That sequence is the story. Let me take the mechanism apart.
The Architecture: Two Layers, Two Trust Models
Ready sits at the application layer. Its product promise is simple: users control their own private keys, hold assets on-chain, and interact with a smart-contract interface. In principle, this is the most user-sovereign architecture available in crypto. Nothing about the wallet's on-chain design made it dependent on any single entity.
The card program was a different machine entirely.
A crypto card is not an on-chain instrument. It is a compliance stack disguised as a payment rail. Behind every card sits a chain of dependencies: a licensed issuer, a BIN sponsor, a card network, a bank partner, a KYC/AML processor, and a settlement provider. Kulipa occupied the center of that stack. It held the bank identification number arrangements. It maintained the banking relationships. It ran the compliance checks. It was the single point through which every card transaction had to pass.
Here is the structural flaw: the on-chain layer and the off-chain layer have completely different trust models. The chain is transparent, permissionless, and verifiable. The issuance stack is opaque, permissioned, and invisible to outside observation. Ready's users could verify their assets on-chain at any moment. But no user — and no wallet team — could verify the health of Kulipa's bank partnerships on-chain. The stability of the entire card product was a secret held by a third party.
The failure was not an exploit. It was the structural consequence of connecting a decentralized asset layer to a centralized settlement layer with no visibility and no redundancy.
Kulipa was not a niche player. It served multiple independent wallets across different ecosystems. This is the consolidation paradox of crypto payments: compliance costs are high, margins are thin, and issuers achieve scale by aggregating demand. The result is a hub-and-spoke topology. Every wallet connects to the same hub.
When the hub fails, every spoke fails. Simultaneously. Ready and Solflare both lost card service on the same night. Their outages were correlated through a single shared dependency.
Correlated downtime is the mathematical signature of a single point of failure. A system is not decentralized when its fiat off-ramp collapses into one entity.
From my Curve Finance stress-testing work in 2020, I learned to push systems to their limits and observe where the failure surfaces. Here, the failure surfaces at the issuer layer. The on-chain asset layer performed exactly as designed — funds remained in user control. But the product layer — the layer the user actually touches — was entirely dependent on one off-chain company.
Zero Observability, Zero Warning
The most damning detail is also the simplest: Lesuisse learned about the shutdown at the same time as users. No notification. No transition period. No handover.
Translate this into engineering terms. A wallet team with a card product treats the issuer as a critical dependency. Critical dependencies require health monitoring, early-warning signals, and contingency triggers. Ready apparently had none of these. No dashboard tracked Kulipa's operational status. No contractual mechanism demanded advance notice.
The silence in the code is the loudest warning sign. But here, there was no code to inspect. Kulipa's financial health, its banking relationships, its regulatory pressures — all of it lived in a black box no wallet team could audit.
I have seen this pattern before. In 2017, I audited Tezos's pre-launch contracts. The team had built elegant formal proofs, but the proofs did not cover the operational layer — the human-run infrastructure around the code. Cryptographic correctness does not equal functional safety. The same lesson applies here. A wallet can be technically sovereign while remaining operationally dependent on a third party it cannot inspect.
The inability to verify a critical dependency is itself a critical vulnerability. Trust is a variable, verification is a constant.
The Migration Trap
The obvious remedy is to find a new issuer. Any reasonable person assumes that a wallet team with users and a product can switch partners.
It cannot be done quickly.
Card issuance is not a software library. Replacing an issuer means renegotiating BIN sponsorship, integrating with a new payment network, completing bank due diligence, passing compliance audits, and reissuing physical and virtual cards to every user. Users must re-perform KYC. Old card numbers die. Recurring payments break. The realistic replacement timeline is three to six months under ideal conditions. Longer, in practice.
This is why the shutdown is not a temporary inconvenience. It is a product kill. Users who relied on the card for everyday spending — the users who chose Ready specifically because it offered a fiat off-ramp — will migrate to alternatives. Some will move to custodial exchange cards, accepting a different trust model because it offers continuity. That migration is easy to underestimate and hard to reverse.
Card users are the highest-quality demographic in crypto. They passed KYC. They linked a bank account. They use crypto as currency, not speculative inventory. This is the segment that powers the "real adoption" narrative for wallet projects. Losing them is disproportionately costly.
Complexity is often a veil for incompetence. Here, the complexity of the compliance stack was a veil for fragility. Every layer added a new point of dependency, and none of those dependencies was visible to the downstream wallet or its users. The product looked complete. It was a house of cards — built of actual cards, ironically.
What the Bulls Got Right
Now the contrarian turn. This event did not invalidate self-custody. It validated the core distinction.
While the card program collapsed, on-chain funds remained safe. Ready confirmed this. If this had been a custodial product — a Binance card or a Crypto.com card — an issuer-level failure would have frozen the assets themselves. Users would have faced both service disruption and asset lockup. Here, the separation of layers worked. The asset layer was genuinely independent of the service layer.
That distinction must be preserved in the post-mortem. Too many observers will use this event to dismiss the entire self-custody-plus-card model. That is lazy analysis. The model worked as designed: the wallet could not prevent Kulipa's collapse, but it also did not expose users to asset loss.
There is also a market-level angle. This event creates economic pressure for redundancy. Wallets that survive the next six months will need to demonstrate multi-issuer or multi-network fallbacks. New entrants may build modular compliance middleware — an issuer interface that can be swapped across banking networks. The short-term narrative damage could accelerate the long-term infrastructure improvement.
The Accountability Question
Who is accountable when an off-chain issuer collapses without warning?
Not the chain. The chain executed correctly. Not the user. The user did what the product asked. Not the wallet team alone — though they will bear the reputational cost.
The issuer is accountable, but issuers can disappear. That is the inconvenient reality: an entity with a banking license can wind down in a weekend, and no smart contract can prevent it.
The industry's response must be structural. Wallet teams should be compelled — by market pressure, if not by regulation — to disclose their issuer dependencies and redundancy plans. Users should demand this information before trusting a card product with everyday spending. The sector should fund on-chain-verifiable issuer health, or settle for a permanent condition: self-custodied assets behind the most fragile fiat exit in finance.
The Hard Question
The next three to six months are the test. Is the Kulipa failure an isolated event, or the first tremor of systemic fragility?
If a second card issuer fails in that window, the market will treat self-custody-plus-card as a permanently fragile category. Users will retreat to custodial alternatives or abandon crypto cards entirely. If no second failure occurs, and replacement issuers emerge, the narrative resets.
I cannot predict which path we take. But one lesson must survive: self-custody solves asset control, not payment access. A wallet that cannot guarantee the stability of its fiat off-ramp is only half a product.
The chain remembers. The marketing team forgets. And the users who lost their cards on a Wednesday morning will remember the difference between an asset that was safe and a service that was not.
Ask your wallet which issuer holds the off-ramp. Then ask what happens when that issuer vanishes overnight. If the answer is "we find out together" — that is not a product. It is a bet.