@Ultegra134Thanks — and yes, multi-language support was overdue. Not every service treats language as a UX feature, but it absolutely is one. If a user has to translate the interface in their head before every action, they're going to make more mistakes and trust the service less. Native language coverage removes that friction entirely.
Also glad the refund change lands well for newer users specifically. That was the main driver — reducing the "grayed-out button with no explanation" barrier for anyone using a swap for the first time.
@bettercryptoGood context on the practical reality — even users comfortable with English often prefer their native language when handling money. Cognitive load is real, and adding "translate everything in my head" on top of a financial transaction is friction that doesn't need to exist. The 6 languages we launched cover a large share of active users; more can follow if demand justifies it.
@wxa7115Really important point and worth spelling out clearly for anyone reading this thread:
If you deposit from a wallet that can send but cannot receive incoming transfers (some custodial exchange addresses work this way), and you leave the refund field empty, and something goes wrong with the swap — the funds can indeed be difficult or impossible to return.The fallback sends coins back to the sender address. If that sender address is a "send-only" custodial address, the recovery path breaks.
For users on self-custody wallets: sender-address fallback works cleanly. No refund address needed.
For users depositing from custodial exchange withdrawal addresses:
providing a refund address is still strongly recommended — just as a safety net for the edge case where something needs to be returned.
We'll add clearer wording on this in the UI itself so users hitting the field understand when leaving it empty is safe versus when it isn't. Thanks for holding us to the honest version — "it's optional" is only accurate when paired with "here's when you should still fill it in."
@PeanutswarThanks for wrapping up the previous contest and launching another one. 🎯 Consistent raffles are one of the reasons this thread stays engaged. Good luck to everyone predicting for August 5.
@AnybodyElseThanks — the refund field was a genuine friction point that trapped new users specifically. Most experienced users never noticed it as a problem because they filled the field instinctively. But onboarding barriers hit hardest exactly the people you're trying to reach for the first time.
On language — noted that your native language isn't yet covered. If more users from the same region ask, it moves up the queue. That's how German, Spanish, French, Polish, and Chinese got prioritized.
@Ultegra134Good suggestion on placement and framing. Positioning the refund field as clearly optional-but-useful (rather than either hidden or prominent) is the right visual balance — signal that it exists, signal that it's not required, signal that it's still there if you want the safety net. Adding to the UI batch.
DEX.fo — No KYC. No AML. No registration