Tools and access

Run the published draft checks, inspect the reference implementation and request a managed company or ESP pilot.

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.

This inventory is deliberately honest about maturity. A planned tool is a tracked deliverable, not a downloadable placeholder.

Resource Status Use
Working Draft 02 + E1 release Published for review Protocol and profiles · 33 schemas · Markdown, schemas, registries, fixtures and checks ZIP · SHA-256 manifest
Protocol documents Available Read scope, roles and publication status
Emabled company and ESP pilot Available by request Consent, receipts and authorized list evaluation ↗
Implementer source repository Draft published Review source and contribution policy ↗
Issuer public keys Published Verify reference signatures ↗
Schemas and canonical bytes Published draft Review JSON schemas and serialization notes
Test vectors Published draft Run positive and negative fixtures locally
Conformance runner Unified Python + Node Run every check locally or in CI
Historical shadow-mode header adapter, outside the corrected core Published draft Parse D-001 headers without changing delivery policy
Public artifact security scan Automated in CI Review checks and remaining manual gates
Managed pilot report Reviewed 2026-10-14 MuMaps consent, CSV/ZIP and revocation results
.NET and TypeScript SDKs Private packages tested Vendor and ESP integration clients; public npm/NuGet distribution pending. Request reviewed pilot guidance.
First public Amoy batch and proof set Published testnet snapshot Signed manifest and anchor JSON · Four public proofs · Report and transaction. Historical evidence with an expired five-minute status window; not mainnet.
Reference resolver Not released Separate verification implementations checked the Amoy snapshot; reviewed public resolver distribution remains pending
Identity Evidence profile status Published metadata Review EVP-01 and OIDC-01 maturity and delivery-mode capabilities. WD-02 adds synthetic EVP receipt projection tests; external EVP cryptographic/browser vectors remain pending
Implementation reports Opening with cohort Versioned evidence from independent implementers

Public repository and local checks

The public source keeps draft ADRs, 22 schemas, fixtures, examples and implementation-report templates together so changes remain traceable. The draft source drop is available on GitHub ↗; schemas, vectors, registries and local runners are published for review. Standalone SDKs and a resolver repository will split out only when their interfaces are stable enough to support independently.

The source drop contains XCIM artifacts and OIDC-related draft vectors. The experimental EVP-01 vendor-origin adapter is deployed in Emabled, while the WD-02 download adds explicit profile schemas and synthetic EVP receipt projection/signature fixtures. They are not external EVP conformance tests. EVP inside Emabled Hosted Consent remains unavailable; public browser/provider end-to-end evidence and independent review remain pending.

git clone https://github.com/saezbaldo/xcim-implementers.git
cd xcim-implementers
python tools/xcim_check.py

Follow the repository's dependency instructions for Python and Node. Test keys and synthetic fixtures are for local checks only.

Request access

Tell us whether you are an ESP, mailbox provider, ISP, gateway, issuer, SDK or research team, what you want to test, and who owns the integration. Companies and ESPs can request the managed consent and list-evaluation pilot. Mailbox, ISP and gateway teams can work toward a paired shadow-mode window with an independent sender. Pilot access is subject to a short technical review. Use the intake template to make the scope and evidence plan explicit.

Request Early Partner access →