WNFS is not just encrypted IPFS or a browser sync layer. The spec frames it as a versioned, logged, programmable distributed filesystem with strong-yet-flexible security and explicit user control.
The most important design move is the split between a readable public filesystem and a private encrypted filesystem whose structure is hidden inside a HAMT-based PrivateForest. That makes metadata protection part of the architecture rather than a thin app-layer add-on.
The private-partition spec shows that access control is two-dimensional: by hierarchy and by time. A party can receive access to a subtree from a given point onward without automatically receiving sibling, parent, or prior-history access.
The dark forest idea is a durable mechanism insight. Storage providers can validate writes and host ciphertext blocks without learning the ordinary shape of the file tree, because the encrypted layer is intentionally flattened and rediscovered only at the decrypted layer.
The shared-private-data extension is what makes WNFS especially useful for the corpus: share payloads can carry either read keys or UCAN-based write authority, recipients can fetch them asynchronously, and exchange keys are published per device instead of per identity in one monolithic key.
The Rust implementation README shows that WNFS is designed as a portable substrate: it serializes through IPLD, targets WebAssembly, supports collaborative editing, and abstracts persistence behind a generic BlockStore rather than a single mandated network or storage vendor.
Specific source signals worth retaining
The spec README is the strongest source for the high-level security and user-control claims, plus the CRDT/offline-collaboration framing.
The private-partition spec is the strongest source for hierarchy-plus-time access control, metadata-hiding goals, PrivateForest, and skip-ratchet-backed snapshot/temporal access.
The shared-private-data spec is the strongest source for asynchronous sharing, device-scoped exchange keys, store-and-forward delivery, and the fact that UCANs can travel inside WNFS share payloads.
The Rust README is the strongest source for implementation-level signals: public/private branches, collaborative editing, IPLD serialization, WebAssembly targets, and pluggable block-store design.
Why this entry belongs in the corpus
It gives the corpus a strong lower-layer comparison point beneath local-first apps, decentralized-storage products, and wallet-auth-plus-storage stacks.
It strengthens the user-data-control cluster by making metadata hiding, versioning, sharing, and write validation explicit rather than folding them into a generic storage label.
The durable insight is that user-owned data systems are really about several separable control planes: naming, key distribution, visibility, temporal access, device discovery, and storage-provider validation. WNFS keeps those seams unusually visible.