SCS Compute Units (CU)
This document explains what the Compute Units of SCS are and specific Compute Unit Costs for each method.
What are SCS Compute Units?
SCS Compute Units (CU) are units that represent the compute resources used by customers when using SCS services. Simply put, the total monthly CU usage is the customer's monthly SCS service usage.
Depending on the Pricing Plan the customer have selected, the customer will receive Base CU that can be used during the month. For Growth Plan and above, even if the Base CUs are used up, auto-scaling is applied automatically and the service can continue to be used without stopping. For CUs consumed by auto-scaling, a different CU price is applied from the Base CU price.
As of Feb 4 2025, a CU is set for each Node RPC Service's JSON RPC API, and the total monthly CU consumed is calculated based on the type and amount of the JSON RPC API called. As the number of services increases in the future, the number of functions that can be used using CU increases.
Note: Not all functions can be used with CU. For example, JSON RPC API's throughput does not auto-scale using CU, and is fixed for each plan selected by the customer.
Please refer to our website for the SCS pricing table.
Node RPC Service
Soneium Mainnet/Minato Endpoints
https://docs.startale.com/reference/eth-accounts-soneium
Method Type | CU |
---|---|
net_version | 0 |
eth_chainId | 0 |
eth_syncing | 0 |
net_listening | 0 |
eth_uninstallFilter | 10 |
eth_accounts | 10 |
eth_blockNumber | 10 |
eth_subscribe | 10 |
eth_unsubscribe | 10 |
eth_feeHistory | 10 |
eth_maxPriorityFeePerGas | 10 |
eth_getTransactionReceipt | 15 |
eth_getTransactionByBlockHashAndIndex | 15 |
eth_getTransactionByBlockNumberAndIndex | 15 |
eth_getUncleCountByBlockHash | 15 |
eth_getUncleCountByBlockNumber | 15 |
web3_clientVersion | 15 |
web3_sha3 | 15 |
eth_getBlockByNumber | 16 |
eth_getStorageAt | 17 |
eth_getTransactionByHash | 17 |
eth_gasPrice | 19 |
eth_getBalance | 19 |
eth_getCode | 19 |
eth_getFilterChanges | 20 |
eth_newBlockFilter | 20 |
eth_newFilter | 20 |
eth_getBlockTransactionCountByHash | 20 |
eth_getBlockTransactionCountByNumber | 20 |
eth_getProof | 21 |
eth_getBlockByHash | 21 |
eth_getTransactionCount | 26 |
eth_call | 26 |
eth_getFilterLogs | 75 |
eth_getLogs | 75 |
eth_estimateGas | 87 |
eth_sendRawTransaction | 250 |
eth_getBlockReceipts | 500 |
debug_traceTransaction | 309 |
debug_traceCall | 309 |
debug_traceBlockByHash | 497 |
debug_traceBlockByNumber | 497 |
eth_signTransaction | 250 |
net_peerCount | 0 |
txpool_status | 0 |
debug_getBadBlocks | 497 |
debug_storageRangeAt | 497 |
debug_traceBlock | 497 |
debug_getTrieFlushInterval | 497 |
Astar Network/Shibuya Endpoints
https://docs.startale.com/reference/eth-accounts-astar-1
No CU is consumed regardless of which method is used.
Astar zkEVM Endpoints
https://docs.startale.com/reference/eth-blocknumber-astar-zkevm-1
No CU is consumed regardless of which method is used.
Updated 3 days ago