Hey ,
  I'll be sure to bring this up with the dev team .

Pablo.

Hi Chatnoir ,
  Glad you like it, we aim to release it tomorrow night .

I would stay away from Stop Loss in general, it's a complex feature to set and when set improperly can cause losses. It's mostly available as a test feature for advanced traders. If you are dead set on using it, drop me an email, I will be happy to help you develop it.

There have been several "under the hood improvements" among them a solution to email trigger flooding on Bitstamp and BTC-E.

The main changes have to do with the graphing engine and how data is presented and can manipulated .

Please let me know if you have any more feedback .

Pablo.

P.S. the next release (after this one) should be a welcome surprise for everyone, stay tuned .

Hi Ahn:),
 Thanks . I will be sure to let you know about the next Beta .

Pablo.

think its awesome you guys are listening to the ppl on the forum and implementing changes this fast.

keep up the good work

**************
V2.5 Released!!!
**************

Friends, V2.5 has been released; you do not need to do anything, your software will update automatically throughout the next 24-48 hours. Please do not hesitate to let me know if you have any issues at all .

Change Log:

* New Charting engine which offers more features and increases availability (also fixes BTC-E issue)
* Fix for buy-order-triggered flood
* Several smaller bug fixes and improvements

Pablo.

I would ask you to reconsider rolling out updates automatically. Some users will want to wait and see if other users find bugs in the newest updates before rolling it out on a production and live environment.

It has been more than once that even beta testers have missed certain bugs which cause (somewhat) serious problems.

If there is a goofup somewhere down the line and a critical bug remains undetected until it goes live across a wide variety of computer users with different setups....well, I am sure those users will be hounding you guys for the BTC that is lost.

I think it is a nice idea. But it is not without serious risks. At least if someone opts-in to install it, you can point back to some kind of Terms of Service that protects you. Rolling out new versions automatically is fraught with all sorts of problems.

Keep this firmly in mind, if the update process is transparent and does not ask for user intervention, the basic thrust is that you are swapping out code and running it on many users computers. Even in large scale rolls outs, companies don't swap out new software versions until they have time to test for bugs that the developers often can't catch on the first try.

I read here about the "Trailing Stop Loss" but from stock trading a trailing stop loss "automatically tracks the stock’s price direction and does not have to be manually reset like the fixed stop loss"
 - because it will auto-update itself and follow the current price. And only when the price drop n% from the current maximum price - it will execute a sell.

But reading here I see that you have to update daily the Stop Loss ? or reset the bot ?

I would like for example to sell 2 BTC at the current price of 900 $. But instead of just selling now, I could wait and use the Butter Bot as a stop loss sell bot. Is that possible ? Can I deactivate the trading bot and just use the TSL feature ?  And so instead of selling right now, I will wait a few days and the bot will sell the 2 btc at the next price drop.

2. If I have 6 bitcoins, can the TSL sell only 2 ?  Do I have to write "4"  in the "Bitcoin reserve" setting ?

3. Does the butter bot react and will sell instant with TSL in case of a sudden drop ? Do I need to set "Trade Frequency" to 1 minute or 5 minutes ?

Hi PuertoLibre ,
   As usual, you are right on the issue.

I have struggled with this situation but as far as I am aware there is no way around it. Google has committed to no longer letting users install third party extensions so everything must come from the Chrome store, but when you update the app on the Chrome store with a new version, it automatically sends it out.

It's a tough issue. We have severely tightened our pre-release protocols and we would certainly prefer to have manual updates. I am not on the forefront of this issue however, so there may be some solution I am missing; I will speak to the devs and let them know everyones position on this.

Pablo.

Is everybody using the new version except me, or did it not push out like was mentioned earlier?  Can you guys put the versoin number somewhere on the windows we see, like an about tab, instead of having to go into chrome settings to check it?

Thanks...

I too haven't seen an update. I guess it must be an issue that creeped in at the last moment?