[docs] Add zk token proof program description #32011
Conversation
|
@mvines, @CriesofCarrots, @nickfrosty, I wrote some docs for the zk-token proof program. If you have any cycles to sanity check what I wrote (non-latex part), then that would be really great 🙏! I can also move the docs to somewhere else that may be more appropriate. |
| - Status: The program is in active development and is not yet available. Please | ||
| follow the feature gate `zk1snxsc6Fh3wsGNbbHAJNHiJoYgF29mMnTSusGx5EJ` for | ||
| updates. |
There was a problem hiding this comment.
Assuming we don't backport this documentation to v1.16 it seems fine to remove this status information entirely, so we don't need to remember to update it later. This PR then ships in v1.17 and by that time the program should have been activated on mainnet
There was a problem hiding this comment.
Yep, sounds good!
Co-authored-by: mvines <[email protected]>
Co-authored-by: Tyera <[email protected]>
| The simplest way to use a proof instruction is to execute it without producing a | ||
| context state account. In this case, the proof instruction can be included as | ||
| part of a larger Solana transaction that contains instructions of other Solana | ||
| programs. Programs such as the SPL Token 2022 program should directly access the |
There was a problem hiding this comment.
Do we need to call out SPL Token 2022 here?
There was a problem hiding this comment.
Hm, yeah I guess it is not necessary.
In general, I mention Token 2022 in the doc because:
- It explains the specific choice of instructions in the proof program
- People can perhaps look at Token 2022 to see an example of how proof program can be used
Here, I was intending the effect of (2), but perhaps we can remove the Token 2022 in this sentence and then we can mention to refer to Token 2022 for examples on how proof program can be used somewhere in the doc.
There was a problem hiding this comment.
Okay, I removed mentioning of Token 2022 here. I had a couple of applications like these solana-labs/solana-program-library#3984 in mind that would need to use the proof program. Perhaps we can update doc with pointers to examples that include Token-2022 and some of these applications once they are complete.
Problem
The docs do not yet contain documentation on the native zk token proof program.
Summary of Changes
Add the zk token proof program description.
The notes on range proofs, group ciphertext validity proofs, and transfer proofs will be added in follow-up PRs.
Fixes #