spec(v1beta0): specify policy reference-script attachment in the core#334
Merged
Conversation
§7.13.4 deferred the `script`/`ref` field semantics to §8, but §8 never described them. A ref-backed policy contributing a read-only reference is a normal extended-UTxO artifact — the same "referenced but not consumed" UTxO already defined chain-agnostically in §7.6 — so it belongs in the core, not the Cardano section. Specify it in §7.13.4: a policy whose script lives at a `ref`, used where its script executes (an input's `from`, or a mint/burn policy), causes that `ref` UTxO to be referenced (not consumed) by the transaction; an output recipient or signer does not. Cover dedup and the hash-only case. Narrow the remaining chain-specific pointer to the script-kind and witness details (§8.4, §8.5). Fix the §4.2.4 field-semantics pointer (was §7.10, the metadata section). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
scarmuega
force-pushed
the
spec/policy-ref-reference-input
branch
from
18dc75c to
bdb4b36
Compare
scarmuega
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Documents the behavior shipped in #332 / #333 and closes a dangling forward-reference in the spec.
Problem
§7.13.4 (
policy) said "the semantics ofscriptandreffields are chain-specific and are described in §8" — but §8 never described them. The spec had no statement of what a policy'srefdoes.Approach
A ref-backed policy contributing a read-only reference is a normal extended-UTxO artifact — the same "referenced but not consumed" UTxO already defined chain-agnostically in §7.6. So it's specified in the core (§7), not the Cardano section. Only the genuinely chain-specific residue — how the script contents are interpreted and witnessed — stays in §8.
Changes
policy) now states: a policy's script executes when used as an input'sfromor amint/burnpolicy; in that case aref-backed policy'srefUTxO is referenced (but not consumed), per §7.6, so the script is available for validation. Used only as an output recipient (to) or signer, it does not. Covers dedup (against §7.6 blocks and repeated uses) and the hash-only case. The remaining chain-specific pointer is narrowed to the script-kind/witness details (§8.4, §8.5).🤖 Generated with Claude Code