# CID Congress #7 - Agenda and Notes 15 January 2026 Event link: https://luma.com/zsa28r1b Template: https://hackmd.io/rW9frB80QnKecTWacRayWg Scribe: ? ## Agenda - Administratrivia - This is every two months on the 3rd Thursday (next one is Jan 15th). We now have a calendar for this series: https://luma.com/cid-congress. - Send us topics & demos! - You might also enjoy DASLing Working Group (monthly meeting), ping robin@ipfs.io for invite. - FOSDEM - Talks by [Robin](https://fosdem.org/2026/schedule/event/W8CJXD-dasl/), [Mosh](https://fosdem.org/2026/schedule/event/TRQ9LV-decentralized-to-doorsteps/), [Alex from bsky](https://fosdem.org/2026/schedule/event/ZT7TB9-at-the-billion-edge-social-graph/), [iroh](https://fosdem.org/2026/schedule/event/T9ACNE-iroh_p2p_connections/), [Max Inden](https://fosdem.org/2026/schedule/event/NKWMN9-modern_network_protocols_--_whats_next_for_firefox_and_the_web/), [David from Spritely](https://fosdem.org/2026/schedule/event/GB387H-re-decentralizing_the_web_platform_with_wasm_gc/) [x2](https://fosdem.org/2026/schedule/event/G3FRDA-beyond_javascript_wasm_gc_present_and_future/), [Eli](https://fosdem.org/2026/schedule/event/PN7WCS-decentralized_public_broadcast_with_streamplace/) ## Minutes - **Overview:** new standards for content provenance and verifiable streaming, specifically targeting deepfake regulation and efficient data transfer. Several attendees are preparing to present at FOSDEM. **1. S2PA (Stupa): A C2PA Fork for Provenance** - **Presenter:** iameli (Eli) - **The Problem:** While the C2PA standard helps combat deepfakes via cryptographic signatures, its implementation by Adobe risks "regulatory capture" with high costs ($1,200/year) and restricted trust lists. - **The Solution:** Eli proposed **S2PA** (Simple Standard for Provenance and Authenticity), an open-source fork of C2PA. - **Key Differences:** - **K256 Support:** Unlike C2PA, S2PA supports K256 signing, making it compatible with blockchain/crypto ecosystems (e.g., AT Proto). - **Deterministic Muxing:** Eli demonstrated a "muxaltree" approach for video, allowing users to combine or split MP4 files (e.g., livestream segments) while keeping the original cryptographic signatures intact. **2. BDASL: Verifiable Streaming with Blake3** - **Presenter:** b5 (Brendan) - **The Innovation:** Presented "BDASL," an extension to DASL for verifiable streaming over standard HTTP range requests. - **The Hard Tech:** The system uses the **Blake3** hash function. A critical advantage is that the Blake3 hash of a file is identical to the hash used for streaming verification (the hash function _is_ a Merkle tree). - **Benefit:** This allows clients to fetch and verify small chunks of massive files (e.g., 600MB video, DuckDB stores, ML tensors) without downloading the entire file first or pre-computing separate verification trees. - **Status:** The spec is close to merging and is already used in production to move petabytes of data. ### Technical Discussions - **Canonical JSON vs. Binary:** Daniel Norman noted that the Radicle protocol uses canonical JSON stored in Git. Robin Berjon warned that canonicalizing text formats is historically error-prone (e.g., float encoding issues) and often implemented incorrectly. He argued that binary formats like DRISL or CBOR are safer and better suited for content addressing. - **Range Requests:** Dorian Taylor suggested using custom units for HTTP range headers, but Brendan countered that browsers require "bytes" to function natively. ### Participant Updates - **Daniel Norman:** Working on geospatial data publishing and extrapolating insights from the Orcestra project in addition to joining the Radworks ecosystem —known for the Radicle code forge– focusing on the Radworks App. - **Dorian Taylor:** Developing "Intertwingler," an application server for dense hypermedia that solves the "404 problem" via content addressing. - **Dipanshu:** New member exploring libp2p and Rust. ## Reference links ## Recording Will be available for 2 weeks