One of Neuzida’s core principles is full traceability: every verification verdict and human override recorded so it can be independently checked later. The obvious instinct is to reach for a blockchain. We looked closely, and chose something simpler and sturdier. Here’s the reasoning, starting with where the technology came from.

Origins of the Distributed Ledger

The father of blind signatures, David Chaum published a research paper in 1982 that would later develop into the first anonymous cryptocurrency, “Digicash.” Thanks to his contribution, blockchain technology has progressed significantly over time.

In a nutshell, blockchain is a decentralized distributed ledger maintained by a peer-to-peer network worldwide. Cryptography allows for secure data, transfer, storage, and immutable tamper-proof transactions.

What Blockchain Gets Right

The genuinely valuable idea inside a blockchain is the hash chain: each record references the cryptographic hash of the one before it. Change any past entry and every subsequent hash breaks, so tampering is immediately detectable. This is what gives a ledger its “append-only, tamper-evident” property, and it is exactly the property an audit trail needs.

That core idea is sound. The question is how much machinery you need around it.

The Hidden Cost of a Private Blockchain

A public chain achieves trust through massive decentralization, but it requires putting data on external nodes, which is a non-starter for sensitive workloads. The usual answer is a private, permissioned blockchain: peers, an ordering service, a certificate authority, and smart contracts, all run in-house.

The problem is that this stack is heavy, and heavy systems fail in quiet ways:

• Operational fragility. Orderers, peers, channels, consensus, and chaincode are a lot of moving parts. Each is a component that can misconfigure, drift, or break, often without an obvious signal until something downstream goes wrong.
• A larger attack surface. Every added service is more code to secure and patch. Private and permissioned does not mean invulnerable. Permissioned ledger frameworks have shipped serious flaws, and because these systems are complex and comparatively rarely deployed, critical vulnerabilities are often discovered late, after they have already been trusted in production.
• Consensus you may not need. Consensus exists to let mutually distrustful parties agree without a central authority. Inside a single organization’s perimeter, there is one trust domain. You are paying the cost of distributed consensus for a problem you don’t have.

In short: a private blockchain spends a great deal of complexity to deliver tamper-evidence, and that complexity is itself a liability.

Neuzida’s Approach: A Tamper-Evident Hash-Chained Log

We keep the part that matters, the hash chain, and drop the parts that don’t.

Every audit record we write includes the hash of the previous record, so the log is append-only and tamper-evident: alter or remove any entry and the chain no longer validates. Periodically, we sign the head of the chain with the same kind of certificate used in content provenance, which makes the log’s integrity externally verifiable as well.

This gives us the integrity guarantee an audit trail actually needs, with a fraction of the surface area to secure.

What Gets Logged

Every auditable event in our verification pipeline is committed to the log:

1. Verification verdicts — the authenticity result for a piece of media, with the inputs that produced it
2. Human overrides — Wisdom-tooling™ review points, approval or rejection decisions
3. Provenance reads — C2PA manifest checks and their outcomes
4. Detection results — AI deepfake risk scores and the signals behind them
5. Access events — who reviewed what, when, and in which role

Each entry includes a timestamp, the actor’s identity, the event type, and a cryptographic hash of the payload, providing proof without storing sensitive content in the log itself.

The Bottom Line

Blockchain’s lasting contribution is the hash chain, not the heavyweight machinery often bolted around it. For a single-organization audit trail, that machinery adds fragility and a wider attack surface in exchange for consensus you don’t need, and the worst flaws in such systems tend to surface only after they’ve been trusted.

So we use a hash-chained, signed log: the same tamper-evidence, far less to go wrong. This is how we build trust in our verdicts, not by hoping the record is intact, but by making any change to it provable.

*References: Blind Signatures for Untraceable Payments