♻️ DEX.fo — Auto Crypto Exchange 💚 NO KYC/AML 💚 Escrow 1 BTC

[examplens]

You are not the first to notice this, and the "infinite loading" look seems to be confusing. I assume that a better solution is to disable the selection of pairs that cannot be swapped on this exchange.
They may be planned to be added, but until then, there is no need to see them in the interface.

XMR works....but not all the time  , for example, now it does, but I did stumble upon situations where it's not available.
It would make no sense to remove it when they see it doesn't work when it's anyhow sort of deactivated, since it doesn't load with the options, I suspect it has something to do with their pools or something since they are actively searching for "fine tunning".

Removing the pair completely from the menu might make some new users think XMR is not available at all and lose them as clients forever.
Not the ideal pair of choices one would want to pick but, until it's fixed, this is what we have.

It is quite normal for a new service to have gaps in the sufficient liquidity of a coin. I assume that over time the dex.fo team will recognise the pattern when it happens and react in a shorter time frame and thus reduce situations where they do not have the opportunity to deliver a swap pair.
I don't think they should completely exclude a coin if it is currently unavailable, but they can disable its selection with info on why they don't currently accept a certain pair.

[Peanutswar]

~
🔓 Refund address is no longer mandatory — by popular demand from the community. Fill it in if you want a safety net. Leave it empty if you don't. Your call.

Though this is my struggle before because this mandate the refund address before committing a transaction its quite give confusion to other users too why having another address below in the deposit address.

Now its good to have a (optional)

wait @DEX.fo_off did you remove guys the percentage of the transaction in Chain or Fast?

I guess it has a factor for the new comers of your platform to have an idea regarding with the fees.

[SamReomo]

Longevity matters the most. Once you become a brand in the industry, then it won't become a regret later, and many will regret why they did not go for longevity. Because with increasing adoption, instant exchanges will become the main hub for many people who want some privacy and don't want to give their KYC to any exchange.

Yes, that's why I call such exchanges as blessing for crypto users because they can use those exchanges from any part of the world and there's no one going to question them for the swaps. Especially people from those countries can use such exchanges where most regulated exchanges can't work and in such times people from those places can use instant exchanges. A user doesn't have to fear for KYC at no KYC exchanges and that means such users can use Tor or VPN without any issue to further increase their privacy.

[hosemary]

By the way, dex.fo team, I know it has been said before about the the refund address being mandatory but if you can't make it optional, then change the comment written on it. Right now it says, "If you don't specify an address, the refund will be made to the sender's address." while we can't even proceed until we specify the address.

They have already made providing a refund address optional, and that's why you see that statement about the case where a user doesn't provide a refund address.
Just leave the refund address field empty, if you don't want to provide a refund address.

[hosemary]

DEX.fo_off, it's really strange how you keep tagging the wrong users.
You tagged me and responded as if I had suggested adding Arabic language, even though I never made such a suggestion.

You even tagged users who have never posted in this thread.
pooya87, xtraelv and Kryptowerk haven't made a single post in this thread, but they were all tagged by you.

[Pmalek]

@bitmover

Exactly right — the CEX withdrawal scenario is the one situation where the refund field genuinely matters. Most experienced users like yourself know to fill it in for exactly that case. Making it optional was the right call for the majority, but the safety net stays available for the edge cases where it counts.

Maybe you can emphasize this further in the text written under "Refund address." Add another sentence where you highly recommend that users depositing from a custodial service double check the refund address and even enter one belonging to a wallet they control or enter an address copied directly from their exchange account.

You should also consider a new entry under Q&A, explaining the best way to deposit from CEXs and custodial platforms with a return address entered.

[Kryptowerk]

@Peanutswar

Thanks for wrapping up the previous contest and launching the next one. 🎯 Consistent activity is what keeps the thread alive.


@bitmover

Exactly right — the CEX withdrawal scenario is the one situation where the refund field genuinely matters. Most experienced users like yourself know to fill it in for exactly that case. Making it optional was the right call for the majority, but the safety net stays available for the edge cases where it counts.


@AmnesiaHaze

Thanks for the test report. Quick clarification though — USDT (BEP20) isn't currently on our supported list. Our current USDT support is ERC-20 and TRC-20 only. If your swap went through a bridge or router that converted BEP20 to a supported network on the way in, that would explain the experience — but that's third-party handling, not our native support.

BEP20 support is on the roadmap along with the broader BSC/BNB integration coming after Solana. When it's live, you'll see it directly in the selector.

Could you double-check which network you used? Want to make sure there's no confusion about supported assets.


@GreatArkansas

Sorry to hear about the delay. Please reach out via SimpleX support directly with your Order ID (8f3xzz001) — the support team can look at the specific order and see what's holding it. Public thread isn't the fastest channel for individual case resolution.

If for some reason you can't reach SimpleX support, let us know and we'll help route it. We don't want any user stuck without a resolution.


@hosemary

Both suggestions are solid.

On Arabic — the Middle East interest in crypto (especially UAE and Saudi retail flows) is real and growing, and coverage there would be meaningful. Adding it to the language priority queue.

