XCIM interoperability

Public evidence for implementers testing the XCIM draft across sending, receiving, Identity Evidence and infrastructure roles.

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.

PROGRAM: IMPLEMENTERSPROFILE: v0.1 DRAFTPUBLIC INTEROP EVENTS: NOT STARTEDUPDATED: 2026-11-10

C01/SR01 live pilot · 26 October 2026

One fresh MuMaps consent produced CURRENT, a cached CURRENT recheck, an incremental REVOKED result and a persisted REVOKED recheck. Both commitments were verified on Polygon testnet. This was a project-operated test ESP and separate receiver; no email was sent.

Read the results, signing incident, trust boundary and production gates.

Deploy to Agents · receipt and CSV pilot · 10 November 2026

A newly configured site retained signing across a backend restart, verified its earlier receipt, obtained a new receipt and completed a two-row ESP CSV evaluation. One contact had matching Emabled permission; the control had no evidence. The matching row’s public proof was unavailable. Same project operator; earlier-profile result, not C01/SR01 conformance.

Read the implementation report and its limits · Choose Company or ESP guidance

MuMaps managed pilot · 2026-10-14

An operator-managed application and ESP pilot completed the permission lifecycle using the Emabled reference issuer. MuMaps and the ESP workspace in this pilot are controlled by the project operator; this report does not count as independent sender/receiver interoperability.

  1. Company setup: site DNS, signed consent manifest, sending-domain authority, application return and Google integration configured.
  2. Registration: the person chose a Google account and continued directly to Emabled preferences through one Google authorization.
  3. Consent: optional purpose-specific permission was recorded separately from registration, with signed receipt and return bindings verified.
  4. ESP: a separate workspace with MFA received a company authorization scoped to the application, purpose, domain, validity period and list budget.
  5. Lists: CSV and ZIP uploads produced an EMABLED_CONSENT_ACTIVE row and an XCIM_NONE control; authenticated exports were checked.
  6. Revocation: the authorized application API revoked the selected purpose. Re-evaluation of both files produced XCIM_REVOKED and the unchanged XCIM_NONE control; both exports were checked.

This records a managed issuer permission test with OIDC-01. No recipient identifiers, tokens or private receipts are included in this report. An active issuer result alone does not establish public XCIM_PASS. The separate public Amoy verification below adds historical proof evidence; it does not retroactively turn this CSV/ZIP permission test into a fresh public-proof test. A recipient self-service portal and independently operated receiver are outside this pilot.

Versioned pilot and capability metadata · Request a company or ESP pilot

First public batch on Polygon Amoy: historical earlier-profile evidence

Published 2026-10-14: Emabled batch 1 commits 19 issuer events and publishes 4 MuMaps proofs: 3 active and 1 revoked at publication. The anchor is finalized in block 50191125.

Testnet, not mainnet. Polygon Amoy (chain ID 80002) is an experimental network. This is a frozen historical snapshot, not a live permission feed, issuer accreditation or a production trust network. Independent sender/receiver interoperability is not established by this pilot. This snapshot predates C01 and does not demonstrate the corrected protocol.

Freshness: the signed status window ran from to (five minutes). That window has expired. The anchor remains historical evidence; current permission needs fresh anchored status. Downloading this batch again does not renew it.

Verification results and limits

On 2026-10-14 at 21:36:08 UTC, a separate receiver and a Python implementation checked public HTTPS downloads without an Emabled session or SQL access. Checks covered Ed25519 signatures with separate role pins, canonical objects, Merkle inclusion, sparse current state, bindings and the anchor, corroborated through two RPC providers.

Historical verification observations, not live permission results
CaseObserved result
Three active control receipts within the signed windowXCIM_PASS
One revoked control receiptXCIM_REVOKED
Valid cached bundle; source unavailability injected in the receiverXCIM_PASS_CACHED
Altered Merkle pathXCIM_LOG_PROOF_FAIL
Cache evaluated at the end of the freshness windowXCIM_STATUS_INDETERMINATE
Previously active bundle checked after actual expiryXCIM_STATUS_STALE

The 19-event issuer log contains 18 receipts and one revocation; the published MuMaps proof set contains four proofs, not a proof for every event. The three active control receipts concern the same identity, not three customers. No production outage was induced for the cache test.

Trust was explicitly pinned by the receiver. This result does not establish issuer accreditation, independent sender/receiver interoperability, mainnet readiness or a production SLA. A fresh CSV/ZIP public-status replay is a separate gate requiring fresh anchored evidence and valid ESP authorization.

Current evidence

Interoperability program state
Capability State Evidence Next gate
XCIM Consent Issuer Operational sandbox; managed pilot verified Emabled public issuer surface ↗ Pair with an independent implementation
Hosted consent and receipts Implemented by Emabled Public keys ↗ Pair with an independent implementation
Identity Evidence schemaWD-02 profiles publishedIndependent protocol draft and schema catalogExternal profile review and EVP end-to-end vectors
OIDC-01 adapterVerified managed pilotMuMaps consent, receipt and list evaluationIndependent implementation test
EVP-01 experimental adapterExperimental vendor-origin handoff deployedDelivery-mode capabilities; no public EVP end-to-end resultPublish reviewable end-to-end evidence
Self-test suite Published draft Unified Python + Node runner with deterministic fixtures Recruit independent sender and receiver
Independent sender No public result yet No implementation report published First ESP cohort
Independent receiver No public result yet No implementation report published First mailbox-provider cohort
Interop-tested pair Not started Two independent implementations required Run a paired test window

What qualifies as evidence

A public result must name the exact draft, implementation version, role, profile, test date, vectors exercised and known limitations. A logo, sandbox account or private demonstration is not an interoperability result. One EVP site working does not establish XCIM interoperability.

Receiver boundary

Receivers do not need to validate EVP or OIDC for every message. Identity Evidence is validated by the XCIM Consent Issuer at grant time; the receiver validates the signed receipt, current state, bindings and local trust policy.

Test windows

The schemas, positive and negative fixtures, and local runners are published for draft review. The first cohort and paired test dates will be announced as independent sender and receiver teams join; teams can request sandbox access and review the Implementers Program ↗.

Machine-readable interop status · Implementation matrix · Tools and access ↗