Validate that eth_call works for reading dynamic data after it has been updated

[IvanKavaldzhiev]

Problem

We need to validate that eth_call can successfully read dynamically changed data (e.g. account balance). Let's say we have an account with zero hbar and token balance. After HAPI/precompile hbar/token transfer to this account is performed and the corresponding .rcd file ingested on mirror-node side, the balance would be updated in the PostgreSQL DB. Validate that performing eth_call read on the updated balances returns correct value.

Solution

Case 1

Create a new account in the PostgreSQL DB on mirror-node side and assert that they have 0 hbars.
Perform a transfer of hbars to this account.
Validate that eth_call retrieves the correct updated account balance.

Case 2

Create a new account in the PostgreSQL DB on mirror-node side and assert that they have 0 amount for a given fungible token.
Perform a transfer of tokens to this account.
Validate that eth_call retrieves the correct updated account's token balance.

Alternatives

No response

[IvanKavaldzhiev]

Some tests were performed with SDK calls sent to local-node instances of hedera-node and mirror-node. The results showed that hbar balance is updated directly after a transfer, while fungible token balance and nft serial number transfers did not show up until a 15-minutes delay. The delay for fungible and nft transfers should be address before releasing the EVM Module with eth_gasEstimate compatibility.