In a two-of-three self-custody wallet, the user and backup keys Unocoin holds can sign without BitGo's key and be broadcast straight to the chain, which is why a working account freeze and an unauthorized outflow are not a contradiction. Unocoin says it has not established how the keys were accessed, and neither company has published a loss figure.
BitGo said on Friday that its systems were not breached and that the outgoing transactions Unocoin is investigating were signed with the user and backup keys the Indian exchange holds itself. The custodian said its review found the transfers were broadcast on-chain without its platform or its participation, that its own key was never used, and that no other clients were affected. It said Unocoin's enterprise account was frozen on November 6 and that the freeze functioned as intended.
Unocoin's account of the same events stops short of naming the keys. In an update published the same day, the exchange said it suspects the backup access mechanism on its wallets was exploited and that it has not established how access was obtained, who authorized the transfers, or which keys signed them. It has published no loss figure, no transaction hashes and no destination addresses. Services have been suspended since November 9, when Unocoin disclosed unauthorized access to its servers and disabled customer logins.
Both accounts can be true at the same time, and the reason sits in how BitGo's wallets are built. Every BitGo wallet carries three keys, a user key, a backup key and a BitGo key, and any two of them produce a valid signature. Routine transactions use the user key together with BitGo's. BitGo's documentation says the backup key can stand in for either of the other two, which means a client holding both the user key and the backup key holds a complete signing quorum on its own. In a self-custody wallet that is the standard arrangement: the client generates the keys and gives BitGo only an encrypted user key and the backup public key, and the documentation states that BitGo never has access to the private user or backup keys.
A quorum held entirely by the client can also be used without BitGo. The company publishes a recovery tool and a written procedure for assembling and signing a transaction without using any BitGo services, taking the encrypted user and backup keys from a customer's recovery card, and then pushing the signed transaction to the network through a block explorer. That is the route BitGo describes these transfers taking. A freeze applied to an enterprise account governs what BitGo's platform will sign and relay. It does not reach a transaction built elsewhere from two keys the client already has.
Unocoin asked both of its custody providers to freeze its accounts on November 6, Fireblocks at 11:24 UTC and BitGo five minutes later, and said both confirmed. Further unauthorized activity followed on November 9, which is when the exchange suspended services. It identified the outgoing transactions on November 12, from an Ethereum address inside its BitGo wallet infrastructure, and said its own frozen account access had kept it from reviewing the full transaction history. On November 13 it said BitGo had supplied the information it had asked for, and BitGo's statement followed the same day.
What neither company has said is how much moved and who moved it. Unocoin says more than 90% of customer cryptocurrency sits in cold storage, and when it first disclosed the server intrusion on November 9 it said no funds had been lost, an assurance it has not since repeated with a figure attached. The only public reading of the exchange's holdings comes from the analytics account Onchain Lens, which posted on November 12 that Arkham Intelligence showed a zero balance across about 81,000 addresses attributed to Unocoin. That covers only addresses Arkham has attributed to the exchange, so it cannot establish total holdings or a loss.
The suspension has run since November 9. Unocoin has estimated four to five working days to rebuild and secure its server infrastructure, followed by security checks before services resume, and it has not said that they have. Two other exchanges are in a comparable position this month. BitMart was hacked a second time while customers were still waiting on withdrawals and has published no loss figure of its own, and Mercado Bitcoin paused withdrawals on November 2 with its own totals still unsettled.
BitGo's statement draws a boundary rather than closing the matter. It says what BitGo's systems and BitGo's key did, and it refers questions about customer funds to Unocoin. The question Unocoin has left open is not whether the freeze held but how keys it holds itself came to sign, and it has not said when it will answer.