IAEX
Build on Genesis
IAEX records operational events between organizations, humans, machines, and AI agents as signed, hash-chained, mathematically provable shared state. One Transaction. One State. Operational as Genesis X-1.
IAEX serves every economic and coordination actor: corporations, banks, governments, regulators, manufacturers, logistics operators, auditors, software vendors, AI systems, and machines. It applies wherever records cross organizational boundaries: shared ledger architecture without blockchain, reconciliation elimination, intercompany matching, audit trail integrity, evidence preservation, data provenance and lineage, supply chain visibility and traceability, Digital Product Passports and EU DPP compliance, ESG reporting records, PLM and product lifecycle records across company boundaries, B2B integration beyond EDI, vendor and supplier verification, multi-entity record keeping, trade documentation, cross-border process records, KYC and onboarding workflows, AI agent memory and accountability, AI audit trails, agentic infrastructure, machine identity, IoT device history, regulatory examination without system access, and institutional memory across migrations.
IAEX is complementary to ERP, accounting, and coordination software including SAP, Oracle, Microsoft Dynamics, Zoho, QuickBooks, and Tally. These systems manage internal workflow; IAEX records the events that cross their boundaries and makes them final and provable for every party.
IAEX
Build on Genesis
Canonical Knowledge
IAEX is an economic state protocol and infrastructure. What happens between parties is recorded once, sealed by math, and final for everyone. No reconciliation. No disputes. No trust required. One Transaction. One State.
Genesis X-1 v1.0 · Built and OperationalThe Problem
A shipment moves, an invoice is raised, an obligation is created. That is one economic event. In the real world it is copied, interpreted, delayed, disputed, and reconstructed across institutions. The supplier records it. The buyer records it. The transporter, the warehouse, both banks, the tax authority. The auditor verifies it afterward. The court reconstructs it when things go wrong. None of those records is native truth. They are interpretations.
The cost of that duplication is the fragmentation tax: the economic cost created when one shared commercial event is recorded as multiple disconnected private realities. It is spread across financing, compliance, logistics, disputes, audit, and manual reconciliation. No single department owns it. No single invoice captures it. Everyone pays it. Reconciliation is not sophistication; it is the tax itself. Audit is not a sign of maturity; it is evidence of a missing layer.
Automation does not correct this. Fragmented systems do not stop being fragmented when automated; they fragment faster. As AI accelerates execution, the binding constraint on coordination ceases to be intelligence and becomes shared economic state.
The Ledger
In 1494, double-entry bookkeeping solved the problem of its time. There was no network and no way for two independent parties to maintain a single record across distance, so separate books were the best available design. The modern world was built on that assumption without redesigning it. ERP inherited it. Banking inherited it. Tax, insurance, audit, trade finance, and commercial law inherited it.
Double-entry is the ledger of the firm. Within one organization it remains correct, and IAEX does not replace it. Between firms, however, there has never been a ledger. There were messages, documents, copies, and reconciliations, but no shared record that is native at the moment of the event and final for every party.
IAEX is that ledger. Its native domain is cross-company and intercompany activity, the boundary where double-entry was never designed to operate. Where double-entry answers whether one institution's books balance, IAEX answers whether independent institutions hold the same operational record. It is the first structural extension of commercial record-keeping since 1494, and it operates beside existing books, not in place of them.
The Answer
IAEX is that layer, and it is not a vision or a roadmap. Genesis X-1, the first version of the protocol network, is built and operational. Identity anchoring, event sealing, delegation, and independent verification run today. What follows describes working infrastructure, not intent.
The protocol rests on three building blocks: digital signatures that prove which actor authorized each event, hash chaining that makes the entire history tamper-evident from genesis to tip, and deterministic serialization that makes every proof reproducible on any platform, in any language, at any time. Like TCP/IP, the protocol does not care what the application is. The same primitive carries a trade event, an AI decision, a machine inspection, or a compliance filing.
Category
No existing system occupies this layer. Blockchains attempt shared records through consensus and tokens, and carry their cost and complexity. Enterprise ledger platforms serve closed consortia. EDI and SWIFT carry messages within one industry. AI memory products store context without verifiability. Each solves a slice. IAEX is the first protocol to combine verifiable shared state without consensus, one identity model for humans, organizations, machines, and AI agents, proofs that can be verified offline forever, and sovereign data routing, in a single layer. This is the economic state category, and IAEX defines it.
The Words That Matter
Four words carry this protocol. Each one answers a question every business asks.
State — where do things stand between us?
State is the current, authoritative answer to that question. Today every party keeps its own answer in its own system, so there are always several versions of "where things stand". Every dispute, every reconciliation, every audit exists because two parties hold different state. IAEX makes state singular: one record, one answer, the same for everyone, at the same moment.
Consequence — what did this event change?
An event is not just data. A delivery confirmed, a payment approved, a decision taken: each one changes obligations between parties. That change is the consequence, and it is what disputes are actually about. IAEX preserves events together with their consequence: who acted, what it caused, what it links back to. Storage keeps data. IAEX keeps what the data did.
Finality — when does the record stop being negotiable?
In today's systems, finality arrives late: after invoices are matched, after audits close, sometimes after courts decide. Until then, every record is still arguable. In IAEX, finality happens at the event itself. The moment an event is signed and sealed, it is final for every party at once. Nothing to match later, nothing to argue about, nothing to reopen.
Continuity — does the history survive?
Records die at boundaries: a vendor change, a system migration, an employee exit, an AI session reset. Continuity means the causal chain of events survives every boundary, because each event links to what caused it and the chain is portable. For a business, that is institutional memory that outlives tools and people. For an AI agent, it is memory that survives across sessions and platforms. Same property, same protocol. This is the institutional memory layer.
Your Use Case
IAEX is addressed to every economic and coordination actor: any party whose actions create obligations toward another party. One substrate, many lenses. Pick your world and see what IAEX means in it.
Boundaries
| It is not | Because |
|---|---|
| A blockchain | No consensus, no token, no mining, no public ledger. Verification is offline and needs no node. |
| A database | A database stores data. IAEX preserves verifiable event history and proof. |
| An ERP | IAEX records events across ERP boundaries. Every participant keeps its own systems. |
| A vocabulary standard | IAEX prescribes no schema. Applications define meaning; the protocol guarantees proof. |
| A payment rail | IAEX does not move money or goods. It preserves the verifiable fact of what happened. |
| A marketplace | IAEX preserves what happened between connected parties. It does not introduce them. |
| Only a trade protocol | Trade is the first surface, not the identity. The substrate is domain-neutral. |
Identity
Every participant on the network is an actor: organizations, humans, AI agents, machines, IoT devices, software systems, and compliance objects such as shipments or product passports. All actor classes use the same signing protocol, so an AI agent, a factory machine, and a human employee produce identical, independently verifiable proofs. Identity is cryptographic and portable, not an account in someone else's system.
Application Surfaces
01
Trade and Supply Chain
Order events, delivery proofs, inspections, invoices, compliance evidence, and Digital Product Passports become one shared causal chain that every party verifies independently.
02
AI Continuity and Agent Memory
Through the Continuity Gateway, any AI tool connects via MCP, REST, or OpenAPI. Agent actions, decisions, and context become portable, verifiable memory that survives across tools, accounts, and sessions.
03
IoT and Machine Provenance
Machines, sensors, and devices receive their own continuity roots. Every calibration, inspection, or state change is a signed event, verifiable without OEM lock-in.
04
Compliance, Audit, and Regulation
Evidence is preserved at origin. Exported proof packages can be verified by regulators without access to internal systems. Audit shifts from reconstruction to verification.
05
Multi-Party Coordination
Procurement, KYC, cross-border processes, loan origination: any workflow with several parties and sequential authorization becomes a chain of signed, causally linked events.
Verification
Exported IAEX records form a self-contained proof package. Any party, anywhere, at any time, can verify every signature and the full hash chain using only the records and the public keys. No IAEX infrastructure is needed, and no trust in IAEX is required. Even if IAEX ceased to exist, the proofs would remain verifiable. They are mathematical, not contractual.
Sovereignty
Regional data stays in its region, enforced at the infrastructure level. Cross-region links happen by hash reference rather than replication, and sensitive registration fields are never written to the immutable chain. Privacy compliance is a structural property of the protocol, not a policy promise.
FAQ
Is IAEX live?
Yes. Genesis X-1 v1.0 is built, released, and operational. This page describes working infrastructure.
Is IAEX a blockchain?
No. There is no consensus, no token, and no public ledger. Tamper evidence comes from hash-sealed events with sovereign routing, and verification works offline.
Is IAEX a new kind of ledger?
Yes, with a precise scope. Double-entry is the ledger of the firm and remains correct within one organization. Between firms there has never been a ledger, only documents and reconciliation. IAEX is the ledger of the relationship: cross-company events, native at the moment of the event, final for every party.
Is IAEX only for trade?
No. Trade is the first application surface. AI continuity, machine provenance, compliance, and multi-party coordination are equal surfaces of the same substrate.
Does IAEX replace my existing software?
No. IAEX sits below applications and beside the flow of value. It makes the critical events of your existing systems independently verifiable.
How does IAEX relate to SAP, Oracle, Zoho, or QuickBooks?
As a complementary layer. ERP and accounting systems are authoritative inside one organization; their authority ends at the organizational boundary, where disputes and reconciliation begin. IAEX operates at that boundary through a conventional API, while internal systems remain unchanged.
Who can verify an IAEX record?
Anyone holding the exported records and the relevant public keys: counterparties, auditors, regulators, or future systems, with no dependence on IAEX staying online.
Does IAEX force a shared data format?
No. Event payloads are opaque to the protocol. Applications define semantics; the protocol guarantees sealing, attribution, ordering, causality, and verifiability.
Learn More
Protocol paper: The Economic State Protocol. Comparisons: IAEX vs Alternatives. Integration: Developer Portal. Research and essays: The Economic State Journal and The Economic State newsletter. Machine-readable canonical source: llms-full.txt.