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
I'm not an Ethereum expert.
In following explain, if I was wrong, please point that.
With my limited knowledge, I think the global state has no relation with the sender of a contract when the contract doesn't save any information about the sender into storage.
There are still some strange logs that need to be investigated, but they are not part of this issue.
If I found any further results, I will create another issue.
Current Behavior
I'm not an Ethereum expert.
In following explain, if I was wrong, please point that.
With my limited knowledge, I think the global state has no relation with the sender of a contract when the contract doesn't save any information about the sender into storage.
Let's check the
Metadata
contract:axon/builtin-contract/metadata/contracts/metadata.sol
Lines 63 to 65 in e719adb
Before 10 minutes, I have been told the solc contract is not used.
Check the following contract:
axon/core/executor/src/system_contract/metadata/mod.rs
Lines 42 to 47 in e719adb
It doesn't save the sender.
But, in the following unit test, the different senders will lead to different
state root
(CI checks is passed).axon/core/run/src/tests.rs
Lines 37 to 54 in 1c6af01
So, I doubt that whether the calculation of
state root
is incorrect.p.s. The accounts of both two senders used in the unit test are empty, so no state for their balance should be existed.
Expected Behavior
The state root should be the same if only the sender is different but the sander is not saved into state.
The text was updated successfully, but these errors were encountered: