Where are my files?
Your file is encrypted on your device, then goes to Walrus, a decentralized storage network.
Walrus splits it into slivers and spreads them over 1,000 shards.
A little more than a third of the slivers is enough to rebuild the whole file.
Your file's bytes never pass through the NMTS server. The Walrus nodes that hold the slivers see only encrypted bytes.
Where is my key?
Your NMTS key is 20 random bytes made on your device.
Your account identifier, sign-in secret, file keys and wallet key are all computed from it. None of them can be turned back into the key.
The key never goes to the server, so NMTS cannot open your files.
If you lose the key, nobody can get it back. NMTS has no reset either.
What if NMTS disappears?
Your encrypted files are on Walrus and stay there for the period you paid for.
With your recovery list saved, the open-source recovery tool rebuilds your files without any NMTS server.
Without the recovery list, the keys that open your files exist only in the NMTS database.
Who pays whom?
NMTS takes no fee.
Your wallet pays Walrus in WAL for storage and Sui in SUI for the records, directly.
You can also pay with credits. One credit stores 1 MB for 28 days.
The free trial is first come, first served, every week.
What does the NMTS server see?
What the NMTS server sees: how many files, the size of each, when each was added and removed.
What it cannot see: the contents, the names, the folders, your NMTS key.
Your IP address is never stored in a form that can be turned back into it.
The limit: if the NMTS server turned malicious, it could send your browser bad code. Every end-to-end encrypted service that runs in a browser shares this limit.
NMTS in numbers
- 20 bytes
- The size of an NMTS key
- 1,000
- Walrus shards your file's slivers are spread over
- โ
- The share of slivers needed to rebuild a file (a little more)
- 4.5ร
- Encoded size on Walrus, against the original
- 2 weeks
- One Walrus Mainnet epoch
- 0 %
- NMTS's fee
- 4
- Public repositories: the CLI, the SDK, the encryption engine, the recovery tool
- ML-KEM-768
- The quantum-resistant key exchange used for sharing, alongside X25519