Hey, quick one about the per-IP limits for ws and rest. We run a grid trading platform (builder 0x0176337C97BB884b8ac4bE2276A5c779ab1156B9) that manages orders for a lot of separate user accounts. Each account needs fill detection to re-place its grid orders, so right now we open userFills + orderUpdates per user over ws. The docs mention a max of 10 unique users across user-specific subscriptions per IP, so we end up capped at around 10 concurrent users per IP. Couple of things I wanted to check: - Is that "10 unique users" limit per IP or per connection? - Can it be bumped for a builder, or is sharding across IPs the only way? - If instead of per-user ws subs we detect fills with rest (orderStatus triggered by allMids price crosses), is that only bound by the 1200 weight/min IP limit, with no per-user cap? Basically trying to confirm whether rest is a valid path to go past 10 users per IP or if we're missing some hidden limit. Thanks!
Hey, quick one about the per-IP limits for ws and rest. We run a grid trading platform (builder 0x0176337C97BB884b8ac4bE2276A5c779ab1156B9) that manages orders for a lot of separate user accounts. Each account needs fill detection to re-place its grid orders, so right now we open userFills + orderUpdates per user over ws. The docs mention a max of 10 unique users across user-specific subscriptions per IP, so we end up capped at around 10 concurrent users per IP. Couple of things I wanted to check: - Is that "10 unique users" limit per IP or per connection? - Can it be bumped for a builder, or is sharding across IPs the only way? - If instead of per-user ws subs we detect fills with rest (orderStatus triggered by allMids price crosses), is that only bound by the 1200 weight/min IP limit, with no per-user cap? Basically trying to confirm whether rest is a valid path to go past 10 users per IP or if we're missing some hidden limit. Thanks!