Chainflip’s Reported $4.86M Vault Withdrawal Is Dated in the Future

Daily Feed
Chainflip’s Reported $4.86M Vault Withdrawal Is Dated in the Future

A reported $4.86 million withdrawal from Chainflip’s Ethereum vault is dated November 21, 2026. That date is in the future at publication, so the withdrawal cannot be treated as a confirmed past event. The transaction and the activity that followed remain claims requiring a corrected date or further verification.

  • Reported amount: 520.2 ETH, 3.25 million USDC and 758, 000 USDT.
  • Reported trail: The stablecoins were swapped for ETH, and 2, 909 ETH was later deposited into Tornado Cash.
  • Unresolved: Bitquery describes an unusual vault nonce, but the cause and the precise flow of ETH remain unclear.

What the reported transaction shows

Onchain Lens reported that a transaction at 07:10:59 UTC on November 21 sent 520.2 ETH, 3.25 million USDC and 758, 000 USDT from Chainflip’s Ethereum vault to a single destination address. The tracker estimated their combined value at about $4.86 million. The stated date is in 2026, so the event cannot be reported as a completed incident at publication without a date correction.

Chainflip operates a cross-chain swap service that lets users exchange assets across different blockchains. The transaction record described by Onchain Lens lists the Ethereum vault as the source of the transfers.

What a valid signature does and does not mean

Onchain Lens said the transaction carried a valid signature for the vault’s aggregate signing key. This means the vault’s on-chain authorization check accepted the transaction. It does not show that the withdrawal was legitimate, identify who produced the signature or prove that a key was stolen.

Bitquery’s analysis describes Chainflip’s vault signing as a threshold process: validators cooperate to produce a signature, rather than one validator acting alone. Bitquery says at least 100 of up to 150 validators must cooperate. This describes the signing setup, but does not explain how the reported transaction was authorized.

Bitquery also reported an anomaly in the vault’s nonce sequence. It says the transaction was the only one among 299, 677 accepted signatures it examined that did not follow the observed sequence, and that the nonce was 39 digits long. Bitquery describes this as a vault nonce. Its account does not establish that it is Ethereum’s standard account-transaction nonce.

A nonce is a value used to track or distinguish transactions. An unusual value may raise questions about the signing or validation process, but it does not, by itself, prove a forged signature or a specific exploit. Bitquery lists several possible explanations, including a stolen key, compromised validator key shares or a validation flaw, but confirms none of them.

Reported laundering trail

AMLBot and Bitquery described a rapid sequence after the withdrawal:

  1. Stablecoin swaps: AMLBot and Bitquery said the USDC and USDT were exchanged for ETH on Uniswap within four minutes.

  2. Transfers and deposits: Bitquery reported that 2, 909 ETH was deposited into Tornado Cash in 38 transactions: 29 deposits of 100 ETH and nine deposits of 1 ETH.

  3. Timing: Bitquery said the sequence, from initial gas funding to the final deposit, took under 10 minutes.

“We believe the laundering was scripted and automated end to end, ” AMLBot said.

That is AMLBot’s assessment. It does not prove who controlled the wallets or what tools were used. Tornado Cash is a mixer that pools deposits, making it harder to link a deposit to a later withdrawal. Using a mixer does not, on its own, identify a depositor.

The 2, 909 ETH figure refers to a later movement of funds, not an additional loss on top of the reported $4.86 million. The available breakdown does not show how much of those deposits came from the original 520.2 ETH and how much came from swapping the stablecoins.

What remains unverified

Bitquery reported that Chainflip changed its Ethereum signing key at 08:53 UTC on November 21, about an hour and 42 minutes after the stated withdrawal time. It also said it saw no further Ethereum vault signatures after the change during its analysis, and that the project’s website showed services down. These are Bitquery’s observations, not a Chainflip post-mortem or confirmation that every network was affected in the same way.

Bitquery said ordinary Ethereum payouts continued for almost two hours after the reported drain. Its analysis found that Arbitrum vault activity that morning looked ordinary, but it did not assess Solana. These limited observations do not establish the status of all Chainflip services.

The available information does not establish whether the funds were recovered or explain the reported withdrawal. Before the event can be treated as confirmed news, the future-dated transaction needs a corrected or reconciled date, and Chainflip’s latest official status and incident communications need to be checked.

Key questions and answers

  • How much was reportedly withdrawn?

    Onchain Lens reported 520.2 ETH, 3.25 million USDC and 758, 000 USDT, estimated at about $4.86 million. The transaction is dated November 21, 2026, which is in the future at publication, so the reported event is not confirmed as a completed incident.

  • Does the valid signature prove a key was stolen?

    No. It shows that the vault accepted the authorization. Bitquery reported an unusual vault nonce, but key theft, compromised validator shares and a validation flaw remain possible explanations, not established causes.

  • How quickly were the funds reportedly moved?

    AMLBot and Bitquery said the stablecoins were swapped for ETH within four minutes. Bitquery tracked 2, 909 ETH into Tornado Cash in a sequence that took under 10 minutes.

  • Is the reported 2, 909 ETH a second loss?

    No. It describes the later movement of funds from the reported withdrawal. The available breakdown does not specify how much was the original ETH and how much came from the stablecoin swaps.

  • Have the funds been recovered?

    The available information does not establish a recovery outcome. Tornado Cash’s legal and developer-liability debate is a separate issue from whether these funds can be recovered.

Share this article

Powered by ADBYTES

Advertise smarter.

Adbytes.Media is a transparent advertising network where advertisers reach real audiences and publishers, affiliates & everyday members earn ADBYTES tokens. Join the community and start earning today.

Back to Blog