Post
Topic
Board Project Development
Re: Haasonline Simple Trade Bot For BTCe and Bitstamp[Main topic]
by
Stephan224
on 24/02/2014, 13:00:15 UTC
I have some real good news reguarding Cryptsy... the past time i noticed (like a lot of you to) that Cryptsy seems to fail publishing prices. However this is not entirely true, Cryptsy is sending the data but there is a small bug inside it. I cannot tell what exactly the impact is of this bug because i do not have the insight in the API in detail. However, the good news is that we can work around it. With this work-around is becomes possible to get the API of Cryptsy a little more stable.

Last night i have made a setup to test this workaround and it its looking good. The test outcome was very positive.

Some in depth-info: The bug seem to be related to the orderstack data from the API of Cryptsy. (thats why it was related to some coins in the beginning, i guess) This part comes back empty from the API and this is the cause the prices are not being recieved. The work-around does not look to the order stack, instead it looks to the last executed order. It reads thats price. (downside of this solution: the sell price is known, charts will show equal buy/sell prices)

Normally i would directly push an update to add this workaround and to solve this issue. But i need to be fair and its a bit impossible at the moment. Despite the test of last night we are in the middle of the next big update. The changes to Cryptsy are embedded inside this update and we do not release beta versions anymore (except to testers). So the timeline to solve this matter is a little bit longer then normally.

But do not worry... the test of the new update is going very well and all the new features are proven to be working very good. We are on shedule for this release, and if this continues today then tonight i will request a few beta testers again like i did before. This means we go toward the public beta test and this normally takes 1 or 2 days. After this the release is planned.

I will give post a sneak preview of the coming changes.

Version 0.9.8.0 (next update, mid this week)
- Alt-coin added: Max & Yac
- Alt-pairs added: Max/Btc, Yac/Btc, Yac/Ltc and Ezc/Btc
- Exchange added: CEX.IO is now supported
- Safety added: Static/Fixed Roof-in (Available within all licenses)
- Safety added: Dynamic Roof-in (Available within Simple and Advanced license)
- Trade Indicator added: MA-histogram indicator (its in fact a MACD-histogram, SMA based. Available within all licenses)
- Trade Indicator added: Dynamic adjusted High/Low indicator (Only available within the Advanced license)
- Insurance added: Disable on losses after X trades (Available within all licenses)
- Insurance added: Never Sell Cheaper (Available within all licenses)
- Insurance added: Only sell at double fee-costs (Available within all licenses)
- New: Trade-bot auto tuning capabilities
- New: Manuel indicator tune capabilities
- New: Windows Classic -interface added (so to server settings to change the interface)
- Improvement: Extra fall-back implemented to read the prices of the Cryptsy API
- Improvement: Auto-setup of the indicator expanded to 120minutes (instead of 60minutes)
- Improvement: The backtest is adjusted to be a little less pessimistic (correction from -0.5% -> -0.2%)
- Bugfix: MA indicator switched back to EMA instead of SMA

I am very sure a few listed features will catch your eye, for example the "Trade-bot auto tuning capabilities". I will explain it in more detail later on, once we get near the release itself. But you can already take my word for it that if you where impressed by the backtest then this will rock your world. This is NO bold statement, we will again go inside the Google History book as first world wide to offer this feature for the crypto coins. (very, very big smile)

But back to Crytpsy.... if the request for testers is posted here i hope some testers will be able to confirm too this workaround is working better. After all, the software must be able to read prices and be able to trade or the rest is useless. (except if you are on a different exchange of course, this issue is isolated to Cryptsy after all)