-
Notifications
You must be signed in to change notification settings - Fork 159
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
[ZIP 220] draft: User-Defined Assets and Wrapped Assets #269
Conversation
which leads to: | ||
|
||
- ZEC balance: ``v1 - v3 = valueBalance`` | ||
- BTC balance: ``v2 - (v4 + v5) = assetBalance`` |
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.
s/BTC/Asset/
|
||
.. code:: | ||
|
||
TODO: Specify GroupHash using Rescue |
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 have an elegantly awful way to specify this so that it ends up with the same \mathcal{V} generator as Sapling does when the asset is ZEC (or TAZ on testnet).
What issuance mechanisms do you have in mind, and why do they need to be whitelisted? |
cv_s1 = [v1] G_zec + [r1] H | ||
cv_s2 = [v2] G_zec + [r2] H | ||
cv_o1 = [v3] G_zec + [r3] H | ||
cv_o1 = [v4] G_zec + [r4] H |
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.
cv_o1 = [v4] G_zec + [r4] H | |
cv_o2 = [v4] G_zec + [r4] H |
This needs to be updated with my idea for how to do UDAs efficiently without a hash-to-group in the circuit. |
Withdrawing this draft ZIP, replaced by #618. |
To-do:
Part of zcash/zcash#830.