On the FAQ page needing an update to reflect recent changes and adding a "recent changes" section — 100% agreed, that's on the near-term list. The refund address update alone requires FAQ correction (as noted earlier by another user), and grouping recent changes helps returning users catch up without re-reading everything.


@MarryWithBTC

Compact FAQ in the OP itself — that's the natural next step. This thread has generated more actual useful Q&A content than any FAQ we could write from scratch. Distilling it into a proper OP section is a much better source than starting from zero.

On Portuguese — good addition to the list. Brazilian no-KYC demand is significant and growing, and Portuguese also covers a broader Portuguese-speaking market (Portugal, Angola, Mozambique). Noted alongside Arabic.


@Ultegra134

Thanks — noting the effort on the German translation means a lot. We deliberately went with human translators rather than machine output for exactly the reason you mentioned. Non-native quality shows immediately in a financial interface and undermines trust in a way no cost-saving justifies.


@xtraelv

Welcome to the thread and appreciate the observation. Consistent engagement with the forum after the initial launch is one of the things we specifically decided to prioritize — because you're right, "post, disappear, occasionally reappear" is unfortunately the norm in this space.

On the FAQ — you and others are pointing at the same real problem. New users shouldn't need to trawl through 20 pages to find answers already given. That's on us to consolidate. Working on it.


@Kryptowerk

Fair — SimpleX setup is one of those things that's simple once you know how, but opaque if you're seeing it for the first time. A short "how to reach our support in 3 steps" guide (with the SimpleX link, how to open it, and what to expect) would help new users considerably. Adding to the near-term content list.


@pooya87

That's a clean solution — one contextual warning line handles the CEX edge case without pushing extra friction on users depositing from self-custody. We'll implement that as part of the refund field UI update we're preparing:

"If depositing from a centralized exchange (Binance, Coinbase, etc.), we strongly recommend providing a refund address."

Simple. Direct. Solves the actual problem. Thanks for the practical framing.


DEX.fo — No KYC. No AML. No registration.

wtf, why are you tagging me? I have a suspicion and it doesn't look good for a "No KYC" exchange. (NO, I never used their service and most likely never will)

Explain yourself, and better without AI written bullshit.
I have my hand on the trigger for negative trust here.
Good luck.

[MarryWithBTC]

DEX.fo_off, it's really strange how you keep tagging the wrong users.
You tagged me and responded as if I had suggested adding Arabic language, even though I never made such a suggestion.

You even tagged users who have never posted in this thread.
pooya87, xtraelv and Kryptowerk haven't made a single post in this thread, but they were all tagged by you.

when he started, he was tagging accurately and was responding to every suggestions, it was cool to be honest.

But recently, I discovered I have been tagged twice to posts or suggestions i didn't make. My last post here was in response to Loyce's review and not about FAQs.

DEX.fo, I'll appreciate if you reverse to what you have been doing before now, or simply not respond to everyone that writes in your thread. Reply only when necessary and this will reduce your workload and make you respond naturally.

[icopress]

wtf, why are you tagging me? I have a suspicion and it doesn't look good for a "No KYC" exchange. (NO, I never used their service and most likely never will)

Explain yourself, and better without AI written bullshit.
I have my hand on the trigger for negative trust here.
Good luck.

Thanks for the comment. I'll talk to Dex about this today.

[DEX.fo_off]

Real quick, separate from everything above — a straight explanation, no spin.

Over the last couple of weeks, replying to a lot of people in a single post led to names getting crossed. A few of you got quoted or thanked for suggestions you never actually made, and a few — Kryptowerk, pooya87, xtraelv — got tagged despite never having posted in this thread at all. Ultegra134 and hosemary flagged the same thing earlier too.

That's on us, not on any of you. It happened because whoever was drafting these batch replies was going through a lot of messages at once and mixed up who said what. Human error — someone moving too fast through a long thread and pairing the wrong name to the wrong point. Not any kind of automated system doing this on its own.

Kryptowerk — understand the reaction completely. Getting tagged out of nowhere by a "No KYC" service, with no context, is a legitimate reason to be suspicious. There's nothing else behind it — no data pull, no targeting, just a mistake in how the replies were put together. Sorry for the confusion.

pooya87, xtraelv — same apology. You didn't say what was attributed to you, that's on us.

Going forward we're dropping the habit of tagging specific names in batch replies — clearly error-prone once there's more than a couple of people to respond to in one post. Replies from here address topics without pinning them to individuals.

Thanks for calling it out plainly. Better to hear it straight than have it fester.


DEX.fo — No KYC. No AML. No registration.

[LoyceV]

someone moving too fast through a long thread and pairing the wrong name to the wrong point.
~
Going forward we're dropping the habit of tagging specific names in batch replies

