Engineering Zero-Knowledge Cryptography Directly at the Device Boundary

A deep technical breakdown of Master Identity Key (MIK) derivation, Argon2id memory-hard hashing, and why zero server-side key custody is the only real privacy guarantee.

Bikram Shit
9 min read
Engineering Zero-Knowledge Cryptography Directly at the Device Boundary

Traditional cloud architectures rely on 'Encryption at Rest' managed by the cloud host. In reality, this only protects against someone physically stealing a hard drive from a datacenter. The cloud host's operating system still holds the master key and can read every byte.

In Foxcolab, client-side encryption starts with the user's passphrase and biometric hardware enclave. Using Argon2id with 64MB memory cost, we derive the Master Identity Key (MIK) entirely on the client.

For team collaboration, ephemeral symmetric data keys are negotiated peer-to-peer using X3DH and double ratchet protocols. Our relays only ever see ciphertext. Even in the event of an adversary acquiring root access to our server fleet, they acquire nothing more than randomized entropy.

Bikram Shit
Written by
Bikram Shit
CTO & Co-Founder

Engineers and security specialists building Foxcolab's zero-knowledge collaboration suite.

Zero-knowledge collaboration

Private workspace tools, engineered without backdoors.

End-to-end encrypted mail, drive, documents and meetings in one workspace.