Evidence package
Operational-readiness evidence for the EPICORTEK Supplier Trust Demo prototype.
L1Demo mode — seeded snapshot of publicly available business registry data. Production integration would require an authorized live source.
L2Mock OID4VCI / OIDC flow for demo. Sign-In Canada / GCKey are referenced as future integration context only.
L3W3C-compatible demo status-list encoding — GZIP-compressed Bitstring Status List in production (Milestone M3)
L4Demo selective disclosure (server-enforced) — cryptographic SD-JWT VC in operational testing (Milestone M6)
L5OID4VP-style simulator — conformant OID4VP in operational testing (Milestone M7)
L6Demo polling: 10 s. Production target: 60 s.
- Generated at
- 2026-10-16T03:32:25.933Z
- Base URL
- https://trust-demo.epicortek.com
- Issuer DID
- did:web:trust-demo.epicortek.com
- KID
- demo-issuer-key-1
Latest credential
- Credential ID
- 96f30337-dbc1-4687-a865-166f8ae71e5e
- Supplier
- EPICORTEK Technologies Inc.
- Status
- True
- Issued at
- 2026-10-08T16:23:22.666Z
- Expires at
- 2027-10-08T16:23:22.000Z
cheqd anchor
- DID
- —
- cheqd anchor
- CHEQD_DID not configured
Endpoint health
/.well-known/did.jsonOK
/.well-known/jwks.jsonOK
/api/status-listOK
/api/did/resolveOK
/api/credential/public/96f30337-dbc1-4687-a865-166f8ae71e5eOK
/api/verify/96f30337-dbc1-4687-a865-166f8ae71e5eOK
Demo steps
Issued✓
Badge rendered✓
Signature valid✓
Revoked–
Red detected–
Metrics
- Issuance time ms
- 17 ms
- Badge render time ms
- 76 ms
- Revocation requested at
- —
- Revocation detected at
- —
- Revocation detection seconds
- —
Flags
- Signature valid
- True
- didResolved
- True
- cheqdResolved
- False
- Status checked
- True
- Status-list signature present
- True
- Client-side verification enabled
- True
- Credential source
- data-vc-url
Evidence Anchoring
Only non-sensitive evidence hashes are prepared for anchoring. Supplier data and credential contents are not written on-chain.
No anchor prepared for this credential.
To prepare an anchor: POST /api/evidence/anchor { credentialId }
Anchoring not configured
Set CHAIN_ANCHOR_MODE=enabled with an endpoint and wallet to enable real on-chain anchoring.
Known limitations
- Uses seeded demo supplier registry data.
- Uses mock OID4VCI/OIDC flow.
- Uses W3C-compatible demo status-list encoding; production uses GZIP-compressed Bitstring Status List.
- Uses server-enforced demo selective disclosure; production uses cryptographic SD-JWT VC.
- Uses OID4VP-style simulator; production uses conformant OID4VP.
- cheqd testnet anchor is optional and anchors issuer identity only.
- Operational testing requires PSPC-authorized live source integration.