Fix Address deserialization compatibility #3307
Merged
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.
Description
Starting with Babbage era it is not possible to decode a TxOut with a bad address, such as one that had trailing junk data or a Ptr address with values that are too large or trailed with junk. That being said, prior to Babbage there was a few Ptrs that violated those restrictions and thus need to be supported. This PR fixes this backwards compatibility of retaining buggy behavior for older eras:
Checklist
fourmolu
(which can be run withscripts/fourmolize.sh
)scripts/cabal-format.sh
)