[ZIP TBD] Shielded Voting Wallet API - #1244
Open
czarcas7ic wants to merge 7 commits into
Open
Conversation
Standalone wallet API specification covering vote discovery, chain query endpoints, delegation/vote-cast transaction wire formats, helper server share submission, commitment tree sync, and nullifier retrieval version selection. Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Claude <noreply@anthropic.com> Made-with: Cursor
Add high-level summary, unify vote servers, consolidate version handling, add vote_round_id encoding table, and clean up open issues. Co-Authored-By: Claude <noreply@anthropic.com> Made-with: Cursor
- Add upgradeability requirement for protocol components - Rename vote_circuits to vote_protocol, add tally version field - Update vote_server description to cover REST API only - Add versioning overview to high-level summary with circuit upgradeability note - Replace semver reference with simple major version scheme - Update rationale, validation rules, and version handling sections Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Claude <noreply@anthropic.com>
czarcas7ic
changed the title
czarcas7ic
changed the title
czarcas7ic
changed the title
czarcas7ic
marked this pull request as ready for review
March 30, 2026 14:17
This was referenced Apr 17, 2026
Round-level display text is served by the chain round response and provides no cryptographic binding in the configuration document, so the configuration schema does not carry it.
Round-level title and description were struck earlier because they are not per-proposal content and the chain is authoritative. Per-proposal description is different: it is user-facing content that should be hash-protected alongside title and options, so a tampered config cannot display a different description than what is committed on-chain. Also specifies that forward slashes must not be escaped (to match the byte output of common Rust / Go JSON encoders) and that non-ASCII bytes are emitted as UTF-8, not `\uXXXX`. These were implicit before and caused divergence between wallet implementations; pinning them in the spec eliminates interop risk. Updated the Vote Configuration Format example, the field-definition table for `proposals`, the canonical-form prose, and the worked example (including its SHA-256 preimage output).
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
draft-valargroup-shielded-voting-wallet-api.md) specifying the REST endpoints, JSON wire formats, and discovery mechanism for wallet integration with shielded on-chain voting.