Ecosystem / Core Infrastructure

INFRASTRUCTURE

Canonical identity for institutions

ACPROTOCOL & ORACLE connects documents, assets and institutions through a persistent canonical identity, making it possible to identify, correlate, query and follow the evolution of an asset.

It was designed to act as an infrastructure layer between the systems that banks, notaries, registries and platforms already use.

FOUR AC ACTIONSIdentify · Correlate · Query · Follow

IDENTIFY

Recognize the same asset across different occurrences and representations.

CORRELATE

Relate occurrences coming from different systems, moments or institutions.

QUERY

Report the identity and recognized state available for that occurrence.

FOLLOW

Preserve the continuity of the asset along its timeline.

WHERE AC CREATES VALUETokenizers and RWA · Banks and Lenders · Notaries and Registries · City Halls and Companies

Different institutions receive different documents related to the same asset. Each one keeps operating in its own system, and AC provides a common layer that recognizes the identity and relates its occurrences.

Tokenizers and RWA

Keep a persistent reference between the real-world asset and its different digital representations.

Banks and Lenders

Relate receivables, documents and occurrences that represent the same asset, reducing information fragmentation across systems and moments.

Notaries and Registries

Associate identity, occurrences and recognized events with the asset history.

City Halls and Companies

Relate documents and records that appear in different departments, archives and administrative stages.

FROM INPUT TO CANONICAL ANSWERACFAST → Universal Engine → Canonical Engine → ACORACLE

The Universal Engine interprets the representation. The Canonical Engine determines the identity.

1

ACFAST — prepares

Identical copies and file sorting, without reading content.

2

Universal Engine — reads and relates

Documents with the same content and similar documents.

3

Canonical Engine — verifies and decides

ACIDN identity and the UNI, DUP, PAR, QTN and INL responses, with the asset timeline.

PROPRIETARY ENGINE
4

ACORACLE — Canonical Identity Oracle

Designed to connect institutions to the same canonical identity, enabling queries and correlations across different systems while preserving source data.

The five public states
ACUNI
AlternatingCurrent Uniqueness

First pass through the AlternatingCurrent.

ACPAR
AlternatingCurrent Parity

Same asset; the document evolved.

ACDUP
AlternatingCurrent Duplication

A canonical record of this asset already exists.

ACQTN
AlternatingCurrent Quarantine

Review pending.

ACINL
AlternatingCurrent Not Located

Identity not located or document illegible.

One identity, different occurrences

Each new occurrence relates to the main identity of the asset. New documents, representations and events appear over time, and AC preserves the relationship between them and the corresponding canonical identity. Evolution is followed and each document stays linked to the same asset.

Institutional view

Documents · Systems · Sources

→
→

Canonical identity

ACIDN · state · timeline

→

Institutions · Queries · Events

Connect the AlternatingCurrent to your institutional environment.

Banks, financial institutions, notaries, registries, tokenizers, RWA and infrastructure operators can request a presentation of the protocol and its use cases.

What has been developed — and what's roadmap →

← BACK TO ECOSYSTEM

Contact

Get in touch

Partners, banks, land registries, exchanges, investors and technical evaluators can write directly to:

Open in my e-mail