Provenance & DLT
Provenance & DLT is designed to record who decided what and when through signed, versioned manifests, with a permissioned ledger as an optional extension. Records stay off-chain.
This page describes a proposed architecture. It is not evidence of an existing deployment.
This component is optional. Records stay off-chain. In the demo it is labelled Optional, simulated.
How it fits the platform
It is optional: the signed-log baseline comes first, and ledger, scoped proofs and settlement contracts are added only for a defined need.
Signed log first
The baseline is designed to be canonical manifests, hashes and an append-only event history, with each signature naming its signer and key version. It is the starting point before any ledger is considered.
Optional extensions
A permissioned ledger, scoped zero-knowledge proofs and settlement contracts are optional extensions, introduced progressively and only for a defined need. Public anchoring, if it were ever used, would carry only permitted commitments.
What never leaves the record
Sensitive knowledge, structures, contracts and assay data are never published on a ledger. They stay in confidential off-chain records. A commitment is not a zero-knowledge proof: a proof verifies an encoded credential, while a commitment only fixes content.
Sources
- NEWMA Technology Architecture and Workflows § 4
- NEWMA technological architecture and technology stack § 2F
- NEWMA Product Requirements Document v1.0 § 3.4
See it in the demo
Opens Demo sign-in. After signing in, choose Signed provenance (/demo/w6-provenance) from the demo dashboard. In the demo this is labelled Optional, simulated.