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

Should RVPs be able to set RVs for Endorsements #302

Open
nedmsmith opened this issue Oct 3, 2024 · 3 comments
Open

Should RVPs be able to set RVs for Endorsements #302

nedmsmith opened this issue Oct 3, 2024 · 3 comments

Comments

@nedmsmith
Copy link
Collaborator

Normally, an RVP mints RVs that are applied to Evidence (only). The question is raised whether it is meaningful if an RVP could also mint RVs for Endorsements.

Note: It is possible for an Endorser to endorse another Endorser's Claims using conditional endorsements so long as the condition expressions are permitted to use possible state expressions.

The current spec is silent. That is to say, the cmtype of the condition ECT is not specified.

@deeglaze
Copy link
Collaborator

deeglaze commented Oct 4, 2024

If cosigning endorsements is always an endorsement, can we say that a conditional endorsement can have optional additions, such that the meaning is just to add the CoRIM issuer's authority to the condition environment/measurement as an endorsement cmtype, or is that too punny?

@nedmsmith
Copy link
Collaborator Author

can we say that a conditional endorsement can have optional additions, such that the meaning is just to add the CoRIM issuer's authority

I believe all forms of endorsement triples allow this already. Even if the condition included authorized-by (used for matching). The addition wouldn't include the matched authority. Even if the addition included authorized-by, that would represent something else in the internal representation than authority.

@nedmsmith
Copy link
Collaborator Author

environment/measurement as an endorsement cmtype

Maybe I'm not following? The triple's predicate determines its cmtype. Otherwise, the cmtype is known to the Verifier as the various inputs are accepted and validated (phase 0 / 1), even if the inputs aren't expressed as CoMID triples. The output from processing an Endorsement triple is still an endorsement. This is true even when an endorsement condition searches over Evidence, corroborated RVs, or other Endorsements.

The question can be recast in terms for whether there is something like "corroboration" for Endorsements. Given the purpose of corroboration is to convert reference state into actual state, applying this to endorsements seems unnecessary since endorsements are defined to be actual state already.

The subtlety may be that for RVs, the totality of the inputs represents more Evidence states than are present in an ACS. While for Endorsement, the conditions describe a search space that is restricted to an Attester's actual states (even though the search may include corroborated RVs and other Endorsements).

I think this means that for RV processing, there's an outer loop of RVs (reference states) that is applied to an inner loop that iterates over the ACS entries.

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

2 participants