Conversation

2) NOT INVESTMENT ADVICE. NOT TRADING ADVICE. (Sorry for the deleted thread -- had a key typo at the start...)
1
5
3) People constantly want higher ratelimits. But not all orders are the same. The core metric here: $ volume per order sent. In other words, how efficient are your orders?
1
3
4) What do FTX's users look like? Well, here is $ traded / orders sent for the top 20 order senders on FTX.
Image
2
7
5) So, one note is that some takers have fewer orders per trade, which makes sense. But even when selecting for liquidity providers, there's a huge range. Some customers are 75x more efficient than others!
1
5
6) What's happening? Well, this, basically:
Quote Tweet
5) Anyway... So what about the other mistake? Well, let's say you want to provide liquidity. A common strategy is: Send a bid 0.20% below the best bid, and an offer 0.20% above the best offer.
Show this thread
1
4
7) And, in case you're wondering who reaches out to us asking for higher ratelimits: it's not the people around $100.
1
10
8) So anyway, we are working on increasing throughput and decreasing latency, which is long overdue. Also, check yo orders.
5
26
Replying to and
Tbh FTX is head of basically every other exchange regarding rate limits. I try to keep the amounts of req as low as possible. I think every dev should be respectful of 3rd party APIs. It's hard to implement gainzybot on other exchanges due to their way stricter rules.
1
12
Replying to and
Yeah some have absurd policies like only 3 keys and with forced expiration. I get the attempt at extra security but how am I supposed to operate with that without pissing ppl off? Biggest problem tho is that they nearly all base rate limits on IP for private endpoints. Now I ...
1
2
have to artificially blow up the count of my server instances just to hit their service from enough IPs. The workload on their end is the same so they win nothing but I have struggle. Not v enticing to integrate them. To top it all off their customer support only knows...
1
2
Show replies