@examplensYou're pushing us toward a more precise position, and honestly you're right to. Let us clarify the mechanics — because the refund story we described earlier deserves more detail so nobody gets misled.
Here's how Chain mode actually works:
User creates an order and sends coins to our address (not to the third-party pool directly)
We route the swap through a vetted pool
Coins from the pool arrive at the user's destination address
The pool never has direct custody of the user's original deposit. We do the routing. So if a pool refuses to execute for any reason —
we still hold the user's original funds and send them back to the refund address. We don't freeze, hold, or block user funds under any circumstances. The user is not in a position where their coins are "stuck" and require KYC to release.
That's the design intent, and it's what makes the refund mechanism actually work as promised.
Where you're right to push us:
we should say this clearly on the site. "We handle the refund from our side, not the pool's side, and we never block funds" is meaningfully different from "the refund mechanism kicks in" — and users deserve the precise version. We'll update the FAQ to spell out the routing mechanics so nobody has to guess.
Thanks for holding us to the precise answer.
@joniboiniYou captured the right question — and yes, we should be proactive about explaining this. "We'll return your coins" as a reactive line does sound like a walkback, but it's actually the design principle from day one:
we don't block, freeze, or hold user funds. Ever. Making that explicit on the site avoids the "vague promise" perception. Point taken.
@TryNinjaFair concern, and worth addressing directly.
In our routing model, the user's original deposit stays under our control until the swap completes. So the "escrow dispute" scenario you're describing doesn't apply the same way — the user never handed their original coins to the third-party pool. If routing fails,
we refund from our custody. We never block, freeze, or withhold funds — no conditions, no KYC required to release, ever.The one thing we can't control is what happens on the destination side after coins are sent. If a user provides an address that gets flagged downstream (their own CEX freezing it, for example), that's between the user and their receiving service. But that's true of every crypto transaction, not something specific to Chain mode.
No escrow needed. No user-to-pool disputes. No blocking on our side. That's the point.
DEX.fo — No KYC. No AML. No registration.