Release Kaspa SilverScript Studio 0.2.8 - #5
Merged
Merged
Conversation
w00c00
marked this pull request as ready for review
August 10, 2026 07:18
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
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.
What changed
6f9e078b1d8b5389212755183b592704de99fea5, while retaining the 0.2.7 and legacy compiler profiles..ssinvitepackages, binding CAIP-2 network, program, covenant, ABI, state layout, and authorization metadata.Validation
kaspanet/silverscriptHEAD verified at6f9e078b1d8b5389212755183b592704de99fea5.npm run verify: 43/43 tests passed; all nine built-in templates fully compiled with realistic parameters; production frontend built.cargo check --lockedpassed.npm audit: 0 known vulnerabilities.Security boundary
SilverScript and Groth16 remain experimental and TN10-only. KCC721 remains pack-only and mainnet fail-closed. Compilation and local preflight are not an independent audit. RustSec still reports inherited unmaintained/unsound warnings in upstream GTK/Kaspa dependency chains; this release is not represented as zero risk.