The security model
Recognitium’s security does not rest on our honesty, our servers, or our survival. It rests on the arithmetic of SHA-256, which is the same for everyone, everywhere, at any power level.
In one minute
What a receipt proves, and what it does not
A receipt proves that a specific fingerprint was settled at a specific position in an append-only sequence, at a specific time. It is proof of when, bound to proof of integrity: it binds the fingerprint, the position, the instant, the previous state of the chain and the new one into a portable proof.
It does not certify that the content behind the fingerprint is true, lawful or authentic. It says nothing about what the data means, unless the holder discloses the original and shows that it hashes to the sealed value. A system that overclaims is a system you cannot audit; we prefer the smaller, provable claim.
Verification is public. It needs no login, no account and no disclosure of the original. An account’s status changes nothing already issued: an unused balance, a suspension, an expiry or a closure does not alter the verifiability of its receipts.
Ticks are spent. Receipts stay verifiable. Private data stays private.
No keys in the sealing path
The settlement path contains no asymmetric cryptography: no signing keys, no certificates, no key ceremony. There is no private key whose theft would let anyone forge a receipt, no rotation schedule to miss, and no authority whose compromise cascades. Verification is pure recomputation: anyone with the receipt’s public fields recomputes one SHA-256 digest and compares. The arithmetic either agrees or it does not.
The key on your account is a different thing. It lets its holder spend your ticks and seal new receipts in your name, which is why you keep it secret. It cannot change, remove or backdate a receipt already issued.
No rewriting the past
Every day at 07:00 UTC our server stamps the current tip of the chain into Bitcoin through OpenTimestamps. Once the proof is final it names a block: the tip of that day existed no later than that block, and every receipt sealed before it inherits the bound. Recognitium cannot move a receipt later than the block, and cannot rewrite the chain behind a tip that Bitcoin has seen without the rewrite showing. The anchors and their proofs are listed in the Journal.
Collision-indifferent, not collision-immune
We do not claim SHA-256 collisions are impossible. We claim something more defensible: the design does not lean on their impossibility. A receipt commits to the specific preimage its holder possesses. To exploit the scheme an attacker needs a second preimage for a fingerprint already fixed on the chain, which is the second-preimage resistance property, not the easier collision game. That distinction is deliberate, and we state it precisely.
Post-quantum posture
Shor’s algorithm breaks RSA and elliptic curves. The sealing path uses neither, so there is nothing for it to attack. A quantum adversary is left with unstructured search for a SHA-256 preimage: about 2128 steps with Grover’s algorithm, the same order of work as recovering an AES-256 key, which NIST uses as the benchmark for its highest post-quantum security category. We state this as a posture, not a slogan: no cryptography is “quantum-proof”, but hash-based settlement is the conservative position available today.
Verify without us
Every receipt verifies with the internet off. The offline verifier is a single page you can save and open from your own disk; it makes no network request. The online verifier checks the live chain, and the specimen receipt on our home page verifies itself in your browser. No account, no permission, no us. If Recognitium disappeared tomorrow, every receipt ever issued would still recompute by its formula, and still match the tips stamped into Bitcoin.
What reaches us, and what does not
Hashing happens on your side, before anything is sent. Sealing receives a fingerprint, 32 bytes of SHA-256, never the document, message or data behind it. We cannot leak, sell or be compelled to disclose content we never held. Client chains stay in their owners’ custody; we do not take custody of them.
Two things are not fingerprints, and we say so. Your account holds an email address, and the SHA-256 commitment of the key your phone keeps behind your face or fingerprint: there is no password to keep, hash or reset, and no recovery code; a lost phone is replaced by the emailed code and your identity verified again. The market signals an AI publishes for you are public by design, and they expire. The privacy policy sets out what we keep and for how long.
Reporting a vulnerability
If you believe you have found a security issue, write to [email protected] (fallback: [email protected]). Machine-readable coordinates live at /.well-known/security.txt (RFC 9116). Every report is read and answered by the founder.