-
Notifications
You must be signed in to change notification settings - Fork 748
Open
Labels
StaleVasilenhancementNew feature or requestNew feature or requestera: babbagein-scopeThis item is being worked and will be part of an upcoming releaseThis item is being worked and will be part of an upcoming releasepriority mediumissues/PRs that SHOULD be addressed. This should be done for the release, but acceptable if it doesnissues/PRs that SHOULD be addressed. This should be done for the release, but acceptable if it doesnpriority: mediumA bug that needs to be addressed after ongoing stories and tasks. For instance can be planned for neA bug that needs to be addressed after ongoing stories and tasks. For instance can be planned for netype: enhancementAn improvement on the existing functionalityAn improvement on the existing functionality
Description
Internal/External
Internal if an IOHK staff member.
Area
Plutus Related to Plutus Scripts (Alonzo).
Describe the feature you'd like
When attempting to attach a plutus script to a transaction that is already satisfying the witness requirement via reference input then we see the following error on submit:
Command failed: transaction submit Error: Error while submitting tx: ShelleyTxValidationError ShelleyBasedEraBabbage (ApplyTxError [UtxowFailure (FromAlonzoUtxowFail (WrappedShelleyEraFailure (ExtraneousScriptWitnessesUTXOW (fromList [ScriptHash "793f8c8cffba081b2a56462fc219cc8fe652d6a338b62c7b134876e7"]))))])
It would be better to catch this at build stage.
To recreate you can use --tx-in-script-file for the spend script and --read-only-tx-in-reference to a utxo with the same script as reference.
Additional context / screenshots
Node/CLI Version: 43393ac
Metadata
Metadata
Assignees
Labels
StaleVasilenhancementNew feature or requestNew feature or requestera: babbagein-scopeThis item is being worked and will be part of an upcoming releaseThis item is being worked and will be part of an upcoming releasepriority mediumissues/PRs that SHOULD be addressed. This should be done for the release, but acceptable if it doesnissues/PRs that SHOULD be addressed. This should be done for the release, but acceptable if it doesnpriority: mediumA bug that needs to be addressed after ongoing stories and tasks. For instance can be planned for neA bug that needs to be addressed after ongoing stories and tasks. For instance can be planned for netype: enhancementAn improvement on the existing functionalityAn improvement on the existing functionality