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.
Below is the blockchain data showing each Merlin withdrawal by xxxkeym matched to a BTC payout from those addresses, plus screenshots of the bridge activity.
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.
This is embarrassing incompetence by Indian LE, who seem incapable of reviewing basic blockchain data.
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.
My hot take is VASPs need to challenge weak jurisdictions like India, Canada, etc due to repeated negligence in criminal cases.
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
Merlin Chain bridge
bc1quzwkggdf6ly06mrrnnled0qdr57w770k45n5n7
bc1qtu66zfqxj6pam6e0zunwnggh87f5pjr7vdr5cd
Gate deposit address - xxxkeym
17mpajZ6Nq3dG3T6wUhaXxYF4Qy9HJnYx5
Other addresses - xxxkeym
3NcBhqKnyo8dfzqfG1p5rbaKJFV8yLnx3u
bc1pkkwqyxn3rm608ryuqg9hyqna0syq4jx5pxkr7pzg8n3usx6tyqfst5u966
0x59fd8E3aEca4FAbb53ef6078D2319Dc174fb66a6
July 15, 2025 BTC theft addresses
bc1qjmf2e4fc2r97rq762055ag3g9uhypavta0payq
bc1q80gq7ctfsm6p9h9jh2k45da87jy6s7a87pj3h0
March 28, 2024 50 M-BTC destination transaction to xxxkeym
0xf1ee67ba1d3f97fb2d4776fa8ffc90f0b7ba7d116de3bf510a2c6aeae7d80def
Syv 🪐 retweeted
THE BLOCK: Ethereum Foundation researcher Justin Drake is urging the crypto industry to begin planning for "bunker mode," recommending a controlled migration of assets to fresh addresses that have never signed a transaction, keeping their public keys hidden behind a hash.
Drake said it is now reasonable to prepare for the possibility that AI could enable fast recovery of private keys from ECDSA public keys, potentially within "months not years."
"Don't rush," Drake said, warning that a disorderly migration could cause more harm than good.
Syv 🪐 retweeted
Blockchain needs infrastructure where privacy, identity, and compliance can coexist.
That’s what Midnight is building.
Syv 🪐 retweeted
Good news on the coming Midnight release & follow-up composability upgrade 👀
As known, the v8 release enables private contracts, with composability (v9) coming after
Thanks to our great audit partners, it look like the composability upgrade (v9) will be also be this year!
🚨SOLIDITY-AUDITOR V4 IS NOW OPEN SOURCE (MIT LICENSE)
A single command now gets up to 85% recall on High severity findings from multi-week contests from last year. This used to cost protocols tens of thousands - we made it FREE, so any dev can build more safely. by PAG team🫡
Syv 🪐 retweeted
ZCode is now open source, and the reported security issues have been addressed.
github.com/zai-org/ZCode
We take the community’s feedback very seriously and apologize for the concern and frustration these issues have caused. We have been working closely with the ZCode team to investigate and remediate the issues raised.
Independent security reviews by third-party firms are now underway. We will share the findings and provide further updates as they become available.
We sincerely appreciate the developer community’s feedback and continued scrutiny. We will continue to monitor the review process closely and provide updates.
In response to the ZCode product security issues reported by the community, we have completed the necessary remediation and sincerely apologize to all our users.
We have open-sourced ZCode at github.com/zai-org/ZCode, placing the code under community scrutiny and making ZCode more open and transparent.
We sincerely thank the community developers who previously identified issues in ZCode. Going forward, we will establish an ongoing product security vulnerability reporting and response process. We welcome developers to continue reviewing ZCode and reporting potential issues, and we will provide rewards based on the severity of the issues reported.
With respect to the code data referenced by the community, we confirm that no such data is retained and that it has never been used for model training.
Following the remediation, we invited the China Academy of Information and Communications Technology (CAICT) and NSFOCUS to conduct security assessments. The results are as follows:
Through its technical assessment, CAICT confirmed that the zcode-prod Alibaba Cloud OSS bucket is in a zero-data state. Security remediation has been completed in the ZCode v3.14.0 client. The Repo Wiki feature has been removed, and the workflow for generating and uploading local repository snapshots has been disabled.
NSFOCUS confirmed that all data objects in the zcode-prod Alibaba Cloud OSS bucket, as well as the bucket itself, have been deleted. Remediation has been completed in the ZCode v3.14.0 client. The Repo Wiki entry point and the associated generation workflow have been removed, and no functional path capable of triggering the generation of local repository snapshots or transmitting local files externally was identified.
Once again, we sincerely apologize and welcome continued scrutiny from the community. The full security assessment report will be released soon.
Hey @Zai_org , why does ZCode silently pack entire workspaces + full .git history and upload to Aliyun OSS on login?
- Server holds the only decryption key
- No UI toggle to disable
- Zero disclosure in privacy policy
Full forensics & fix:
blog.ferstar.org/en/posts/zc…
Syv 🪐 retweeted
BREAKING: Michael Burry says OpenAI and Anthropic's AI safety warnings are fake hype to cover for slowing growth ahead of their IPOs.
"we are so awesome it could become dangerous"
Syv 🪐 retweeted
Prudent institutional investors should only consider trusting a crypto-asset network after it has operated reliably for at least ten years without a hard fork. #Bitcoin
Syv 🪐 retweeted
JUST IN: Kimi AI temporarily pauses new subscriptions after demand for Kimi K3 pushes its computing capacity near its limits.
Syv 🪐 retweeted
The Argentine peso has lost 99.66% of its value against the dollar since 2013.
$10,000 in 2013 pesos is worth $34 today.
Syv 🪐 retweeted
Replying to @halas_dev_
@halas_dev_ forked solidity-auditor V3 and tweaked it for Move. If this isn't the power of open-source, idk what is👏
Syv 🪐 retweeted
Privacy is no longer enough.
Enterprises, institutions, and governments need confidential smart contracts, confidential state, selective disclosure, and compliance-ready infrastructure.
All on a blockchain built to scale.
That’s Midnight.
Syv 🪐 retweeted
hackathons are underrated as a learning tool.
blogs and announcements show the happy path. building something with the tech in 48 hours shows the rough edges, the parts docs don't cover. that's where the real understanding is.
the fastest way to learn a tool is still to ship something small with it.





































