Bitcoin Forum
May 26, 2024, 05:31:45 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 [20] 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 »
381  Economy / Speculation / Re: Chances of $150 again on: November 05, 2013, 11:33:25 AM
Bears got shot down. not much to say about it. If you think single digits is still a posibility, you are delusional.
382  Economy / Speculation / Re: BTC at $205? Should I buy into a rally? on: November 05, 2013, 11:31:18 AM
IMHO bears get what they deserve. OP is left behind and it's his own fault...
383  Bitcoin / Project Development / Re: Haasonline Simple Trade Bot For BTCe and Bitstamp[Main topic] on: November 05, 2013, 11: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.

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!
384  Bitcoin / Project Development / Re: Haasonline Simple Trade Bot For BTCe and Bitstamp[Main topic] on: November 05, 2013, 10: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
385  Bitcoin / Project Development / Re: Haasonline Simple Trade Bot For BTCe and Bitstamp[Main topic] on: November 05, 2013, 10:17:12 AM
Looking forward to play around with the next version Smiley.
386  Economy / Services / Re: Butter Bot!: New Bitstamp, BTC-E, and MtGox EMA Trading Platform on: November 05, 2013, 08:40:04 AM
I began trading crypto earlier this year and found it difficult to track the movements and trends (especially overnight), so I've downloaded the Butter Bot demo and am intrigued by the moving averages, tweaking settings, etc.

I'm currently running the 30 minute trade frequency setting, but I'm wondering what would happen if there is to be another crash in the BTC market similar to April (which I suspect is coming soon). I was sitting in front of my computer when it happened in April, and as I recall, the market went from 260 USD down to 50 USD or so in the matter of 15-30 minutes. If my trade frequency is set to 30 minutes, isn't it possible that the bot could entirely miss the start and finish of the crash and I'd end up selling at 50, if this were to happen again?
YES.

Imho this is a weakness in the bot. Every selfrespecting bot should have a stop-loss percentage set based on the high it achieved while being bought. The bot should pull the latest ticker information every minute in between it's regular intervals to act upon the stop-loss.

Hi Saan1ty Smiley,
   Interesting question. The bots Trailing Stop Loss (TSL) feature, does exactly that, it takes the highest value since you turned on the bot and sells all your BTC for fiat if price falls by the percentage specified.

I say this every couple of pages:  It is an easy feature to understand in principle, but it is very hard to use in combination with EMA and can result in losses if improperly set. The argument on this can go either way, if it were me, I would have my bot on a 30 or 15 minute interval and not use TSL; I would just rely on the bot to act correctly.

Now a lot can go wrong in a flash crash/rocket recuperation, there is no magic setting that will protect you against all cases. A shorter time frame will make the bot more reactive, but it could follow false signals and incur some losses. In the end, you can't look at this in single trades, even if we are discussing large market movements, you have to look at it in aggregate over time or you are really just looking at noise.

Please let me know if you need anything at all Smiley.

Pablo.

Hi thanks for the reply! It's close but it's not exactly what I mean:

The system you currently have can abruptly stop trading when there is no reason to.

I suggest a trailing stop loss per trade:

I buy 10 BTC at 200, and have a stop loss set at 10 %:
the market climbs to 250 and then drops to 225 (a drop of 250 = 10% of the high) therefor the bot executes a sell order.
After this trade the stop loss should be reset untill you buy the next time based on the indicator.

Also I notice you have to set the trading fee manually (this should be an api call to the exchange every X minutes to check what the trading fee is).
Bitstamp has a trading fee based on your volume.


Hey Smiley,
  I think I see what you mean, a sort of "step" stop loss. I will tell you up front that I am not the trading consultant so I can not judge how effective this would be, but I will bring it up with the appropriate people, strikes me as a sane suggestion Smiley.

Pablo.

What I basically mean is a trailing stop loss that resets per trade :-). But your current implementation has it's merits too: post crash it might be wise to temporarily stop the bot and start it again manually if the market has calmed down a bit.

Maybe have both as an option with a clear explanation with what the difference is.

Also: EMA Crossovers are basically a pretty weak trading system. If you like MA's a lot you should consider switching to MACD as it is superior.

Hope you don't take my feedback too harsh, I'm just trying to help you make a better bot Smiley.
387  Economy / Services / Re: Butter Bot!: New Bitstamp, BTC-E, and MtGox EMA Trading Platform on: November 04, 2013, 10:40:32 PM
I began trading crypto earlier this year and found it difficult to track the movements and trends (especially overnight), so I've downloaded the Butter Bot demo and am intrigued by the moving averages, tweaking settings, etc.

I'm currently running the 30 minute trade frequency setting, but I'm wondering what would happen if there is to be another crash in the BTC market similar to April (which I suspect is coming soon). I was sitting in front of my computer when it happened in April, and as I recall, the market went from 260 USD down to 50 USD or so in the matter of 15-30 minutes. If my trade frequency is set to 30 minutes, isn't it possible that the bot could entirely miss the start and finish of the crash and I'd end up selling at 50, if this were to happen again?
YES.

