-
Notifications
You must be signed in to change notification settings - Fork 721
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
2547: API refactoring to move scripts into the txbody r=Jimbo4350 a=dcoutts REMOVE: Merge #2498 after this PR has been merged This is the first step in a refactoring that we will need for Alonzo support. The refactoring will put the scripts within the tx body at the sites where they are used. For Shelley era scripts we can do it either way round, but for Alonzo it makes much more sense to place the script at the use sites. So to break the Alonzo changes into steps we do the refactoring for the existing Shelley-based eras first. The ideas here have been co-authored with Jordan Millar and most of the code changes here appeared first in his Alonzo branch. - [x] Update the API tests for these API changes - [x] Update the CLI for these API changes There are a couple breaking changes: - You must specify auxiliary scripts with `--auxiliary-script-file` instead of `--script-file` - Scripts witnessing txins, certificates, withdrawals and minting must be paired with the thing they are witnessing. E.g: ``` --certificate-file $certfile --certificate-script-file $scriptfile --tx-out $txout --minting-script-file $scriptfile --withdrawal $withdrawal --withdrawal-script-file $scriptfile --tx-in $txin --txin-script-file $scriptfile ``` - Scripts are no longer specified at the tx signing stage. They are specified at the txbody stage. Co-authored-by: Duncan Coutts <duncan@well-typed.com> Co-authored-by: Jordan Millar <jordan.millar@iohk.io>
- Loading branch information
Showing
34 changed files
with
859 additions
and
631 deletions.
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.