-
Notifications
You must be signed in to change notification settings - Fork 59
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
EOF smart contracts support #903
Conversation
# Conflicts: # evm_loader/program/src/error.rs # evm_loader/program/src/evm/eof.rs
# Conflicts: # evm_loader/program/src/evm/validate.rs
opcode table improvement
EOF optimization
Added EOF tests
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that to test this EIP, a couple of tests with deployment and interaction with the contract via execute_transaction_steps_from_account will be enough. I suggest placing these tests in a separate file. Using execute_transaction_steps_from_account will be sufficient to test the new binary format. There is no need to test all contracts currently used in tests for the new format. A eof-contract can be placed in an existing pytest.CONTRACTS_PATH directory.
db12972
to
e134af6
Compare
* Fixed test_call_contract_function_with_neon_transfer test
@anton-lisanin I don't have questions about tests. |
# Conflicts: # Dockerfile # evm_loader/program/src/evm/mod.rs # evm_loader/program/src/evm/opcode.rs # evm_loader/program/src/evm/opcode_table.rs # evm_loader/program/src/evm/stack.rs # tests/conftest.py # tests/utils/contract.py
The CI run of PR requires the passing of secret variables. |
No description provided.