Evidence
Evidence in PressChain is a first-class record linked to a Capsule. It is not a free-form comment and it is not a hidden moderation annotation. Evidence has an identifier, type, URI, content hash, media metadata, submitter, primary flag, active state and an independent tally. The V3 evidence registry lets applications preserve both supporting material and later dispute material without rewriting the original Capsule.Evidence record
The active contract stores:metadataURI and coverUrl support structured presentation.
Evidence is anchored to an existing Capsule
Both canonical and dispute evidence require the referenced Capsule to exist. The registry rejects the zero Capsule ID and missing Capsules. That guarantees evidence is not floating in the protocol without a publication context.Canonical versus dispute evidence
NormaladdEvidence rejects evidence type 255. That value is reserved for submitDisputeEvidence, which creates a record labeled DISPUTE_EVIDENCE.
This gives applications an explicit way to render evidence that supports or documents the publication separately from evidence introduced to challenge it.
Primary evidence
TheisPrimary flag lets a publisher identify evidence that is especially central to the Capsule. Applications should not interpret “primary” as “proven true.” It describes relationship and importance, not a universal truth judgment.
For example, an original court filing might be marked primary evidence for an article about that filing, while a secondary news article about the same case would not be.
Active state
Evidence can be marked inactive by protocol administration. Deactivation does not erase the record. This preserves the audit history while allowing clients to distinguish current active evidence from a record that should no longer participate in normal presentation. A robust indexer stores both the historicalEvidenceAdded event and current active state.