RPC Differences

Monad aims to match the RPC behavior as close as possible to Geth’s behavior, but due to fundamental architectural differences, there are some differences listed below.

1. eth_getLogs currently have a maximum block range of 100 blocks. Because Monad blocks are much larger than Ethereum blocks, we recommend using small block ranges (e.g. 1-10 blocks) for optimal performance. When requesting more, requests can take a long time to be fulfilled and may timeout.
2. eth_sendRawTransaction may not immediately reject transactions with a nonce gap or insufficient gas balance. Due to asynchronous execution, the RPC server may not have the latest world view. Thus these transactions are allowed as they may become valid transactions during block creation.
3. eth_call and eth_estimateGas do not accept EIP-4844 transaction type, because EIP-4844 is not supported.
4. eth_call and eth_estimateGas do not accept EIP-7702 transaction type, because EIP-7702 is not currently supported.
5. eth_maxPriorityFeePerGas currently returns a hardcoded suggested fee of 2 gwei. This is temporary.
6. eth_feeHistory currently also returns default values as the base fee in testnet is hardcoded. This is temporary.
7. eth_subscribe does not support the syncing or newPendingTransactions subscription types
8. Reorganizations never occur in the newHeads and logs subscription types (for eth_subscribe) -- only real-time data for finalized blocks is presented
9. Monad-specific extensions to the newHeads and logs subcription types (called monadNewHeads and monadLogs) are provided to offer better latency