AddedPlutusScriptAPI, evalScripts, TxInfo, valContext etc. #2192
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
|
@j-mueller can you have a look at this too. |
michaelpj
reviewed
Mar 22, 2021
| P.TxInfo | ||
| transTx tx = | ||
| P.TxInfo | ||
| (map transTxIn (Set.toList allinputs)) |
There was a problem hiding this comment.
Possible non-determinism alert! I guess it's probably fine... do we guarantee that the Ord instance on inputs is stable?
TimSheard
force-pushed
the
ts-txinfo-start
branch
from
dae8900
to
1d42448
Compare
michaelpj
reviewed
Mar 24, 2021
TimSheard
force-pushed
the
ts-txinfo-start
branch
from
db1ab81
to
18ad6c1
Compare
TimSheard
changed the title
|
We are past the WIP stage. I think we should merge, and workout the FakePlutus later. |
JaredCorduan
approved these changes
Mar 26, 2021
redxaxder
approved these changes
Mar 26, 2021
Added the module Cardano.Ledger.Alonzo.TxInfo Had to add SafeToHash and HashAnnotated instances for Alonxo Tx.
This module lets us experiment with small changes to the Plutus TxINfo and associated types. We made a few changes to make the structure more closely align with the actual Ledger code. Got close to completion on translating a Alonzo.Tx into a FakePlutus.TxInfo. Next step mke the changes in FakePlutus real in Plutus.
DCert, Wdrls, and others Worked out how to actually call plutus in eval_scripts.
Renamed module Caradano.Ledger.Alonzo.RunPlutus to Caradano.Ledger.Alonzo.PlutusScriptApi. Completed the ValidateScript instance for Alonzo, and the evalScripts function. Cleaned up the Utxos modue, that was way over constrained.
Renamed NativeScript constructor of Script to TimelockScript.
TimSheard
force-pushed
the
ts-txinfo-start
branch
from
68a458d
to
537aa18
Compare
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.
Added the module Cardano.Ledger.Alonzo.TxInfo
Had to add SafeToHash and HashAnnotated instances for Alonxo Tx.
This is an attempt to write the translation from Alonzo Tx to Plutus TxInfo.
There are many discontinuites between what the Ledger understands as a Tx and the information that Plutus wants included in TxInfo. This start isolates some of those differences, and is meant to start a discussion about what shoud really be in TxInfo on the Plutus side.
The next step, nce that is straightened out, is to embed TxInfo into Plutus Data.