-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] nullifier post #1
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love the overall structure of the post but think it's way too wordy rn. That can be fixed by cutting out extraneous explanation + adding in more diagrams to break up the text
|
||
This enables applications such as [semi-anonymous message boards](https://twitter.com/heyanonxyz), since a user merely needs to prove existence of at least 1 valid signature per message in order to be sure that such a message is legitimate. However, such applications have the advantage that there is no uniqueness constraint on the provers: that is, the same wallet proving themselves as a member multiple times is intended behavior. However, there are many applications that require a maximum of one action per user, like claiming an airdrop. | ||
|
||
**One address <-> one nullifier** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think walking through why other solutions don't work is a super useful exercise, but it's just way too much text. Maybe if you did a numbered list of options? Or a table comparing each of the methods and which properties they have / don't have?
content/posts/nullifier.md
Outdated
description: "Unique pseudonymity??" | ||
--- | ||
|
||
**ZK ID systems** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Prefer not using "zk-id" term here, personal taste. Also this intro section feels bloated/wordy, perhaps it would better function as a standard paper intro where it goes through the sections of the rest of the blog post
content/posts/nullifier.md
Outdated
|
||
Note that hash has to be a function that hashes directly to the curve, meaning the output is an (x, y) pair instead of a scalar. hash2 is a traditional hash function like sha256 or posiedon. This construction assumes the discrete log problem is hard. We use exponential notation here so you can apply your usual intuitions about discrete log, but these exponentiations are actually implemented as elliptic curve multiplications. | ||
|
||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not just use a picture here of LaTeX equations? Instead of putting text in directly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yup, made it into LaTeX -- can't figure out how to properly line break and colors are annoying so might just screengrab instead
|
||
We hope that people will choose the appropriate algorithm for their chosen point on the interactivity-quantum secrecy tradeoff for their application, and hope that including this information helps folks make the right choice for themselves. Folks prioritizing shorter term secrecy, like DAO voting or confessions of the young who will likely no longer care when they’re old, might prioritize this document’s nullifier construction, but whistleblowers or journalists might want to consider the semaphore construction instead. | ||
|
||
**New usecases enabled** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This section feels like a bit of a repeat of previous examples covered. Maybe it'd be better to just mention all of these at the start and end with the definition of the nullifier?
Agree with wordiness; I think more paragraphs can be broken at natural clause breaks to make the piece punchier. But also may be too much effort at this stage and excited to see this go out! Imo not strictly necessary to do this prior to posting. |
Vivek feedback:
Aayush Response Re Tex-ing all equations is annoying due to color and layout Vivek response yeah no appendix is fine |
Things left to do
Done