Rewrite Privacy on Dusk around its privacy capabilities - #149
Merged
Conversation
HDauven
approved these changes
Sep 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Refocus the privacy overview on Phoenix, Hedger, Citadel 2, and XSC. Add a concise explanation of privacy-preserving smart contracts and selective disclosure, and replace the status-focused FAQ with questions about privacy, verification, and auditing.
Remove the review date and availability column so the Learn page explains capabilities without operational-status commentary. Link component names directly to their supporting documentation.
Validation
npm run verify: 69 pages built, all internal links valid, 4 tests passed.git diff --check: passed.