A persistent mathematical identity for a real-world asset whose state can change without losing its identity, provenance or evolutionary history.
The AC⚡IDN mathematical identifier recognizes the same asset across any file extension, spelling, format or system of origin — and preserves its full evolution over time.
From physical document to blockchain-anchored canonical identity — the full cycle in seconds.
When the vertical requires field tracking, the canonical identity is published as a QR — free reading for citizens, millisecond verification for institutions.
The same asset lives in many files, formats and systems. Without a canonical identity, every new occurrence may look like a different asset.
Examples in a register operation. On query, the result reflects the asset’s current state.
AC⚡ does not replace the hash: it uses the hash for the file and canonical identity for the asset.
Three architectural families, one single backbone: the Canonical Life Cycle of the asset — from the birth of its identity to its authorized evolution.
Generates identity. Produces a deterministic identifier from the asset's permanent elements — the same asset always produces the same AC⚡IDN, in any spelling, format or system.
Verifies identity. Deterministic canonical decision with permanent memory (AC⚡Master Keys) and five public responses: AC⚡UNI [Uniqueness] · AC⚡DUP [Duplication] · AC⚡PAR [Parity] · AC⚡QTN [Quarantine] · AC⚡INL [Identity not located or document illegible].
Preserves evolution. Detects duplication and builds the asset's tree and its updated timeline — versions, variants and the chain of authorizations behind every change, without ever losing canonical identity.
HASH BREAKS — ALTERNATING CURRENT
FROM PAPER TO IMMUTABLE IN SECONDS
"A traditional hash tells you whether two files are identical. AC⚡PROTOCOL Alternating⚡Current tells you whether they represent the same asset — and what happened to that asset over time."
Behind these three families, two distinct layers: the Universal Engine (AC⚡MAP + AC⚡SCAN) interprets and prepares any input; the Canonical Engine never interprets — it verifies, from Canonical Keys and deterministic rules. See the full architecture →
From the engine's mathematics to the global ecosystem — each layer with a single responsibility.
On top of canonical identity rises the application layer: tokenization, trading and federation of RWAs by jurisdiction — Country → State → Municipality → Category. In planning; architecture documented in the AC⚡Papers.
The canonical identity is the same. What changes is where the proof comes from.
Paper or scanned documents created before any canonical identity. Assisted reading of the content, with a declared evidence level and verification where required. Once admitted, the asset enters the timeline like any other.
Registries, central bank, notary offices, digital signatures. The proof does not come from reading the paper — it comes from the source. Deterministic identity, with no reading and no interpretation.
The asset is born with a canonical identity at the very moment of its creation, through native integration into document creation and registration systems. No reading, no extraction, no later reconstruction.
ROADMAPThe origin of the data changes. The identifier does not.
The engine's internal architecture is protected by a pending patent and disclosed under a non-disclosure agreement.
Banks, land registries, exchanges and RWA platforms: the founding partners program opens together with the public API. Get in touch for early access to the technical documentation.
Standardizing humans is impossible.
Standardizing machines is mathematics.
It's not magic. It's Mathematical Engineering.
AC⚡PROTOCOL — Alternating⚡Current of Canonical Identity.