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

Attesting to origin-held state #130

Open
smhendrickson opened this issue Jan 3, 2022 · 0 comments
Open

Attesting to origin-held state #130

smhendrickson opened this issue Jan 3, 2022 · 0 comments
Labels

Comments

@smhendrickson
Copy link
Collaborator

A client wishes to attest with an origin that they hold something of value, maybe a subscription. To implement this in PATs there are two obvious routes:

  1. Allow the attester and origin to be the same entity. Attester can directly check for the clients subscription credentials
  2. Allow the client to pass some extra (blind?) signed value that indicates to the issuer they meet the appropriate criteria. Maybe the client got this from the origin before engaging in the PATs protocol.

Note I am assuming most origins wouldn't store traits like subscriptions directly with attesters, although some platforms could support this.

Which route to go here isn't obvious to me. (1) has a simpler flow, but requires many origins to also become attesters. (2) may require less overall changes to the architecture, but may also be adding an entity, the 3P attester, that isn't really needed for this use case.

@tfpauly tfpauly added the enhancement New feature or request label Jul 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants