Sutton approved PR #935 on June 14 and then merged it, changing the consensus-client CovenantBinding inner type. [1] [2] (PR #935)
The PR changes kaspa_consensus_client::CovenantBinding so it wraps a new CovenantBindingInner instead of directly wrapping kaspa_consensus_core::CovenantBinding. (PR #935) The reason is consistency with other consensus-client transaction types, but the practical bug is developer-facing: a WASM getter could return a clone, then a setter on that clone would silently fail to update the original object. (PR #935)
The same PR adds native Rust and Python SDK-friendly outputs() and set_outputs() methods on GenesisCovenantGroup, while keeping the JavaScript-facing versions exposed under the expected JS name. (PR #935) That makes the change small but useful: covenant bindings behave more like the rest of the client wrapper layer and are less surprising for SDK users. (PR #935)
All sources link to public messages in the Kaspa Core R&D (public) Telegram channel.