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 TypeCU
net_version0
eth_chainId0
eth_syncing0
net_listening0
eth_uninstallFilter10
eth_accounts10
eth_blockNumber10
eth_subscribe10
eth_unsubscribe10
eth_feeHistory10
eth_maxPriorityFeePerGas10
eth_getTransactionReceipt15
eth_getTransactionByBlockHashAndIndex15
eth_getTransactionByBlockNumberAndIndex15
eth_getUncleCountByBlockHash15
eth_getUncleCountByBlockNumber15
web3_clientVersion15
web3_sha315
eth_getBlockByNumber16
eth_getStorageAt17
eth_getTransactionByHash17
eth_gasPrice19
eth_getBalance19
eth_getCode19
eth_getFilterChanges20
eth_newBlockFilter20
eth_newFilter20
eth_getBlockTransactionCountByHash20
eth_getBlockTransactionCountByNumber20
eth_getProof21
eth_getBlockByHash21
eth_getTransactionCount26
eth_call26
eth_getFilterLogs75
eth_getLogs75
eth_estimateGas87
eth_sendRawTransaction250
eth_getBlockReceipts500
debug_traceTransaction309
debug_traceCall309
debug_traceBlockByHash497
debug_traceBlockByNumber497
eth_signTransaction250
net_peerCount0
txpool_status0
debug_getBadBlocks497
debug_storageRangeAt497
debug_traceBlock497
debug_getTrieFlushInterval497

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.