Topic: Haasonline Simple Trade Bot For BTCe and Bitstamp[Main topic] - page 104. (Read 416703 times)
November 06, 2013, 08:09:34 PM
Am interested in this bot but would like to know from what I have seen can do more than 15 trades in a day more like 15 to 20 trades per min.
November 06, 2013, 06:24:59 PM
I'm considering trying this soft, can someone tell me how much he is doing avg / day / btc in trading ?
thanks !
thanks !
I'm doing between 5 - 15 trades a day using default rsi and .1 as my BTC trade amount and 1 ltc as my LTC trade amount as I want to get as many trades in as possible and take advantage of small movements this new version seems to be better suited for this just loaded today and don't have numbers on it yet.
November 06, 2013, 06:18:12 PM
I'm considering trying this soft, can someone tell me how much he is doing avg / day / btc in trading ?
thanks !
thanks !
November 06, 2013, 05:31:05 PM
Seem to have a situation where the updates are not staying active. I tried to test the connection under settings and it wipes out my last buy sell numbers?
November 06, 2013, 09:05:05 AM
The price is based on crypto coins because you will be earning crypto coins from it. There is no relation to the market price such as dollars. So i am sorry, but the price remains the same. The price is ROI based expressed in crypto coins.
@miaoux:
I made a fall-back procedure to hopefully solve the nonce problem. The next version will try to sync again with the exchange and will try to use create a new nonce value. If this fails 3 times you will see the nonce error again. But in that case the problem must be on your side.
@miaoux:
I made a fall-back procedure to hopefully solve the nonce problem. The next version will try to sync again with the exchange and will try to use create a new nonce value. If this fails 3 times you will see the nonce error again. But in that case the problem must be on your side.
November 06, 2013, 06:10:55 AM
I have just one question!
Since the BTC value has risen, will be there any price drop for the bot?
Thank You!
Tad
Since the BTC value has risen, will be there any price drop for the bot?
Thank You!
Tad
November 06, 2013, 04:34:23 AM
@Crypt1c:
You must be kidding i hope.... you never read i help i guess?
- Set your raise and drop to $0.26 instead of $10.0, you are way to high now.
- Remove all the indicators from the trade bot and start with 1 RSI or 1 MACD indicator at default settings.
Go ahead and start with this config, you will see the software will work better. Press the benchmark once in a while and browse though the charts to see whats is happening. Once you get what is happening you can start adding more indicators and fine-tune them. But whatever you do, read the help first and understand first what you are doing.
You must be kidding i hope.... you never read i help i guess?
- Set your raise and drop to $0.26 instead of $10.0, you are way to high now.
- Remove all the indicators from the trade bot and start with 1 RSI or 1 MACD indicator at default settings.
Go ahead and start with this config, you will see the software will work better. Press the benchmark once in a while and browse though the charts to see whats is happening. Once you get what is happening you can start adding more indicators and fine-tune them. But whatever you do, read the help first and understand first what you are doing.
November 06, 2013, 02:06:13 AM
I recently purchased the Simple Trade Bot and have discovered a few bugs, I'm using version 0.9.0.1 beta.
Bug 1-: The bot intermittently reads the wrong price at Bitstamp and activates a sale because it thinks the current price is below the drop-loss price when this is not the case.
http://i.imgur.com/BVhHhEq.jpg
In the screenshot above this occurred three times. Buy price twice and sell price once.
Bug 2-: The bot crashes with an Unhandled Exception when I click Direct Exchange and select BitStamp as the Exchange Website.
http://i.imgur.com/LUxrrOR.jpg
Bug 1-: The bot intermittently reads the wrong price at Bitstamp and activates a sale because it thinks the current price is below the drop-loss price when this is not the case.
http://i.imgur.com/BVhHhEq.jpg
In the screenshot above this occurred three times. Buy price twice and sell price once.
Bug 2-: The bot crashes with an Unhandled Exception when I click Direct Exchange and select BitStamp as the Exchange Website.
http://i.imgur.com/LUxrrOR.jpg
November 05, 2013, 05:03:45 PM
As an update to my Nonce mismatch problems, it seems that if I don't touch the Benchmark trade bot then everything works as expected.
There must be some kind of error forced if I start using the benchmarking facility (even with a minimal data set).
There must be some kind of error forced if I start using the benchmarking facility (even with a minimal data set).
November 05, 2013, 06:21:27 AM
The current implementation of the MACD is based on this step:
- Calculate divergence between them (Short - Long) (This is the MACD)
When the MACD passes the 0-line there is a crossover of the MA lines and then a signal is given by the indicator.
This is the implementation running right now. First i want to get things fully working without bugs and then i am planning on adding more and more indicators. One of them will be called "MACD-MA Cross-over" and that one will work as you have described, based on an smooth MACD cross-over momentum.
About the suggestions;
- Yes i will add the fee to the benchmark tool, at this moment it is still missing because my focus was on other things. But good thing you remind me of this.
- Transaction fees are up to date with the new version. I am polling them on a bigger interval, but it is polled and updated at the next version.
- Loading historical data from the internet is a feature i really want to add, but again my focus was on other things. I will rush this feature for the version after the next version.
- I will investigate the "Trailing Stop-Loss", at this moment i am working on a equal concept that monitors if the order gets filled and if not after X time then it will cancel the order. This this is stuff coming in the future. Maybe the Trailing Stop-Loss is better, i will have a look for sure. Thanks!
@nowywbitcoinowymswiecie:
Sorry, but i will never rush a release or do a pre-release. Sometimes i will do a Alpha release, but that is for big changes to the trade-engine only. I can understand people may want this version already, but if it does not work as expected or if it makes wrong trades then i will get a lot of complains. I can better avoid that and make sure first everything works first.
- Calculate divergence between them (Short - Long) (This is the MACD)
When the MACD passes the 0-line there is a crossover of the MA lines and then a signal is given by the indicator.
This is the implementation running right now. First i want to get things fully working without bugs and then i am planning on adding more and more indicators. One of them will be called "MACD-MA Cross-over" and that one will work as you have described, based on an smooth MACD cross-over momentum.
About the suggestions;
- Yes i will add the fee to the benchmark tool, at this moment it is still missing because my focus was on other things. But good thing you remind me of this.
- Transaction fees are up to date with the new version. I am polling them on a bigger interval, but it is polled and updated at the next version.
- Loading historical data from the internet is a feature i really want to add, but again my focus was on other things. I will rush this feature for the version after the next version.
- I will investigate the "Trailing Stop-Loss", at this moment i am working on a equal concept that monitors if the order gets filled and if not after X time then it will cancel the order. This this is stuff coming in the future. Maybe the Trailing Stop-Loss is better, i will have a look for sure. Thanks!
@nowywbitcoinowymswiecie:
Sorry, but i will never rush a release or do a pre-release. Sometimes i will do a Alpha release, but that is for big changes to the trade-engine only. I can understand people may want this version already, but if it does not work as expected or if it makes wrong trades then i will get a lot of complains. I can better avoid that and make sure first everything works first.
Thanks for the answers!
I'm glad you will add MACD as I described as well. It's a bit strange tho, that you call your current implementation MACD while it truly isn't. I would personally call the current implementation MA-Crossover and the implementation I suggest MACD, but it's your call obviously.
Also I'm very happy to see that you are working on order monitoring. In my opinion it is essential!
November 05, 2013, 06:19:49 AM
@nowywbitcoinowymswiecie:
Sorry, but i will never rush a release or do a pre-release. Sometimes i will do a Alpha release, but that is for big changes to the trade-engine only. I can understand people may want this version already, but if it does not work as expected or if it makes wrong trades then i will get a lot of complains. I can better avoid that and make sure first everything works first.
Sorry, but i will never rush a release or do a pre-release. Sometimes i will do a Alpha release, but that is for big changes to the trade-engine only. I can understand people may want this version already, but if it does not work as expected or if it makes wrong trades then i will get a lot of complains. I can better avoid that and make sure first everything works first.
Sure! Completely understandable. But changes look great.
November 05, 2013, 06:12:18 AM
The current implementation of the MACD is based on this step:
- Calculate divergence between them (Short - Long) (This is the MACD)
When the MACD passes the 0-line there is a crossover of the MA lines and then a signal is given by the indicator.
This is the implementation running right now. First i want to get things fully working without bugs and then i am planning on adding more and more indicators. One of them will be called "MACD-MA Cross-over" and that one will work as you have described, based on an smooth MACD cross-over momentum.
About the suggestions;
- Yes i will add the fee to the benchmark tool, at this moment it is still missing because my focus was on other things. But good thing you remind me of this.
- Transaction fees are up to date with the new version. I am polling them on a bigger interval, but it is polled and updated at the next version.
- Loading historical data from the internet is a feature i really want to add, but again my focus was on other things. I will rush this feature for the version after the next version.
- I will investigate the "Trailing Stop-Loss", at this moment i am working on a equal concept that monitors if the order gets filled and if not after X time then it will cancel the order. This this is stuff coming in the future. Maybe the Trailing Stop-Loss is better, i will have a look for sure. Thanks!
@nowywbitcoinowymswiecie:
Sorry, but i will never rush a release or do a pre-release. Sometimes i will do a Alpha release, but that is for big changes to the trade-engine only. I can understand people may want this version already, but if it does not work as expected or if it makes wrong trades then i will get a lot of complains. I can better avoid that and make sure first everything works first.
- Calculate divergence between them (Short - Long) (This is the MACD)
When the MACD passes the 0-line there is a crossover of the MA lines and then a signal is given by the indicator.
This is the implementation running right now. First i want to get things fully working without bugs and then i am planning on adding more and more indicators. One of them will be called "MACD-MA Cross-over" and that one will work as you have described, based on an smooth MACD cross-over momentum.
About the suggestions;
- Yes i will add the fee to the benchmark tool, at this moment it is still missing because my focus was on other things. But good thing you remind me of this.
- Transaction fees are up to date with the new version. I am polling them on a bigger interval, but it is polled and updated at the next version.
- Loading historical data from the internet is a feature i really want to add, but again my focus was on other things. I will rush this feature for the version after the next version.
- I will investigate the "Trailing Stop-Loss", at this moment i am working on a equal concept that monitors if the order gets filled and if not after X time then it will cancel the order. This this is stuff coming in the future. Maybe the Trailing Stop-Loss is better, i will have a look for sure. Thanks!
@nowywbitcoinowymswiecie:
Sorry, but i will never rush a release or do a pre-release. Sometimes i will do a Alpha release, but that is for big changes to the trade-engine only. I can understand people may want this version already, but if it does not work as expected or if it makes wrong trades then i will get a lot of complains. I can better avoid that and make sure first everything works first.
November 05, 2013, 05:55:54 AM
Hi Stephan,
Good stuff! The chances of going out of scope now are much slimmer.
Maybe another double-check on MACD:
- Set Short EMA to 12 (Can be variably set by User)
- Set Long EMA to 26 (Can be variably set by User)
- Calculate divergence between them (Short - Long) (This is the MACD)
- Calculate a 9 Period EMA on the divergence (This is the smoothed signal line) (Can be variably set by User)
- MACD Crossover = MACD - Smoothed Signal Line
- If the result of the MACD Crossover is positive -> Buy signal
- If the result of the MACD Crossover is negative -> Sell signal
Is this how your implementation works as well? (The calculation of the smoothed signal line is an important step!)
Couple more feature requests:
- Add transaction fees to the benchmark tool calculations
- Keep transaction fees up to date (bitstamp has changing transaction fees based on your volume)
- Option to pull historical data from exchanges to easily benchmark on one year historical data for example.
- Trailing Stop-Loss (http://www.wikinvest.com/wiki/Trailing_Stop_Order)
Regards,
San1ty
Definitely, San1ty changes are much apprecitated!Good stuff! The chances of going out of scope now are much slimmer.
Maybe another double-check on MACD:
- Set Short EMA to 12 (Can be variably set by User)
- Set Long EMA to 26 (Can be variably set by User)
- Calculate divergence between them (Short - Long) (This is the MACD)
- Calculate a 9 Period EMA on the divergence (This is the smoothed signal line) (Can be variably set by User)
- MACD Crossover = MACD - Smoothed Signal Line
- If the result of the MACD Crossover is positive -> Buy signal
- If the result of the MACD Crossover is negative -> Sell signal
Is this how your implementation works as well? (The calculation of the smoothed signal line is an important step!)
Couple more feature requests:
- Add transaction fees to the benchmark tool calculations
- Keep transaction fees up to date (bitstamp has changing transaction fees based on your volume)
- Option to pull historical data from exchanges to easily benchmark on one year historical data for example.
- Trailing Stop-Loss (http://www.wikinvest.com/wiki/Trailing_Stop_Order)
Regards,
San1ty
But- Stephan - relese what You have so far. Present issues are a little annoying and screen Youve just posted looks like HUGE improvement!
November 05, 2013, 05:41:28 AM
Hi Stephan,
Good stuff! The chances of going out of scope now are much slimmer.
Maybe another double-check on MACD:
- Set Short EMA to 12 (Can be variably set by User)
- Set Long EMA to 26 (Can be variably set by User)
- Calculate divergence between them (Short - Long) (This is the MACD)
- Calculate a 9 Period EMA on the divergence (This is the smoothed signal line) (Can be variably set by User)
- MACD Crossover = MACD - Smoothed Signal Line
- If the result of the MACD Crossover is positive -> Buy signal
- If the result of the MACD Crossover is negative -> Sell signal
Is this how your implementation works as well? (The calculation of the smoothed signal line is an important step!)
Couple more feature requests:
- Add transaction fees to the benchmark tool calculations
- Keep transaction fees up to date (bitstamp has changing transaction fees based on your volume)
- Option to pull historical data from exchanges to easily benchmark on one year historical data for example.
- Trailing Stop-Loss (http://www.wikinvest.com/wiki/Trailing_Stop_Order)
Regards,
San1ty
Good stuff! The chances of going out of scope now are much slimmer.
Maybe another double-check on MACD:
- Set Short EMA to 12 (Can be variably set by User)
- Set Long EMA to 26 (Can be variably set by User)
- Calculate divergence between them (Short - Long) (This is the MACD)
- Calculate a 9 Period EMA on the divergence (This is the smoothed signal line) (Can be variably set by User)
- MACD Crossover = MACD - Smoothed Signal Line
- If the result of the MACD Crossover is positive -> Buy signal
- If the result of the MACD Crossover is negative -> Sell signal
Is this how your implementation works as well? (The calculation of the smoothed signal line is an important step!)
Couple more feature requests:
- Add transaction fees to the benchmark tool calculations
- Keep transaction fees up to date (bitstamp has changing transaction fees based on your volume)
- Option to pull historical data from exchanges to easily benchmark on one year historical data for example.
- Trailing Stop-Loss (http://www.wikinvest.com/wiki/Trailing_Stop_Order)
Regards,
San1ty
November 05, 2013, 05:25:12 AM
Alright, i will give a sneak preview whats is coming this week....
I was hoping to release a new version yesterday, but i am facing some technical challenges that need to be solved first.
@miaoux:
I have really no glue what is going on in your case. I am using static trade amounts here and the trading working as expected.
The current version v0.9.0.1 does not look to the wallet amount. It tries to place the order normally without checks. When i place a order the order will be stored into the memory too. On each update the software looks if the order is still active at the exchange and if not then it will allow trading again.
Maybe is it a idea to have a look at your trade history? The order is located there and if the order is filled you should have the coins. The wallet should show it.
It has absolutely no effect to "refresh" the wallet itself, its 1:1 on the API with the exchange and i am just only showing the information i get.
It has use to click "All-in" each X time, but like i recommend, a static value is better on the current version.
I was hoping to release a new version yesterday, but i am facing some technical challenges that need to be solved first.
@miaoux:
I have really no glue what is going on in your case. I am using static trade amounts here and the trading working as expected.
The current version v0.9.0.1 does not look to the wallet amount. It tries to place the order normally without checks. When i place a order the order will be stored into the memory too. On each update the software looks if the order is still active at the exchange and if not then it will allow trading again.
Maybe is it a idea to have a look at your trade history? The order is located there and if the order is filled you should have the coins. The wallet should show it.
It has absolutely no effect to "refresh" the wallet itself, its 1:1 on the API with the exchange and i am just only showing the information i get.
It has use to click "All-in" each X time, but like i recommend, a static value is better on the current version.
November 05, 2013, 05:17:12 AM
Looking forward to play around with the next version 
.
. November 04, 2013, 10:40:52 PM
It is better now to use a static value. This will ensure trading on long term. I am doing this on my computers here too.
At the next update i will adjust the all-in trade amount dynamically so this problem can no longer come back.
At the next update i will adjust the all-in trade amount dynamically so this problem can no longer come back.
I only use a static amount already. (I've tried 0.01BTC, 0.1BTC, 1BTC and 0.95BTC) on BTC-e, BtcUsd.
The only time I used "All In" is to test whether it resets the wallet (which it does if you click/unclick).
In all other cases, with version 0.9.0.1 beta, it appears as if the lack of wallet update may be causing the failure of followup trades due to 'lack of funds' (assuming the debug log is correct and the Trade-bot is sending a Buy/Sell signal when it says it is - I have no reason to think otherwise right now).
I can say for certain that on mine, the USD value does not update after a buy or a sell for the very first trade. I'm still waiting to see if a subsequent trade is successful.
E.g.
Trade amount 0.1 Btc - Coins Position: Bought. USD in wallet initially $2.7. BTC value approx $200
> Trade occurs, sale of 0.1 Btc happens, I should have approx $22 in my wallet, but this isn't the case (unless I click/unclick all-in to refresh) - it's ~$2.
> Bot sends a buy order for 0.1 Btc - which fails. Presumably due to a check on having sufficient funds failing due to wallet being < $22?
November 04, 2013, 07:38:35 PM
It is better now to use a static value. This will ensure trading on long term. I am doing this on my computers here too.
At the next update i will adjust the all-in trade amount dynamically so this problem can no longer come back.
At the next update i will adjust the all-in trade amount dynamically so this problem can no longer come back.
November 04, 2013, 06:19:08 PM
Edit: Doesn't work on mine. It seems that after each unique buy or sell, the wallet fails to update correctly after the event. I'm guessing that's why my debug log is lined with actions, but no corresponding trade unless I manually reset the wallet using this "All-in" hack. As a result, my bot only ever carries out a single action (it seems).
Indeed, the "All in" trick seems to work only for the next trade.
Been observing it more, it just bought and the "All in" amount didn't get updated with the deducted fee. I believe the problem lays there, it buys whatever amount of coins but the fee is not deducted from this amount after the buy operation so when later trying to sell it errors since it's trying to sell more coins than what you have.
November 04, 2013, 06:08:30 PM
I wrote about this problem (page 20), I'll just put here another print screen with the error for information))
Pressing "all-in" also shows this error.
I hope new version will solve this problem
http://i.imgur.com/Dg4JTSC.jpg
Pressing "all-in" also shows this error.
I hope new version will solve this problem
http://i.imgur.com/Dg4JTSC.jpg
Jump to: