Home → CYRQODE → CYRQODE: event journal and proof

Product

CYRQODE: event journal and proof

CYRQODE proves what really happened: one mark on a product and a chain of immutable events — who made it, from what, under whose approval and when.

Tell us what needs to be proven in your process. We will come back with a connection option: marks, your own ledger on the protocol, or the CYRQODE ledger.

In short

CYRQODE is a BizDNAi technology: one mark on a product with a chain of immutable events behind it — what happened, in what relation, under whose authority.

Every accounting system answers 'what is recorded'. CYRQODE answers a different question: what actually happened and whether it can be proven a year from now.

A record proves that a document with exactly this content existed on the stated date without storing the document: the journal holds a SHA-256, not the content.

Personal data never enters the journal: an event refers to an entity identifier, not to a person.

What CYRQODE consists of

ElementWhat it is
CYRQODEbrand of the technology
BUIPprotocol of identity, events and proofs
Circle Markphysical sign carrying a stable entity identifier
BizDNAiowner of the technology

How it works

Mark on the product (Circle Mark)
Scanner: reading the identifier
CYRQODE journal: event record
Verification: document hash against the record

The mark encodes exactly one entity identifier — a UUID — plus the profile's service fields. Name, date, author, price, expiry date and any text are not in the mark: all of that changes, the mark does not.

A journal record contains the fact, the time, participants as identifiers and references to evidence as hashes. There is no personal data, no document content and no commercial terms in the journal.

What a record proves

The record proves that a document with exactly this content existed on the stated date without storing the document itself. Anyone can check: compute the SHA-256 of their own copy and compare it with the record.

The technology can prove that an action was performed by an entity with the proper permit at the proper time — knowing neither the name nor the position.

Proof levels

The first journal record (6 September 2026) has proof level PL-0 — an owner statement. Signatures and independent witnessing are a later layer, and the record page states this explicitly.

What is public and what is not

Licences: specification and schemas — CC BY 4.0, code — Apache 2.0.

Rule in case of doubt: if it belongs to the protocol — public, if it belongs to operations — private. You can open the closed at any time; you cannot close the open.

PublicPrivate
protocol specification, schemas, test vectorsledger core, resolver, projections and aggregates
client libraries, mark generator, scanneraccess policies, operations
demonstrational registry recordsdata of specific legal entities

How to connect

OptionWhat is needed
Marks only, no ledgerYou generate marks and read them in your own system; no agreements needed — the licences allow it
Your own ledger on the protocolYou implement storage yourself while following the event format, canonicalization and signature
The CYRQODE ledgerYou send events to the service and use the ready resolver; the service address, namespace identifier and credentials are required

Two principles

The core is industry-neutral: manufacturing is the first and most saturated consumer, but not the subject of the protocol. Manufacturing fields live in a separate profile.

Personal data never enters the ledger: an event refers to an entity identifier, not to a person.

Frequently asked questions

What is CYRQODE in simple terms?+

A mark on a product and an event journal behind it. The mark lets you prove what really happened: what it is made of, who made it, on which equipment, under whose approval, with which documents.

How is it different from an accounting system?+

An accounting system answers 'what is recorded'. CYRQODE answers a different question: what happened, in what relation to everything else, under whose authority, and whether it can be proven a year from now.

Does personal data enter the journal?+

No. An event refers to an entity identifier, not to a person. Only the data owner knows the name and position in their own system.

Does CYRQODE store the documents themselves?+

No. The journal holds the document's SHA-256. The record proves that a document with this content existed on the date without storing the document itself.

Can we use marks only, without a ledger?+

Yes. You can generate marks and read them in your own system — the licences allow it, with no agreements required.

Free · no obligation

Free digital audit

We will review your data and show where the discrepancies, risks and losses are. You get a report with specifics — even if you decide to work with another contractor.

The price depends on your situation, after the free audit.

Submit a request

By clicking the button you agree to the privacy policy. We reply on WhatsApp during business hours.