search

michaelgrosner / tribeca

A high frequency, market making cryptocurrency trading platform in node.js
Other
3.99k stars 949 forks source link

Bot going too fast? #112

Open renkcub opened 7 years ago

renkcub commented 7 years ago

Watching in Coinbase, it appears there is a lag between moving orders in which it does not appear there is an open order.

The bot moves very fast.

Is this a lag on Coinbase GUI part, or is there really a lag between? I would estimate it only appears that 10-25% of the time, there is actually an open order. The rest is the delay between canceling and reopening a new order.

However, this is only how it shows in Coinbase GUI. Thoughts?

Camille92 commented 7 years ago

Hi indeed Tribeca is very fast.

It can send up to 2000 orders a minute to the exchange, so there is no way to see it in the GUI or follow it with your naked eyes.

At the time of writing it is sending around 450 orders a minute on Coinbase for me.

renkcub commented 7 years ago

OK, good to know. In that case, this is pretty much a non-issue.

renkcub commented 7 years ago

reopening as I talked to my coder and he says the bot CANCELS and REPLACES orders and doesn't use a MOVE function. This means there is downtime between orders.

Has anyone calculated what % of the time Tribeca has no order in the system?

michaelgrosner commented 7 years ago

@renkcub What do you mean by MOVE? GDAX doesn't support replace/move (https://docs.gdax.com/#orders). There is a small period with no order in the exchange, but it sends both the cancel and then the new order at the same time.

jodom1979 commented 6 years ago

Is there a way to limit how quickly tribeca makes and cancels orders? Like, limit how quick it accesses the API per second?