Gelato
  • Introduction
    • Gelato, The Web3 Cloud Platform
  • Rollup As A Service
    • Introduction
    • Rollup Stacks
      • Arbitrum Orbit
        • Run a Full Orbit Node
      • OP Stack
        • Run OP Node
    • Deploy your Rollup
    • Customization
      • Data Availability
        • Celestia
        • Avail
        • Eigen DA
      • Custom Gas Token
      • Marketplace
        • Gelato Services
        • Data Indexers
        • Block Explorers
        • Oracles
        • Bridges
        • Account Abstraction
        • On & Off-ramp
        • Community
        • Identity & KYC
        • Others
      • Verifier Node Package
    • Public Testnet
  • RPC Nodes
    • Introduction
    • Compute Units
    • Using RPC Nodes
    • Supported Networks
    • Pricing and Plans
    • FAQ
  • Web3 Services
    • Web3 Functions
      • Understanding Web3 Functions
        • Trigger Types
        • Typescript Function
        • Solidity Function
        • Automated Transactions
      • Security Considerations
      • Template & Use Cases
      • Quick Start
        • Writing Typescript Functions
          • Event Trigger
          • Private Typescript Functions
          • Callbacks
        • Test, Deploy & Run Typescript functions
        • Writing Solidity Functions
        • Test, Deploy & Run Solidity Functions
        • Initiate an Automated Transaction
      • Create a Web3 Function Task
        • Using the UI
        • Using the Safe App
        • Using a Smart Contract
        • Using the Automate SDK
      • Analytics & Monitoring
      • Supported Networks
      • Subscription & Payments
      • Legacy Automate Migration Guide
    • Relay
      • What is Relaying?
      • Security Considerations
        • ERC-2771 Delegatecall Vulnerability
      • Templates
      • Quick Start
        • Sponsored Calls
        • Non-Sponsored Calls
      • ERC-2771 (recommended)
        • SponsoredCallERC2771
        • CallWithSyncFeeERC2771
          • Relay Context Contracts ERC2771
      • Non-ERC-2771
        • SponsoredCall
        • CallWithSyncFee
          • Relay Context Contracts
      • Relay API
      • Gelato's Fee Oracle
      • Tracking your Relay Request
      • Supported Networks
      • Subscriptions and Payments
        • 1Balance & Relay
        • SyncFee Payment Tokens
        • Relay Pricing
      • ERC2771 Migration Guide
    • VRF
      • Understanding VRF
      • How does Gelato VRF Work?
      • Security Considerations
      • Template
      • Quick Start
      • Create a VRF Task
        • Create a Fallback VRF
        • Migrating from Chainlink VRF
      • Supported Networks
      • Pricing & Rate Limits
    • Oracles
      • Understanding Gelato Oracles
      • Quick Start
      • Data Providers
        • Stork
        • Choas Labs
      • Migrating from Chainlink Oracles
      • Available Price Feeds
      • Supported Networks
      • Pricing & Rate Limits
    • Account Abstraction
      • Understanding ERC4337
      • Introduction to Gelato Bundler
      • Templates & Examples
      • Quick Start
      • Sponsored UserOps
        • Using 1Balance
        • Using Zerodev Paymaster
      • Non-Sponsored UserOps
        • Pay with Native
        • Pay with ERC20
      • Supported Networks
      • Bundler API Endpoints
        • eth_sendUserOperation
        • eth_estimateUserOperationGas
        • eth_getUserOperationByHash
        • eth_getUserOperationReceipt
        • eth_supportedEntryPoints
        • eth_maxPriorityFeePerGas
        • eth_chainId
    • 1Balance
      • 1Balance Alerts
      • Subscription Plans
      • Subscription Notifications
      • USDC Addresses
    • AI Agents
    • Teams
  • GELATO DAO
    • DAO & Token (GEL)
    • GEL Token Contracts
    • Governance Process
  • Social Media
Powered by GitBook
On this page
  • Understanding Compute Units (CUs)
  • What are Compute Units
  • Why use Compute Units?
  • Rollup Multiplier
  • CU Costs for Common Calls
  1. RPC Nodes

Compute Units

Understanding Compute Units (CUs)

What are Compute Units

Compute Units (CUs) measure the computational resources consumed by your API calls. They provide a standardized way to quantify usage across different types of requests.

Why use Compute Units?

CUs ensure transparent and fair pricing. Instead of flat rates, you pay based on the actual computational cost of your requests. This approach prevents overpaying for simple queries while accurately reflecting resource usage for complex operations.

Rollup Multiplier

Not all rollups require the same computational power to process API requests. Some are lightweight, while others demand significantly more resources. To account for these variations, we apply a Rollup Multiplier to Compute Units (CUs), ensuring that pricing accurately reflects the underlying computational cost.

How Compute Units Are Calculated Method Responses × Rollups Multiplier = Compute Units (CUs)

This ensures that high-throughput rollups, which consume more resources, are fairly priced compared to smaller chains. By aligning costs with computational intensity, Rollup Multipliers prevent inefficiencies, optimize pricing, and help developers scale seamlessly.

Below are the multipliers for different rollups:

Network
Methods
Multipliers

All Rollups

All methods*

1

CU Costs for Common Calls

Method
CU Cost

batch

CU of method # of times the method is called

debug_traceBlockByHash

170

debug_traceBlockByNumber

170

debug_traceCall

170

debug_traceTransaction

170

erigon_forks

24

erigon_getHeaderByHash

24

erigon_getHeaderByNumber

24

erigon_getLogsByHash

24

erigon_issuance

24

eth_accounts

10

eth_blockNumber

10

eth_call

26

eth_chainId

0

eth_createAccessList

10

eth_estimateGas

87

eth_feeHistory

10

eth_gasPrice

19

eth_getBalance

19

eth_getBlockByHash

21

eth_getBlockByNumber

16

eth_getBlockReceipts

500

eth_getBlockTransactionCountByHash

20

eth_getBlockTransactionCountByNumber

20

eth_getCode

19

eth_getFilterChanges

20

eth_getFilterLogs

75

eth_getLogs

75

eth_getProof

21

eth_getStorageAt

17

eth_getTransactionByBlockHashAndIndex

15

eth_getTransactionByBlockNumberAndIndex

15

eth_getTransactionByHash

17

eth_getTransactionCount

26

eth_getTransactionReceipt

15

eth_getUncleByBlockHashAndIndex

15

eth_getUncleByBlockNumberAndIndex

15

eth_getUncleCountByBlockHash

15

eth_getUncleCountByBlockNumber

15

eth_maxPriorityFeePerGas

10

eth_newBlockFilter

20

eth_newFilter

20

eth_newPendingTransactionFilter

20

eth_protocolVersion

0

eth_sendRawTransaction

250

eth_subscribe

10

eth_syncing

0

eth_uninstallFilter

10

eth_unsubscribe

10

net_listening

0

net_version

0

web3_clientVersion

15

web3_sha3

15

PreviousIntroductionNextUsing RPC Nodes

Last updated 2 months ago