Topic: Haasonline Simple Trade Bot For BTCe and Bitstamp[Main topic] - page 54. (Read 416703 times)

Can anybody please explain to me:

1. As an 'old' customer having bought the STB bot in December 2013, how much do i need to pay in to get the full version of the trading server?
2. how much would it have cost to get the full trading server if i was a new customer who did not have the STB?

I agree

The next improvement I would like to be personally would simply be extending the benchmark period. Is this what interests other users or are others more interested in the auto tuning capabilities?

Also the benchmark trade log should be separate from the bot's trade log. The bot's trade log should be tied to that bot after it is created, and record all actual trades. It would be good to save the benchmark trade log, but the separation of the two is really what's important to me here.

Thanks

These are the two features I most wanted. Thanks!

A technicality: I believe you mean "Only sell at or greater than double fee-costs" (on top of purchase cost).

hey stephan,

the new features and the cryptsy fix are nice. i would like to test it

Count me in as a guinea pig as well. I have btc-e bots running well and would like to experiment with cryptsy.

Hi Stephen, nice info I can test cryptsy working if you want .... Thank you.

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)

Can you check if you have set the right to read Info and to Trade? Most people forget this step and then you are unable to connect.

yes i did create a new API key (with its new secret code) and this still does not work when testing bot with this new key.

cryptsy was fine until the 19th February.
so Stephan has to check the API for trading.

im trading on btc-e fine,are you sure that your order is not getting filled 100%? Somtimes in the trade history it has 2-3 buys or sells in order to fil your order depending on the size, then all together it should fill your order 100%.

 if you can not connect via api, create a new api and connect.

cryptsy has always had issues, and they just changed the api.

Do You ppl read at all? Just 4 or 5 posts above - Cryptsy updated API and haasbot can´t use it properly now. I hope devs fix this ASAP, because I bought this bot right for microtrading on Cryptsy (because there are loads of FREE and good alternatives for trading on other exchanges, like Gekko for example)

+1

so in this case its the bot. simple as that.

didn't know that this problem also effects btce.

so since 4 days we loose trading & therefore the opportunity to gain more currency.
Other bot supporter provide compensation in form of extension if there are issues (cryptotrader).

again I change4d API tradekey on cryptsy and the bot says "connected" and is not trending for a nothing or having signal.
The old stb is at least doing trades.

@ Stephan: seriously its time now for having a working bot with working options and not 24/7 changes that screw everything more. pls. look into the issues and fix it.

We are all now patient since over almost 2-3 month and paid either for full/half or advanced bot.

$urfer ,
create a new api at btc-e and see if it keeps happening.

I'm trying to connect to my BTC-e account - not crypsy.

As far as i can tell I have setup everything correctly on my BTC-e account, ie checked both Read and Trade checkboxes...

There is nothing more i can do on my BTC-e account to make API connection work, but bot test connect still failing.

however, cryptsy added on the 19th a new API feature etc. maybe the bot need to be updated to that.

I am still using the latest Simple Tradebot (0.9.0.14beta) on its own (ie am not yet using the web server etc) ...

My problem is that the bot cannot connect to my BTC-e account via the API.  
In December was the last time i used the bot (version 0.9.0.7) and back then i had no problem connecting to BTC-e via the API.
I now found that my API key and secret code which worked back then no longer work, and so last night i created a new API key and secret code...  but these too do not work!

I get:

"the given connection settings do NOT work properly, the connection to the API has failed.
Credentials are invalid()"

HELP please ...

I still have the problem with the trade bots, new version doing nothing after testing, old version trading ok...
both times each tradebot was running running alone.

The new version always say on all charts on all trading pairs on all active bots: data column for axis 0 cannot be of type string and showing nothing else.
Is this now cryptsy or the bot???

There is something wrong with Crypts. I am getting this in my log for a whole day:

Polling failed, no prices are availible for Cryptsy at MoonLtc.