Chainflip halted its cross-chain swap protocol on November 21 after a suspected $4.86 million drain from its Ethereum vault. Its FLIP token fell about 30%, according to CoinDesk's report published at 16:41 UTC. The Block reported a 34% decline in its own report that day. Those figures describe separate reporting snapshots, rather than a fixed closing price.
The security question centers on an accepted withdrawal signature. Blockchain investigators found that the transaction passed the vault's authorization check, putting the process that produces those signatures under scrutiny. Chainflip acknowledged a potential exploit and disabled deposits, withdrawals, swaps and quoting.
The loss estimate comes from external investigators. Chainflip had not confirmed the cause or a final loss figure at the time of reporting.
One withdrawal emptied three asset balances
Crypto.news, citing Onchain Lens and AMLBot, reported that the withdrawal took 520.2 ETH, 3.25 million USDC and about 758,000 USDT. The transaction occurred at 07:10:59 UTC on November 21 and sent the assets from the same vault to one destination.
The stablecoins accounted for just over $4 million of the estimated loss. With most of the missing dollar value held in dollar tokens, a fall in ETH's price alone cannot explain the reduction in the vault's assets.
AMLBot said the stolen stablecoins were converted into ETH and most of the proceeds entered Tornado Cash within minutes. The rapid conversion changed the form of the assets recovery efforts would need to pursue.
For users, the immediate operational consequence extended beyond the drained balances. Chainflip's pause stopped the services needed to start and complete swaps through the protocol. A user waiting for a transfer and a liquidity provider with assets committed to the system face different exposures, but both depend on the protocol processing withdrawals again.
A valid signature bypassed the usual sequence
Bitquery's investigation identified an unusual nonce, the number attached to a signed request to prevent reuse. Ordinary Chainflip requests followed a running sequence. The drain carried a 39-digit number outside that sequence.
The firm examined 299,677 accepted signatures and said this was the only one that broke the count. Its interpretation was that the authorization came from outside the network's ordinary signing process.
Bitquery also recorded a key change at 08:53 UTC, about one hour and 42 minutes after the withdrawal. Its check through 11:23 UTC found no further Ethereum signatures after that change.
These findings make the authorization path the central technical issue. Because the vault accepted a request that appeared correctly signed, investigators must examine the machinery that creates and checks permission to move funds, including how an unauthorized withdrawal could pass those checks.
A key change can restrict future use of an old key. It cannot reverse a transfer already accepted by Ethereum.
Distributed signing still controls pooled funds
Chainflip's documentation describes a threshold signing system designed around 100 participants from a set of 150 validators. Validators hold secret shares and collaborate to produce a signature. The aggregate private key is intended to exist implicitly across those shares, without being assembled into a single stored secret.
The documentation also describes a test signing ceremony before funds are assigned to a new key. That design distributes authority over withdrawals, while the resulting signature gives the destination blockchain a single authorization to verify.
The incident therefore raises a specific custody question: whether the deployed signing process preserved the protections described by that design. An accepted signature alone does not show that 100 validators knowingly approved a theft.
For users assessing control over their own wallet assets, the practical boundary is the moment funds move into a protocol-controlled address. Keeping the keys to the sending wallet does not give that wallet authority over money already deposited elsewhere. Recovery then depends on the receiving system's controls and response.
September's reimbursement creates a separate test
Chainflip had already suffered a September exploit involving its Tron integration. The Block reported that the earlier incident exploited transaction memo processing and caused about $736,000 in stablecoin losses.
Validators subsequently voted to reimburse affected liquidity providers from protocol surplus funds.
That history gives users a concrete precedent for reimbursement, although the current estimated loss is larger. The earlier vote committed a particular pool of resources to a particular incident. A new reimbursement would require its own funding and decision.
The two incidents also demand different technical responses. Fixing transaction parsing addresses the September failure. The November investigation concerns authorization of an Ethereum withdrawal. Treating both as a single recurring software bug would obscure the work needed before service resumes.
Overview
Chainflip's suspected $4.86 million Ethereum vault drain combined missing assets with a protocol-wide service pause and a sharp FLIP decline. Investigators traced an accepted signature outside the usual request sequence, making withdrawal authorization the focus of the investigation.



