Plutus V2 in the Babbage Era #2661
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
JaredCorduan
commented
Feb 18, 2022
| @@ -93,8 +93,6 @@ instance FromCBOR (Annotator Plutus.Data) where | |||
| instance ToCBOR Plutus.Data where | |||
| toCBOR = Cborg.encode | |||
|
|
|||
| deriving anyclass instance NoThunks Plutus.BuiltinByteString | |||
There was a problem hiding this comment.
It seems Plutus.BuiltinByteString no longer has a Generic instance to make this work. But it also does not appear to be needed anymore.
JaredCorduan
commented
Feb 18, 2022
| | TranslationLogicErrorDoubleDatum | ||
| | LanguageNotSupported | ||
| | InlineDatumsNotSupported | ||
| | ReferenceScriptsNotSupported |
There was a problem hiding this comment.
Note that there is no worry of breaking predicate failure serialization here in the node-to-client protocol since these errors are never raised in the Alonzo era.
JaredCorduan
commented
Feb 18, 2022
| PlutusV1 | ||
| (txEx unknownInput shelleyOutput emptyRedeemers) | ||
| TranslationLogicErrorInput | ||
| silentlyIgnore (txEx unknownInput shelleyOutput) | ||
| ], | ||
| testGroup | ||
| "Plutus V2" |
There was a problem hiding this comment.
We will need a new collection of tests in the Babbage era to replace these tests, but first we need the Babbage rules to be completed.
JaredCorduan
force-pushed
the
jc/plutus-v2-now-exclusively-babbage
branch
from
eb34593 to
2b6c79b
Compare
JaredCorduan
force-pushed
the
jc/plutus-v2-now-exclusively-babbage
branch
2 times, most recently
from
826f420 to
3603038
Compare
The use of Plutus V2 is no longer tied to the protocol major version 7, but instead the Babbage era. Moreover, the transaction context for Plutus V2 now includes Babbage specific data, and V2 is now forbidden in the Alonzo era. The txInfo function from the Alonzo era is now a class method, enabling different eras to have different behavior.
JaredCorduan
force-pushed
the
jc/plutus-v2-now-exclusively-babbage
branch
from
3603038 to
efaca54
Compare
lehins
approved these changes
Feb 23, 2022
Co-authored-by: Alexey Kuleshevich <alexey.kuleshevich@iohk.io>
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.
The use of Plutus V2 is no longer tied to the protocol major version 7, but instead the Babbage era. Moreover, the transaction context for Plutus V2 now includes Babbage specific data, and V2 is now forbidden in the Alonzo era.
The
txInfofunction from the Alonzo era is now a class method, enabling different eras to have different behavior.closes #2663