[Dijkstra] phase 1 requiredTopLevelGuards (stacked PR)
#1010
Conversation
This file contains hidden or 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 closes issue #1000.
and add TODO/reminder for `txRequiredTopLevelGuards` type change
+ Remove contradiction between "ref inputs may refer to earlier tx outputs in the batch" vs "all inputs must exist before applying any tx in the batch." The new text punts the exact constraint to the UTxO rules (where it belongs). + Fix Plutus bullet (old "nor earlier versions" reads like "no Plutus at all"). + Align fees with current Agda (`txFee : InTopLevel …`), but leave room for later CIP-driven updates.
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
5 tasks
+ a minimal `UTXOS` rule as a stub/hook (so `UTXO` can call something), + a minimal `UTXO` rule with just the new phase-1 premise (plus an explicit "calls UTXOS"), + a minimal `UTXOW`; just a wrapper over `UTXO` for now.
4 tasks
4 tasks
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.
Description
Stacked PR (please review PR #1009 before this one!)
The branch for this PR should be rebased on master once #1009 is merged.
This PR closes issue #1002 by introducing a predicate for testing that required top-level guards are present among the top-level guards and
UTXOSrule as a stub/hook (soUTXOcan call something),UTXOrule with just the new phase-1 premise (plus an explicit "calls UTXOS"),UTXOW; just a wrapper overUTXOfor now.Copilot-generated Description
This pull request introduces significant updates to the Dijkstra-era ledger specification, focusing on support for CIP-0112/0118 guard credentials, batch transaction structure, and the introduction of minimal UTxO and UTxOW transition skeletons. Major changes include updates to transaction body fields, the addition of new phase-1 structural checks for required guards, and the initial scaffolding for Dijkstra's UTxO and witnessing layers. Documentation and changelog entries have also been updated to reflect these changes and clarify the new transaction validity model.
Transaction structure and guard credentials:
TxBody.txRequiredGuardstoTxBody.txGuards(now a set of credentials, not just key hashes) and addedTxBody.reqSignerHashesfor required signers. ThetxRequiredTopLevelGuardsfield is now a list of(Credential × Maybe Datum)pairs to allow duplicates and argument passing. [1] [2]TxInforecord and construction to include the newtxGuardsand usereqSignerHashes, ensuring both phase-1 and guard credentials are available for validation.Guard request grouping and checks:
txGuards.UTxO and UTxOW transition skeletons:
UTxOandUTXOWtransition systems, with explicit phase-1 guard checks inUTXOand a stubbed-out batch processing structure. These files serve as hook points for future full batch semantics and phase-2 execution. [1] [2] [3] [4]UtxoandUtxowmodules.Documentation and changelog:
Checklist
CHANGELOG.md