Blockchain notary

Important transactions rarely happen inside one system. A notary, client, bank, adviser, registry, and regulator may all touch the same case, but each party keeps its own copy, its own timestamps, and its own audit trail. The result is repeated checking, long email chains, and uncertainty about which version was actually approved.

Blockchain Notary gives those parties one verifiable transaction history without creating one central owner of every document. The workspace coordinates the case; the permissioned ledger provides a shared proof layer. Each participant can verify what happened, who attested to it, and whether the underlying file still matches the recorded fingerprint.

A case starts with a defined protocol: the parties, required documents, identity checks, signing order, notarial actions, and the conditions that must be met before finalization. Every meaningful step becomes an event in an ordered case timeline.

A share transfer, for example, can require verified representatives, a final deed, signatures from all parties, and a notarial attestation. The application shows what is complete, what is blocking the transaction, and which exact proof was included in the finalized block.

The blockchain never needs the deed, passport scan, chat transcript, or client record. Those files remain in encrypted storage under the retention and access rules of the organization. The proof layer receives only the minimum cryptographic evidence needed to recognize the file and the event.

For each final document the application calculates a deterministic fingerprint, such as SHA-256, and combines it with the event type, timestamp, signer or attester identity, and case reference. Changing a single byte creates a different fingerprint, which makes later tampering visible without revealing the document itself.

This is not an anonymous cryptocurrency network. Validators are approved organizations with a defined role in the ecosystem. They confirm the same ordered events, hold one another accountable, and make it difficult for any single operator to rewrite the history.

The governance model matters as much as the code. Membership, key rotation, node operation, data residency, incident response, software upgrades, and the legal meaning of an attestation all need explicit rules. The product therefore treats network governance as part of the application, not as infrastructure hidden behind it.

Blockchain adds value when several independent parties need the same proof and no single database owner is the natural source of truth. If one trusted organization controls the entire process, a signed audit log may be simpler. The product is aimed at the harder cross-organization cases.

A reusable protocol engine makes the same foundation suitable for different transaction types. Each implementation can define its own participants, evidence, approvals, retention rules, and final proof bundle.

The direction builds on earlier blockchain work by Justin Schlee. For Stichting Oasebos he programmed a custom blockchain that let participants irreversibly register purchased rainforest certificates. In KNB innovation work, he helped explore a notarial privacy ecosystem combining verified identity, secure communication, timestamps, and hash-only registration on a permissioned network.

The presentation behind this page also shows prototype interfaces for validated building dossiers and a distributed network of notarial nodes. Those experiments point to the same lesson: the useful product is not a blockchain explorer. It is a clear workflow in which people can complete a real transaction, while the blockchain quietly provides shared integrity underneath.