Not every useful Kaspa builder update lands first in the core R&D channel. The local-first SilverScript Studio releases are a clean external companion to the July-August Silverscript syntax freeze.
The w00c00/kaspa-silverscript-studio project describes itself as a local-first bilingual Kaspa SilverScript contract studio. By August 10 it was already shipping v0.2.8, after the v0.2.7 line that community posts had flagged for pinned compiler support, local preflight, safer transaction building, wallet and template UX, and live TN10 testing across macOS, Windows, and Linux. (repo) (release v0.2.8)
The v0.2.8 notes are specific. The default compiler pin moves to official kaspanet/silverscript@6f9e078..., with SHA-256 verification of the compiler binary. Older pins remain available so Studio 0.2.7 projects and earlier reproducible builds do not go dark overnight. Compatibility review looks for runtime byte(...) casts and ambiguous scalar int(byte) conversions, and the release text is blunt: Studio never guesses signedness. (release v0.2.8)
The more interesting product move is versioned operation packages. New lifecycle and atomic .ssinvite files carry a canonical v1 covenant descriptor that commits to CAIP-2 network, program SHA-256, covenant ID, ABI, state layout, control-principal declarations, and operation authorization principals. Import recomputes those commitments and rejects tampering. Legacy descriptor-free packages still open, but with a visible warning. (release v0.2.8)
TN10 support is framed as experiment, not mainnet encouragement. The release adds a Groth16 proof-release template that uses official g16.verify, exact fixed-recipient payout, explicit bounded fees, and local engine preflight. Kaspa x402 is documented only as a pinned alpha interoperability profile. Its current upstream escrow is not exposed as deployable until the project is ported to current syntax, vectors are reproduced, and adversarial lifecycle tests pass. (release v0.2.8)
The release also keeps the safety language honest. SilverScript and the new template remain experimental. Mainnet stays fail-closed. Successful compilation and preflight are not independent security review. That matches the current core-channel posture around Silverscript v1: the language is moving fast enough that tooling has to pin compilers, surface breaking changes, and refuse silent reinterpretation of bytes and integers. (release v0.2.8) [1]
Read together with the core Silverscript PR storm, Studio is not the protocol story. It is the first practical answer to a predictable builder problem: if the compiler is still tightening toward v1, local tooling needs pinned toolchains, portable covenant descriptors, and explicit rejection of unsafe guesswork.
All sources link to public messages in the Kaspa Core R&D (public) Telegram channel where Telegram sources are used.