What works today
This sandbox exists so you can integrate the credential APIs now. Testers can collect a synthetic credential, store it in a live wallet, present a proof and refresh its status, against a hosted issuer, status registry and verifier that human.tech runs for you. You can register a schema and issue credentials of that schema using the Tenant Gateway. See Issuance through the Tenant Gateway.
What this environment is
An invited sandbox using test data and test authorities. It does not issue an authoritative credential and does not make an identity or eligibility decision. It is not production-grade, and no dependency or security review has been performed.
Who operates which service, and what that means for your role, is The current sandbox.
What you can build
| You want to | You can, today |
|---|---|
| Add wallet sign-in to your site | You can integrate Sign in with TridentGold with the RP SDK. The wallet signs the user in directly to your service. Start here. |
| Get a credential into a tester's wallet | You can register a schema and issue credentials of that schema using the Tenant Gateway. The issuer SDK is published, in the private 0.1.0-mvp.5 prerelease. Each schema also needs approval and publication by the TridentGold team before use. Read the issuer docs. Testers can already collect the synthetic police-certificate credential themselves; see How to test. |
| Check credential evidence | You can request a zero-knowledge proof with a DCQL query, and read the verified result: disclosed values, predicate results and, if requested, a nullifier. Start here. |
| Try the end-to-end journey by hand | You can install the TestFlight app, collect a synthetic credential and present it to the hosted demo. How to test. |
Scope of the sandbox integration
| Area | What is available |
|---|---|
| Credential | The synthetic schema TridentGold Sandbox PCoC Attestation v1, which is not an authoritative Police Certificate of Character, and synthetic schemas a partner organization defines on a fixed four-attribute template through the Tenant Gateway. Each partner schema needs approval and publication by the TridentGold team before use; see Defining a schema. Arbitrary schemas are not supported. |
| Issuance | Issuer-owned claims, private invitation, wallet holder binding, activation, and encrypted storage. There is no one-credential-per-person guarantee. |
| Presentation | A signed, expiring request and wallet consent for one configured proof profile; the wallet proves natively and the hosted verifier checks the proof. Verifiers choose what to request within the sandbox allowlist; see What you can request. |
| Presentation result | A verified result with the disclosed values, predicate results and, if requested, a nullifier; or a rejection category; or no answer before expiry. |
| Credential status | Signed status updates and freshness checks. Revocation is coordinated with the sandbox operator; the SDK exposes no revocation method. |
| Trust | Configured issuer and verifier identities, resolved from a signed trust list. Verifier requests go through one shared sandbox verifier; see About this sandbox. |
| Connectivity | Online issuance, presentation and status refresh. QR codes launch an online session; they do not carry an offline proof. |
| Durability | This sandbox can be reset. A reset of the sandbox status registry clears the status of every credential in it, and synthetic credentials then have to be issued again. Do not build anything that assumes a sandbox credential survives, and tell your testers the same. This is a property of the sandbox environment only. |
| Trust freshness | Every component that reads this sandbox's signed trust list or registry checkpoint refuses one more than 24 hours after it was issued, so the sandbox stops working about a day after it was last re-signed. This is a property of the sandbox environment only. |
Revocation
Issuer- and operator-initiated revocation is implemented. The registry applies the transition, the wallet shows the resulting state, and the verifier refuses a presentation against a revoked credential. In this sandbox the operator performs the revocation; ask your contact.
A holder cannot revoke their own credential in this release.
Not available yet
Android for the credential journey (the credential flow is iOS and TestFlight today). Offline presentation. Schemas outside the four-attribute Tenant Gateway template. Running your own verifier deployment. Requests under your own verifier identity, and automatic verifier onboarding. A revocation method in the SDK. A stable account identifier from a verifier result (a nullifier is stable for one scope label but is not an account identifier).
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 an active sandbox credential. |
| Tenant Gateway | Running. Your contact gives you its URL and a tenant API key. See Issuance through the Tenant Gateway. |
| Verifier API | The hosted sandbox verifier, with no key or registration, for requests within its allowlist. See Requesting and reading proofs. |
| TypeScript SDK | The six-package @human.tech/tridentgold-* bundle at 0.1.0-mvp.5, including the issuer SDK, signed and published as a private prerelease to the invited sandbox cohort; ask the TridentGold team for access. See SDK installation. There is no public npm release and no stable v1 API. |
| 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.
Toward v1
The wallet and the issuer, holder and verifier integration remain the path forward. Upcoming work extends it with stable SDK contracts, published artifacts, broader credential queries, trust onboarding, independent verifier deployment, and interoperability validation, alongside the outstanding reviews and operational work.
The current signed-session HTTP interfaces are specific to this sandbox and do not establish full OID4VCI, OID4VP, or DCQL conformance. These prerelease interfaces may change; pin versions. See Architecture for the broader standards direction.