sharing an error message popping up trading .xyz pairs : '...WARNING ORDER REJECTED: {'status': 'err', 'response': 'Too many cumulative requests sent ...', while trading more than 1 USDC per request
is it a bug ? might be related to the "growth mode" for .xyz pairs with <10% of trading volume being computed
sharing an error message popping up trading .xyz pairs : '...WARNING ORDER REJECTED: {'status': 'err', 'response': 'Too many cumulative requests sent ...', while trading more than 1 USDC per request
is it a bug ? might be related to the "growth mode" for .xyz pairs with <10% of trading volume being computed
When growth mode is activated for an HIP-3 perp, protocol fees, rebates, volume contributions, and L1 user rate limit contributions are reduced by 90%.
https://hyperliquid.gitbook.io/hyperliquid-docs/trading/fees
When growth mode is activated for an HIP-3 perp, protocol fees, rebates, volume contributions, and L1 user rate limit contributions are reduced by 90%.
https://hyperliquid.gitbook.io/hyperliquid-docs/trading/fees
right, shouldn't the rule on "Address-based limits" be adapted ? currently results in liquidity providers being blocked at >10usdc per order
right, shouldn't the rule on "Address-based limits" be adapted ? currently results in liquidity providers being blocked at >10usdc per order
Can someone help me with how I can improve reliablity on my order submissions for HIP-3 markets?
Can someone help me with how I can improve reliablity on my order submissions for HIP-3 markets?
This isn't exactly the right channel to debate policy, but no. Growth mode is already a subsidy from the protocol, nodes, and peers; I'm not willing to further subsidize it by allowing 10x the transaction handling workload per dollar volume. If you're doing a trial run of your system before scaling committed capital, use https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/exchange-endpoint#reserve-additional-actions
This isn't exactly the right channel to debate policy, but no. Growth mode is already a subsidy from the protocol, nodes, and peers; I'm not willing to further subsidize it by allowing 10x the transaction handling workload per dollar volume. If you're doing a trial run of your system before scaling committed capital, use https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/exchange-endpoint#reserve-additional-actions