Warning Indefinite Hold of 18+ ETH by N.exchange via Exodus Swap

[Trêvoid]

Summary of Incident from OP GlebG I am documenting a critical issue involving the Exodus wallet’s integrated swap feature and the service provider N.exchange . My transaction of 18+ ETH (approx. $40,000) has been frozen indefinitely by N.exchange following a swap attempt. Despite being a legitimate miner providing full documentation to satisfy KYC/AML requirements, I am facing a "stonewalling" tactic where the exchange provides no timelines, no justification for the hold, and refuses to cite the legal framework governing their actions.

Incident Details​

Category	Details
Integrator	Exodus Wallet (Swap feature)
Provider	N.exchange
Amount	18+ ETH (~$40,000)
Issue	Indefinite hold of funds post-KYC/AML submission
Support Status	Over 40 emails sent; repetitive, non-substantive replies

---

The Problematic Process​

• The Hand-off: Exodus disclaims responsibility, forcing users to deal directly with the third-party provider (N.exchange) when swaps fail.
• KYC/AML Compliance: I provided all requested documentation—including mining equipment records and proof of wallet access—within 20 minutes of the request.
• Lack of Transparency: N.exchange refuses to disclose why my transaction was flagged, what specific risk indicators were triggered, or when the review might conclude.
• Regulatory Concerns: N.exchange claims a UK registration but lacks authorization from the Financial Conduct Authority (FCA). They refuse to clarify which jurisdiction's laws they are applying to justify the seizure of assets.

Recurring Support Response​

Despite my cooperation, the communication remains automated and unhelpful:

"Thank you for your patience. We understand the importance of this matter and are actively reviewing your case. Unfortunately, at this time, we cannot provide a specific timeline..."

Strategic Assessment​

N.exchange appears to be intentionally delaying the review process. Given the reports from other users of funds being held for up to a year, this behavior suggests a systemic issue rather than a standard compliance delay.

Source (https://bitcointalk.org/index.php?topic=5580229.0)