Financial automation shouldn’t expose sensitive investor and transaction data.
A tokenized bond, for example, might only be available to investors from certain countries.
The application needs to confirm that the buyer qualifies, without making their identity or personal documents public.
It also needs to:
→ enforce restrictions on future transfers
→ coordinate delivery of the asset and payment
→ make relevant records available for authorized review
Dusk lets developers build privacy-preserving smart contracts for these workflows.
Using zero-knowledge proofs, an application can verify that an eligibility requirement is met without revealing the private information behind that check.
Selective disclosure allows specific information to be shared with authorized reviewers when needed.
The application’s design determines what stays confidential, what can be verified publicly and what authorized reviewers can access.
Explore the Dusk documentation below ↓