When you upload a file to Hivenet, a lot happens behind the scenes—but all of it serves one purpose: making sure your data is locked down and stored safely.
Let’s walk through a high-level view of what happens when you upload a file.
Step-by-step: how encryption works during upload
Your file is split into smaller chunks
This helps with speed, storage, and redundancy across the network.Each chunk gets a unique “block key”
This is generated from the dedup key + the chunk’s contents. It ensures each chunk is uniquely encrypted.Chunks are compressed
This saves space and helps the upload process go faster.Chunks are encrypted using their block key
So even if someone got a chunk (which they won’t), they couldn’t read it.Chunks are broken down again into smaller “shards”
These shards are what get stored across Hivenet’s distributed network.
How chunks become a file again
After all the encrypted shards are created:
A reference file is generated that links the shards together as one file
This reference data is encrypted too—using a new block key
And that block key? It’s encrypted with the read key, for even more protection
Everything is layered, encrypted, and distributed. The result? Your file is unreadable, unreconstructable, and invisible to anyone without your encryption passphrase.
Next, we’ll walk through what happens when you want your file back.
Previous:
⬅️ Encryption begins when you create your account