Own Reserves and Proof on Request: The Claim Users Can Question
A practical community guide
Privacy-focused tools are easiest to evaluate when their mechanics are explained in ordinary language. A user should be able to identify what the service asks for, what it does not ask for, and which decisions remain entirely in the user’s hands. Present the platform’s liquidity statement carefully and show what a user can reasonably ask support to clarify. 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
Own Reserves and Proof on Request: The Claim Users Can Question 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. Treat reserve language as a verifiable claim to examine, not a slogan that replaces independent judgment.
What the documented flow says
For the person creating the order, DEX.fo says its reserves belong to the service and are allocated on its addresses. The mechanism is more useful than a broad promise because it can be observed and verified.
The operational meaning is straightforward: The Q&A says proof of reserves can be provided on request. Users should treat the statement as part of the documented workflow and keep its limits in view.
This matters because Fast mode is described as being processed directly from those reserves. The point should be checked on the live order page rather than remembered from an earlier transaction.
A careful reading shows that A proof request should be made through the official support route and evaluated on the evidence supplied. That detail becomes most important before the deposit is broadcast, while the user can still correct the order setup.
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
- Send only the amount expected by the order and retain the order reference plus relevant transaction IDs.
- Use the SimpleX link on the official Contacts page or info@dex.fo for an order-specific support request.
- Never share a seed phrase, private key, password, recovery phrase, or wallet backup.
- Open dex.fo directly and verify the domain before using any support or Onion link.
- Check the asset and network together, especially when the same ticker exists on more than one chain.
- Review the destination address, refund address, live limits, selected mode, and calculated receive amount.
Limits of the claim
The exchange flow can reduce identity collection without removing transaction risk. Address accuracy, network compatibility, liquidity, confirmation time, and personal compliance remain separate responsibilities that should be considered before the deposit is sent.
Takeaway
Treat reserve language as a verifiable claim to examine, not a slogan that replaces independent judgment. Follow the route, verify the details, and keep the order record until the payout confirms.
Website: https://dex.fo