Hello, quick question -
We have a master account that does HL actions (usdSend, activation) for accounts that delegate to it.
Market orders execute through the delegated wallets, so volume accrues there, not to the master account.
As a result it has the ~10k starter allowance with $0 attributable volume and hits the " Too many cumulative requests sent" rate limit.
For an account such as this with high-actions but low volume, what do you recommend as the fix?
1. Purchase requests with reserveRequestWeight? or
2. Rotating a pool of master accounts?
And is there any way for volume on the delegated/user wallets to count toward the master account's allowance?
Hello, quick question -
We have a master account that does HL actions (usdSend, activation) for accounts that delegate to it.
Market orders execute through the delegated wallets, so volume accrues there, not to the master account.
As a result it has the ~10k starter allowance with $0 attributable volume and hits the " Too many cumulative requests sent" rate limit.
For an account such as this with high-actions but low volume, what do you recommend as the fix?
1. Purchase requests with reserveRequestWeight? or
2. Rotating a pool of master accounts?
And is there any way for volume on the delegated/user wallets to count toward the master account's allowance?
Hi gents! Does having an own node helps to overcome HL's "address-based API rate limits" ?
Hi gents! Does having an own node helps to overcome HL's "address-based API rate limits" ?
no only ip based requests to info server
no only ip based requests to info server
thank you very much, you've evidently introduced me to the world of running a node. i don't currently do that, i assumed the REST API was the best way to interact with hyperliquid. was my assumption wrong, is working with my own node generally better?
thank you very much, you've evidently introduced me to the world of running a node. i don't currently do that, i assumed the REST API was the best way to interact with hyperliquid. was my assumption wrong, is working with my own node generally better?
almost certainty, they probably have no way to rate limit you if you're using a node.
almost certainty, they probably have no way to rate limit you if you're using a node.
look at the specific call. if you're hitting your node, no rate limit. if you're hitting their API, then its their rules.
look at the specific call. if you're hitting your node, no rate limit. if you're hitting their API, then its their rules.
did you ever fix this? I have the same exact issue
did you ever fix this? I have the same exact issue
node doesnt let you call exchange methods, it only spin up an info server so you still have to deal with address based limits through other means
node doesnt let you call exchange methods, it only spin up an info server so you still have to deal with address based limits through other means
For data processing, 100% better to pull the data directly from the node, this is the meta in HL 🙂
For data processing, 100% better to pull the data directly from the node, this is the meta in HL 🙂
Hello, quick question -
We have a master account that does HL actions (usdSend, activation) for accounts that delegate to it.
Market orders execute through the delegated wallets, so volume accrues there, not to the master account.
As a result it has the ~10k starter allowance with $0 attributable volume and hits the " Too many cumulative requests sent" rate limit.
For an account such as this with high-actions but low volume, what do you recommend as the fix?
1. Purchase requests with reserveRequestWeight? or
2. Rotating a pool of master accounts?
And is there any way for volume on the delegated/user wallets to count toward the master account's allowance?
Hello, quick question -
We have a master account that does HL actions (usdSend, activation) for accounts that delegate to it.
Market orders execute through the delegated wallets, so volume accrues there, not to the master account.
As a result it has the ~10k starter allowance with $0 attributable volume and hits the " Too many cumulative requests sent" rate limit.
For an account such as this with high-actions but low volume, what do you recommend as the fix?
1. Purchase requests with reserveRequestWeight? or
2. Rotating a pool of master accounts?
And is there any way for volume on the delegated/user wallets to count toward the master account's allowance?