(Closed) Butter Bot!: Premier Bitstamp, and BTC-E EMA Trading Platform (Closed)

[fible1]

Finally after much tweaking I've been able to see it execute a trade without help using the 0/# setting.

These are my current options
Hourly
Buy 1: 0, Buy 2: 0.01
Sell 1: 0, Sell 2: -0.01

This acts just as I thought it would and sends a message like, "Sell Order Imminent" on the crossover itself (within 1 hour of the crossover), followed 1 hour later with "Sell Order Trigger" after the first notification was sent.

I would like if there was a noob friendly setting so you could just have two checkboxes that would be something like

Buy All Exactly At Crossover [checkbox] (Hover Tooltip - Warning! Choosing this option could possibly lead to a buy that is not based on a trend! This will also override any thresholds set. Do you still want to use this setting?)
Sell All Exactly At Crossover [checkbox] (Hover Tooltip - Warning! Choosing this option could possibly lead to a sell that is not based on a trend! This will also override any thresholds set. Do you still want to use this setting?)

DresdenReader,
      I like the checkbox idea (maybe for more than just crossover options), I will bring that up with the rest of the team to see what they think.

Be sure to post any other suggestions you may have .

Pablo.

[dresdenreader]

Not a problem! I consider myself a power user, so I'm always tweaking settings and try to notice when programs might be improved by adding things here and there for ease of usability and what not.

I know that with the nature of this program its not in all of our best interests to make this super easy to use, but for your existing customers I do see this as definitely being a decent usability upgrade for those that would rather not bother with thresholds and are just looking for a bit that will buy and sell at the crossovers, but also gives advanced users the tools to further personalize their experience with the software.

[Kuroth]

Finally after much tweaking I've been able to see it execute a trade without help using the 0/# setting.

These are my current options
Hourly
Buy 1: 0, Buy 2: 0.01
Sell 1: 0, Sell 2: -0.01

This acts just as I thought it would and sends a message like, "Sell Order Imminent" on the crossover itself (within 1 hour of the crossover), followed 1 hour later with "Sell Order Trigger" after the first notification was sent.

I would like if there was a noob friendly setting so you could just have two checkboxes that would be something like

Buy All Exactly At Crossover [checkbox] (Hover Tooltip - Warning! Choosing this option could possibly lead to a buy that is not based on a trend! This will also override any thresholds set. Do you still want to use this setting?)
Sell All Exactly At Crossover [checkbox] (Hover Tooltip - Warning! Choosing this option could possibly lead to a sell that is not based on a trend! This will also override any thresholds set. Do you still want to use this setting?)

In back testing your settings:   Starting Balance $1,000,  0.55 Trading Fee  Time Frame of back Test Apr 30,2013 to July 24,2013

I show with your settings you would have earned

2013-07-24 19:00 Simulation completed. Balance: 7.729 BTC (734.91 USD)

With the .025 settings it would have earned


2013-07-24 19:00 Simulation completed. Balance: 10.259 BTC (975.50 USD)


So the 0.25 settings still test out better.. 

[dresdenreader]

It's funny, I wish I could show you a specialized EMA at 2 hour frequency from January 1st to the most recent sell signal. Looking at something like 10k on January 1st to 340k at the most recent sell signal.

[Kuroth]

It's funny, I wish I could show you a specialized EMA at 2 hour frequency from January 1st to the most recent sell signal. Looking at something like 10k on January 1st to 340k at the most recent sell signal.

Well man if you have that kind of monster, what you doing here with us guppies?

[dresdenreader]

lol, you're getting me wrong, I don't have that. If I did have that I probably wouldn't be discussing this. I too, am a guppy.

MtGox
Time Period: 2 Hours
Daily Chart
Moving Averages
Exponential 11
Exponential 34

First Buy - January 4th, 10,000 USD @ 13.50

Last Sell - July 18th 324,752 USD @ 97

The four biggest gains are here:

Buy March 16th 46.9
Sell March 23rd 66
45,790

Buy March 24th 68
Sell April 10th 200
134,677

