the other thing make the situation worst is it seems like Haasbot not use the last price as limit order price, it tend to use a price slightly low/high than last price. This kind of strategy can generate more profit in a flat market, but just a disaster in a trend market
order never get chance to be executed
I wonder why there were hanging so many unfulfilled trades on Cryptsy, so I start to experimenting with my own (very basic java) bot and found out something strange and very annoying.
There are 3 ways how to connect to Cryptsy API. One is only for pushing realtime trading data (and probably not used by Haasbot), second is for various market and trading data, its public and don´t require API keys (and probably not used by Haasbot either, because without API keys You can´t even read prices with Haas) and third is for ordinary API access to get all possible data and to be able to trade and it requires API keys. This is most probably the one Haasbot use and suddenly worst of them - no matter how often You call API commands, last trade price is cached on server and updates once in about 15 minutes, furthermore inacurrate to actual price. Other data like open orders and recent trades are updated correctly, just this last price is somehow screwed.. Seems to me like some filthy Cryptsy game and I am curious how Haasbot is getting last price.