Minimum and Maximum Limits: Check Before Funding

A practical community guide

The strongest form of transparency is procedural. It tells the user what happens first, what information is required, when the network takes over, and what record should be kept until the exchange is complete. Turn the limit warning into a clear pre-deposit habit, especially because the platform displays route-specific limits before the swap. This article keeps the discussion close to the current DEX.fo workflow rather than extending the feature into claims the source material does not support.

Why this topic matters

Minimum and Maximum Limits: Check Before Funding matters because a crypto transfer becomes difficult or impossible to correct after broadcast. The useful question is therefore not only whether the feature sounds private, fast, or convenient. The better question is where it changes the order, which information the user must verify, and which parts remain dependent on a blockchain or an external wallet. Use the live limit shown for the exact order, not a number remembered from an earlier swap.

What the documented flow says

This matters because Minimum and maximum amounts are displayed before the exchange operation. The point should be checked on the live order page rather than remembered from an earlier transaction.

A careful reading shows that A deposit below the required minimum may not be processed. That detail becomes most important before the deposit is broadcast, while the user can still correct the order setup.

In practical terms, A deposit above the maximum can create a serious loss risk under the stated terms. It also gives support a clearer record if the order later needs to be reviewed.

For the person creating the order, Limits can differ by asset, network, route, and available liquidity. The mechanism is more useful than a broad promise because it can be observed and verified.

Where it fits in the order

A DEX.fo order begins with the exchange pair and the live route conditions. The user then provides a destination address and a required refund address, reviews the displayed minimum and maximum, and chooses an available execution mode. The service generates a one-time input address for that order. After the expected amount reaches the required confirmation state, the route is processed and the output is sent to the destination address.

This sequence is short, but the fields are not interchangeable. The destination address receives the purchased asset. The refund address is the return route for the asset being sent and cannot be changed after order creation. The one-time input address is the order-specific place where the deposit is made. Keeping those three roles separate prevents a simple interface from becoming a source of avoidable confusion.

Practical checklist

1. Review the destination address, refund address, live limits, selected mode, and calculated receive amount.
2. Send only the amount expected by the order and retain the order reference plus relevant transaction IDs.
3. Use the SimpleX link on the official Contacts page or info@dex.fo for an order-specific support request.
4. Never share a seed phrase, private key, password, recovery phrase, or wallet backup.
5. Open dex.fo directly and verify the domain before using any support or Onion link.
6. Check the asset and network together, especially when the same ticker exists on more than one chain.

Limits of the claim

Timing estimates are not guarantees. The incoming blockchain must confirm the deposit, the route must be processed, and the outgoing blockchain must confirm the payout. Each stage can move at a different speed.

Takeaway

Use the live limit shown for the exact order, not a number remembered from an earlier swap. Follow the route, verify the details, and keep the order record until the payout confirms.

Website: https://dex.fo