Iāve now launched the Kaspa Privacy Initiative.
Itās an independent, community-led effort to explore optional privacy for native KAS. And judging by the response to my previous post, thereās clearly a lot of interest in making this happen.
Iām not a cryptographer or Kaspa core developer. My role is initiator / project steward: to get the ball moving, organize the research, bring the right people together and keep pushing toward something concrete.
I also use AI extensively for research, documentation and prototyping. I think that can dramatically accelerate the work, but security-critical architecture and code will still need review from people with deep Kaspa, ZK and privacy expertise.
What I felt was missing was an open place where the community could work together toward a privacy protocol for native KAS that is not built around a new token, a company or personal gain.
No new token. No custodian. No predetermined architecture.
Weāre starting by figuring out what can already be built with Toccata, what may require vProgs, and what architecture can eventually give native KAS strong optional privacy with permissionless exits.
Everything is open from day one. If you understand Kaspa, ZK, privacy systems, wallets, security or simply see flaws in our assumptions, I want you involved.
GitHub š
github.com/olafweller/kaspa-ā¦