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
Some of the tests seem to be considering empty accounts to calculate the post state root. From what I understand about the protocol, the empty accounts should be treated similar to non-existing accounts, so this would be incorrect behavior. Is there any exception to this rule I am not aware of?
A quick example to illustrate what I am talking about:
Correct final state root according to the test file (includes the empty account 0xc94f5374fce5edbc8e2a8697c15331677e6ebf0b): 0x1c57ca04dea8d4f09c81c54593838c45cf059d13dcfb9f9d70dca2bc1ad285e9
State root I would expect (not considering account 0xc94f5374fce5edbc8e2a8697c15331677e6ebf0b): 0x1531bd9ebfed425c01ab97871c2f5415683b614160c0de07e95ca46a3f8222e3
I could observe similar behavior in the following tests for all forks:
Some of the tests seem to be considering empty accounts to calculate the post state root. From what I understand about the protocol, the empty accounts should be treated similar to non-existing accounts, so this would be incorrect behavior. Is there any exception to this rule I am not aware of?
A quick example to illustrate what I am talking about:
Correct final state root according to the test file (includes the empty account 0xc94f5374fce5edbc8e2a8697c15331677e6ebf0b):
0x1c57ca04dea8d4f09c81c54593838c45cf059d13dcfb9f9d70dca2bc1ad285e9
State root I would expect (not considering account 0xc94f5374fce5edbc8e2a8697c15331677e6ebf0b):
0x1531bd9ebfed425c01ab97871c2f5415683b614160c0de07e95ca46a3f8222e3
I could observe similar behavior in the following tests for all forks:
I didn't check how the non-legacy tests are behaving.
Are the tests really expecting the correct state root?
The text was updated successfully, but these errors were encountered: