A working comparison of IAEX against the systems that today carry pieces of the world's economic state — and the layer none of them provides.
A one-line position against each. The detail follows below.
A closed cooperative for one industry. IAEX is open infrastructure for every industry, with the same tamper-proof guarantees and stronger causal proof.
Tamper-proof through public consensus and a token. IAEX achieves tamper-proof through hash-sealed events and sovereign routing — without a coin and without forfeiting residency.
A vocabulary, hard-won within an industry, brittle across industries. IAEX deliberately is not a vocabulary — it is the substrate any vocabulary can ride on.
The status quo: bilateral, expensive, unverifiable, the source of the fragmentation problem. IAEX replaces the bilateral integration with one-time participation in a network.
A peer-by-peer view. None of these systems is wrong — each is shaped for its own purpose. IAEX is shaped for a different one.
A globally adopted messaging cooperative for cross-border bank instructions. Standardised message types, member-only network, and decades of operational reliability inside finance.
Bound to banking. Operates a single global pipe; residency is layered, not native. Records messages but does not seal causal chains across non-bank parties.
IAEX is universal — it carries any economic event, not only bank instructions. It is sovereign by routing, not by configuration. And it provides causal proof across every party in a transaction, not just the financial leg.
Tamper-proof state without a single trusted operator. Open participation, public verification, and a track record for digital-asset settlement.
Public ledgers are incompatible with sovereign data residency. Token economics become an institutional adoption barrier. Throughput and cost are bound to consensus mechanics, not to event volume.
IAEX provides tamper-proof guarantees through hash-sealed events rather than global consensus, with no token and regional sovereignty by construction. Cross-region linkage is by hash reference — never by replication.
Hard-won, mature semantic standards for retail, logistics and adjacent supply-chain documents. Carry real interoperability inside the industries that adopted them.
Each is anchored in a single industry's worldview and resists generalisation. Onboarding is heavy, version churn is constant, and they say nothing about identity, time, sovereignty or causal sequence.
IAEX is not a vocabulary — and refuses to become one. It is the layer beneath GS1, EDI, UBL, FHIR, and any future industry standard. Vocabularies ride on top; the protocol carries them all.
Pragmatic. Where two well-funded counterparties need to exchange documents, they build the integration. The status quo for most B2B integration today.
Integrations are n × (n−1). Each pair is a bespoke project. Records are bilateral, unverifiable to outside parties, and unlinked across the wider transaction. This is the fragmentation problem.
A participant integrates once with the protocol, not once per counterparty. Every event becomes a fact, addressable by every authorised party — auditor, regulator, bank — without bilateral plumbing.
Provide trusted seals on individual documents under sovereign legal frameworks. Long-established, accepted in court, embedded in commercial practice.
Per-document, per-event, manual. Seals do not link to one another; chains of causation are reconstructed by hand. No machine-readable continuity across a transaction's lifecycle.
IAEX provides the equivalent seal at protocol level, on every event, with causal links between them. Notarial functions remain valuable above this layer; IAEX makes the substrate consistent.
Decades of work to define semantic resources within a sector — patient records, clinical observations, claims. Within the sector, real interoperability.
By design, single-industry. Cross-industry continuity — health to insurance to payment — is out of scope and structurally cannot be added without losing the single-industry focus.
IAEX provides cross-industry continuity exactly because it does not pick one industry's vocabulary. Sectoral standards continue to exist and ride on the substrate. The continuity comes from causal hash links, not shared vocabulary.
The same comparison in tabular form. Positions for non-IAEX systems are generalised; specific deployments may differ.
| IAEX | SWIFT | Public blockchain | GS1 / EDI | ERP-to-ERP | Audit / notary | |
|---|---|---|---|---|---|---|
| Industry scope | UNIVERSAL Vocabulary-agnostic by design |
SINGLE Banking only |
UNIVERSAL Token-centric in practice |
SINGLE Per-industry profiles |
BILATERAL Per-pair scope |
PER-DOC Document-class specific |
| Governance | FEDERATED Region-anchored, open protocol |
COOPERATIVE Single global operator |
DECENTRALISED Coin-aligned |
STANDARDS BODY | PRIVATE Bilateral contracts |
SOVEREIGN Or private |
| Tamper-proof | PER EVENT Verifiable by any reader, every event sealed |
OPERATOR-ATTESTED | CONSENSUS-BOUND | NONE Document-level only |
BILATERAL Trust-based |
DOCUMENT-LEVEL |
| Data residency | BUILT-IN Identity-derived routing — sovereignty by construction |
CONFIGURED | PUBLIC | CONFIGURED | PER-INTEGRATION | SOVEREIGN By instrument |
| Onboarding effort | MINIMAL Identity + emit. No shared schema |
HEAVY Membership, BIC, message standards |
LIGHT TECHNICALLY Heavy operationally |
HEAVY Vocabulary mapping per partner |
VERY HEAVY Bespoke per pair |
PER-DOCUMENT Manual |
| Causal traceability | YES Hash-linked across parties & regions — distinctive |
NONE Message-level only |
WITHIN CHAIN | NONE | NONE Manual reconciliation |
NONE Document-level |
| Commercial model | INFRASTRUCTURE Per-event, per-actor. No token |
COOPERATIVE FEES | TOKEN / GAS | MEMBERSHIP + implementation |
CAPEX Per integration |
PER-DOCUMENT |
Why we chose these seven, and how IAEX is positioned along each.
Whether the system serves one industry or generalises across all economic activity. Most existing infrastructures were built inside an industry and reflect its assumptions — message types, document classes, regulatory framing.
Universal by refusing to encode any single industry's vocabulary. This is the entire reason the protocol can serve as a base layer for plural economic activity.
Centralised, federated, or decentralised — and the implications for sovereignty, accountability, and resistance to capture. Each model has well-known trade-offs.
Federated by region. Each region's substrate may be operated by a regionally accountable entity under that jurisdiction's law. The protocol itself is open.
Whether records, once written, are independently verifiable as unaltered — and crucially, by whom. A guarantee that depends on trusting the operator is materially weaker than one that does not.
Per-event seal, verifiable by any reader holding the prior chain. The integrity guarantee does not depend on the operator's good behaviour.
The extent to which the system respects sovereign jurisdiction over the data it carries — not as a deployment switch, but as an architectural property.
Identity-derived routing. The region of an event is determined by the credentials of the actor that submits it. There is no central operator with cross-region visibility.
What a new participant must do — administratively, technically, semantically — to begin emitting and receiving verifiable events.
Enrol an identity, emit events. No shared schema is mandated. Vocabulary agreements remain bilateral or sectoral, exactly where they belong.
Whether one event can be cryptographically demonstrated to be a consequence of another, across organisations and across regions, without trusting any single observer.
The distinguishing property. Every event may declare a prior event by hash; the declaration itself is sealed. The result is a tamper-evident causal graph that spans systems, industries and borders.
How the system is funded, who pays, and what economic incentives shape its evolution. A token-based model creates one set of incentives; a cooperative model another; an infrastructure model a third.
Infrastructure pricing — per event, per actor, no token. Aligned with the economics of every other base-layer infrastructure participants already pay for.
Across every party, every system, every border.