Did you do this?

Setting up your client to use I2P

Your traffic will be open for anyone to inspect if you run the Crave client over clearnet. If you would like to hide the fact that you are using Crave, as well as the physical location from where your Crave traffic originates, you should set up your wallet to connect only to the I2P darknet.

To do this, download and install the I2P router(see below). After starting the router, you will need to enable the SAM application bridge. In the I2P web interface (http://127.0.0.1:7657/configclients), click on the box to automatically run the application bridge at startup, and then click on "start". By default, the SAM application bridge listens to 127.0.0.1 on port 7656. If you need to change this behavior, this can be done in one of three ways:

•    From the preferences menu in the Crave graphical interface, click on I2P, and then modify the IP number and port for the SAM application bridge. For the changes to take effect, restart the application.
  
•    Edit the variable clientApp.1.args in the file clients.config that is located in your local I2P folder and then restart I2P.
•    From the command line, start the Crave daemon (usually named craved) by specifying the following options: -samhost=<ip or host name> and -samport=<port>. For more options, use the command Craved --help.

Once this is done, start the Crave client, open the application preferences, click on the I2P menu, and then click on the button "use I2P only". Close the application and relaunch it. At this point, all your traffic will be encrypted and pass through the I2P network.

Please note that it will take several minutes to make connections to the I2P network when starting I2P for the first time.


Where to download I2P

The official I2P release can be downloaded here: https://geti2p.net/en/download.

The Abscond bundle is an easy to install software package with all you need to connect to I2P and let you use the most common features. It can be downloaded here: https://hideme.today/dev/.

While I think its great to have multiple markets,  I'm not a huge fan of 3 party escrow.

The main reasons being this:

• Untrustworthy escrow agents who may steal escrow, fail to release escrow or collude with (or be) one of the parties.
• Escrow agents with strong reputation may be doing a long con to take off with or extort a large payment or group of payments.

And for this I'm glad Sling has two party escrow.

Reasons why?  Or you want to just bash/fud.

The interface looks fine, if similar. 

They even don't want you in the crave thread LOL..  just a troll meant to spam whatever.

The thing is, even if its' from Bob's group and it turns out to be useful... so what.. its good.

People will have a choice of a couple of coin/markets.  

Its not a bad thing.

Ah old blazin8888 aka. killacam8888 ...  

Likes to spam but nobody listens.  

Multiple options are always a good thing.  

The only problem I don't like is most of these coins using Tor.   See here: https://blog.torproject.org/blog/thoughts-and-concerns-about-operation-onymous
They should switch to I2P only, at least until Tor can sort things out more.  

Sling dev said he would implement I2P after the market.

Good times...

Some of these people need certain medications in order to live...

Maybe where you live,   I have clients at relief camps in remote locations of a jungle. 

There are no laws on what can be bought and sold there.

Yea..  not everyone is coin racists  

I'm in a bunch of different ones,  to me,  most all alts have or had some type of value - if nothing else for a learning experience.

In before / this is where trolls will bring up NXT  and / or mac only bitmarkets

NXT is a java nightmare!!  I wouldn't touch it with a 100 ft. pole.  Plus it wasn't distributed well - at all.

Some Tor instructions for anyone who may find it useful:

Compile and use Tor - Ubuntu & Debian distros Guide
Reasons for doing this: Many times packages are outdated.

1. Make sure you have all build-essential and automake packages installed.

2. Download latest libevent from :
   a. http://libevent.org/

3. Extract the libevent folder (by command or archive manager)
   a. tar xzf libevent-2.0.22-stable.tar.gz

4. Compile libevent
   a. cd libevent*
   b. ./autogen.sh
   c. ./configure
   d. make
   e. sudo make install
   f. sudo ldconfig

5. Download the latest Tor source tarball from :
   a. https://www.torproject.org/download/download.html.en

6. Extract the Tor folder (by command or archive manager)
   a. tar xzf tor-0.2.6.7.tar.gz
   b. cd tor*
   c. ./configure && make

7. Now you can run tor as src/or/tor  
or you can run make install (as root if necessary) to install it into /usr/local/
and then you can start it just by running "tor"

8. Check that the Tor service is running on port 9050:
   a. ss -aln | grep 9050

9. Start and stop Tor with:
   a. src/or/tor
   b. src/or/tor stop


Further instructions:

#Make directory that is readable/writeable by the user that will be running Tor.

mkdir /home/username/hidden_service/

If you installed Tor Browser, look for Browser/TorBrowser/Data/Tor/torrc inside your Tor Browser directory. On OS X, you must right-click or command-click on the Tor Browser icon, and select "Show Package Contents" before the Tor Browser directories become visible. Many distributions default to having a SOCKS proxy listening on port 9050, but others may not. In particular, the Tor Browser Bundle defaults to listening on a random port.

Tor puts the torrc file in /usr/local/etc/tor/torrc if you compiled tor from source, and /etc/tor/torrc or /etc/torrc if you installed a pre-built package.

#Configure torrc, usually found in /usr/local/etc/tor

nano /usr/local/etc/tor/torrc

#add the following & save:

    HiddenServiceDir /home/username/hidden_service/
    #HiddenServicePort <virtualseenport> <localhostip>:<anyport#>
    HiddenServicePort 30137 127.0.0.1:30137
    #HiddenServicePort 18333 127.0.0.1:18333

The directory can be different of course, but (both) port numbers should be equal to your P2P listen port
Sling port is 30137, RPC 30138
Be sure to forward the port in router and open in firewall!


Once you've changed your torrc, you will need to restart tor for the changes to take effect. (For advanced users, note that you actually only need to send Tor a HUP signal, not actually restart it.)
#Restart Tor

sudo src/or/tor stop
sudo src/or/tor


#Make note of created *hiddenservicename*.onion in:

ls /var/lib/tor
/var/lib/tor/YOURHIDDENSERVICENAME/hostname


#Start up Sling:

./sling-qt -irc=0 -proxy=127.0.0.1:9050 -onlynet=Tor -externalip=yourhiddenservice.onion -listen

People might want to buy coins so they can purchase things on SLINGRoad...

In pure p&d minds, that is not possible. 

Nope almost time to start buying products ! 

Forget p&d and market shit...  I want to see what's for sale !!
 

Again, for people who may want to mask their IP if selling "things" -

Example of how to setup Sing wallet with TOR:
Via command line parameters you get your tor proxy running and then tell the wallet to run through that proxy, only use the tor network, and give it a tor hidden service addnode.

e.g. like this:

I just wish I had some tor onions to add 

Does anyone have a list of tor "addnodes" I could add to my .conf ?

I don't see any tor ones in the op.

I wonder what will be some of the first products available for sale....

LoL  if you always listen to your testicles you might end up with kids and a life you don't want

lol

748,673 Sling

http://sling.blockexplorer.cc/stats/

First, that's only for osx,  we need software meant for all the main platforms.

Second, hate to break the news to you but bitcoin isn't really that anonymous, even with mixing.

Some altcoin markets can add a second layer of anonymity & privacy in conjunction with btc.

These are valid needs.

What if I told you different devs use the same graphic service?