<aside> ⚠️ This document is shared with 3rd-party node operators. Edit with caution.

</aside>

External link: https://bit.ly/scroll-l2geth-rpc

• Last updated: 18 January 2024. Changelog

Recommendations for RPC Providers

<aside> ❗ Scroll inherits most APIs from go-ethereum. Any destructive operations (e.g. debug_setHead) that are disabled for Ethereum should also be disabled for Scroll.

</aside>

We recommend that RPC providers expose the scroll_estimateL1DataFee custom API and disable all other scroll_ and debug_ APIs.

Furthermore, we recommend that RPC providers enable the --rollup.verify flag. See below for details.

Note: If your service supports the following tracing APIs for Ethereum, we recommend that you also enable these for Scroll.

debug_traceBlockByHash
debug_traceBlockByNumber
debug_traceTransaction
debug_traceCall
debug_traceBlock

Documented Public APIs

scroll_estimateL1DataFee

Estimates how much ETH is required to cover L1 data fee for this transaction. The transaction will not be added to the blockchain. For the transaction to be processed, the sender account must have enough ETH to cover both L1 data fee and L2 gas fee.

Parameters

• Object - the transaction call object. (Same as in eth_estimateGas.)
• QUANTITY|Tag: integer block number encoded as a hexadecimal string, or the string “latest”, “earliest”, or “pending”.

Returns

QUANTITY - the estimated amount of ETH (in wei) required for L1 data fee, represented as a hexadecimal string.