Manyfestation opened Silverscript PR #130 to support covenant state-transition decoding by producing state-tracking markers at compile time. [1] (Silverscript PR #130)
The PR records bytecode offsets for covenant output-state validation points. For normal validateOutputState, the compiler records where the next state and output index are available on the stack; for validateOutputStateWithTemplate, it also records template prefix, suffix, and hash positions. (Silverscript PR #130)
Manyfestation said his implementation is leaner than Sutton's proposal in several ways: it flattens markers per contract rather than per entrypoint, infers the validation type from custom template markers, uses a single dictionary per output-state verification, and avoids adding another state_layouts artifact. [2]
The design point is state decoding without making contract authors or decoders carry too much parallel metadata. Manyfestation said support for validateOutputStateWithTemplate could also be done by storing compiled contracts, but his approach lets the running script expose the template prefix and suffix at runtime. [1] Sutton immediately asked for a high-level comparison against the proposal, which is the right signal: this is not merged yet, but it is now specific enough to review. [3]
All sources link to public messages in the Kaspa Core R&D (public) Telegram channel.