-
Notifications
You must be signed in to change notification settings - Fork 1
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
[Feature Request] Threshold multi-sig controller #42
Comments
this are interesting features, as you point out, the more complex the logic, the harder the implementation. |
Yeah, I feel like something like this could have endless use cases, particularly in a business or legal context, or something in the IoT space. I'll try to think up some concrete ones. As mentioned in #41 (comment) we can at least achieve n-of-n multi-sig with an array for One possible solution to make this (non-weighted) threshold multi-sig is a new top level property such as The more refined weighted threshold multi-sig is as I said, more cumbersome to express, at least at the top-level of the DID document. Something I need to think about - maybe that is adding too much complexity. |
apologies here too for the delay I think I should refer to the comment I left in #41 too I think we should clarify that issue before this one. Thank you again for the comments! |
I am closing the issue to keep a clean view of active ones |
As an extension of #41, m-of-n multi-sig would be useful for control over a DID.
This also is referring to control over a DID document (so perhaps
controller
array and somethreshold
to meet).Use-case examples:
Weighted votes would be even better - though this can become more cumbersome to express in a DID document (if it needs to).
The text was updated successfully, but these errors were encountered: