Recognitium Recognitium · Quantum Settlement

Making the past irrevocable.

Who can tell if a payment instruction has changed? Follow one approval from the moment it is recorded to the moment someone tries to use it again.

02 · The payment instruction

One instruction.
One approval.

The front belongs to the bank. The amount, the payee and the instruction stay on its servers. The bank calculates a SHA-256 fingerprint there. The same bytes always give the same fingerprint.

Front · Bank
Approved amount €240

Payee Supplier A

Back · Recognitium
The only input from the instructionSHA-256 · 32 bytes

Recognitium gives this fingerprint a dated place in the chain and returns the receipt. SHA-256 works one way. The fingerprint alone cannot be decoded into the instruction.

First use
Accepted once
Second use
Refused · already spent
Calculated on your device. A random reference stays with this private sample, so guessing the amount alone cannot reproduce its fingerprint.

The past is locked by math.

Each receipt includes the fingerprint of the link before it. To pass off €420 as the original €240, someone would have to replace that link and every link after it. Their version would disagree with the bank’s saved receipt or the published anchor.

The future waits for physics.

For an online link that includes an unpredictable public pulse, the pulse has to arrive first. You can count ahead to the next position. Its exact fingerprint still depends on a value the world has yet to reveal.

The bench instrument aims to supply that event locally. Its design locks the input first, then makes a physical measurement. Whether the measured value can be recovered afterward is a bench question.

03 · The next approval

Anyone can copy the chain to check its history.

Who can authorize the next step?

We replaced the continuation of a key with the continuation of a chain.

Your phone unlocks a one-time approval. The service checks it, spends it and advances. A copy of the last approval is already spent.

04 · The two walls

There are only two ways to stop someone from rewriting the past.

Make the work unaffordable: a secret key, a proof of work, a vault. The material is still there; reaching it costs more than they have.

And a richer adversary erodes that wall every year.

Or make the material absent before they arrive.

Everyone before us paid. The second wall was never built, because it needs something no computer has ever produced:

an object with no recipe.

05 · The mission

One approval. One action.

Yesterday’s approval still proves the bank approved €240. When the bank used it, the chain moved forward. A copy points to the step already used. The bank checks the current step before paying, so it refuses the copy.

The same rule works wherever someone has to say yes. A clinician can sign in and open an encrypted record. A person can let an AI agent change one file. The receipt records what was allowed, and the next action needs its own approval.

Status, said before the promise

The receipt service runs today in software: a public sequence of more than 300,000 entries, its time set against the national clock at the Observatoire de Paris, its last entry written into Bitcoin every day since 5 September 2026. The material of the draw is held by us, published and anchored so that any use would show. The instrument that moves it beyond everyone's reach, ours included, is built and on the bench.

06 · What you hold

A receipt is a dated proof of order.

It binds the fingerprint of your data, thirty-two bytes and nothing else, to a position in a public sequence and to an event that had not yet happened when your data was locked.

Anyone can check it, offline, with one public formula, holding the sequence or its daily anchor, and no one's permission. If Recognitium disappears, every receipt still checks. One cent a receipt, or one receipt for a whole batch.

YOUR FINGERPRINT · 32 BYTES ONE POSITION · UTC(OP) BITCOIN · DAILY BEFORE AFTER
Live

Who did this?

No password anywhere. A value born in your phone behind your face or fingerprint, used once, dead the instant it is seen. A second use seals a public fork for everyone to see.

Live

What happened, and when?

The receipt, the public sequence, the national clock, Bitcoin every day. Checked by a stranger, not believed on our word.

Live in software · physical at the bench

In what order, for everyone?

One public order that every private ledger binds itself to, without a vote and without a blockchain. Each party keeps its own data; only the order is shared.

Live in the API

Who can read it?

An envelope that proves it was opened, and proves when it was not. Nothing in it is ever ours to read.

The receipt attests to the recorded version, its order and its time. The truth of the underlying statement is a separate question.

The bank keeps the funds. The receipt service takes the instruction’s fingerprint. A sender who also needs confidentiality can use an encrypted envelope.

07 · One chain step

Who can open the file? What may the AI change?

Léa receives an encrypted test plan. The same one-use chain check can identify her, unlock her copy and limit an AI agent to the edit she approves.

  1. Authenticate

    Recognize Léa

    Léa unlocks her phone with Face ID. Her phone presents the next step in her chain. The service checks it and recognizes her account.

  2. Decrypt

    Open the test plan

    That check releases the missing piece her phone needs to decrypt the file addressed to her. Léa can now read the plan.

  3. Authorize

    Change one line

    Léa approves replacing “Draft” with “Ready for review”. In our local AI prototype, the agent may make that exact edit to that file, once.

The receipt shows what Léa approved. If the agent changes the wording, picks another file or tries again, the gateway refuses.

08 · One dated incident

4 November 2026

What happened

Crédit Mutuel Arkéa announced that orders were issued in the bank's own name, from a provider's platform, and executed by other banks as if the bank had sent them. About a hundred million euros left before part of it was blocked.

What a bank could test

With Recognitium in front of the signing system, each order consumes a one-time permission and cites the last position of the public order, and the receiving bank checks that receipt before it executes.

The first order without a receipt, or the first permission used twice, is refused, and the refusal is sealed.

The test has a clear result. A spent approval must be refused before signing.

We hold none of the bank's keys. We read none of its data. We never say an order was legitimate, only that it was in the order, or that it was not.

09 · Why no one built it before

Wiesner wanted a quantum state to last the life of a banknote.

Mondex, and every secure chip since, kept a secret.

Bitcoin burns.

Everyone who tried either paid for the past or tried to keep the physics. We spend it.

The parts were on every shelf. The idea of using an event up was not.

10 · Uruk, about fifty-two centuries ago

The first name that survives in the human record is on a clay tablet. It records a quantity of barley, a duration of thirty-seven months, and a word: Kushim. The name has decayed past recovery; the quantity and the duration have not. The record outlived the thing it was about.

Writing was invented for receipts. Everything else came after.

11 · The vision

What will Recognitium look like in ten years?

Imagine a small factory in Lille at two in the morning. A machine needs a part. The owner has given her agent permission to spend up to €800. In Turin, a supplier checks that permission and ships the part. The bank can honour the order once. Each business keeps its own books.

I want a two-person business to have the reach of a multinational. An insurer could cover that single order. An arbitrator could check its terms years later. A one-cent receipt could help two strangers do €800 of business while a city sleeps. If a billion machines come to act for us, I want each one to be able to show whose permission it carried.

In 2036, you should still be able to check the words I signed in 2026.

Check the Declaration’s receipt
Recognitium

Every lock before this one had a key that someone held.

This one is closed by a key that no one ever held.

Making the past irrevocable.

Signature of José Niño
José Niño, Founder of Recognitium

recognitium.com · every receipt in this presentation verifies offline, with SHA-256 alone