preserve Alonzo script integrity hash bug #2730
Merged
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
In the Alonzo era, the map of languages to cost models was mistakenly encoded using an indefinite CBOR map (contrary to cannonical CBOR, as intended) when computing the script integrity hash. For this reason, PlutusV1 remains with this encoding. Future versions of Plutus, starting with PlutusV2 in the Babbage era, will use the intended definite length encoding. PR #2703 accidentally reversed this Alonzo bug, this commit restores it.
lehins
approved these changes
Apr 18, 2022
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.
In the Alonzo era, the map of languages to cost models was mistakenly encoded using an indefinite CBOR map (contrary to canonical CBOR, as intended) when computing the script integrity hash.
For this reason, PlutusV1 remains with this encoding. Future versions of Plutus, starting with PlutusV2 in the Babbage era, will
use the intended definite length encoding.
PR #2703 accidentally reversed this Alonzo bug, this commit restores it. See https://github.com/input-output-hk/cardano-ledger/pull/2703/files#diff-600ae5ce75fa519690c6b948aa3c3453878235d279c5b800efe49e79d2927363L494-L500