Native KAS
Private claims should remain backed by native KAS. The project does not introduce a separate privacy token.
Independent · Open source
Native KAS.
Optional privacy.
Your money. Your choice of what to share.
We’re researching a way to hold and send native KAS privately — with verifiable backing and the freedom to exit without anyone’s permission.
THE IDEA
Privacy by choice.
Built on Kaspa.
Kaspa is transparent by default. Our goal is an optional shielded domain where people can hold and transfer native KAS with financial privacy.
Optional privacy
People should choose when to use privacy. The aim is to hide internal amounts and ownership links while keeping the rules verifiable.
Self-custody & decentralization
Users should control their own keys and funds, with permissionless exits and no privileged party able to approve, block or take their money.
Open source, open protocol
Specifications, code and technical decisions are developed in public. Anyone should be able to review the work, build on it and run compatible infrastructure.
Value for Kaspa L1 & miners
The design should bring activity and transaction fees to Kaspa L1 and its miners. Sustainable infrastructure must support the network it relies on.
Verifiable rules
No unbacked value. No double spending. Research and independent review should test these requirements before users are asked to rely on them.
RESEARCH LOG
Follow the work.
Loading the latest updates…
Recent work from the project’s GitHub repository.
SUPPORT THE RESEARCH
Help move the research forward.
Independent research takes time and has real costs. If you’d like to help, contributions in KAS are welcome.
Donations can cover ongoing project costs, such as the domain, VPS infrastructure, development tools and social accounts. We will transparently report how donations are used. Development funds remain separate from any protocol reserves.
Meet the supporters →Initiated by Olaf Weller. An independent, community-led initiative. Not an official Kaspa Core project.