XCIM Protocol status
The corrected consent Internet-Draft is published, 20 October 2026. The corrected protocol concerns explicit recipient-to-sender consent, independently attested and blockchain anchored. Earlier implementation and test results below describe historical work; they do not establish conformance to the corrected revision.
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.
Historical Working Draft 02 + E1 with a 30-schema catalog, version matrix, profile documents and compatibility policy. Those historical requirements do not establish C01 conformance. The separate 26 October C01/SR01 pilot is identified below.
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.
Implemented by the reference issuer
Emabled, the managed XCIM Consent Issuer operated by We Are 14 Inc., runs an isolated XCIM sandbox. Its implementation provides:
- Public operator console with OIDC authentication, hosted XCIM consent handoff, onboarding and MFA controls.
- Application registration, versioned consent manifests and an OIDC-01 identity-evidence path.
- Signed consent receipts, revocation lifecycle processing and webhook delivery infrastructure.
- Ed25519 keys held and used through Google Cloud KMS, with the public issuer key set available at api.emabled.com.
- Isolated Cloud SQL persistence, background workers, least-privilege workload identities and health-checked services on GKE.
Historical Identity Evidence architecture
The earlier working drafts explored identity-evidence profiles independent of OAuth client identity. Their implementation status is retained below as historical evidence, not as C01 conformance:
- EVP-01 - experimental Email Verification Protocol evidence.
- OIDC-01 - OpenID Connect evidence.
The profile-neutral Identity Evidence layer is implemented. OIDC-01 was exercised in the MuMaps managed pilot. EVP-01 has an experimental vendor-origin handoff adapter deployed, while the Emabled-hosted EVP mode remains unavailable. WD-02 publishes both profile documents and version-dispatched schemas; a public EVP end-to-end result and external review remain pending. Profile status is maintained in the shared source.
Corrected consent protocol
- Explicit recipient-to-sender consent for precisely identified communication types.
- Third-party attestation of address control and a separate affirmative decision.
- Immutable blockchain evidence with revocable current consent.
- Message-independent verification; no required XCIM mail headers, MP/MSA, DKIM processing or SMTP replay state.
Implementation evidence and remaining work
The 26 October 2026 live C01/SR01 pilot verified real consent, unchanged reuse and incremental revocation with a separate receiver and admitted Polygon testnet adapter. Production hardening, historical anchor refresh, recipient workflows, scale and independent interoperability remain open. The frozen local reference suite retains its test-only adapter and cannot independently establish a public positive result; its limitations must not be transferred to the separate live implementation.
Document index · Implementation guidance · Public network status ↗