Skip to content
This repository has been archived by the owner on Apr 4, 2024. It is now read-only.

several issues with the passing receipt to hooks change #868

Closed
yihuang opened this issue Jan 4, 2022 · 0 comments · Fixed by #869
Closed

several issues with the passing receipt to hooks change #868

yihuang opened this issue Jan 4, 2022 · 0 comments · Fixed by #869

Comments

@yihuang
Copy link
Contributor

yihuang commented Jan 4, 2022

System info: ethermint main

Steps to reproduce:

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.]

@yihuang 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
fedekunze added a commit that referenced this issue Jan 4, 2022
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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant