Closed zaynepokt closed 5 months ago
For the Base blockchain, both Archival and Non-Archival nodes are supported. Developers can use a singular Chain Relay ID for accessing both Archival and Non-Archival data. This simplifies the process and ensures that you have access to comprehensive blockchain data without needing to switch between different Relay IDs.
Should fix a couple things, something like this:
For both the Base and Base Testnet blockchains, both Archival and Non-Archival requests are supported. Developers can use a singular Endpoint for accessing both Archival and Non-Archival data. This simplifies the process and ensures that you have access to comprehensive blockchain data without needing to switch between different Endpoints.
Base
Base is an open-source optimistic rollup built on the Ethereum blockchain. Rollups are L2 blockchains designed to enhance the scalability of layer one (L1) blockchains like Bitcoin and Ethereum. By bundling hundreds of transactions and submitting them to L1 as a single transaction, rollups significantly reduce gas fees for the end user. Base was pioneered by Coinbase using Optimism’s OP stack, marking it as the second L2 deployed on the OP Stack after the Optimism Mainnet. Its EVM compatibility ensures that developers can effortlessly deploy their EVM codebase from Ethereum and other compatible chains directly to Base. For a deeper understanding of the specific methods for Base, refer to their official documentation here.
Archival and Non-Archival Support
For the Base blockchain, both Archival and Non-Archival nodes are supported. Developers can use a singular Chain Relay ID for accessing both Archival and Non-Archival data. This simplifies the process and ensures that you have access to comprehensive blockchain data without needing to switch between different Relay IDs.
Chain Relay IDs for Supported Methods
Each blockchain we support has a specific Portal API prefix and RelayChainID, which are integral parts of our supported methods functionality. These are used to correctly route and process requests.
Supported Methods
Supported methods are API functions specific to a given blockchain, enabling interaction with its distinct features. The following is a comprehensive list of our supported methods, along with brief descriptions to understand their purpose and functionality:
eth_accounts
eth_blocknumber
eth_call
eth_chainId
eth_createAccessList
eth_estimateGas
eth_feeHistory
eth_gasPrice
eth_getBalance
eth_getBlockByHash
eth_getBlockByNumber
eth_getBlockTransactionCountByHash
eth_getBlockTransactionCountByNumber
eth_getCode
eth_getLogs
eth_getProof
eth_getStorageAt
eth_getTransactionByBlockHashAndIndex
eth_getTransactionByBlockNumberAndIndex
eth_getTransactionByHash
eth_getTransactionCount
eth_getTransactionReceipt
eth_getUncleByBlockHashAndIndex
eth_getUncleByBlockNumberAndIndex
eth_getUncleCountByBlockHash
eth_getUncleCountByBlockNumber
eth_getWork
eth_hashrate
eth_maxPriorityFeePerGas
eth_mining
eth_protocolVersion
eth_sendRawTransaction
eth_submitWork
eth_syncing
net_version
net_listening
net_peerCount
web3_clientVersion
web3_sha3
txpool_content
txpool_inspect
txpool_status