RPCs required for EVM Compatibility

[fuxingloh]

packages/testsuite-web3-rpc should contain a list of tests for ensuring EVM Compatibility. The definition of EVM Compatibility should be researched. There are a few tests included, however, more is required.

[DieHard073055]

The list of RPCs to test:

• Accounts:
  • getBalance
  • getCode
  • getStorage
  • getTransactionCount
• Blocks
  • getBlock
  • getBlockWithTransactions
• Logs
  • getLogs
• Network
  • getNetwork
  • getBlockNumber
  • getGasPrice
  • getFeeData
  • ready
• Transactions
  • call
  • estimateGas
  • getTransaction
  • getTransactionReceipt
  • sendTransaction
  • waitForTransaction

[fuxingloh]

The list of RPCs to test:

@weiyuan95 can you review this list of RPCs?

[weiyuan95]

Looking at https://github.com/paritytech/frontier/tree/master/ts-tests/tests , it looks like Substrate already has pretty good OOTB testing for compatibility for their EVM pallet, and they use web3 and ethers to test as well, which is essentially the 2 major EVM clients.

We can implement the same test logic on our end and use those tests as a 'snapshot' to guard against any potential regression we might introduce.

[DieHard073055]

Theres quiet a few tests at frontier, should I pick a subset of them which is more meaningful to us? And do you have any suggestions of what those tests should be?

[weiyuan95]

TBH, everything looks important/comes from EVM except for

• deprecated (for obvious reasons)
• netapi (not execution specific AFAIK)
• precompiles (i dont think we are using any currently, based on my convo with Webster)
• RPC constants (looks like some Frontier hardcoded values)
• web3api (looks frontier specific)

[DieHard073055]

Prasana mentioned that its important to make sure all the calls used by metamask works.