You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently have an issue to track using EIP1559 #1952 however this might bring some unexpected behavior therefore the fix was not implemented in the PR above.
One of the following solution should be considered and then the test can be enabled back:
Move away from anvil and use a evm localnet that support pre-EIP1559 txs (although it seems Anvil is the most reliable option and geth doesn't support custom chain ID)
Implement EIP1559 as per the issue above
Use a patched version of Anvil in the future
This test should be considered to be added the next time we integrate a new EVM chain (we need to fix about adding it to the epic if we create a new epic for a chain intergration)
The text was updated successfully, but these errors were encountered:
The PR: #1900 add a new
TestMigrateChainSupportName
E2E test for chain migrationThis test is currently commented out in the list of admin E2E tests to run in
cmd/zetae2e/local/local.go
for the following reasons:We currently have an issue to track using EIP1559 #1952 however this might bring some unexpected behavior therefore the fix was not implemented in the PR above.
One of the following solution should be considered and then the test can be enabled back:
This test should be considered to be added the next time we integrate a new EVM chain (we need to fix about adding it to the epic if we create a new epic for a chain intergration)
The text was updated successfully, but these errors were encountered: