Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Getting Started with Algorithmic Cryptocurrency Trading

jaynagpaul.com

Post reply on HN
Print view View original

31–40 of 45 posts

Re: Getting Started with Algorithmic Cryptocurrency Trading

#31

Post by canttestthis »

ctchocula wrote: post #30
canttestthis wrote: post #26

Earlier quoted context omitted.

Could you link me to where it says GDAX has 0% fee on limit orders? I couldn't find it.

"When you place an order at the market price that gets filled immediately, you are considered a taker and will pay a fee between 0.10% and 0.25% for BTC books and 0.10% and 0.30% for ETH books. When you place an order which is not immediately matched by an existing order, that order is placed on the order book. If another customer places an order that matches yours, you are considered the maker and your fee will be 0…

Ah thanks. I found the page earlier but shame on me for not reading all of it.

Re: Getting Started with Algorithmic Cryptocurrency Trading

#32

Post by RandomInteger4 »

lvturner wrote: post #25
a13n wrote: post #24

Earlier quoted context omitted.

Hmm, just looking at GDAX's API, you aren't able to tell who's making an order. You don't know if it's one account with ten orders, or ten accounts with one each. So I don't see why multiple accounts would be an advantage.

One thing that springs to mind is that it would allow you to have POSITIONS on both sides of the market, you could use this to create a series of small sell orders that would lure the bots down towards a larger buy order. You could do this by just placing orders, but I guess in some instances it would be beneficial to be able to hold positions in both directions.

The API let's you take positions on both sides with a single account, or prevent yourself from self-trades by setting a flag.

EDIT: Nvm, the flag just specifies what the behavior is in the event that the system encounters a self-trade: decrement and cancel, cancel resting, cancel incoming, cancel both.

Re: Getting Started with Algorithmic Cryptocurrency Trading

#33

Post by ctchocula »

canttestthis wrote: post #31
ctchocula wrote: post #30

Earlier quoted context omitted.

"When you place an order at the market price that gets filled immediately, you are considered a taker and will pay a fee between 0.10% and 0.25% for BTC books and 0.10% and 0.30% for ETH books. When you place an order which is not immediately matched by an existing order, that order is placed on the order book. If another customer places an order that matches yours, you are considered the maker and your fee will be 0…

Ah thanks. I found the page earlier but shame on me for not reading all of it.

No problem. The key is choosing "Limit Order" and checking the "Post Only" box under "Advanced". That will prevent your order from turning into a taker order if you accidentally set the Limit Price too high when buying/too low when selling.

Re: Getting Started with Algorithmic Cryptocurrency Trading

#36

Post by kbart »

RandomInteger4 wrote: post #28
joosters wrote: post #19

Earlier quoted context omitted.

That's nothing to do with the language! UNIX processes return an exit code, not a true/false flag.

What question does the exit code answer? Are there any errors? No (0) there are no errors. The concept of using 0 to mean false is not new to javascript is what I was getting at.

"Are there any errors? No (0) there are no errors."

Not necessarily. It's just a (mostly POSIX and Linux kernel) convention to use 0 as "no error" result, but there are plenty of code that returns 0 as an error and >0 for success. It has nothing to do with C language itself, as C functions let you return pretty much anything or nothing at all (void functions).

Re: Getting Started with Algorithmic Cryptocurrency Trading

#37

Post by joosters »

RandomInteger4 wrote: post #28
joosters wrote: post #19

Earlier quoted context omitted.

That's nothing to do with the language! UNIX processes return an exit code, not a true/false flag.

What question does the exit code answer? Are there any errors? No (0) there are no errors. The concept of using 0 to mean false is not new to javascript is what I was getting at.

Again, it's not a yes/no flag. The question is rather 'what error happened?' - in which case, it makes eminent sense for 'no error' to be the first exit code, hence 0.

Re: Getting Started with Algorithmic Cryptocurrency Trading

#38

Post by spentcoin »

brndnmtthws wrote: post #2

If you want to lose money, this is a good way to do it. You're better off buying what you believe in and holding it. It's easy to fit a perfect model to historical data, but it rarely works going forward, unless you have insider information.

I make profits on something like 95% of my trades when I'm trading manually. I do so because I have a bunch of rules that I stick to... If a market is too 'hot' I don't touch it. If the market turns right when I buy I set my profitable limit and let it sit until the market does eventually flip back around and the trade fills. This ruleset that I stick to is essentially a basic algorithm. An algorithm that could be improved upon vastly by adding on-the-fly TA and sound, complex math (that my brain is too slow to calculate). Those who believe an algo can't reliably make profits trading also believe that humans can't reliably make profits trading since every decision we make is a result of some form of algorithm.

Re: Getting Started with Algorithmic Cryptocurrency Trading

#39

Post by boomlinde »

RandomInteger4 wrote: post #28
joosters wrote: post #19

Earlier quoted context omitted.

That's nothing to do with the language! UNIX processes return an exit code, not a true/false flag.

What question does the exit code answer? Are there any errors? No (0) there are no errors. The concept of using 0 to mean false is not new to javascript is what I was getting at.

The question it answers is "what was the exit status of the process", where zero typically means success, and non-zero means that there was some kind of error or exceptional exit condition. The most important difference from a boolean is that the exit status is often used to enumerate several kinds of exit conditions, some of which are defined in POSIX (sysexits.h).

In a shell, for example, the 0 exit status is normally actually truthy:

    $(exit 0) && echo hello

Re: Getting Started with Algorithmic Cryptocurrency Trading

#40

Post by edf13 »

spentcoin wrote: post #38
brndnmtthws wrote: post #2

If you want to lose money, this is a good way to do it. You're better off buying what you believe in and holding it. It's easy to fit a perfect model to historical data, but it rarely works going forward, unless you have insider information.

I make profits on something like 95% of my trades when I'm trading manually. I do so because I have a bunch of rules that I stick to... If a market is too 'hot' I don't touch it. If the market turns right when I buy I set my profitable limit and let it sit until the market does eventually flip back around and the trade fills. This ruleset that I stick to is essentially a basic algorithm. An algorithm that could be im…

Exactly... And one of the big benefits of algo trading is that it takes the emotion out of the decision.

That's the main factor of human losses and mistakes. We always doubt ourselves.

You turn your 95% trading rules into an algo you can be sure it won't take a quick out to cut it's loss when it looks like the market is going wrong... the machine will always trust itself.

Post reply on HN