Evidence ledger

The evidence ledger records meaningful events in a request’s lifecycle as an append-only, tamper-evident chain.

​

What is recorded

Entries can cover request creation and sending, client submissions, review decisions, reminders, completion, exports, and other material workflow events. Payloads are deliberately structured and sanitized rather than storing raw document text in audit metadata.

​

Hash chain

Each entry includes the previous entry hash. NeuDocs computes a SHA-256 hash from the previous hash and the canonical event data. Changing, removing, or reordering an entry breaks recomputation from that point.

​

External anchoring

NeuDocs can anchor a request’s chain head through OpenTimestamps. A confirmed proof ties that fingerprint to a Bitcoin block without publishing the client document itself. Blockchain confirmation may be pending, and external calendar or explorer services can be temporarily unreachable. The UI distinguishes those states from an invalid proof.

​

Evidence identity settings

A firm can choose how much request-origin context the ledger retains:

• Off: do not retain optional identity context.
• Hashed: retain privacy-preserving hashes where configured.
• Full: retain fuller context for firms whose lawful evidence requirements justify it.

Choose the least data needed for your purpose and document the lawful basis in your own policy.

​

Reports and bundles

• Evidence report: a readable request timeline with fingerprint and QR cross-check.
• Evidence bundle: entries, hashes, and OpenTimestamps proofs needed for independent verification.
• Public verifier: neudocs.app/verify recomputes the chain and checks proofs without relying on the stored status strings.