Imho this is a weakness in the bot. Every selfrespecting bot should have a stop-loss percentage set based on the high it achieved while being bought. The bot should pull the latest ticker information every minute in between it's regular intervals to act upon the stop-loss.

Hi Saan1ty Smiley,
   Interesting question. The bots Trailing Stop Loss (TSL) feature, does exactly that, it takes the highest value since you turned on the bot and sells all your BTC for fiat if price falls by the percentage specified.

I say this every couple of pages:  It is an easy feature to understand in principle, but it is very hard to use in combination with EMA and can result in losses if improperly set. The argument on this can go either way, if it were me, I would have my bot on a 30 or 15 minute interval and not use TSL; I would just rely on the bot to act correctly.

Now a lot can go wrong in a flash crash/rocket recuperation, there is no magic setting that will protect you against all cases. A shorter time frame will make the bot more reactive, but it could follow false signals and incur some losses. In the end, you can't look at this in single trades, even if we are discussing large market movements, you have to look at it in aggregate over time or you are really just looking at noise.

Please let me know if you need anything at all Smiley.

Pablo.

Hi thanks for the reply! It's close but it's not exactly what I mean:

The system you currently have can abruptly stop trading when there is no reason to.

I suggest a trailing stop loss per trade:

I buy 10 BTC at 200, and have a stop loss set at 10 %:
the market climbs to 250 and then drops to 225 (a drop of 250 = 10% of the high) therefor the bot executes a sell order.
After this trade the stop loss should be reset untill you buy the next time based on the indicator.

Also I notice you have to set the trading fee manually (this should be an api call to the exchange every X minutes to check what the trading fee is).
Bitstamp has a trading fee based on your volume.
388  Economy / Services / Re: Butter Bot!: New Bitstamp, BTC-E, and MtGox EMA Trading Platform on: November 04, 2013, 10:10:35 PM
I began trading crypto earlier this year and found it difficult to track the movements and trends (especially overnight), so I've downloaded the Butter Bot demo and am intrigued by the moving averages, tweaking settings, etc.

I'm currently running the 30 minute trade frequency setting, but I'm wondering what would happen if there is to be another crash in the BTC market similar to April (which I suspect is coming soon). I was sitting in front of my computer when it happened in April, and as I recall, the market went from 260 USD down to 50 USD or so in the matter of 15-30 minutes. If my trade frequency is set to 30 minutes, isn't it possible that the bot could entirely miss the start and finish of the crash and I'd end up selling at 50, if this were to happen again?
YES.

Imho this is a weakness in the bot. Every selfrespecting bot should have a stop-loss percentage set based on the high it achieved while being bought. The bot should pull the latest ticker information every minute in between it's regular intervals to act upon the stop-loss.
389  Economy / Securities / Re: [ActiveMining] The Official Active Mining Discussion Thread [Self-Moderated] on: November 04, 2013, 10:02:19 PM
I'm LMAO, Bitfunder shutting down, what a surprise!
If only someone would have suggested going direct or havelock back when BTCT was shutting down...
390  Economy / Services / Re: Butter Bot!: New Bitstamp, BTC-E, and MtGox EMA Trading Platform on: November 04, 2013, 08:03:22 PM
When the client is running locally you seem to be contacting your own server a lot (over SSL).
I think people have a right to know what exactly you are sending back to your own server.

Care to explain? Even when saving API keys, butter-bot.com is contacted...
391  Economy / Securities / Re: [IPVO] [Multiple Exchanges] Neo & Bee - LMB Holdings on: November 04, 2013, 12:45:25 PM
Ex-trader, that's enough. You have made your point 1,000 times.

Stop being an idiot.

Would still be nice if CryptoCyprus would explain a little why the points of ex-trader are wrong.
392  Bitcoin / Project Development / Re: NEW Giveaway for "MasterCoins" - the new protocol layer built on bitcoin on: November 04, 2013, 11:31:33 AM
Changed my Forum Signature Wink.

BTC - 1E7XwA93NA3DMpqxtYRs9wHdQ7Thmb8PJo
393  Bitcoin / Project Development / Re: Haasonline Simple Trade Bot For BTCe and Bitstamp[Main topic] on: October 30, 2013, 06:21:11 PM
Stephan I think you misunderstood my post. The benchmark tool shows several trades but the active bot (pictured on the left in my previous post) only made 2 transactions in the same time period on the same settings.

For instance it bought at interval 2411 at 193.21 and then didn't sell it even 8 hours later after the price had gone well above the target price twice, the benchmark indicates atleast 2 instances that would meet the requirements to sell.




You practically answered your own question. Because the benchmark doesn't starts with a buy, the entire dynamic is changed. There is a bug with the benchmark mode.

I think Stephan understood. :-)
394  Economy / Securities / Re: [IPVO] [Multiple Exchanges] Neo & Bee - LMB Holdings on: October 29, 2013, 10:13:54 PM
Too easy.

Ruby vs php
Both suck.

Quote
Mac vs Windows
Both suck.

Quote
Coke vs Pepsi
Both suck.

Lol QFT!

