Back
KASPA.NEWS Articles
Kaspa Core R&D Channel

Infrastructure Cleanup Follows The Release

Thursday, June 11, 2026

Post-release cleanup was not only consensus work. coderofstuff raised process debt around semver practices, work tracking, old open PRs, missing issue links, and PR descriptions that make outside review harder. (source) (source)

SDK and RPC cleanup still landed without changing the release schedule. Sutton said five PRs merged that day were safe renames or outside node-level boundaries, touching only pure RPC or SDK surfaces. (source)

Mining infrastructure had its own follow-through. The group discussed consolidating maintained CPU miner repositories, with someone235 saying only one should be maintained and Elichai saying he could transfer his repo under the organization name if needed. (source) (source)

The Stratum Bridge thread also clarified that internal CPU mining flags are gated behind a build-time parameter, mainly for testnet rather than realistic mainnet use. A later status update said the in-process Stratum Bridge was stable on both mainnet and TN10, with synced nodes, accepted blocks, and internal CPU mining activity in logs. (source) (source) (source) (source)


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

More Kaspa Articles