Buy April 17th 85
Sell April 26th 135
213,899

Buy July 8th 77
Sell July 18th 97
324,752

This would have been, buy all sell all at exactly the crossovers from January 1st all the way up until July 18th if you had invested 10k on the first Buy signal on January 4th. Yes, I'm sure this could probably be tweaked but these were my results. But since the software is limited to 1 hour max and doesn't allow you to trade at exactly the crossovers I wont be able to try these specific settings.

[dresdenreader]

I am however considering doing something like, split half of my account into Bot funds and split half my account into manual buy/sell funds and see where I end up after 1 month of use.

[fible1]

This would have been, buy all sell all at exactly the crossovers from January 1st all the way up until July 18th if you had invested 10k on the first Buy signal on January 4th. Yes, I'm sure this could probably be tweaked but these were my results. But since the software is limited to 1 hour max and doesn't allow you to trade at exactly the crossovers I wont be able to try these specific settings.

Hi Dresden ,
   We are looking into tweaking the time frames but there are technical issues there we have to overcome.

If you are interested in trading at crossovers, the settings discussed above work well:

These are my current options
Hourly
Buy 1: 0, Buy 2: 0.01
Sell 1: 0, Sell 2: -0.01

We do not advocate these settings because as back testing shows 0.25 works much better; but it is easy to do.

Please let me know if you need anything.

Best,
   Pablo.

[Kuroth]

Ahhhh Ok..  I see what your saying..  Yea if we could ever get more time settings would be interesting trying it

lol, you're getting me wrong, I don't have that. If I did have that I probably wouldn't be discussing this. I too, am a guppy.

MtGox
Time Period: 2 Hours
Daily Chart
Moving Averages
Exponential 11
Exponential 34

First Buy - January 4th, 10,000 USD @ 13.50

Last Sell - July 18th 324,752 USD @ 97

The four biggest gains are here:

Buy March 16th 46.9
Sell March 23rd 66
45,790

Buy March 24th 68
Sell April 10th 200
134,677

Buy April 17th 85
Sell April 26th 135
213,899

Buy July 8th 77
Sell July 18th 97
324,752

This would have been, buy all sell all at exactly the crossovers from January 1st all the way up until July 18th if you had invested 10k on the first Buy signal on January 4th. Yes, I'm sure this could probably be tweaked but these were my results. But since the software is limited to 1 hour max and doesn't allow you to trade at exactly the crossovers I wont be able to try these specific settings.

[dresdenreader]

This would have been, buy all sell all at exactly the crossovers from January 1st all the way up until July 18th if you had invested 10k on the first Buy signal on January 4th. Yes, I'm sure this could probably be tweaked but these were my results. But since the software is limited to 1 hour max and doesn't allow you to trade at exactly the crossovers I wont be able to try these specific settings.

Hi Dresden ,
   We are looking into tweaking the time frames but there are technical issues there we have to overcome.

If you are interested in trading at crossovers, the settings discussed above work well:

These are my current options
Hourly
Buy 1: 0, Buy 2: 0.01
Sell 1: 0, Sell 2: -0.01

We do not advocate these settings because as back testing shows 0.25 works much better; but it is easy to do.

Please let me know if you need anything.

Best,
   Pablo.

Definitely. I'm still in the experimentation stage. I'm not a big enough player to where I care that much if lose some BTC or USD in the process of trying to figure out what works the best.

[fible1]

I just want to let everyone know that we are on track for V2 release next week.

The code has been entirely rewritten from scratch and several important features added such as:

-Support for BTCE
-Server Back End to improve stability and support
-Fiat Reserve
-BTC Reserve
-Increased speed, and versatility.
-No need to reset, just set it and go.
-Recoding of "Trailing Stop Loss," bot is disabled when TSL is triggered to avoid rebuy fees.

The website and the bot interface are also going to be relaunched, we hope everyone loves the new product!

BUY NOW: There is still time to get in on the "Early Adopter" deal before we launch V2. Anyone who purchases before the V2 launch will receive a FREE 1 year subscription to V2, an HUGE value.

