-
Notifications
You must be signed in to change notification settings - Fork 102
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
multi: concretely define split commitments, add routines to generate+verify them #52
Conversation
|
||
// RootAsset is the asset containing the root of the split commitment | ||
// tree from which the `Proof` above was computed from. | ||
RootAsset Asset |
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.
Leaving this trail here, but: we could opt to just leave this out of the actual encoding as the proof file and VM context will be able to obtain this information for verification purposes. Leaving it in place for now tho.
Doesn't seem to be working properly, and we'll also need to manually handle some files due to an issue in SQL itself.
…tSet We actually want a real type here: this isn't attempting to be used for refactoring or references some external concrete type.
One other case we need to address is fully spending an input Taro UTXO using the on-chain address flow: in this case the sender no longer has an asset to use to commit to the new split set. They may need to retain a dummy zero value asset split just for that transition, then can drop it later.
cc1258d
to
15abb8e
Compare
Pushed up some commits adding bread crumbs and fixing up some of my comments from the old PR. |
…handling Fix asset commitment group handling
Split off from #27.
Fixes #3