Skip to content
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.

Sign up for GitHub

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

Add text clarifying where group controllers might be listed. #883

Merged
merged 3 commits into from
Mar 26, 2025
Merged

Add text clarifying where group controllers might be listed. #883

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1b644d5
Add text clarifying where group controllers might be listed.
msporny Mar 3, 2025
8799335
Improve language around verification thresholds.
msporny Mar 20, 2025
5caf733
Clarify that multisig control to change is DID Method specific.
msporny Mar 26, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4025,7 +4025,15 @@ <h3>Group Control</h3>
In the case of group control, the [=DID controllers=] are expected to act
together in some fashion, such as when using a cryptographic algorithm that
requires multiple digital signatures ("multi-sig") or a threshold number of
digital signatures ("m-of-n"). From a functional standpoint, this option is
digital signatures ("m-of-n"). These additional thresholds for
verifying a proof can be expressed in a [=verification method=] as described in
Section [[[#verification-methods]]] or can be an intrinsic part of the
verification material of the [=verification method=], where the number of [=DID controllers=] that
participated in the generation of a particular digital signature are hidden for
privacy reasons. Verification methods that require a proof be produced by a combination of cryptographic operations performed by members of a group can be used to control the contents of a DID document; exactly how this is realized depends on individual DID method specifications.
</p>
<p>
From a functional standpoint, this option is
similar to a single [=DID controller=] because, although each of the
[=DID controllers=] in the [=DID controller=] group has its own graph
node, the actual control collapses into a single logical graph node
Expand Down