If anyone has any questions, please drop me a line.

Pablo.
www.btcbots.com

[Kuroth]

Looking forward to the release..   

[PuertoLibre]

I just want to let everyone know that we are on track for V2 release next week.

The code has been entirely rewritten from scratch and several important features added such as:

-Support for BTCE
-Server Back End to improve stability and support
-Fiat Reserve
-BTC Reserve
-Increased speed, and versatility.
-No need to reset, just set it and go.
-Recoding of "Trailing Stop Loss," bot is disabled when TSL is triggered to avoid rebuy fess.

The website and the bot interface are also going to be relaunched, we hope everyone loves the new product!

BUY NOW: There is still time to get in on the "Early Adopter" deal before we launch V2. Anyone who purchases before the V2 launch will receive a FREE 1 year subscription to V2, an HUGE value.

If anyone has any questions, please drop me a line.

Pablo.
www.btcbots.com

-Recoding of "Trailing Stop Loss," bot is disabled when TSL is triggered to avoid rebuy fess.


Could you explain more about this particular feature?

[dresdenreader]

Could you explain why this hasn't sold anything yet?




This seems pretty straightforward to me.

Before the 20:00 mark the first threshold, 0, would have been met (That's when the crossover occurred).
Exactly at the 20:00 mark, the second threshold would trigger because -0.01 is < -0.029

I can maybe imagine some lag and the sell not going off until 21:00, but it still hasn't, what the heck?

[dresdenreader]

Nevermind, I'm an idiot, 0 is technically greater than any negative number.

I just changed the sell thresholds to -0.01 and -0.02 and it triggered a sell almost immediately.

[fible1]

Nevermind, I'm an idiot, 0 is technically greater than any negative number.

I just changed the sell thresholds to -0.01 and -0.02 and it triggered a sell almost immediately.

Perfect, no problem .

Please let me know if you need anything.

Pablo.

[fible1]

I just want to let everyone know that we are on track for V2 release next week.

The code has been entirely rewritten from scratch and several important features added such as:

-Support for BTCE
-Server Back End to improve stability and support
-Fiat Reserve
-BTC Reserve
-Increased speed, and versatility.
-No need to reset, just set it and go.
-Recoding of "Trailing Stop Loss," bot is disabled when TSL is triggered to avoid rebuy fess.

The website and the bot interface are also going to be relaunched, we hope everyone loves the new product!

BUY NOW: There is still time to get in on the "Early Adopter" deal before we launch V2. Anyone who purchases before the V2 launch will receive a FREE 1 year subscription to V2, an HUGE value.

If anyone has any questions, please drop me a line.

Pablo.
www.btcbots.com

-Recoding of "Trailing Stop Loss," bot is disabled when TSL is triggered to avoid rebuy fess.


Could you explain more about this particular feature?

Hi,
   Yes, I'm happy to explain .

Trailing stop loss allows you to set a value which is a percentage. Then the bot will sell all your BTC for USD if the max price of BTC since you turned on the bot falls below your Trailing Stop Loss setting by the percentage you have specified. It is a safeguard feature in case of a crash.

In the past, if the TSL was triggered but the market went up again, the bot could in theory rebuy incurring possible losses through fees. We have recoded it so that a TSL trigger will pause the bot until an operator has had a chance to review everything and reset it.

We believe this mode will be much more efficient.

Please let me know if you have any other questions ,

Pablo.

[jubalix]

can some on explain, if this bot worked to acquire more btc, why would you need to even bother selling it...?

[PuertoLibre]

I just want to let everyone know that we are on track for V2 release next week.

The code has been entirely rewritten from scratch and several important features added such as:

-Support for BTCE
-Server Back End to improve stability and support
-Fiat Reserve
-BTC Reserve
-Increased speed, and versatility.
-No need to reset, just set it and go.
-Recoding of "Trailing Stop Loss," bot is disabled when TSL is triggered to avoid rebuy fess.

The website and the bot interface are also going to be relaunched, we hope everyone loves the new product!

BUY NOW: There is still time to get in on the "Early Adopter" deal before we launch V2. Anyone who purchases before the V2 launch will receive a FREE 1 year subscription to V2, an HUGE value.

If anyone has any questions, please drop me a line.

Pablo.
www.btcbots.com

-Recoding of "Trailing Stop Loss," bot is disabled when TSL is triggered to avoid rebuy fess.


Could you explain more about this particular feature?

Hi,
   Yes, I'm happy to explain .

Trailing stop loss allows you to set a value which is a percentage. Then the bot will sell all your BTC for USD if the max price of BTC since you turned on the bot falls below your Trailing Stop Loss setting by the percentage you have specified. It is a safeguard feature in case of a crash.

In the past, if the TSL was triggered but the market went up again, the bot could in theory rebuy incurring possible losses through fees. We have recoded it so that a TSL trigger will pause the bot until an operator has had a chance to review everything and reset it.

We believe this mode will be much more efficient.

Please let me know if you have any other questions ,

Pablo.

Trailing Stop Loss = A percentage value. (Got it)

"Then the bot will sell all your BTC for USD if the max price of BTC since you turned on the bot falls below your Trailing Stop Loss setting by the percentage you have specified. "

TSL is 1.0 %
If Max_Price_of_BTC < TSL
Then
Sell_All_BTC_For_USD

"It is a safeguard feature in case of a crash."

Huh....?

< I am confused.

=================

I understand that TSL is made to tackle a very critical problem of the average price going up rather than down. In day trading you cannot honestly lose if you turned all BTC to USD and the price plummets. (except in cases where it reaches zero)

You'd always want to increase your BitCoins by following a basic principle.

A) Sell your BTC for USD At the highest peaks, B) then when the price plummets buy the coins you sold plus whatever else extra you can afford at the lower price point. C) Then, when the price goes up again, you resell the BTC for USD again and you end up with more USD than the first round.

