XCIM Network status
First Amoy testnet batch finalized · No production trust network · Updated 2026-10-15
Latest specification · draft-saez-xcim-04
Experimental individual Internet-Draft. A bounded C01/SR01 testnet pilot verified consent reuse and revocation on 26 October 2026; production readiness remains open.
Reference implementation evidence
Reviewed 2026-10-26. Each row identifies its implementation scope. The 26 October C01/SR01 pilot is separate from the earlier-profile managed pilot and frozen reference fixtures. No production trust network or independent ESP interoperability is claimed.
| Capability | State | Evidence and scope |
|---|---|---|
| C01/SR01 consent lifecycle | Verified bounded testnet pilot · 26 Oct 2026 | One fresh MuMaps consent: CURRENT, cached CURRENT without renewal, incremental REVOKED and persisted REVOKED. Both anchors verified under admitted testnet trust. Same operator; pilot closed; production gates remain. |
| Company onboarding | Operational pilot | Company workspace, application setup, site DNS, signed manifest, sending-domain authority and return configuration. |
| Identity and hosted consent | Verified managed pilot | MuMaps registration uses one Google authorization, followed by a separate, optional purpose-specific consent decision. |
| Receipts and revocation | Verified managed pilot | Signed receipt issuance, authenticated API revocation and subsequent list re-evaluation were exercised end to end. |
| Managed ESP list evaluation | Verified managed pilot | Separate ESP workspace with MFA, revocable company authorization, JSON/CSV jobs, CSV/ZIP console uploads and authenticated result exports. |
| Lifecycle webhooks | Deployed; external test pending | Signed delivery infrastructure, company delivery history and recovery controls are implemented; an external receiver test remains a release gate. |
| Draft implementation artifacts | Published draft | Working Draft 02 with Erratum E1 publishes 33 unchanged schemas and corrected Python/Node tools, with 12 new E1 regression tests. Original WD-01 and WD-02 releases remain unchanged; synthetic checks are not live proof verification. |
| Public proof verification | Verified test-network snapshot | First public batch finalized on a Polygon test network: 19 events and four MuMaps proofs, checked by separate verification implementations. Historical evidence only; the five-minute status window has expired. Not mainnet or independent sender/receiver interoperability. |
| Emabled SDK distribution | Private packages tested | .NET and TypeScript integration packages have consumer tests; public npm/NuGet releases are pending. |
Managed pilot report · Shared implementation status JSON
Earlier pilot evidence is preserved in the historical test-network report. It does not demonstrate operational C01/SR01 conformance.
Identity Evidence metadata
| Field | State | Meaning |
|---|---|---|
| Identity Evidence schema | WD-02 profiles published | Explicit wire dispatch: OIDC-01 receipt 0.1, experimental EVP-01 receipt 0.2 |
| EVP-01 profile | Experimental / not network-critical | Experimental vendor-origin handoff deployed; not a receiver-time dependency |
| OIDC-01 profile | Reference implementation active | MuMaps managed pilot verified |
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.
Shared component status and remaining gates
| Component | Status | Remaining operational gate |
|---|---|---|
| Multi-issuer registry | Not public | Independent operating authority, admission review and signed lifecycle |
| Event and current-state roots | Published Amoy testnet snapshot | First batch published; ongoing fresh status requires renewed batches |
| Polygon anchor | Finalized on Amoy testnet | Batch 1 in block 50191125; no mainnet or production trust claim |
| Reference resolver | Not released | Reviewed package distribution and verification against current public evidence |
Draft tree algorithms and vectors are published. Public batch 1 adds real anchored evidence, but its expired snapshot does not establish current permission or continuous network operation.
Failure semantics
Missing sufficiently fresh current evidence produces
XCIM_STATUS_INDETERMINATE. Managed list evaluation exposes
issuer permission separately from public-proof availability.
EMABLED_CONSENT_ACTIVE must not be presented as
XCIM_PASS without verified, sufficiently fresh public evidence.
The historical test observed XCIM_STATUS_STALE after actual
expiry and XCIM_STATUS_INDETERMINATE at the cache boundary.
status.json · network-status.json · Pilot evidence · Support