Skip to content

feature: local hash-chained sync receipts (provenance, no secret material) #53

Description

@solomonneas

What

Emit a lightweight local, append-only receipt per sync: timestamp, source/sink identity, event type, content hash of the payload, previous-event pointer, signature. Records that a sync happened and over what digest, without logging cookie or secret values.

Why

Gives operators tamper-evident provenance and auditability the tool currently lacks, and makes pantry syncs citable evidence in Brigade-style workflows. Schema adapted from Li, "Blockchain-Based Distributed Provenance and Data Integrity Assurance Research for Digital Heritage Archives", IEEE ISPDS 2025 (doi:10.1109/ISPDS67367.2025.11391054) and Kalaiselvi et al., "Novel Immutable Data Provenance in Embedded Systems", IEEE ICCCA 2025 (doi:10.1109/ICCCA66364.2025.11325500): keep the local hash chain, drop the blockchain layer. Aligns with the integrity and provenance objectives in NIST CSF 2.0 (doi:10.6028/NIST.CSWP.29).

Effort

M

Source: three-lane research sweep (repo audit + comparables + literature), independently reviewed before filing; run 20260724-040709-e9fc6818.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestsize/MMedium: about a day

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions