content-addressable-storage-immutability
/content-addressable-storage-immutability
Chroni przed modyfikowaniem plików w magazynach adresowanych treścią, gdzie nazwa pliku jest hashem (SHA256, IPFS CID): Blossom, IPFS, ProofMode, bez optymalizacji typu faststart czy kompresji.
- Autor
- divinevideo ↗
- Repozytorium
- divine-mobile ↗
- Licencja
- AGPL-3.0
- Ostatnia zmiana repozytorium
- 27.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 3
Brak sygnałów. Repozytorium zmienione 27.10.2026, bez odwołań do wycofanych modeli i API.
AGPL-3.0, copyleft: przeróbki udostępniane innym muszą mieć tę samą licencję.
Co robi i kiedy
Chroni przed modyfikowaniem plików w magazynach adresowanych treścią, gdzie nazwa pliku jest hashem (SHA256, IPFS CID): Blossom, IPFS, ProofMode, bez optymalizacji typu faststart czy kompresji.
Wyzwalacze z opisu
Oryginalny opis (EN)
CRITICAL: Never modify files in content-addressable storage systems where the filename IS the content hash (SHA256, IPFS CID, etc.). Use when: (1) Working with Blossom protocol, IPFS, or any CAS system, (2) Considering "optimizing" stored files (faststart, compression), (3) Implementing transcoding or processing pipelines for hash-identified content, (4) Building on top of ProofMode or any cryptographic verification system. Modifying files in place breaks hash verification and content integrity.
Jak działa
- Problem
- Context / Trigger Conditions
- The Fundamental Rule
- What Goes Wrong
- Solution: Store Derivatives Separately
- Implementation Pattern
- Verification
- Common Mistakes
- Notes
- References
Podgląd SKILL.md
---
name: content-addressable-storage-immutability
description: |
CRITICAL: Never modify files in content-addressable storage systems where the filename
IS the content hash (SHA256, IPFS CID, etc.). Use when: (1) Working with Blossom protocol,
IPFS, or any CAS system, (2) Considering "optimizing" stored files (faststart, compression),
(3) Implementing transcoding or processing pipelines for hash-identified content,
(4) Building on top of ProofMode or any cryptographic verification system. Modifying
files in place breaks hash verification and content integrity.
author: Claude Code
version: 1.0.0
date: 2026-01-31
---
# Content-Addressable Storage Immutability
## Problem
In content-addressable storage (CAS) systems, files are identified by their content hash.
If you modify a file in place (even "harmless" optimizations), the content no longer
matches its identifier, breaking the entire system's integrity guarantees.
## Context / Trigger Conditions
- Working with Blossom protocol (files at `/{sha256}`)
- Working with IPFS (files at `/ipfs/{CID}`)
- Any system where filename = hash of content
- Considering file optimizations like:
- MP4 faststart (moving moov atom)
- Image optimization/compression
- Metadata stripping
- Format conversion
- Systems using ProofMode or cryptographic verification
## The Fundamental Rule
**NEVER modify a file stored at its content hash.**
The hash IS the identity. Change the content → change the hash → file is now at wrong address.
## What Goes Wrong
```
Original file: abc123... (hash) → contains bytes X
After "optimization": abc123... (hash) → contains bytes Y
Result:
- Hash abc123 no longer verifies
- ProofMode signatures invalid
- Content-addressable lookups return wrong data
- Cryptographic proofs broken
- Data integrity compromised
```
## Solution: Store Derivatives Separately
If you need optimized/processed versions, store them at separate paths:
```
/{hash} ← Original file (NEVER MODIFY)
/{hash}/hls/master.m3u8 ← HLS transcoded version
/{hash}/faststart.mp4 ← Faststart optimized version
/{hash}/thumb.jpg ← Thumbnail
/{hash}/720p.mp4 ← Resolution variant
```
The original stays byte-for-byte identical. Derivatives live in subdirectories.
## Implementation Pattern
```rust
// WRONG - modifies original
async fn process_video(hash: &str) {
let path = format!("/{}", hash);
let video = download(&path);
let optimized = apply_faststart(video);
upload(&path, optimized); // ❌ BREAKS HASH!
}
// RIGHT - creates derivative
async fn process_video(hash: &str) {
let original_path = format!("/{}", hash);
let derivative_path = format!("/{}/faststart.mp4", hash);
let video = download(&original_path);
let optimized = apply_faststart(video);
upload(&derivative_path, optimized); // ✓ Original untouched
}
```
## Verification
- Original file hash still verifies: `sha256sum file == filename`
- ProofMode signatures still valid
- Content lookups return expected data
## Common Mistakes
1. **"It's just moving metadata"** - Still changes bytes, still breaks hash
2. **"We'll update the hash reference"** - Now you have dangling references everywhere
3. **"No one will notice"** - Verification systems WILL notice
4. **"It's an optimization"** - Optimize derivatives, not originals
## Notes
- This applies to ANY content-addressable system, not just Blossom
- IPFS, Git objects, Docker layers all follow this principle
- If you need the optimized version as primary, the client should upload it that way
- Transcoding to new formats (HLS, DASH) is fine because they're clearly separate files
## References
- [Content-addressable storage (Wikipedia)](https://en.wikipedia.org/wiki/Content-addressable_storage)
- [Blossom Protocol (BUD-01)](https://github.com/hzrd149/blossom)
- [IPFS Content Addressing](https://docs.ipfs.tech/concepts/content-addressing/)
Wersje
W bazie nie ma innych skilli o nazwie content-addressable-storage-immutability.
Identyczna treść występuje jeszcze w 1 innych folderach na GitHubie. Tu pokazujemy jedną, najlepiej ocenioną kopię.
Migawka bazy z 13.11.2026 · wersja paczki 66470129f099 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 1 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100ipfs
Zapisuje i pobiera pliki w IPFS, przypina treści, wgrywa metadane NFT i obsługuje zdecentralizowane przechowywanie adresowane treścią. - 100blossom-content-addressed-url-filtering
Naprawia ciche pomijanie plików wideo i mediów przy moderacji lub transkodowaniu z serwerów Blossom, gdy kod wyciągający adresy URL filtruje po rozszerzeniach plików. - 100product-sdk-cloud-storage
Wysyła i pobiera dane w zdecentralizowanym storage opartym na CID, korzystając z klienta CloudStorageClient i funkcji store(). - 100pinata-webhooks
Odbiera i weryfikuje webhooki Pinata dla plików IPFS, w tym podpisy Standard Webhooks oraz zdarzenia dodania i usunięcia pliku.