Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Telos reth integration test #23

Open
3 of 6 tasks
rozzaswap opened this issue Jun 12, 2024 · 1 comment
Open
3 of 6 tasks

Telos reth integration test #23

rozzaswap opened this issue Jun 12, 2024 · 1 comment

Comments

@rozzaswap
Copy link

rozzaswap commented Jun 12, 2024

Things to ensure we include in both the container and in the integration test:

  • Make sure we have a create & openwallet action in the container, and an assertion about their nonces in the test
  • Call approve on an erc20 contract twice with the same value. This should put duplicate/identical state diffs on the tevm side so we can test that we handle it properly (revm won't give us the 2nd duplicate since no state was actually changed)
  • Check that block number in a solidity contract is the same as the RPC for that transaction. Both in the container for sync as well as after we are live using an alloy test.
  • Blocks with various combinations of doresources, setrevision and regular transactions all in the same block. Mostly resources and transactions, as gas price changes with doresources, we should make sure that we use the correct gas price when the transaction happens before and after the gas price change. Also should test replay/trace transaction methods to ensure they use the correct gas price and revision number as well
  • Send 2930 AND 1559 transactions in the live test and assert failure, these should be rejected by the EVM contract and/or by the RPC
  • Send incorrect RLP encoded transactions (trailing zero values, the value field as leading zero, etc..)
@poplexity poplexity changed the title Write tests for telos reth Telos reth integration test Sep 18, 2024
@poplexity
Copy link
Member

Hijacking this issue to collect things that we should add to the docker container and to the integration tests assertions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants