A custody dispute between BitGo and Indian cryptocurrency exchange Unocoin has erupted into a public standoff after a series of suspicious wallet transfers prompted Unocoin to suspend its services — and each party to point in a very different direction. BitGo, one of the most prominent institutional digital asset custodians in the industry, has flatly denied that any breach occurred on its infrastructure, asserting that the transfers in question were executed using cryptographic keys held exclusively by Unocoin, with no participation from BitGo's systems whatsoever.
At the center of this incident is a question that the broader crypto custody industry has long wrestled with: when a multi-party key arrangement is compromised, who is responsible — the custodian that holds the institutional keys, or the client entity that controls its own share of the signing authority? BitGo's position is unambiguous. The firm says the disputed transactions were authorized through Unocoin-held keys, placing the locus of any potential misuse squarely within the Indian exchange's own operational perimeter.
Unocoin, for its part, is not disputing that its keys were the mechanism used. Instead, the exchange has zeroed in on what it suspects was a misuse of a backup mechanism — a contingency feature built into multi-signature or multi-party computation custody setups to allow fund recovery in emergency scenarios. Backup mechanisms of this nature are standard industry practice, but they represent an inherent tension in custody architecture: a system designed to prevent catastrophic loss of access can itself become a vulnerability if credentials or access procedures are inadequately secured. If Unocoin's hypothesis is correct, it would mean an attacker — or an insider — found a way to weaponize a recovery path rather than a primary signing channel.
The practical consequences of this standoff are immediate and serious for Unocoin's users. The exchange has suspended services while the investigation remains ongoing, leaving customers unable to access their funds or execute trades. For an exchange operating in India's rapidly growing but still regulatory-sensitive crypto market, an extended service suspension carries reputational weight that is difficult to recover from, regardless of where fault is ultimately assigned. The timing is also notable — Indian regulators and financial watchdogs have been increasingly scrutinizing crypto platforms, and any prolonged outage tied to a custody incident will draw institutional and regulatory attention.
From a technical standpoint, the architecture of a multi-party custody arrangement means that neither BitGo nor Unocoin acts unilaterally under normal conditions. Transactions typically require cooperation between key-holders — the custodian, the client, and sometimes a third-party recovery agent — before funds can move. BitGo's denial is therefore more than a legal hedge; it reflects a genuinely plausible technical reality. If the transfers were executed using only Unocoin's keys, it could indicate that the backup path was structured in a way that allowed single-party authorization under specific conditions, bypassing the standard multi-signature threshold. That would represent a significant design or configuration oversight.
What remains unclear is whether this was an external attack exploiting a known or unknown vulnerability in Unocoin's backup credential management, or whether it involved some form of internal misuse. The language Unocoin has used — "misuse of a backup mechanism" — is deliberately cautious and does not rule out either possibility. Investigations of this kind typically take weeks before forensic blockchain analysis and internal audit trails can produce a definitive account of what happened, who authorized what, and whether the transfers resulted in actual loss of funds.
The incident also raises harder questions about how the custody industry communicates responsibility boundaries to its clients. BitGo's contracts and service-level agreements almost certainly define the scope of its liability in terms of its own key material, meaning clients who hold their own keys in a split arrangement bear responsibility for securing those keys operationally. That may be legally sound, but it creates an accountability gap that becomes painfully visible when something goes wrong. Retail and institutional clients of crypto exchanges rarely understand that their exchange's choice of custody vendor does not transfer all security responsibility to that vendor.
Until Unocoin completes its probe and publishes findings — or is compelled to by regulators — the full picture of what happened to those wallets will remain incomplete. What is already clear is that both companies face a trust deficit with their shared user base, and that the structural ambiguities in multi-party custody arrangements deserve far more transparent disclosure than they currently receive from platforms operating at the retail level.
Written by the editorial team — independent journalism powered by Bitcoin News.