Chainalysis links 107 BTC burn to five-wallet cluster after a $1M custodian round trip
One 12-year-dormant wallet sent 20.00010537 BTC to a large custodian, got 20.00006037 BTC back, then burned it in May.
On-chain analysis tied to Chainalysis indicates five Bitcoin wallets likely controlled by a single early holder burned 107 BTC in May, worth about $8.5 million at the time. A standout leg of the activity saw a roughly 12-year-dormant wallet route about $1 million in BTC through a large custodian in March, receive nearly the same amount back three weeks later, and then destroy the coins.
Key Takeaways
- A roughly 12-year-dormant wallet sent 20.00010537 BTC to a large custodian and received 20.00006037 BTC back three weeks later, a 4,500-satoshi gap, before the coins were later burned in May.
- Chainalysis identified strong indicators that five wallets shared common ownership and collectively burned 107 BTC in May, worth roughly $8.5 million at the time.
- The five wallets were initially funded on the same day in April 2014 and later routed near-matching dollar-equivalent BTC amounts to the same deposit address at a large centralized exchange or custodian.
- One wallet’s 2022–2024 deposit behavior was sized to dollars, not BTC, sending 19.6 BTC in 60 transfers where 58 of 60 were within 10% of about $10,400 and arrived in clusters.
A $1M BTC “Round Trip” Ends in a Burn
A Bitcoin wallet that had been inactive for almost 12 years moved its entire balance through a large centralized custodian in March, received nearly the same amount back three weeks later, and then burned the coins in May by sending them to an unspendable address.
The headline number is 20 BTC. The detail that matters is the near-1:1 return. The wallet sent 20.00010537 BTC out and received 20.00006037 BTC back, a difference of 4,500 satoshis, or around $3.
That sequence complicates a common trader shortcut: “sent to exchange equals sold.” Here, the coins re-emerged on-chain almost intact before being deliberately destroyed, which makes the custodian hop a weak directional signal on its own.
Bitcoin educator Bennet summarized the pattern bluntly: “The whole balance went out to what looks like an exchange hot wallet, and almost exactly the same amount came back three weeks later. Seven weeks after that, it was burned.”
The On-Chain Trail: Exact Amounts, Timing, and the Three-Day Split
The March movement began after roughly 12 years of dormancy. The wallet sent 20.00010537 BTC to what Bennet described as “a custodian of some kind.” Three weeks later, 20.00006037 BTC returned to the same originating address.
The returned amount did not come back as a single output. It was split across three consecutive-day transactions: 7 BTC, 7 BTC, and 6.00006037 BTC. Bennet interpreted the round-number chunks as consistent with a custodian daily withdrawal limit.
The small difference between what went in and what came back is the tell. Four thousand five hundred satoshis is operational noise in BTC terms. It reads more like fees or handling friction than a trade-sized haircut.
What the chain cannot answer is what happened inside the custodian. The deposit address behavior described in the analysis fits a static customer deposit address that gets swept and consolidated into an omnibus wallet. Once that sweep happens, the public record stops being a clean ledger of intent.
Chainalysis’ Cluster: Five Wallets, One Controller, and Mt. Gox Provenance
The March round trip sits inside a larger pattern: five wallets that ultimately burned Bitcoin in May. Chainalysis assessed the five addresses show “strong indicators of common ownership,” pointing to a single controller rather than unrelated holders coincidentally choosing to destroy coins.
The coordination shows up early. All five wallets were initially funded on the same day in April 2014. Each later sent almost the same dollar-equivalent amount of BTC to the same deposit address at a large centralized exchange or custodian.
Chainalysis traced most of the funds back to Mt. Gox, “suggesting the owner was an early adopter of Bitcoin.” The timing is not clean enough to claim direct withdrawals in April 2014, since Mt. Gox ceased trading in February 2014. Bennet still argued the provenance can fit an early holder who got coins off the venue before the collapse: “It’s entirely possible that the owner of these coins was one of the lucky ones who managed to get their coins off the exchange before it collapsed.”
A separate behavioral clue sits in the 2022–2024 activity. One of the five addresses sent 19.6 BTC to the same custodian in 60 transactions. The BTC sizes varied from about 0.15 BTC to 0.62 BTC, but 58 of 60 transfers were within 10% of approximately $10,400 when sent, despite BTC’s price more than quadrupling over the period. Bennet’s read was direct: “This suggests to me a planned liquidation strategy.” He added that “while payment size was constant,” “frequency was not — these $10k transfers came in clusters,” which can also fit ad hoc cashflow needs rather than a fixed schedule.
Signals Traders Can Take From This Kind of Exchange Flow
The clean narrative traders like is simple. Coins go to an exchange, supply is about to hit the market. This episode is the counterexample. A large custodian deposit preceded a near-identical return, and the eventual outcome was a burn, not an observable distribution.
The first constraint is attribution. Chainalysis confirmed the counterparty was a large centralized exchange, but it does not publicly disclose the names of services it identifies. Without a named venue, traders cannot map the flow to known internal policies, withdrawal limits, or wallet labeling that would tighten interpretation.
The second constraint is omnibus opacity. Bennet described the deposit address as one that does not maintain a balance and is swept into transactions with dozens of other inputs before consolidation into an omnibus wallet. That structure breaks the chain of custody on-chain. The record cannot resolve whether the BTC was sold, held, or transferred elsewhere while inside the custodian.
There are still practical tells worth tracking.
Follow-up clustering that identifies the custodian would change the quality of the signal, because it would let the market compare this behavior to known exchange wallet management patterns. Additional burns from the same wallet cluster would extend the 107 BTC total and keep the “supply removal” narrative alive, even if the absolute size remains small relative to BTC’s broader float.
Renewed activity from other long-dormant wallets with similar Mt. Gox-linked provenance would matter more than the one-off burn, especially if those coins also route through custodians before re-emerging on-chain. And if the ~$10.4k-sized clustered transfer behavior resumes from any of the five wallets, it would suggest the actor is still operational rather than having fully exited.
My Read: The Burn Matters Less Than the Message About Interpreting Custody Hops
The threshold that matters here is not 107 BTC. It is the 4,500-satoshi gap on a 20 BTC round trip. That is small enough to treat the custodian hop as a handling event, not a liquidation event, and it breaks the reflexive “exchange inflow equals sell pressure” read.
If the custodian remains unidentified and the deposit address keeps behaving like a swept, static deposit into an omnibus wallet, this stays a cautionary case study rather than a tradable signal. The practical takeaway is simple: custody hops can be liquidity theater, and the market only learns something when the coins either stay parked, re-emerge in size, or repeat the pattern at scale.