May I suggest to just quote a small relevant part of each post? That makes it clear who you're replying to, and you can't really go wrong if you copy/paste the complete quote (but don't make the quote too large).

[TokenTikas]

I'm trying to use the Dex.Fo exchange but it's showing this. My internet is working fine and I also tried refreshing but I can't click to go to the next step for the exchange. Has anyone used the Dex.Fo exchange today? Is anyone else facing this problem? I'm entering everything correctly, but I still can't move to the next step in any way.

[hosemary]

I'm trying to use the Dex.Fo exchange but it's showing this. My internet is working fine and I also tried refreshing but I can't click to go to the next step for the exchange. Has anyone used the Dex.Fo exchange today? Is anyone else facing this problem? I'm entering everything correctly, but I still can't move to the next step in any way.

Unless you were trying to swap Monero, the issue is probably on your end. I just tried it and I was able to place a swap order without any issues.
Try again with a VPN or a different browser and see if it works.

[TokenTikas]

Try again with a VPN or a different browser and see if it works.

Yes, Dex.Fo working now. I was trying for a long time but I couldn't get to the next step, so came to the last step and asked here if anyone is having this problem. I tried using VPN but it still didn't work but later I closed everything on the computer and opened it again and tried without VPN, now it's processing without any problems. Thanks for your quicks response and for your suggestion.

[DEX.fo_off]

May I suggest to just quote a small relevant part of each post? That makes it clear who you're replying to, and you can't really go wrong if you copy/paste the complete quote (but don't make the quote too large).

Good suggestion, and honestly overdue given the mess we made with tags. Switching to this from here — a short quote of the actual line being answered instead of a name tag. Removes the ambiguity completely, since the quote itself shows who said what.

Try again with a VPN or a different browser and see if it works.

Thanks for jumping in on this one before we even saw it — good call, and turned out to be a stuck session rather than anything on our end. Appreciate you helping TokenTikas get sorted.


DEX.fo — No KYC. No AML. No registration.

[FP91G]

I'm trying to use the Dex.Fo exchange but it's showing this. My internet is working fine and I also tried refreshing but I can't click to go to the next step for the exchange. Has anyone used the Dex.Fo exchange today? Is anyone else facing this problem? I'm entering everything correctly, but I still can't move to the next step in any way.

Unless you were trying to swap Monero, the issue is probably on your end. I just tried it and I was able to place a swap order without any issues.
Try again with a VPN or a different browser and see if it works.

Dex.Fo doesn't work in Google Browser via a separate VPN, but after launching a second free browser-based VPN, the site opens.
Try Windscribe, a free VPN, it might be better.

[Pmalek]

Dex.Fo doesn't work in Google Browser via a separate VPN, but after launching a second free browser-based VPN, the site opens.
Try Windscribe, a free VPN, it might be better.

Why do you say that? It seems to be working just fine. I just initiated a test swap (without depositing) using Google Chrome and my VPN turned on. Everything seems ok. It would be weird that no-KYC and anonymous swap platform doesn't allow you to use VPNs. It works via Tor also, a system even more privacy-focused than VPNs.

[DEX.fo_off]

Dex.Fo doesn't work in Google Browser via a separate VPN, but after launching a second free browser-based VPN, the site opens.

Thanks for reporting this — that's not expected behavior, and we don't block or filter VPN traffic on our end (no-KYC service, VPN and Tor use are normal and expected from our side, including our own Tor mirror). Could you share which VPN provider you were using when it failed, and whether you saw an actual error message or just a stuck/blank page? That'll help narrow down whether it's a specific IP range getting flagged somewhere upstream (routing/CDN level) rather than anything intentional on our part.

Why do you say that? It seems to be working just fine. I just initiated a test swap (without depositing) using Google Chrome and my VPN turned on.

Matches what we'd expect — VPN and Tor traffic both work normally in the vast majority of cases, which is why FP91G's report stands out as worth digging into rather than dismissing. If it turns out to be provider-specific (some VPN IP ranges get caught in broader abuse blocklists maintained by third parties, not by us), that's useful to know and worth documenting for other users hitting the same VPN.


DEX.fo — No KYC. No AML. No registration.

[TokenTikas]

Thanks for jumping in on this one before we even saw it — good call, and turned out to be a stuck session rather than anything on our end. Appreciate you helping TokenTikas get sorted.

But one thing seems to me that the exchange took longer than normal to complete. The exchange confirmation time started on 21/07/2026 (00:49:00) and finished at (04:40:56). I thought it would take at most about one hour for the exchange to be fully completed but then I saw that it took almost four hours for the exchange to be fully completed. Although I did not panic about these things, it seems to me that it took a little longer than expected.

[MarryWithBTC]

Thanks for jumping in on this one before we even saw it — good call, and turned out to be a stuck session rather than anything on our end. Appreciate you helping TokenTikas get sorted.

But one thing seems to me that the exchange took longer than normal to complete. The exchange confirmation time started on 21/07/2026 (00:49:00) and finished at (04:40:56). I thought it would take at most about one hour for the exchange to be fully completed but then I saw that it took almost four hours for the exchange to be fully completed. Although I did not panic about these things, it seems to me that it took a little longer than expected.

Can you cross-check?

4hrs have deviated so much from the estimated time. I have never gotten it above 60 mins. It is usually within 30 - 60 mins. I also applaud you for being calm within this period. I have followed competitors thread where people will start complaining once it gets to 2hrs without processing.