Add ERC: Privacy Address Format #1373
Open
+653
−0
Conversation
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
A client-side address format specification for privacy-preserving tokens using zk-SNARK optimized cryptography.
Collaborator
|
The commit 6476f25 (as a parent of 2b8ec0c) contains errors. |
abcoathup
reviewed
Nov 24, 2025
abcoathup
reviewed
Nov 24, 2025
- Update eip number to assigned 8091 - Update discussions-to URL
Add documentation for potential extended use cases of the encryption public key beyond note encryption, including private messaging, encrypted metadata, cross-protocol notifications, and wallet-to-wallet communication. This addresses community feedback about whether the encryption key should be restricted to note encryption only or support general-purpose encryption. The update clarifies that implementations are free to extend the key usage while providing privacy considerations for such extensions.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
This EIP defines a standardized client-side privacy address format for privacy-preserving tokens on Ethereum. The format uses a versioned prefix (
pv+ version number) to support cryptographic evolution and future upgrades.Privacy Version 1 (pv1) is the initial version defined by this standard, using the Baby Jubjub elliptic curve for zk-SNARK optimization. Future versions (pv2, pv3, etc.) MAY adopt different cryptographic schemes, such as post-quantum resistant algorithms.
The format is designed for privacy-preserving token protocols, including native privacy tokens, dual-mode tokens, and wrapper protocols that add privacy capabilities to existing ERC-20 tokens.
Key Characteristics:
By standardizing the privacy address format at the client level, this proposal enables interoperability between privacy-preserving dApps and seamless privacy asset transfers across the Ethereum ecosystem.