The first thread after the previous cut-off was not about adding more surface area. IzioDev pushed for reducing scope and keeping the next work isolated, saying a large PR with extras like Go formatting support or account-list changes risks becoming "a monster PR that very few wants to read rigorously." He suggested reusing existing PSKT / PSKB internals instead of defining new primitives. [1]
The dependency discussion then moved to where Rusty Kaspa should stop and SilverScript should begin. IzioDev asked for current views on RK and SilverScript dependency requirements, noting that SilverScript needs RK domain-object understanding and client wrappers, while RK may want to expose compiler or higher-level SDK pieces. [2]
Michael Sutton pushed the boundary in the other direction: "if for instance the wallet requires silverscript that would be a signal that it's time to move the wallet out of rk :)." He added that other higher-level SDKs should probably live in a third repository with dependencies on both Rusty Kaspa and SilverScript. [3] [4]
IzioDev then framed a practical getting-started path: copy a SilverScript file, install minimal dependencies, wire a small Rust entry point to compile and print a genesis or funding address, then execute transitions from there. The important line was ownership: "it is essential to me that we are responsible for the wires." [5]
The review-process warning was blunt as well. After demisrael suggested using an AI agent or fleet to review a small PR, IzioDev answered that he would not approve a PR without personally inspecting every line, and Sutton added that node and wallet areas still require a diligent expert human eye, with AI only assisting PR digestion. [6] [7] [8]
All sources link to public messages in the Kaspa Core R&D (public) Telegram channel.