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

Automated gas consumption test: normal EOS transfer #305

Open
taokayan opened this issue Oct 9, 2024 · 1 comment
Open

Automated gas consumption test: normal EOS transfer #305

taokayan opened this issue Oct 9, 2024 · 1 comment
Assignees

Comments

@taokayan
Copy link
Contributor

taokayan commented Oct 9, 2024

Develop automated tests to verify the gas consumption are same across the following executors (including using the latest gas algorithm with custom gas parameters):

  • executor in the evm-runtime contract
  • executor in evm-node
  • executor used in gas estimation via rpc
  • executor in transaction trace
  • executor in vmTrace

for the following transactions:

  • Sending EOS to an EVM account that doesn't exist from an EOS account via trustless bridge
  • Sending EOS to an EVM account that does exist from an EOS account via trustless bridge
  • Sending EOS to an EVM account that doesn't exist from an EVM account
  • Sending EOS to an EVM account that does exist from an EVM account
  • Sending EOS to an EOS account that does exist from an EVM account via trustless bridge
@elmato
Copy link
Contributor

elmato commented Oct 16, 2024

I think we can use eth-brownie to help us with the setup of the contracts (uniswap pools, nft, etc) and also with the interaction with the EVM since all our integration tests are using python already.

We can look into hardhat.config used in eos-evm-node and also scripts.

We will be measuring the executor in the evm-runtime contract by using the balance difference and the gas price?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Progress
Development

No branches or pull requests

3 participants