Compute Units (CUs)
Compute Unit is a way to measure your RPC request usage on ThunderStack RPC. We provide each user a daily quota of usage, and each method will consume a cost based on the resource required for execution. You can think of this as you have a balance in your account and each method has its own price. This will be deducted from your account upon submission of RPC requests. The price of each RPC method is called Compute Unit. Based on this calculation, we enable our users to utilize the daily request quota more efficiently. In short, you only pay for what you use.
For different subscription tiers, there may have different daily usage quotas.
CUs of RPC Method
Below are the CUs for each method. We define the CUs based on the resource required for execution.
Supported Method
eth_accounts
5
eth_blockNumber
5
eth_chainId
5
eth_syncing
5
net_listening
5
net_version
5
web3_clientVersion
5
eth_subscribe
10
eth_uninstallFilter
10
eth_unsubscribe
10
web3_sha3
10
eth_signTransaction
10
net_peerCount
10
eth_gasPrice
15
eth_getBalance
15
eth_getBlockByNumber
15
eth_getCode
15
eth_getStorageAt
15
eth_getTransactionByBlockHashAndIndex
15
eth_getTransactionByBlockNumberAndIndex
15
eth_getTransactionByHash
15
eth_getTransactionReceipt
15
eth_getBlockByHash
18
eth_getBlockTransactionCountByHash
18
eth_getBlockTransactionCountByNumber
18
eth_getFilterChanges
18
eth_newBlockFilter
18
eth_newFilter
18
eth_newPendingTransactionFilter
18
eth_call
20
eth_getTransactionCount
25
eth_getFilterLogs
50
eth_getLogs
50
eth_estimateGas
75
eth_sendRawTransaction
150
debug_traceTransaction
280
debug_traceCall
280
debug_traceBlockByNumber
1800
debug_traceBlockByHash
1800
Unsupported Method
If ThunderStack RPC received requests using unsupported RPC method, the CUs are 2 for each request.
How does ThunderStack RPC calculate my daily CU quota?
We accumulate the daily usage by account. Regardless of how many API Keys you created in your account, we calculate the usage by summing the entire usage across all API Keys.
What happens if I run out of daily CU quota?
If you keep sending RPC request even though you've reached the daily CU quota, the request will fail and you will receive http 429 error and an error code: -32005
Copy
What happens if I send a request with incorrect payload?
If you're sending a RPC request with an incorrect payload, it will cost:
If incorrect method: it will cost you 2 usage for incorrect or unsupported RPC method.
If other parameters are incorrect, or execution failed due to the wrong payload: it will consume the original cost of each method.
How much daily quota do I have?
Last updated