What is Recognitium?
Recognitium runs a public receipt chain. Give it the fingerprint of any digital event, a payment, a contract, a database entry, an AI action, and it returns a receipt that binds that fingerprint to a position in one unbroken timeline. Anyone can verify the receipt offline, forever, without an account and without us. Quantum Settlement is the name of the invention behind it: a random event born for each receipt, consumed, sensed dead, and only then a receipt.
Does Recognitium ever see, process, or store our private data?
Never. Your data is hashed locally on your machine before transmission. Only a 32-byte SHA-256 fingerprint enters our infrastructure. We settle the fingerprint; your contracts, balances, prompts and documents never leave your environment. Your account holds an email address, never what you seal.
How is this fundamentally different from a blockchain?
Consensus systems force everyone to agree on a single public state by burning energy or capital. Recognitium lets everyone keep their own private data, but interlocks their sequence so that any rewrite becomes visible to everyone holding a receipt. Finality in a single tick, with no mining, no gas fees, and no content made public.
What happens if Recognitium disappears tomorrow? Can receipts still be verified?
Yes. Any counterparty, court, auditor or machine can recompute a receipt offline with standard SHA-256: no API call, no account, no dependency on us. That proves the receipt is consistent in itself; that it belongs to the chain is checked against the chain and its daily Bitcoin anchor, which anyone can also do without us.
Why can’t an event be backdated or a receipt forged?
Every receipt carries the tip of the receipt before it, and the next receipt carries its tip. To change one you would have to change every receipt after it, in every copy held by every client, mirror and anchor, including the daily anchor in Bitcoin. A forged receipt can be made to look self-consistent; it cannot be made to belong to the anchored chain. That is the difference between a claim and a record.
How does this differ from traditional digital signatures and timestamping services?
Traditional systems rely on stored private keys and institutional custody. When a system stores customer data or retains the keys to sign records, it does not sell irreversibility: it warehouses the power to change history, massively expanding the attack surface. A system cannot claim the truth of a fact if its architecture retains the hidden capability to reverse it. Recognitium receives only a one-way hash, binds it to a random event consumed in the act, and keeps no signing key. We do not sell promises of truth. We sell a position in an anchored timeline.
What about future quantum computers?
Post-quantum by construction, not immune. The sealing path uses SHA-256 only, no RSA, no elliptic curves, so Shor’s algorithm has nothing to attack. What remains is unstructured search against a 256-bit preimage, the class NIST rates Category 5. There are no private keys to migrate. No cryptography is quantum-proof, and we say so.
Can a Recognitium receipt serve as evidence?
A receipt is evidence of existence, order and integrity at a stated time, and anyone, including a court, can rerun the arithmetic that proves it. Whether a court admits it and what weight it gives it is the court’s decision, as with any exhibit. The Proof Policy states exactly what a receipt proves and what it does not.
Which tier are today’s receipts?
Software, and every receipt says so. The tier is bound into the payload, so a receipt cannot be relabelled without breaking its tip. Today’s stamp is csprng-512, a computational source of randomness. The bench of the physical instrument is being built, under a public preregistration anchored in Bitcoin. When it passes its tests, new receipts carry the new stamp and old ones keep theirs.
How do we integrate Recognitium into our existing stack?
Integration takes minutes via a single REST API call, from any language, with nothing to install. You pass a 32-byte hash from your database, backend, or workflow, and receive a portable JSON receipt in return. No infrastructure overhaul or migration required.