NAOMS for developers
← Back to overview

NAOMS · building block

File storage

Chunked storage with indexing and direct transfer between devices.

A file is split into 1MB chunks, each hashed with BLAKE3 and encrypted before it is stored, making storage content-addressed. Two indexes sit alongside it, a lexical index over filenames and a semantic index over extracted content, so files can be found by what they contain. Chunks move directly between devices peer-to-peer, gated by an access check on each request.

What a person notices

What you get as a developer

File storage handles the case signed storage alone doesn’t: content too large to treat as one unit.

How it connects

Related