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.

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

How to distinguish between witness proofs and controller proofs #114

Open
brianorwhatever opened this issue Oct 2, 2024 · 4 comments
Open
Labels
discuss Let's talk about this at our next meeting

Comments

@brianorwhatever
Copy link
Contributor

Currently the only difference between a witness proof and a controller's proof is that the witness will likely be a did:tdw. This isn't a particularly useful way to determine which is which. I think we need a better technique.. might be one reason for #66

@swcurran
Copy link
Collaborator

swcurran commented Oct 2, 2024

As I was writing this — I think the answer is that the DID of the DID Controller MUST be a did:key, and MUST be in the authorized key array. Conversely, witness did’s MUST NOT be did:key, and witness DIDs MUST be in the witness list.

A bit of data sniffing, but I don’t think outrageous. The question is whether it is better or worse than using Proof Chains, given their lack of implementations?

@swcurran
Copy link
Collaborator

@brianorwhatever -- do you want to see this added to the spec? Seems it would be useful.

@brianorwhatever
Copy link
Contributor Author

For now what I am doing is checking if the verification method is a did:tdw or did:key. tdw is assumed to be a witness and key is assumed to be a controller

@swcurran swcurran added the discuss Let's talk about this at our next meeting label Oct 22, 2024
@swcurran
Copy link
Collaborator

Action: As a clarification, without changing the version. @swcurran

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss Let's talk about this at our next meeting
Projects
None yet
Development

No branches or pull requests

2 participants