Emit covenant state tracking metadata#130
Open
Manyfestation wants to merge 1 commit into
Open
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
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.
Emit covenant state-tracking metadata
This PR records bytecode offsets for covenant output-state validation points.
For regular
validateOutputState, the compiler records where the next state and output index are available on the stack. For "with template" validation viavalidateOutputStateWithTemplate, it also records the template prefix, suffix, and hash positions.These offsets are first tracked per entrypoint using an explicit pending-marker structure, then adjusted after the compiler stitches the final contract script. The resulting artifact metadata lets state decoders replay script execution and capture the exact values needed to verify expected P2SH outputs.