Quote from: maverick1337 on May 12, 2013, 07:18:52 PM

Quote from: eduk on May 12, 2013, 06:48:58 PM

Quote from: rikigst on May 12, 2013, 06:41:20 PM

eduk, I've noticed you happen to know how far fible1's paid version has developed. As per 2 days ago, Tobbelino's one was much better (not to mention, free). This volatility check addition is a must-have, and I saw it was implemented in fible1's version, too. Any clue on how it performed? Is tobli's version always the best one?

Here is the volatility one I made yesterday https://bitcointalk.org/index.php?topic=67591.msg2122016#msg2122016 which is free because most of it is other peoples work as it is TobbeLino's version with a volatility check, I'm still testing though, I literally finished coding the modification last night and have only run it for about 10 hours today. But it is avoiding sells and buys.

I'm also figuring out other ways to make it smarter, as during stable periods like we've seen these last few days it an be too agressive.

Is there anyway to avoid having the bot sell at a loss? I was on the unfortunate end of my bot buying at the top and selling at the bottom and would of rather saved those coins. Or is it simply better to have the bot do its thing and eventually come out on top?

In my opinion, the volatility check wouldn't have let the bot buy btcs in the first place, thus it wouldn't have sold at a loss: what we've been experiencing for the last days were strong price raises which weren't supported by the market itself for the following hours (letting the price fall again).
By checking for AT LEAST two intervals that the volatility is above the threshold, your situation could be avoided (the sample immediately after the price explosion would have had a low volume, not allowing the bot to buy).

Since this is turning into community-driven development, I think that strategy-based commits should be done one at a time, evaluating each time which improvents can be done, and how. (this is because, IMHO, stop-loss strategy would be redundant w/ volatility check, but I could be proven wrong easily once everybody gets the volume-check version)