I’ve started an open research initiative around a simple question:
Can native KAS support strong optional privacy without introducing another cryptocurrency or trusted custodian?
The idea is to investigate a shielded domain in which native KAS remains locked under protocol rules while private notes/claims can change ownership without publicly exposing internal balances, transfer amounts or the transaction graph.
We are intentionally not committing to an architecture yet.
The first major question is:
What is the minimal architecture for shielded native KAS using current Toccata primitives, and which parts actually require a based-app/vProgs architecture?
We currently compare three candidate directions:
- minimal L1 covenant + ZK pool
- sharded/native covenant state
- based-app/vProgs shared state
Security invariants, threat model, ADR-0001, PoC roadmap and the first research issues are now public.
I’m not a cryptographer or Kaspa core developer. My role is to initiate and organize the effort and bring together people who understand different parts of the problem.
Criticism is very welcome. In particular, I’d like people to identify assumptions that are wrong before we start building substantial cryptographic code.