Release and compatibility
The current ZKNC MVP connects the TridentGold mobile wallet to a hosted issuer, status registry, and verifier. Participants can receive a synthetic credential, store it, approve a presentation, and check its status after issuer revocation.
This is an invited sandbox release using test data and test authorities. It does not issue authoritative credentials or provide a production identity or eligibility decision.
App and integration access
| Component | Access and compatibility |
|---|---|
| iOS app | Distributed to invited testers through TestFlight. Confirm the assigned version and build with your testing contact; an earlier app build may not include this credential journey. |
| Hosted verifier demo | Open the credential demo. Requires a compatible wallet and active sandbox credential. |
| Issuer and verifier APIs | Onboard with the team for the assigned endpoints, server authorization, and compatible request profile. |
| TypeScript SDK | Current implementation and package checks are complete for the four-package @human.tech/tridentgold-* bundle at 0.1.0-mvp.2. Signing and distribution are pending. See SDK installation for package names and the download/install procedure once a release is available. No public npm release or stable v1 API is announced here. |
| Android and web | Separate account and app test experiences exist. They are not a promise that this iOS credential release has equivalent coverage on those platforms. |
TestFlight processing and tester eligibility determine which app builds you can install. These docs do not announce a specific new build as available. See How to test for installation and the credential journey.
Supported scope
| Area | Current integration |
|---|---|
| Credential | Synthetic TridentGold Sandbox PCoC Attestation v1. No arbitrary schemas or authoritative Police Certificate of Character. |
| Issuance | Issuer-owned claims, private invitation, wallet holder binding, activation, and encrypted storage. No one-credential-per-person guarantee. |
| Presentation | Signed, expiring request and consent for the configured proof profile; native wallet proof generation and hosted server verification. |
| Relying-party result | Authenticated acceptance/rejection and a coarse reason. Disclosed attributes and an account identifier are not returned by the result endpoint. |
| Credential status | Signed status updates and freshness checks. Revocation is coordinated with the sandbox operator; the current SDK exposes no revocation method. |
| Trust | Configured issuer/verifier identities. A new verifier needs coordinated onboarding. |
| Connectivity | Online issuance, presentation, and status refresh. QR codes launch an online session; they do not carry an offline proof. |
The status service can observe requests for a credential's status witness in this MVP; private witness retrieval is not included. Status publication also depends on trusted sandbox operators. This release makes no production availability or independent security-audit claim.
Toward v1
The wallet and issuer → holder → verifier integration remain the path forward. Upcoming work extends the integration with stable SDK contracts, published artifacts, broader credential queries, trust onboarding, independent verifier deployment, and interoperability validation.
The current signed-session HTTP interfaces are specific to this sandbox. They do not establish full OID4VCI, OID4VP, or DCQL conformance. Prerelease interfaces may change; pin versions and review migration guidance before updating. See Architecture for the broader standards direction.