Correct the specification of the flat encoding of constr
tags
#7154
+20
−16
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.
Fixes cardano-scaling/cardano-blueprint#32
Fixes https://github.com/IntersectMBO/plutus-private/issues/1620
The specification said that tags in
constr
terms should be encoded using a bitstring of length 64. This isincorrect: they should be encoded using the standard variable-length encoder for natural numbers.
See also #7149, which made the textual parser check tag values more carefully.