Questions & Answers
What are cryptocurrencies you support?
Litecoin, Bitcoin, Monero, Dash, Ethereum and Ethereum's ERC-20 tokens
Who are your liquidity providers? Can you proof your reserves?
We do not use any third-party liquidity providers and all our reserves belong to us, allocated on our nodes. We can provide a proof of reserves on request.
How exchanges are performed?
We generate a one-time input address exclusively for you. Once you transfer the required amount to it and it gets confirmed, you will receive the cryptocurrency purchased.
Do you need any documents from me in order to exchange?
No. We are a non-KYC exchange. We also never require SoF.
What is your .onion address?
Do you collect any client metadata (browser info, IP, etc)?

We don't collect any metadata.

Do you have an affiliation program?

Yes, follow this link to participate.

What is aggregation?

We operate with two pools of addresses for BTC deposits and transfers - mixed and aggregated. In a mixed pool all received and sent transactions are mixed together and there is no way to discover how many people are behind certain addresses and traceability is extremely difficult, which is very good for privacy but bad for risk scoring. In the aggregated pool all transactions we receive from users are collected on a known single address which is also used to send payments, what will clearly show you have interacted with our exchange and it's good for interacting with other major exchanges to avoid any risks of frozen funds.

These are cons and pros of each pool:

  • Aggregated pool (bc1qu2dq8w8lv8v3l7lr2c5tvx3yltv22r3nhkx7w0)
    • No risks of being frozen at major exchanges due to low risk score given by chain analysis platforms
    • Chain analysis platforms will know you have interacted with an exchange and won't increase a risk score of your sending addresses
    • Can be useful when someone asks you for a source of funds
    • Reduced privacy
  • Mixed pool
    • Strong privacy
    • Nearly impossible traceability of funds by chain analysis platforms
    • P2P-alike
    • High risks of frozen funds at major exchanges due to high risk score given by chain analysis platforms
Why my Bitcoin order payout is taking so long to confirm?

If you have selected the slow (or "free") fee mode during the order creation, we have sent Bitcoin to you and used the lowest possible mining fee so you don't have to pay it. The confirmation of a such transaction might vary from 12 hours to around a week, depending on the current mempool workload on the Bitcoin network.

You can speed it up by using your wallet's CPFP functionality. Since the unconfirmed transaction we have sent to you is spendable, you can spend it with a higher fee to incentivize confirmation of both transactions, which is the most simple way to get it included into the blockchain.

We recommend using the quick fee mode if you need your transaction confirmed fast, but we will charge you the blockchain mining fee.

Why my Monero order is taking so long to be paid?

Due to the fact we are using a single wallet for all incoming and outgoing Monero payments and its protocol limitations of UTXOs being spendable strictly after 10 confirmations, multiple orders involving Monero within our system may cause delay to your order, since we are only able to process one order once a UTXO from a previous order is fully confirmed.

Why my Bitcoin Lightning order is in the error state?

Bitcoin Lightning (also BTCLN or LN) network is a very dynamic system in its early development stage still but evolving rapidly. Sometimes the payout of your invoice may fail due to a variety of reasons and some of them are known:

  • Android battery management killing the app's network: If you use a mobile wallet such as Phoenix or Wallet of Satoshi, please ensure your app is open in the foreground during the payment attempt of your invoice. There is a known issue that if the app is sent to background, Android's batery optimization engine may restrict the app's network access in order to increase battery life, which will make your app unable to receive payments. Ensure your app is either (a) open in the foreground or (b) you configure your OS to exclude that app from Android's battery optimization.
  • Lack of inbound liquidity: Ensure your wallet is currently capable of receiving payments and has enough inbound liquidity.

If you still have issues, you can ask us for help by mentioning your wallet's software name.

Why no Telegram?

Our communications framework consists mainly of desktop applications and Telegram doesn't support end-to-end encryption ("Secret Chats") in their desktop app since the initial release, thus we consider transmission of payment and other private data via Telegram insecure, including using bots and standard chats, since neither of them support end-to-end encryption. We do not use mobile devices due to risks associated with a wide exposure of manufacture supply chains to hardware backdoors. More details can be found here and in the following discussion

WARNING: We strictly recommend against usage of Telegram bots for making exchange operations, because Telegram bots do not have any end-to-end encryption capabilities thus all your interactions with them are stored in the plain text on Telegram servers, available for data extraction any time later. Any service offering you swap operations via a Telegram bot has no understanding of security implications of a such service and most probably doesn't care about your privacy or possible consequences. Telegram actively cooperate with the law enforcement.

Any wallet recommendations?
  • Desktop
  • Mobile
  • WARNING: We do not recommend any mobile wallets that are not included into the official F-Droid repository. Projects that do not have technical capabilities to accomplish the inclusion criteria or simply avoiding doing so should be considered risky. The main purpose of being included to F-Droid is to ensure the compiled binaries are built from the current release source code without any modifications, because any project included to F-Droid is compiled by F-Droid's infrastructure and not by the project's team that can be compromised any time (this concept is called "reproducible builds").

  • Browser
  • Hardware