Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ContractID's in record result don't resolve EIP-1014 addresses correctly #2922

Closed
tinker-michaelj opened this issue Feb 26, 2022 · 1 comment
Assignees
Labels
Bug An error that causes the feature to behave differently than what was expected based on design.
Milestone

Comments

@tinker-michaelj
Copy link
Collaborator

Description

  • When calling a contract with an EIP-1014 address, the contractCallResult.contractID has a nonsensical X.Y.Z form derived from parsing the EIP-1014 address as a "mirror" 0x00..00X address.
  • When logging an event from within a contract with an EIP-1014 address, the contractLogInfo.contractID has the same nonsensical X.Y.Z form.

Steps to reproduce

Call and log events from within a contract created with CREATE2.

Additional context

No response

Hedera network

testnet

Version

v0.23.0

Operating system

No response

@tinker-michaelj tinker-michaelj added the Bug An error that causes the feature to behave differently than what was expected based on design. label Feb 26, 2022
@tinker-michaelj tinker-michaelj added this to the 0.23.1 milestone Feb 26, 2022
@tinker-michaelj tinker-michaelj self-assigned this Feb 26, 2022
@tinker-michaelj
Copy link
Collaborator Author

Fixed by #2919.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug An error that causes the feature to behave differently than what was expected based on design.
Projects
None yet
Development

No branches or pull requests

1 participant