XCIM Network status
Reference sandbox active · No production trust network · Updated 2026-08-13
PROTOCOLv0.1 draft
EMABLED CONSENT ISSUEROperational
HOSTED CONSENTOperational
PUBLIC KEYSPublished
SHARED NETWORKNot launched
Operational reference capabilities
- Emabled API, console and background worker are health checked on GKE.
- Hosted consent and an OIDC-backed identity-evidence path are deployed in the isolated reference sandbox.
- Receipt, relay, revocation, batch and webhook Ed25519 signing keys are managed through KMS; public verification keys are published.
- Consent manifests, signed receipts, revocation lifecycle and webhooks are implemented in the reference sandbox.
Identity Evidence metadata
| Field | State | Meaning |
|---|---|---|
| Identity Evidence schema | Drafting | Profile-neutral receipt fields are being frozen |
| EVP-01 profile | Experimental / not network-critical | Reference adapter in development; not a receiver-time dependency |
| OIDC-01 profile | Reference implementation active | Operational in the Emabled sandbox |
These fields distinguish a profile definition, a reference implementation, an external experiment and production recommendation. They are not interchangeable. The shared source is identity-evidence.json.
Unpublished shared components
| Component | Status | Publication dependency |
|---|---|---|
| Multi-issuer registry | Not public | Schema and admission policy |
| Event and current-state roots | Not public | Normative proof algorithms and vectors |
| Polygon anchor feed | Not public | Test-network anchoring profile |
| Reference resolver | Not released | Verification profile and security review |
Failure semantics
No unavailable component is represented as healthy. Missing sufficiently
fresh current state produces XCIM_STATUS_INDETERMINATE, not
an assumed pass, revocation or forgery.