XDC Network logo XDC Network logo

XIM Protocol · Research preview

The XDC Interledger Messaging Protocol

A verification-agnostic messaging and settlement fabric for heterogeneous ledgers, institutional networks, and financial rails.

XDC Network Research & Engineering · September 2026

Public chaine.g. Ethereum Permissionedledger Institutionalnetwork XIM MESSAGING XDC NetworkSettlement Financial railsISO 20022

Protocol thesis

“Interoperability as authenticated message exchange.”

XIM does not force every connected network into a single consensus system. Instead, it defines canonical messages, deterministic identifiers, cryptographic commitments, replay protection, verification policies, execution semantics, and acknowledgements between independently governed trust domains.

Each source–destination lane selects an explicit verification policy appropriate to the value, finality, privacy, and trust characteristics of that lane.

Core concepts

Six building blocks of the protocol

Together they let independent ledgers and institutional networks exchange value and instructions without sharing a single consensus system.

  • 01

    Canonical Messages

    A deterministic interledger envelope independent of source-chain transaction formats, with domain-separated message IDs for replay resistance.

  • 02

    Lane-Scoped Verification

    Supports native proofs, light clients, zero-knowledge proofs, threshold attestations, TEE attestations, and hybrid verification.

  • 03

    Commitment-Oriented State

    Message hashes, sparse Merkle roots, and append-only transition logs provide auditability without global replication of foreign-chain state.

  • 04

    Universal Asset Identity (UAID)

    UAID separates economic asset identity from chain-specific contract addresses and representation risk.

  • 05

    Policy-Aware Routing

    Routes are constrained by jurisdiction, asset support, privacy, verification strength, value limits, liquidity, deadline, and finality.

  • 06

    Independent Risk Controls

    Lane-scoped monitors can rate-limit, pause, or downgrade compromised lanes without globally halting unrelated routes.

Reference architecture

Separation of routing, verification, execution, settlement, and risk

Illustrative workflows

Built for cross-domain financial movement

From public chains to private institutional ledgers and ISO 20022 payment instructions, each workflow keeps verification explicit end to end.

An adapter observes source finality, builds proof evidence, commits the message, verifies on XDC, executes settlement, and emits an acknowledgement.

  1. 01Observe source finality
  2. 02Build proof evidence
  3. 03Commit the message
  4. 04Verify on XDC
  5. 05Execute settlement
  6. 06Emit acknowledgement

Authorized gateways commit to private institutional events while preserving selective disclosure and avoiding public replication of confidential transaction data.

  1. 01Authorized gateway
  2. 02Commit to private event
  3. 03Selective disclosure
  4. 04No public replication of confidential data

A gateway authenticates financial instructions, creates a settlement intent, verifies HSM-backed evidence, executes destination settlement, and returns reconciliation output.

  1. 01Authenticate instruction
  2. 02Create settlement intent
  3. 03Verify HSM-backed evidence
  4. 04Execute settlement
  5. 05Return reconciliation

Security posture

XIM does not eliminate trust. It makes trust explicit, modular, measurable, and isolatable.

Every lane declares how its messages are verified, so risk can be assessed and contained lane by lane.

  • Authenticity

    Destination acceptance requires source evidence satisfying the selected lane policy.

  • Replay Resistance

    Consumed message IDs cannot execute twice on the same destination security domain.

  • Lane Isolation

    A compromised or anomalous lane can be paused without globally halting unrelated lanes.

  • Auditability

    State transitions are reconstructible from authenticated commitments and event records.

Where it applies

One fabric for many kinds of networks and assets

  • Public blockchains
  • Permissioned ledgers
  • Institutional networks
  • Stablecoins
  • Tokenized assets
  • Trade finance
  • ISO 20022-compatible payment workflows

Implementation roadmap

Twelve-week staged minimum viable implementation

XIM is a research preview. The next stage is implementation, public test vectors, reproducible benchmarks, adversarial testing, audits, and formal analysis before production use.

  1. Weeks 1–2

    Protocol Freeze

    XIM v0.1 schema, NetworkID/UAID format, state machine, lane policy model, and test vectors.

  2. Weeks 2–5

    XDC Contracts

    MessageRegistry, VerifierRegistry, RiskManager, replay protection, and event model.

  3. Weeks 3–7

    First Adapters

    XDC and Ethereum observers/executors, deterministic encoding, and threshold-attestation bootstrap.

  4. Weeks 5–8

    Commitments & SDK

    SMT library, batch roots, TypeScript/Go SDKs, and REST/gRPC API.

  5. Weeks 7–10

    Security & Operations

    Rate limits, lane pause, key rotation, monitoring, chaos/failure tests.

  6. Weeks 10–12

    Pilot

    Ethereum–XDC testnet message transfer, asset-transfer demonstration, and benchmark report.

View the full roadmap in the paper

FAQ

Questions about XIM

XIM, the XDC Interledger Messaging Protocol, is a verification-agnostic messaging and settlement fabric for heterogeneous ledgers, institutional networks, and financial rails.

No. XIM does not force every connected network into a single consensus system. It defines how independently governed trust domains exchange authenticated messages.

Each source–destination lane selects an explicit verification policy. XIM supports native proofs, light clients, zero-knowledge proofs, threshold attestations, TEE attestations, and hybrid verification.

Lane-scoped risk monitors can rate-limit, pause, or downgrade a compromised or anomalous lane without globally halting unrelated routes.

XDC Zero supports communication between a subnet and XDC Mainnet. XIM extends this approach to heterogeneous blockchains, institutional ledgers, and authenticated financial gateways. Learn more about privacy-focused enterprise networks.

Not yet. XIM is a research preview. Implementation, public test vectors, reproducible benchmarks, adversarial testing, audits, and formal analysis come before production use.

Read the XIM research paper

By Atul Khekade, Ritesh Kakkad, Wanwiset Peerapatanapokin and Behnam Mohammadkhani, XDC Network Research & Engineering.

Content adapted from the XIM protocol site.

Need More Help?

Seeking help with setting up an XDC masternode? Access XDC documents, ask in the XDC Forum, or join Telegram's Developers community for assistance.