LOGGING POLICY

We keep NO logs of the ASB daemon. Instead, we run separate instances - one for the clear net, lokinet, and the other over tor - in a console window on various alternating servers. This allows us to constantly monitor active swaps right as they are being conducted. It also ensures that there is no paper trail for swap clients on our end. It creates a little more work for us, but ensures the privacy of clients 10x fold. No IP address of any kind are logged by us.

NOTE: In lieu of recent scammers contacting is via BitMessage and Session, we do keep an offline record of the following information: BTC RCVD, XMR SENT, BTC PRICE, XMR PRICE, TIMESTAMP, SWAPID. You'll notice no detailing information is saved by our offline records. We keep these so we can verify with any party that claims they have made a swap with our service. The extensive details are kept in the ASB database that is coded into the atomic swap software by Comit-Network. More on how we secure that below.

ASB DATABASE

With the release of asb 0.9.0 details of each swap are contained in an SQLite database on the server. Because this contains sensitive information, such as Bitcoin and Monero addressses along with other peer information, we store the database on an encrypted LUKS image. This protects users against any offline access to the filesystem. It also protects us as well because there is information about our process in the database. One key thing to note is that the database does not contain IP addresses currently. We hope there will not be implementation of that information in future releases. It is worth mentioning that we host our services dynamically for better security. Rotating these services provides an extra layer for you and us. 

We do publish our successful swaps here on this page, but we obscure the swap ID on this site as seen below.

APACHE LOGS

$ cat xmrswap.me.conf | grep "Log"
        #LogLevel info ssl:warn
        ErrorLog ${APACHE_LOG_DIR}/xmrswap.me/error.log
        CustomLog /dev/null common

HELPFUL HINTS

Because we host our atomic swap providers on various servers, we don't see the IP addressses come through on the ASB console side. However, we do occasionally run iftop to inspect the traffic to and from the server in order to identify any threats. It's possible this may coincide with an active swap, though is unlikely. Here is what you can do to better protect your privacy:

NOTE: the  swap command used to run an atomic swap does not always tunnel through your tor proxy, if you're using one. In our tests, the only time tor was actively used was when it was connecting to an onion address - or to a Rendezvous point with tor providers. When we performed swaps with ourselves over the clearnet, the swap CLI did not go through tor. In order to mitigate this you can do the following to ensure that the swap commad will connect over tor to any host and preserve your anonymity :

1.)  Edit /etc/tor/torsocks.conf , uncomment the following line, and then restart tor:

#AllowOutboundLocalhost 1

$ sudo systemctl restart tor

2.)  In the terminal that your are running the swap comand (or swapfe if using the GUI), first enter the following command after starting your tor service:

$ . torsocks on

3.)  Then run your swap command or swapfe:

$ ./swap --debug buy-xmr --change-address <your_btc_address> --receive-address <your_xmr_address> --seller <seller_multiaddress>

or

$ python3 swapfe

EXPLANATION: The first line allows connections to the localhost not to proxy through tor. This is necessary because swap CLI will connect to the monero-wallet-rpc daemon through the localhost. The second instruction will proxy all commands run in that terminal over your torsocks port. The third is the swap command which will now be proxied over tor ensuring you remain anonymous.

Done: BtcRedeemed