I recently stopped drinking any soft-drink! The first days were rough, but it was worth it!

Also: Node.JS FTW!
395  Bitcoin / Project Development / Re: Haasonline Simple Trade Bot For BTCe and Bitstamp[Main topic] on: October 29, 2013, 03:40:33 PM
Dear Stephan224 - I think I found one issue with internet connection. When internet connection drops TradeBot stops refreshing rates BUT it shows last update time continuosly.
I have internet connection through 3G modem. Connection is very stable but once per day modem reconnects. Today I was trying to recieve samples from exchange portal so Ive started trading Bot and put window in background. After few hours Ive checked and found that currency graph are not updated.

I agree, there should definately be retries when the bot disconnects.
396  Economy / Securities / Re: [IPVO] [Multiple Exchanges] Neo & Bee - LMB Holdings on: October 29, 2013, 01:51:11 PM
On to the next question, why even use an RDBMS?
MongoDB Anyone? Grin
397  Economy / Securities / Re: [IPVO] [Multiple Exchanges] Neo & Bee - LMB Holdings on: October 28, 2013, 11:15:20 PM
klee, as anonymous as any retard in this forum, how confused are you about databases and what is used and where? Never mind, this is a rhetorical question.
If those clowns are going for Oracle... pff. good luck and thank you for a early warning. You sure know how to piss yor investors money away.
Have a nice ride to...

ex-trader accountants do not evaluate "business models". You probably meant "business plan" with shiny predictions for future income (aka fiction)
Indulge me!
Whats your experience dude? Ever worked in something as big as NeoBee might be?

Or hacking alone in your bedroom all day? Ever worked in a real company?? With people? You know...

I think you're missing the point. $47k per CPU is not an acceptable expense for a company that has raised maybe $1-2M. Every one of these initial dollars are precious. If they are all gone before NEOBEE is cash-positive, it fails.

NEOBEE has painted itself into a corner. No dilution. ALL of the public shares are up for sale at the current price point.

If they cannot succeed with the cash they have now, they will not succeed at all, because they have no way to raise more. And they sure are being careless with that cash.

Vycid gives NEOBEE a "don't buy" based on the way they are burning their capital and the absurdly optimistic business plan.

Don't they also have a user based license scheme instead of using CPU's?

I'm not an Oracle licensing expert, but my understanding is that it is "too expensive for a (crowdfunded) startup". If anyone can correct that assumption I would be interested to hear it.

Me neither, also their website is a mess.

By the way: I was defending Oracle a little bit earlier on, but that doesn't mean I'm opposed to using postgre...
398  Economy / Securities / Re: [IPVO] [Multiple Exchanges] Neo & Bee - LMB Holdings on: October 28, 2013, 11:11:21 PM
klee, as anonymous as any retard in this forum, how confused are you about databases and what is used and where? Never mind, this is a rhetorical question.
If those clowns are going for Oracle... pff. good luck and thank you for a early warning. You sure know how to piss yor investors money away.
Have a nice ride to...

ex-trader accountants do not evaluate "business models". You probably meant "business plan" with shiny predictions for future income (aka fiction)
Indulge me!
Whats your experience dude? Ever worked in something as big as NeoBee might be?

Or hacking alone in your bedroom all day? Ever worked in a real company?? With people? You know...

I think you're missing the point. $47k per CPU is not an acceptable expense for a company that has raised maybe $1-2M. Every one of these initial dollars are precious. If they are all gone before NEOBEE is cash-positive, it fails.

NEOBEE has painted itself into a corner. No dilution. ALL of the public shares are up for sale at the current price point.

If they cannot succeed with the cash they have now, they will not succeed at all, because they have no way to raise more. And they sure are being careless with that cash.

Vycid gives NEOBEE a "don't buy" based on the way they are burning their capital and the absurdly optimistic business plan.

Don't they also have a user based license scheme instead of using CPU's?
399  Economy / Securities / Re: [IPVO] [Multiple Exchanges] Neo & Bee - LMB Holdings on: October 28, 2013, 09:53:42 PM
klee, as anonymous as any retard in this forum, how confused are you about databases and what is used and where? Never mind, this is a rhetorical question.
If those clowns are going for Oracle... pff. good luck and thank you for a early warning. You sure know how to piss yor investors money away.
Have a nice ride to...

ex-trader accountants do not evaluate "business models". You probably meant "business plan" with shiny predictions for future income (aka fiction)

Why are you so opposed to oracle? What other big recurring costs do they have besides guaranteeing their customer data is safe?.
400  Economy / Securities / Re: [IPVO] [Multiple Exchanges] Neo & Bee - LMB Holdings on: October 28, 2013, 09:22:36 PM
Wow, this klee guy is retarded... Earned a spot on the ignore list.

The other guys are pretty much spot on about their database remark, the opensource alternatives are just as good and have professional paid support.
Anyway I understand why they opted to go for Oracle as database software, it's expensive but pretty good, also it's a little easier to find a suitable oracle developer.

So please everyone stop behaving like you know anything about this stuff...

-A full-time DBA
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 [20] 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!