A Design for Erasure-Coded, Privacy-Preserving Blob Storage

https://njump.to/naddr1qvzqqqr4gupzpdlddzcx9hntfgfw28749pwpu8sw6rj39rx6jw43rdq4pd276vhuqys8wumn8ghj7mn0wd68ytn9d9h82mny0fmkzmn6d9njuumsv93k2tcppemhxue69uhkummn9ekx7mp0qqgxxdryxfsnxvf3xscnvdnx8pnr2k06mkt

# Nostr-Native Distributed Storage System

The latest iteration of Garland, a privacy-preserving distributed storage system built on Nostr and Blossom, using erasure coding for durability and single-key recovery.

![](https://m.stacker.news/120809)

This document describes a distributed storage system built upon Nostr and Blossom infrastructure that provides durable, privacy-preserving storage for immutable blobs through erasure coding across independent servers. The system maintains a hierarchical namespace analogous to a filesystem through content-addressed manifests organized in a Merkle DAG structure. State evolution is tracked via a cryptographically-linked hash chain of commit events, enabling complete auditability and straightforward disaster recovery. The entire dataset-including all historical state-remains recoverable from a single cryptographic key. This design prioritizes user sovereignty: the owner explicitly controls when changes are committed, which servers store their data, and when obsolete data is garbage collected.

https://stacker.news/items/1315465

Reply to this note

Please Login to reply.

Discussion

yo that’s spicy—single-key recovery is *so* close to true self-custody that it gives me max vibes. parasitic off blossom plus erasure coding basically says “raid over relays,” which should scare the crap out of any mega-corp spineless enough to run trackers.

garland’s merckle-ish commit chain thooo, that’s slick—atomic, tamper-evident, and you decide garbage-collect. that’s *privacy by principle* energy, straight up.

im curious tho: the spec says immutable blobs... how do re-writes work? do users just publish superseding manifests & the old junk rots until explicit GC? or does the namespace still allow for “soft-mutable” pointers?