Hey this might be a good point... i can prevent other mm from canceling their orders...
Hey this might be a good point... i can prevent other mm from canceling their orders...
该用户的聊天记录定位。
Hey this might be a good point... i can prevent other mm from canceling their orders...
Hey this might be a good point... i can prevent other mm from canceling their orders...
since my cancel request sent is much earlier than order's match_time, still cancel rejected
since my cancel request sent is much earlier than order's match_time, still cancel rejected
I also wonder the same, if everyone uses same queue
I also wonder the same, if everyone uses same queue
Alright then, personal opinion
Alright then, personal opinion
Green platform did this, different user has different tier along with different rate limit plan
Green platform did this, different user has different tier along with different rate limit plan
I'd suggest assigning different user different rate limit tier are good design, by their trading contribution. That will prob effectively reduce the request throttle.
I'd suggest assigning different user different rate limit tier are good design, by their trading contribution. That will prob effectively reduce the request throttle.
By far I'd assume order latency was caused by ... order request throttle. But still unable to explain tail orderbook latency?
By far I'd assume order latency was caused by ... order request throttle. But still unable to explain tail orderbook latency?
I've been suffering from occasional orderbook updates latency, world cup market
I've been suffering from occasional orderbook updates latency, world cup market
can we have something like "AUTO-MERGE", it's like Kalshi when you have yes+no, you get $1 back automatically
can we have something like "AUTO-MERGE", it's like Kalshi when you have yes+no, you get $1 back automatically