Founder of Bitsquare here…
We have already added Zcash to our supported coins. So would be great to see some ZCashers there!
Bitsquare is a desktop application available for all majore OS using a custom P2P network (similar to Bitcoins P2P network) over Tor (hidden services). But no Tor setup required, it is integratd in Bitsquare. Bitsquare protects your privacy and you don’t need to register. It is open source (AGPL) and not run by a company or VC funded but a community project.
Bitsquare never holds users funds. The funds are either in the users control or in a Multisig (the Bitcoin side).
The exchange process is similar like at LocalBitcoins but fully decentralized.
Bitsquare handles the transfer of the altcoin out of system, that makes it a no-brainer for us to add a new coin.
The security of the exchange is based on the same mechanisms which are used for Fiat exchanges.
2of3 Multisig, security deposit and an arbitration system. Please read the white paper for more info.
If anyone wants to trade Zcash on Bitsquare he simply adds an account for Zcash which requires only the Zcash address and then creates an offer or takes an existing offer for buying or selling ZEC against BTC. The transfer of ZEC is done by the BTC buyer from his external ZEC wallet to the BTC sellers ZEC address.
In the process of automating quote aggregation from some of the exchanges. When pulling from bitsquare, have already hit countless 301s due to out of date documentation covering the public webservice APIs, plus having hloc() giving ‘Invalid interval parameter’ when calling with interval param set to either half_*, auto, week and year strings.
Can someone responsible for managing the docs update https://market.bitsquare.io/api/@ManfredKarrer?
And any news for when you’ll be implementing RPC calls support client side for executing trades?
The hloc API has been fixed to match the documentation.
Can you provide example request(s) that are giving you 301 errors?
An initial bitsquare (app) api is in testing and should be in next major release. It will enable wallet operations as well as making and cancelling offers. The rest of the API to perform and confirm trades will come later.
All of the webservice APIs appeared to be misplaced and are within their own subdir of API, so a ‘/’ must be appended, otherwise you’ll get 301s.
Examples:
$ for i in 'hloc?market=xmr_btc' 'depth?market=xmr_btc' 'markets' 'offers?market=xmr_btc' 'trades?market=btc_eur&limit=2' 'ticker?market=btc_eur'; do curl -A ' ' "https://market.bitsquare.io/api/"$i -I; done
ok, I see what you mean. I was dimly aware of that ocurring but since my client code handles redirects internally it was never a problem for me and no one else mentioned it until now.
The redirects were caused by default apache behavior. I’ve added an .htaccess file now that overrides it, so the urls work as documented without redirect if trailing slash is omitted. Also trailing slash still works.
Please give it a try and let me know on github if you find any more issues.
Some libs are capable of handling the redirects internally while others are more strict and less forgiving, so I can see how one could miss the redirect if opting for first.
Just updated my nosetests and am now getting 200s all the way down, so thank you
