ZachXBT Challenges $3M Gate Freeze Over Alleged Merlin Bridge Tracing Error in India
Key Takeaways
- •ZachXBT claims Indian authorities froze a Chinese investor's Gate account, which held about $3 million at the time, after mislabeling Merlin Chain bridge addresses as wallets linked to a pig-butchering scam.
- •The underlying case involves an alleged $1.7 million loss in BTC, USDT, DOGE and SOL in May 2025, registered by Andhra Pradesh CID as Cr. No. 10/2025 with a charge sheet filed in March 2026.
- •According to ZachXBT, the investor bridged 50 BTC into Merlin in March 2024, more than a year before the alleged theft, and he found no on-chain connections between the user and the fraud.
- •ZachXBT said an Indian court directed Gate to transfer the frozen funds, now valued near $1.5 million, to the complainant, while Gate states that no assets have been handed over.
- •Gate says the transaction path provided by Indian police traces differently from ZachXBT's published analysis and is seeking authorization to share additional evidence while supporting the user's formal defense with local counsel.

On-chain investigator ZachXBT has challenged the blockchain tracing used to freeze a Chinese investor's Gate account, arguing that Indian authorities misidentified addresses belonging to the Merlin Chain bridge as wallets linked to a pig-butchering scam — a fraud in which perpetrators cultivate trust with victims over time before persuading them to transfer funds.
The account has reportedly been restricted for nearly 16 months. ZachXBT said it held approximately $3 million when it was frozen and would be worth about $1.5 million at current valuations. He also claimed that an Indian court ordered Gate to transfer the funds to the complainant in the underlying case.
Gate said, however, that no assets have been handed over and that the transaction path provided by Indian police differs from the one described by ZachXBT. The exchange said it is seeking authorization to share additional evidence with ZachXBT and the affected user.
ZachXBT's account of the case
The case concerns a pig-butchering victim who allegedly lost $1.7 million in BTC, USDT, DOGE and SOL in May 2025. Andhra Pradesh CID registered the matter as Cr. No. 10/2025 and filed a charge sheet in March 2026.
According to ZachXBT, Indian law enforcement froze the Gate deposit address 17mpajZ6Nq3dG3T6wUhaXxYF4Qy9HJnYx5 in July 2025 after the user deposited 15 BTC from 3NcBhqKnyo8dfzqfG1p5rbaKJFV8yLnx3u in transaction 885f3afab562251b222363cf12095e864ddb94636674b01f0cdb05997e5a54a0. ZachXBT said that transaction was cited by Indian law enforcement in its notice.
He said the 3NcBhqK address had been funded by the investor's own withdrawals from OKX and Binance in January 2023, and that the BTC remained dormant for years before being deposited at Gate. Indian authorities did not freeze the investor's OKX or Binance accounts, which ZachXBT identified as the original sources of the 15 BTC.
ZachXBT said Gate froze the investor's entire account, which contained roughly $3 million at the time and about $1.5 million at the time of his post. He claimed that the Indian court order directed all of the funds to the complainant.
The Gate deposit address also received two deposits totaling 15 BTC in 2025 from bc1pkkwqyxn3rm608ryuqg9hyqna0syq4jx5pxkr7pzg8n3usx6tyqfst5u966, another address ZachXBT said was controlled by the investor. Shortly before those deposits, the address was funded in three transactions by bc1quzwkggdf6ly06mrrnnled0qdr57w770k45n5n7 and bc1qtu66zfqxj6pam6e0zunwnggh87f5pjr7vdr5cd.
Those two addresses had been reported as alibarbit[.]bit, the same scam named in an Indian law enforcement press release. ZachXBT said that identification was incorrect because both addresses belonged to the Merlin Chain bridge, which he said is unlabeled in many compliance tools. He described xxxkeym as a regular Merlin user trading tokens on the Bitcoin layer-2 network and said the incorrect label was the only link between the user's transaction history and the alleged scam. The mechanism is structural: bridges hold user funds in shared, bridge-controlled addresses, so transactions from many unrelated users route through the same on-chain points, and screening tools assess funds moving through that infrastructure by the label attached to it.
ZachXBT published the following statement on X on November 17, 2026: ZachXBT's post
Indian law enforcement froze $3M from an innocent Chinese investor after mistaking a crypto bridge for a pig butchering scam. Now an Indian court has ordered Gate to hand his funds to a person they never belonged to. My analysis of how Indian LE traced through an unlabeled service and wrongly froze @xxxkeym's Gate account:
The case stems from a pig butchering victim who allegedly lost $1.7M of BTC, USDT, DOGE & SOL in May 2025. Andhra Pradesh CID registered it as Cr. No. 10/2025 and filed a charge sheet in March 2026.
In July 2025, xxxkeym had Gate deposit address 17mpajZ6Nq3dG3T6wUhaXxYF4Qy9HJnYx5 frozen after depositing 15 BTC from 3NcBhqK in the following transaction: 885f3afab562251b222363cf12095e864ddb94636674b01f0cdb05997e5a54a0
This is one transaction Indian LE cites in its notice. 3NcBhqK was funded by xxxkeym's own OKX & Binance withdrawals in Jan 2023 and the coins sat dormant for years until the Gate deposit. Indian LE never froze his OKX or Binance accounts, the actual source of the 15 BTC, which tells you how flawed their justification is.
Gate froze his entire account, which held roughly $3M at the time and about $1.5M today. The Indian court order hands all of it to the complainant.
Gate deposit address 17mpajZ also received two deposits for 15 BTC total in 2025 from bc1pkkwqyxn3rm608ryuqg9hyqna0syq4jx5pxkr7pzg8n3usx6tyqfst5u966, which is also controlled by xxxkeym. Shortly before the deposits to Gate, bc1pkkw was funded in three transactions by bc1quzwkggdf6ly06mrrnnled0qdr57w770k45n5n7 & bc1qtu66zfqxj6pam6e0zunwnggh87f5pjr7vdr5cd.
bc1quzw & bc1qtu66z were reported as alibarbit[.]bit, the same scam named in Indian LE's press release. That was a mistake. Both belong to the Merlin Chain bridge, which is unlabeled in most compliance tools. xxxkeym is simply a normal Merlin user trading tokens on the L2. This wrong label is the only place the scam touches his transaction history.
xxxkeym bridged 50 BTC into Merlin on March 28, 2024, over a year before the alleged May 2025 theft. His three withdrawals came out of that balance. I found zero onchain connections between xxxkeym and the theft.
Separately on July 15, 2025 xxxkeym had a 7 BTC private key compromise theft which was reported to local police and also SlowMist was engaged. His stolen funds flowed to Wasabi.
Indian LE, the prosecutor and the judge all signed off on this, Gate froze the account, and LE did a full press release about it recently, while the real victim here (the Gate user) hasn't had access to his funds for nearly 16 months.
Merlin transaction history
ZachXBT said the investor bridged 50 BTC into Merlin on March 28, 2024, more than a year before the alleged May 2025 theft. He identified three Merlin withdrawals and corresponding Bitcoin destinations:
Merlin source transactions from xxxkeym
- 10.1368 BTC — March 25, 2025 — 0x975081c2a62355019561c3ec0d01c72bf0dadf7121d46764bbb13ac0013a9a06
- 4.9071 BTC — May 6, 2025 — 0xa30f7b770e2e8e2e2d0fc0d390aa800e7f880e8e129d1b705dbc4167fc878769
- 9.9796 BTC — June 17, 2025 — 0x147429d324520c9ebee8015b0214dbd7bdce97ee37ad25e11819f4b04aecc049
Bitcoin destination transactions to xxxkeym
- 10.1367 BTC — March 28, 2025 — 55ab5373c2daa69b1728e6551b59f9dc661d1d78786face798d5251ccbe4685a
- 4.907 BTC — May 9, 2025 — b2222fe38856e65420f15051a4cc419a92868803dec69a218f007948972ea367
- 9.9795 BTC — June 19, 2025 — 094f01388638523fb29aac0a0d4f70adf6949fede0847a45cef2c3f930692c73
ZachXBT listed the following Merlin Chain bridge addresses:
- bc1quzwkggdf6ly06mrrnnled0qdr57w770k45n5n7
- bc1qtu66zfqxj6pam6e0zunwnggh87f5pjr7vdr5cd
He identified the Gate deposit address as 17mpajZ6Nq3dG3T6wUhaXxYF4Qy9HJnYx5 and listed the following other addresses associated with xxxkeym:
- 3NcBhqKnyo8dfzqfG1p5rbaKJFV8yLnx3u
- bc1pkkwqyxn3rm608ryuqg9hyqna0syq4jx5pxkr7pzg8n3usx6tyqfst5u966
- 0x59fd8E3aEca4FAbb53ef6078D2319Dc174fb66a6
The BTC theft addresses identified in the post were bc1qjmf2e4fc2r97rq762055ag3g9uhypavta0payq and bc1q80gq7ctfsm6p9h9jh2k45da87jy6s7a87pj3h0. ZachXBT also listed the March 28, 2024 transaction representing 50 M-BTC sent to xxxkeym: 0xf1ee67ba1d3f97fb2d4776fa8ffc90f0b7ba7d116de3bf510a2c6aeae7d80def.
He separately said that xxxkeym suffered a 7 BTC theft caused by a private-key compromise on July 15, 2025. The incident was reported to local police, SlowMist was engaged, and the stolen funds flowed to Wasabi.
Gate disputes the reported fund flow
Gate said it had reviewed ZachXBT's claims and found that the route provided by Indian police did not match the route described in the investigator's post. The exchange said it could not publish the records without authorization and was seeking permission from authorities to share further evidence with ZachXBT and the affected user.
Gate published its response on X on November 17, 2026: Gate's statement
Thank you @zachxbt for the time and care you put into this, and for reaching out to us. We're on the same side here and we all want this resolved accurately and fairly. From the start, our priority has been our user. When the request came in, we asked the Indian police for more evidence rather than moving any assets, and no assets have been handed over. After internal review, it seems like the materials the police shared with us trace a different path from the one in your post, and unfortuantely we can't share those details publicly without authorization. We're already in active conversation with the police to get their consent to share more evidence with you and our user, so the facts can be clarified first. If what different parties received doesn't line up, we want to understand that too. We welcome and appreciate you joining us in looking into this. The court has also already issued an order in this case. As a platform, we have to respect valid court orders, so the most important thing now is helping our user move into the formal defense process as quickly as possible. That is the fastest way to a real resolution, and we're working with local counsel to support it.
Gate emphasized that none of its assets had been transferred. It acknowledged that a court order had been issued and said the exchange must respect valid court orders while helping the user enter the formal defense process with the assistance of local counsel.
The dispute highlights the role of address labels in exchange compliance systems and law enforcement investigations, which routinely screen transactions against shared address-labeling databases to assess exposure to illicit funds. ZachXBT argued that incomplete or incorrect labels for bridge infrastructure can cause legitimate transactions to appear connected to illicit activity. Gate's statement indicates that the company's internal review is based on a different fund flow from the one presented publicly by ZachXBT.
The facts remain disputed, and Gate said it is working with Indian authorities to obtain permission to release further records. The affected user has not had access to the account for nearly 16 months, according to ZachXBT. The next developments to watch are whether Indian authorities authorize the release of the records Gate says trace a different path, and how the user's formal defense process, which Gate is supporting through local counsel, engages the court order already issued.
Source: CryptoNinjas