NodeWitness four-step graphic: 122.86137042 BTC leave at 07:41, 122.86136932 BTC arrive at 08:01 at an address where they remain unspent, Chainflip leaves an on-chain message at 21:12, and the return address is still empty at 09:13 on 22 November, block 977,024, Madrid time
NodeWitness' own graphic. Reading at block 977,024, 22 November 2026, 09:13, Madrid time.

The 122.86 BTC That Left Chainflip on Saturday Is Still Unspent, and the Return Deadline Is Monday

Chainflip has given the attacker until 19:38, Madrid time, on Monday to send back 90% of what was taken [1]. In our full node's reading of block 977,024, the 122.86137042 BTC the protocol says left its vaults was still sitting at one address, and the published return address had not received a single satoshi [1][3].

The first public count was the Ethereum side: about $4.86 million in ether, USDC and USDT. Later on Saturday, Chainflip Labs published a message addressed to the attacker and added bitcoin to the list: 122.86137042 BTC, 520.2243399 ETH, 3,249,631.41 USDC and 758,141.33 USDT [1]. Chainflip does not publish a dollar total. Cointelegraph puts the combined haul at about $12 million [2]. At the $59,095 price in our 09:13, Madrid time, reading on 22 November, the bitcoin alone was worth about $7.26 million [4].

The official bitcoin figure is not just a press number. It is on the Bitcoin record, to the satoshi.

The official amount left at 07:41 and had not moved by Sunday morning

That new address, bc1qmj0x9pkyup07j09axvvr6aquqfsdw254nlz5lz, exists only for this movement. It received the 122.86137042 BTC at 07:41 and, twenty minutes later, at 08:01, Madrid time, in block 976,865, sent 122.86136932 BTC to bc1qm777twlzmelyutungyfw65ykn2l5kn68e6v4g6. The 110-satoshi gap is the fee [3].

In the reading of block 977,024, at 09:13, Madrid time, on 22 November, those 122.86136932 BTC were still unspent at that third address, which had not sent anything and had no pending transactions in the mempool [3].

Four cards on a dark background: 122.86137042 BTC leave at 07:41, 122.86136932 BTC arrive at 08:01, Chainflip's on-chain message at 21:12, and the return address still empty at 09:13 on 22 November, block 977,024, Madrid time
The three hops of the bitcoin leg and the return address, as of block 977,024 [3].
Step Madrid time Block Amount Transaction
Leaves an address with 1,845 transactions 21 Nov, 07:41 976,863 122.86137042 BTC 20262de3…155b7a
Arrives at the address that still holds it 21 Nov, 08:01 976,865 122.86136932 BTC ac38a5ae…fd2cb4
Chainflip's on-chain message to that address 21 Nov, 21:12 976,943 1,000 sats and an OP_RETURN 0f75dbd5…24f004
Reading: balance there / at the return address 22 Nov, 09:13 977,024 122.86137932 BTC / 0 —

Source: reading from our full node, block 977,024 [3]. The 122.86137932 BTC balance is the 122.86136932 BTC from the theft plus the 1,000 sats in Chainflip's message.

In that reading, the 122.86136932 BTC that arrived at 08:01, Madrid time, on 21 November was still unspent, and nothing was waiting in the mempool [3].

The addresses can be checked in our address analyzer.

Monday's deadline, and a return address that is still empty

At 21:12, Madrid time, on 21 November, in block 976,943, an on-chain message to the address holding the bitcoin was confirmed. The OP_RETURN text reads: "Chainflip: return 90%, keep 10%. Addresses and terms: chainflip.io/return" [1][3]. The same transaction also sent 1,000 sats to that address, and those sats were still unspent in our reading [3].

On its terms page, Chainflip tells the attacker to keep 10% and return 90%: 110.57523337 BTC to bc1qux4nruxvwfxyv2n5d4fw0a363d4lxn5f45rats and 2,618.1 ETH to an Ethereum address, by 18:38 UTC on 23 November, which is 19:38, Madrid time [1]. If both amounts arrive in time, it says it will treat the incident as a white-hat recovery, ask no further questions and withdraw its reports and complaints with law enforcement agencies [1].

As of block 977,024, the bitcoin return address had no confirmed transactions and nothing in the mempool [3].

Chainflip says it has traced how the attack was prepared: Tornado Cash funding on 11 November, a purchase of the FLIP token, a validator account registered on 20 November and the server behind it. It also says it has identified the mechanism of key exposure, prevented such future attacks, and found metadata that law enforcement could use to identify the attacker [1]. Those are the protocol's claims. This reading does not test them. It follows the bitcoin.

Chainflip has appeared in a stolen-coin trail before. In the fake-alert theft from NGRAVE's app, Bitquery's tracing had bitcoin passing through this same cross-chain swap service [5].

The return addresses are for the attacker. Do not send funds to them.

We track the effect on the bitcoin market separately.

Sources

Labelled by type.

  1. Chainflip Labs, Message from Chainflip Labs, checked on 22 November 2026. Theft figures (122.86137042 BTC, 520.2243399 ETH, 3,249,631.41 USDC and 758,141.33 USDT), return terms, deadline (18:38 UTC on 23 November 2026), return addresses and the protocol's account of how the attack was prepared. (Primary, official statement)
  2. Cointelegraph, Chainflip confirms $12M hack, offers attacker 10% bounty, 22 November 2026. Relays the statement, the roughly $12 million combined total and the earlier $4.86 million figure for the Ethereum side. (Secondary, press)
  3. NodeWitness, our own bitcoin reading with our full node, block 977,024 (22 November 2026, 09:13, Madrid time). Outflow, arrival and on-chain message transactions, balances and mempool for the addresses involved, and the address analyzer. (Primary, own data)
  4. NodeWitness, market ticker, reading at 09:13, Madrid time, on 22 November 2026. Price of $59,095 from CoinGecko data. (Primary, own data with third-party price)
  5. Bitquery, Fake NGRAVE app alerts drained $2.65M from 84 wallets, 19 October 2026. In that tracing, bitcoin passing through Chainflip. Cited in our piece on the three hardware-wallet attacks. (Secondary, on-chain analysis by a data company)

More in Price and market

See all 37 articles in Price and market →

Last updated: November 22, 2026