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

11–20 of 45 posts

Re: Getting Started with Algorithmic Cryptocurrency Trading

#11

Post by RandomInteger4 »

paulgb wrote: post #4
senatorobama wrote: post #3

Earlier quoted context omitted.

Checked the GitHub. > Many people are reporting losses in live trading even if the simulation results and/or paper trading is positive. Someone's missing the big picture.

Oh, the issues from that repo are entertaining. This issue alone should be enough to make the case that you shouldn't build a production trading system in JavaScript. https://github.com/DeviaVir/zenbot/issues/1037

This isn't a javascript problem. They were trying to be too clever and test whether a value was set in the same statement where that value was used for a comparison.

The non-truthiness of 0 is something present in many languages.

Re: Getting Started with Algorithmic Cryptocurrency Trading

#12

Post by RandomInteger4 »

pcmaffey wrote: post #9
paulgb wrote: post #4

Earlier quoted context omitted.

Oh, the issues from that repo are entertaining. This issue alone should be enough to make the case that you shouldn't build a production trading system in JavaScript. https://github.com/DeviaVir/zenbot/issues/1037

`0 === false` is maybe the only thing that I actually hate about javascript. Mutability, I understand and thus can deal with it. Scope, no biggie. But resolving a number to false, when all other numbers resolve to true? Inexplicable. EDIT: `!0`

falsiness of 0 is not unique to javascript.

int main (int argc, char* argv[]) {

  return 0;
}

Re: Getting Started with Algorithmic Cryptocurrency Trading

#13

Post by turboturbo »

pcmaffey wrote: post #9
paulgb wrote: post #4

Earlier quoted context omitted.

Oh, the issues from that repo are entertaining. This issue alone should be enough to make the case that you shouldn't build a production trading system in JavaScript. https://github.com/DeviaVir/zenbot/issues/1037

`0 === false` is maybe the only thing that I actually hate about javascript. Mutability, I understand and thus can deal with it. Scope, no biggie. But resolving a number to false, when all other numbers resolve to true? Inexplicable. EDIT: `!0`

This is only the case with `==` in JavaScript, not `===`. I think most would consider using `==` a bad practice these days. That said, I agree with your point

Re: Getting Started with Algorithmic Cryptocurrency Trading

#15

Post by pcmaffey »

turboturbo wrote: post #13
pcmaffey wrote: post #9

Earlier quoted context omitted.

`0 === false` is maybe the only thing that I actually hate about javascript. Mutability, I understand and thus can deal with it. Scope, no biggie. But resolving a number to false, when all other numbers resolve to true? Inexplicable. EDIT: `!0`

This is only the case with `==` in JavaScript, not `===`. I think most would consider using `==` a bad practice these days. That said, I agree with your point

Right, is really only ever an issue using shorthand (!someVar).

Re: Getting Started with Algorithmic Cryptocurrency Trading

#16

Post by paulgb »

RandomInteger4 wrote: post #11
paulgb wrote: post #4

Earlier quoted context omitted.

Oh, the issues from that repo are entertaining. This issue alone should be enough to make the case that you shouldn't build a production trading system in JavaScript. https://github.com/DeviaVir/zenbot/issues/1037

This isn't a javascript problem. They were trying to be too clever and test whether a value was set in the same statement where that value was used for a comparison. The non-truthiness of 0 is something present in many languages.

It's not specific to JavaScript (I've made the same bug in python), but it should be a sign that a language designed to make websites interactive fulfills different requirements than a language designed for building real money trading systems.

Re: Getting Started with Algorithmic Cryptocurrency Trading

#18

Post by a13n »

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.

Can you expand on why you don't think algo trading with predictive algorithms is a viable strategy?

GDAX has 0% fees on limit orders. Say you set a limit sell at +1% and a stop loss at -1%. You could trigger a buy whenever you predict that it's >80% likely to hit +1% before -1%.

Plug in everything you can get (trades, order book, etc) from GDAX's WebSocket API into an RNN, and I'd guess you can be right more than you're wrong. Aka profitable.

Re: Getting Started with Algorithmic Cryptocurrency Trading

#19

Post by joosters »

RandomInteger4 wrote: post #12
pcmaffey wrote: post #9

Earlier quoted context omitted.

`0 === false` is maybe the only thing that I actually hate about javascript. Mutability, I understand and thus can deal with it. Scope, no biggie. But resolving a number to false, when all other numbers resolve to true? Inexplicable. EDIT: `!0`

falsiness of 0 is not unique to javascript. int main (int argc, char* argv[]) { return 0; }

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

Re: Getting Started with Algorithmic Cryptocurrency Trading

#20

Post by joosters »

scottmsul wrote: post #8

I was hoping to see some discussion about market-making bots or arbitrage bots, which I know for a fact can make money. Can these kinds of prediction bots actually beat random chance? I assumed price fluctuations mostly followed a random walk.

That's not really related to it being a bot, though. For any form of trading (whether manually or through some form of automation), of course there's going be some choice of buys & sells that return a profit.

How you choose such a profitable strategy is a huge area of discussion. However, it's a completely different subject to the article, which is just focused on the mechanism of running a bot.

Post reply on HN