Also similar problem space to Provenance Marks, which we presented on in the CCG back in early June: CCG Presentation: https://www.w3.org/events/meetings/dda13eef-820e-4cc5-b28f-f5c79f06052d/20250603T120000/ CCG Slides: https://developer.blockchaincommons.com/assets/pdfs/2025-06-provenance-marks.pdf Video of a different presentation at: https://www.youtube.com/watch?v=vKAK6j4mqgE Spec: https://github.com/BlockchainCommons/Research/blob/master/papers/bcr-2025-001-provenance-mark.md Rust Library: https://github.com/BlockchainCommons/provenance-mark-rust Rust CLI Library: https://github.com/BlockchainCommons/provenance-mark-cli-rust Swift Library: https://github.com/BlockchainCommons/Provenance There is a comparison of Cryptographic Event Logs and Provenance Marks at: https://hackmd.io/@bc-community/HycjswAIyx One observation is that there is some distinction about architecture focusing on witnesses (which requires more infrastructure) vs cryptographic logs (which requires less infrastructure). I would suggest that this group try to keep the architecture for what it does somewhat independent and not bound to each other, but can leverage both. -- Christopher Allen
Received on Sunday, 13 July 2025 23:34:23 UTC