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
{{ message }}
This repository has been archived by the owner on Apr 4, 2024. It is now read-only.
I find it confusing to set it to the to address, may I know the context of this change? the receipt.contractAddress in rpc API only means the newly created contract address.
Expected behavior: semantic of receipt field should be compliant to other places.
Actual behavior: [What actually happened]
Additional info: [Include gist of relevant config, logs, etc.]
The text was updated successfully, but these errors were encountered:
yihuang
changed the title
The semantic of contract address field in receipt passed to hooks is different from ethereum
several issues with the passing receipt to hooks change
Jan 4, 2022
yihuang
added a commit
to yihuang/ethermint
that referenced
this issue
Jan 4, 2022
Closes: evmos#868
Solution:
- contract address in receipt should only be the newly created contract
- fix the order of operations in state transition
- compute contract address in `ApplyTransaction` on the fly
Closes: #868
Solution:
- contract address in receipt should only be the newly created contract
- fix the order of operations in state transition
- compute contract address in `ApplyTransaction` on the fly
Co-authored-by: Federico Kunze Küllmer <31522760+fedekunze@users.noreply.github.com>
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
System info: ethermint main
Steps to reproduce:
to
address, may I know the context of this change? thereceipt.contractAddress
in rpc API only means the newly created contract address.Expected behavior: semantic of receipt field should be compliant to other places.
Actual behavior: [What actually happened]
Additional info: [Include gist of relevant config, logs, etc.]
The text was updated successfully, but these errors were encountered: