-
Notifications
You must be signed in to change notification settings - Fork 12
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
Clarification on supported proof types #78
Comments
The VCDI deliverable description is quite different now that a few PRs have been merged. |
It's worth pointing out that even if things are not standardized under this charter I believe there's an understanding that additional proof suites can be defined and registered under the extension registry as well |
I just want to make sure that the charter itself does not say all allowed verification methods / proofs will be produced by the working group and I want to make sure the charter still allows room for innovation through a registry (process). So I guess the PR #85 should address this. |
Current charter states as follows (emphasis are mine). Will this address your concerns (that I agree with)?
|
The associated PRs which reflect the consensus of the group (and lack thereof) have been either merged or closed. Closing this Issue. |
The charter currently says:
I just want to make sure that this is not an exhaustive list and other proof types might be supported (even though they won't be standardised under this charter). We should probably add some language to the charter that clarifies that the above ^^ are concrete examples for proof types and their serializations but other are considered valid as well.
The text was updated successfully, but these errors were encountered: