Silverscript Moves Toward A Real v1 Gate

Silverscript also picked up concrete pre-release work. saefstroem asked why compile_checkdatasig_call simply dropped all arguments and pushed OpTrue when Kaspa does not have that opcode; someone235 answered that the opcode should be deleted and replaced by checksigfromstack. ^{[1] [2]}

When asked whether Silverscript was stable enough to use, someone235 said: "I'm going to release an official v1 soon." He also said OpZkPrecompile support was expected "in the coming week." ^{[3] [4] [5] [6]}

The more important bug report was about fixed-length entrypoint arguments. saefstroem showed a byte[4] contract where tag.length == 4 compiled into a no-op-style 4 == 4 check instead of using OpSize, meaning longer input could still pass. ^[7]

someone235 listed three options: document the behavior, make x.length use OpSize while adding a separate type-length accessor, or validate entrypoint input lengths at script start. Sutton said a developer who specifies a fixed length or struct expects that boundary to be validated, and someone235 leaned toward the full input-checking path, at least before adding advanced opt-outs later. ^{[8] [9] [10]}

Sutton marked the related Silverscript work as mandatory before release, and someone235 opened the tracking issue. ^{[11] [12]}

All sources link to public messages in the Kaspa Core R&D (public) Telegram channel.