秋田预测市场 · Discord 审计

Aravindh | Avail参与话题 1消息总数 2

该用户的聊天记录定位。

Reset

聊天记录

共 2 条,显示第 1-2 条
Aravindh | Avail 2026-06-02 16:49:14 Hyperliquid Hyperliquid主账户API速率限制引发节点解决方案讨论

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?

Aravindh | Avail 2026-06-01 21:53:15 Hyperliquid Hyperliquid主账户API速率限制引发节点解决方案讨论

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?