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

Implement signing mechanism for families of providers #678

Closed
willscott opened this issue Aug 18, 2022 · 3 comments
Closed

Implement signing mechanism for families of providers #678

willscott opened this issue Aug 18, 2022 · 3 comments

Comments

@willscott
Copy link
Member

We see cases where providers:

  • want to provide different data protocols at different endpoints
  • want an alias at a new node with a new identity

we should be able to handle these cases efficiently. To do so we need:

  • signing from both identities
  • message indicating the additional identity being added / removed
@willscott
Copy link
Member Author

A design is at #804

This issue should now track implementation of the spec

@willscott willscott changed the title Design signing mechanism/expectations for families of providers Implement signing mechanism for families of providers Oct 11, 2022
@momack2
Copy link

momack2 commented Nov 21, 2022

Is work happening against this somewhere? AFAIK this is going to be completed and launched by EOQ - correct?

@willscott
Copy link
Member Author

yes
@ischasny has implemented this - it's in v0.9.2 of the provider with #292
and here in #1014 - which is rolled out to the cid.contact indexers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants