Test the end-to-end journey
Walk through sample credential issuance and presentation with the repository components.
Use the issuer, verifier, sample client, TypeScript SDK, and holder wallet to test a focused workflow—such as employee qualification checks or contractor onboarding—and identify what production would still require.
Choose one credential journey, test how the issuer, holder wallet, verifier, and client fit together, and document the gaps before deciding whether to invest in deployment.
Walk through sample credential issuance and presentation with the repository components.
See how the holder wallet, verifier, and relying-party client connect through the TypeScript SDK.
Agree success criteria and list the interoperability, security, privacy, and operational gaps before planning production.
A modular demo architecture covering issuer, verifier, holder wallet, and client SDK. The repository is a technical reference; it does not claim certification, regulatory compliance, or production readiness.
Keep the first evaluation to one credential and one relying-party journey.
Define the credential, who issues it, which wallet holds it, and which service needs to verify it.
Use the demo components to examine issuance, wallet presentation, and the verifier-facing client integration.
Record test results and the security, privacy, interoperability, operations, and compliance work still needed.
An SSI (Self-Sovereign Identity) platform enables verifiable digital credentials, with user-controlled data and service-side cryptographic verification.
OID4VCI handles issuance of digital credentials to the wallet. OID4VP handles credential presentation and verification during login, onboarding, or authorization.
It is presented as a demo and integration reference. The repository does not establish protocol conformance, EUDI Wallet or eIDAS compliance, security assurance, or production readiness. These require separate evidence and deployment-specific assessment.
Potential benefits depend on the credential, wallet, verifier, and operating model selected. This demo does not establish fraud reduction or regulatory compliance for a deployed service.
Start with the README, agree on success criteria, and use the demo to scope a focused integration pilot.