docs: expand Viewing Keys article with comprehensive coverage - #1905
Open
qwenbona wants to merge 1 commit into
Open
docs: expand Viewing Keys article with comprehensive coverage#1905qwenbona wants to merge 1 commit into
qwenbona wants to merge 1 commit into
Conversation
Expands the existing 67-line stub into a full ~2300-word article covering: - All four key types (FVK, IVK, OVK, payment disclosure) - ZIP 310/ZIP 316 derivation hierarchy - Practical zec-cli commands - Compliance and audit use cases - Security considerations
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
1 participant
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
Expands the existing 67-line Viewing Keys stub into a full ~2300-word article.
New content added:
zec-clicommands for each key typeWhy:
The existing article covers only the basics (what a viewing key is + one zcashd command). The expanded version provides the depth needed for developers, compliance teams, and power users.
UA for tips: u1placeholder (will update if tipped)