A curious, though sad for one of its users, story has unfolded on the Bitcointalk forum. A user with the nickname XLXer reported that the crypto exchanger GhostSwap blocked his funds amounting to 20.5 ETH (Exchange ID: r6gfns7qebjs43e4).

According to XLXer, on May 24, 2026, he transferred about 88.9 ETH through the bridge aggregator Jumper.xyz to his new addresses and made four consecutive exchanges on GhostSwap. The irony, in his opinion, is that three of the four transactions went through successfully, and only the third one was blocked. The author rightly notes: if the source had been "dirty" the AML system would have triggered on all four transactions, and if it had been clean — on none of them. Such selective blocking looks more like a deliberate seizure of funds than a legitimate check.

In the comments, users quickly rubbed the author's nose in his main mistake — the lack of proper due diligence on the service. According to user Slow death, if the author had googled reviews, he would have found plenty of complaints about GhostSwap. User mabji1 was even more categorical, stating that "HitBTC = GhostSwap".

The situation was clarified by an experienced forum member. According to user examplens, sending multiple transactions from a single source often raises suspicion with AML systems. He even linked the author's addresses to Tornado Cash, although XLXer himself stated that he had never used Tornado Cash.

The very essence of the problem was revealed thanks to users FinneysTrueVision and examplens. As it turned out, GhostSwap is not fully independent — it uses the centralized exchange HitBTC as its liquidity provider. According to user examplens, GhostSwap has several accounts on HitBTC registered under straw men. When funds on one of the accounts get blocked upon receiving the third transaction, the service simply switches to the next account to process the fourth. That's exactly why the blocking looks "selective".

Because of this dependence on a centralized exchange, as user XLXer notes, GhostSwap was forced to change its slogan from "NO KYC" to "Privacy-Focused Crypto Swaps". Their partner OrangeFren, for its part, added a warning to its website that GhostSwap may request KYC, openly acknowledging the problem.

The author of the post now doubts whether to go through verification, as he had hoped to resolve the conflict amicably. This story is an excellent reminder: services promising privacy without KYC often actually depend on large centralized exchanges that can freeze your money at any moment. Always check the reputation of a platform and test it with small amounts before trusting it with large capital.

Update from November 1, 2026: what's known since the post went up

Sept 17 — user OrangeFren replied in the thread to the case author's complaint about getting no response, and showed that some of the emails never actually arrived: the message included a bounce report from the mail.w14.tutanota.de server with a "554 general failure" error, with the recipient address redacted. The case author replied that the email is working now and the message can be resent, and attached screenshots of the last email from GhostSwap (dated Sept 14) and his own reply from the same day.

Sept 18 — user JollyGood ballparked 20.5 ETH at roughly $53,000 (at $2,580 per ETH), and said that since the funds were frozen by the liquidity provider, going through KYC is probably unavoidable anyway — but even that doesn't rule out a refusal.

Sept 24 — the case author noted that GhostSwap still hadn't written to him, even though OrangeFren had asked the exchange to send at least one message.

Sept 28 — he pointed out it'd been two weeks since the last reply, and OrangeFren's appeal had gone unanswered.

Oct 1 — examplens wrote that GhostSwap is still listed on OrangeFren with an orange warning pointing to the thread, and that he's the one who left the review on KYCnot.me instead of the case author.

Oct 3 — examplens listed the platforms worth reaching out to: Reddit (where, per him, a similar 12.5 ETH case had already been posted); Monerica (where GhostSwap is, per his claim, a sponsor, and where the service is tagged unverified until a resolution is confirmed); and other directories. He also noted the exchanger had been pouring money into PR marketing — there are reviews on big portals, but with comments turned off. The same day, a WeLiveCrypto rep chimed in in the thread: after reviewing the post, they're going to tag the service as a potential-risk project, but at that point the catalog site had script glitches, so the update got pushed back.

Oct 8 — the case author said that, per OrangeFren, GhostSwap is replying to them — but for him, nothing has changed. When he went through support on the site, they asked for the transaction ID, and once he sent it, communication broke off again.

Oct 15 — he reported that GhostSwap had asked OrangeFren to take down the warning about his case, and OrangeFren refused, saying the warning matters for users regardless of whether the case author is their client. In the same message, the author asked about other platforms for complaints and noted that his attempt to post on Reddit flopped because his account was too new. JollyGood replied that he can't really help on regulators, but thinks OrangeFren did the right thing keeping the warning up.

Oct 22 — user decodx bumped the thread and asked whether the email mess had hit GhostSwap too. The case author replied that email is fine, but the exchanger hasn't been answering for over a month — neither by email nor on SimpleX, where their last message was also more than a month ago. He also pointed out that the service's homepage now sports a banner reading "Anonymous No KYC Crypto Exchange for 1,600+ Coins" and noted that he himself has used OrangeFren plenty of times over the past month, but believes keeping GhostSwap in the listing until the matter is resolved is a risk to users.

Oct 29 — the case author wrote that the silence has now dragged on for over a month and a half, and that GhostSwap filed a complaint against his review on Trustpilot. The same day, user albon asked how a service calling itself NO-KYC can operate through a third-party liquidity provider with KYC, said GhostSwap should have disclosed this scheme upfront, and that responsibility for communicating with the client lies squarely on them; he also advised splitting exchanges into smaller amounts. The case author replied that all four exchanges came from the same source, and only the third one got blocked.

Monitoring data as of November 1, 2026

KYCnot.me: Incident opened Sept 16, 2026, medium severity, −12 to the trust score. The description says the arrival of funds at the HitBTC address is confirmed, and the incident will stay open until the 20.5 ETH is returned or a return agreement is reached. The card's KYC policy is marked "Shotgun KYC", level 3 out of 4 — verification can be requested or funds frozen at any stage; card status is "community contributed" meaning it hasn't been verified by the catalog team; overall score is 3/10, with Privacy 31 and Trust 34; reviews are mixed. There's also a mention of a previous 12.4 ETH case that was closed by a return in Monero from escrow on OrangeFren.

Monerica: Card updated Oct 2, 2026; status at check time — verified; KYC policy — Shotgun KYC; liquidity — third party. Two deposit guarantees are declared, totaling 40K USD: 35K via orangefren and 5K via kycnone. The official catalog test is dated June 15, 2026, rating 4.3 across 12 ratings. In the review dated Oct 3, submitted on behalf of the case author, the amount 20.5 ETH is listed, ID r6gfns7qebjs43e4, the Bitcointalk thread number, and a request to tag the service as unverified until the matter is resolved. In the reply, the Monerica moderator noted that the case is dated the same day as a previously settled case involving the same asset, that the review was submitted under a different PGP key, and that after the previous case GhostSwap's sponsorship was pulled and then restored; per him, the catalog isn't ready to back them again, and the card now explicitly flags the service as using third-party liquidity and possible KYC.