The only way to lose in this strategy is if (Part C) never happens again OR (In part A) you sell too low and misjudge where the peak is.

So Trailing Stop Loss is there to prevent (Part A) from happening or limiting the loss (Stop Loss percentage?). Do I understand this correctly? Or is a Trailing Stop Loss different than a regular Stop Loss?

----------------------

What is catching me off guard is that you are supposed to be using TSL as a function to determine where there is a loss by the average price in a period going up (after a Sell_All_BTC gets triggered). Or did I just read that wrong?

Usually a "crash" is defined as a downward market. If this is the case wouldn't it be extremely profitable to ride the market downhill and at the lowest crossover signal to trigger a Buy_All_BTC?

Or is B-Bot's strategy completely different from what I have described? (I know, I know, "Trends" not "Day Trading")

[dresdenreader]

----------------------
What is catching me off guard is that you are supposed to be using TSL as a function to determine where there is a loss by the average price in a period going up (after a Sell_All_BTC gets triggered). Or did I just read that wrong?

Usually a "crash" is defined as a downward market. If this is the case wouldn't it be extremely profitable to ride the market downhill and at the lowest crossover signal to trigger a Buy_All_BTC?

Or is B-Bot's strategy completely different from what I have described? (I know, I know, "Trends" not "Day Trading")

I've been thinking along the same lines.

The problem with going with "trends" in one hour increments owes to how volatile the BTC market is. Unlike the stock market, where crashes are protracted over days and weeks, crashes on MtGox and BTCE are protracted over minutes and hours.

Those 1 to 2 hours could make all the difference in a crash situation, and the way the bot currently works with thresholds could lead to you losing a lot of money if say the first threshold for a sell is reached when BTC drops from say 90 to 80, its entirely possible that price to crash all the way down to 60 in that next hour or two. So you're looking at a situation where if you had say 10 BTC and a crossover occurred, you could have sold at say 85 when the crash was happening, instead of the 65 that will happen because the bot hasn't hit its thresholds yet.

That's why I proposed the earlier feature that would allow a user to only buy and sell AT crossovers, or at least allow the mix of the two. For example I could see myself wanting to use thresholds in all my buy situations but only wanting to use strictly crossovers in all of my sell situations.