4EVERLAND Documents
HomeTwitterDiscordBlogs
  • Welcome to 4EVERLAND
  • Get started
    • Our Features
    • Quick Start Guide
      • Registration
      • Login options
        • MetaMask
        • OKX Wallet
        • Binance Web3 Wallet
        • Bitget Wallet
        • Phantom
        • Petra
        • Lilico
      • Usage Introduction
      • Dashboard stats
      • Account
        • Linking Your EVM Wallet to 4EVERLAND Account
        • Balance Alert
    • Billing and Pricing
      • What is LAND?
      • How to Obtain LAND?
      • Pricing Model
      • Q&As
    • Tokenomics
  • HOSITNG
    • What is Hosting?
      • IPFS Hosting
      • Arweave Hosting
        • Auto-Generation of Manifest
      • Internet Computer Hosting
      • Greenfield Hosting
    • Guides
      • Creating a Deployment
        • With Git
        • With IPFS Hash
        • With a Template
      • Site Deployment
      • Domain Management
        • DNS Setup Guide
        • ENS Setup Guide
        • SNS Setup Guide
          • The gateway: 4sol.xyz
        • SPACE ID Setup Guide
      • Project Setting
        • Git
      • Troubleshooting
      • Common Frameworks
    • Hosting Templates Centre
      • Templates Configuration File
    • Quick Addition
      • Implement Github 4EVER Pin
      • Github Deployment Button
    • Hosting API
      • Create Project API
      • Deploy Project API
      • Get Task Info API
      • IPNS Deployment Update API
    • Hosting CLI
  • Storage
    • Bucket
      • IPFS Bucket
        • Get Root CID - Snapshots
      • Arweave Bucket
        • Path Manifests
          • Instructions for Building Manifest
          • Auto-Generation of Manifest
        • Arweave Tags
        • Unleash Arweave
      • Guides
      • Bucket API - S3 Compatible
        • Coding Examples
          • AWS SDK - Go (Golang)
          • AWS SDK - Java
          • AWS SDK - JavaScript
          • AWS SDK - .NET
          • AWS SDK - PHP
          • AWS SDK - Python
          • AWS SDK - Ruby
        • S3 Tags Instructions
      • 4EVER Security Token Service API
      • Bucket Tools
      • Bucket Gateway Optimizer
    • 4EVER Pin
      • Guides
      • Pinning Services API
      • IPFS Migrator
    • Storage SDK
  • Gateways
    • IPFS Gateway
    • IC Gateway
    • Arweave Gateway
    • Dedicated Gateways
      • Gateway Access Controls
      • Video Streaming
      • IPFS Image Optimizer
    • IPNS Manager
      • IPNS Manager API
  • RPC
    • Guides
    • API Keys
    • JSON Web Token (JWT)
    • What's CUs/CUPS
    • WebSockets
    • Archive Node
    • Debug API
    • Chains RPC
      • BSC / opBNB
      • Ethereum
      • Optimism
      • Polygon
      • Taiko
  • AI
    • AI RPC
      • Quick Start
      • Models
      • API Keys
      • Requests & Responses
      • Parameters
    • 4EVER Chat
  • RaaS - Beta
    • What's Rollups?
    • 4EVER Rollup Stack
  • DePIN
    • 4EVER Network
    • Storage Nodes
  • More
    • Use Cases
      • Livepeer
      • Lens Protocol
      • Optopia.ai
      • Linear Finance
      • Snapshot
      • Tape
      • Taiko
      • Hey.xyz
      • SyncSwap
    • Community
    • Tutorials
    • Security
    • 4EVERLAND FAQ
Powered by GitBook
On this page
  • CU
  • CUs of RPC Method
  • Supported Method
  • CUPS (Rate Limit)
  1. RPC

What's CUs/CUPS

CU

Compute Unit serves as a metric for tracking your RPC request usage. Users are allotted a monthly usage quota, and each method incurs a cost corresponding to the resources needed for execution. Conceptualize this as maintaining a balance in your account, with each method having its own individual price.

Upon submission of RPC requests, the applicable cost is deducted from your account. This cost is denoted as the Compute Unit price for each RPC method. Through this approach, we empower our users to optimize their monthly request quota more effectively.

In essence, you are solely charged for your actual usage.

CUs of RPC Method

Below are the CUs for each method. We define the CUs based on the resource required for execution.

Supported Method

BSC, Ethereum, Polygon, Optimism, opBNB

Method
CUs

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

Ethereum only

Method
CUs

eth_protocolVersion

5

eth_createAccessList

10

eth_feeHistory

10

eth_maxPriorityFeePerGas

10

eth_getUncleByBlockHashAndIndex

15

eth_getUncleByBlockNumberAndIndex

15

eth_getUncleCountByBlockHash

15

eth_getUncleCountByBlockNumber

15

Polygon API

Method
CUs

bor_getAuthor

15

bor_getCurrentProposer

15

bor_getCurrentValidators

15

bor_getRootHash

15

bor_getSignersAtHash

15

eth_getTransactionReceiptsByBlock

250

CUPS (Rate Limit)

The Compute Unit Per Second (CUPS) indicates the amount of CU consumed per second during requests. Each RPC method carries a distinct weight, ensuring more efficient calculations than simply tallying the number of requests sent within a second across different use cases.

See below the CUPS for different tiers of users:

Key Type
CUPS

Free Key

300

Last updated 1 year ago

If you have any questions, please join our , or send us an email at .

Discord server
contact@4everland.org