feat: seperate target address and the code address #553
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bajpai244
force-pushed
the
feat/seperate_to_and_code_address
branch
2 times, most recently
from
4d47c59
to
256d59f
Compare
bajpai244
force-pushed
the
feat/seperate_to_and_code_address
branch
from
256d59f
to
40fd703
Compare
bajpai244
changed the title
Eikix
reviewed
Nov 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request type
Please check the type of change your PR introduces:
What is the current behavior?
The separation of target address and the code address are not supported, this PR adds support for this and fixed the bug to resolve
toaddress correctly.Resolves: #551 #552
What is the new behavior?
toaddress is now resolved.Does this introduce a breaking change?