[S2S] Server-to-Server and Canonical VCI Harmonization
Open
Nobody has claimed this yet.
server-to-server
- Dominant language
- No language data
- Stars
- 125
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Issue tracking harmonizing shared features between Server-to-Server and Canonical VCI. This should happen before the first S2S Implementors Draft
Overlapping features:
- IAE and VerificationData Request/Response
- [Deferred] Credential Endpoint and Credential Get
- Proofs / KeyData
- Credential Offer
- Notifications (wallet -> issuer)
- Credential Metadata and Credential Configurations
- Identifiers model
- Credential Versioning
- Encryption
Features that may make sense to push down from S2S to
- issuer -> wallet notifications
- lifecycle management
- Credential Status
- Asynchronous Verification/Verification Status
This is the larger issue to track this overarching effort
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the listed shared features between Server-to-Server and Canonical VCI, including verification, proofs, credential offers, metadata, identifiers, versioning, and encryption. Track which features should be harmonized or pushed down before the first S2S Implementors Draft; done means the overarching scope and agreed harmonization decisions are documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100