You sign in. Nothing is typed.
Your wallet signs a one-time login message, so no password exists to leak. Then your browser unlocks your personal vault key, which is used only on this device.
wallet signature → session · vault key unlocked locallyPrivate storage · Robinhood Chain
ZNode Grid seals every file in your browser, then spreads three copies across independent storage nodes run by real people, not one company's cloud. If a node fails, the grid repairs itself and nothing is lost.
How it works
Scroll to follow one document from your desk, through the grid, and back again.
Your wallet signs a one-time login message, so no password exists to leak. Then your browser unlocks your personal vault key, which is used only on this device.
wallet signature → session · vault key unlocked locallyThe file and even its name are encrypted with AES-256-GCM on your device. The storage nodes that hold it only ever see noise.
plaintext never leaves the browserThe sealed file is copied to three independent storage nodes, spread across different operators where possible. No single machine holds the only copy.
replication factor 3 · least-loaded placementNodes heartbeat every few seconds. When one stops, the coordinator rebuilds its copies on a healthy node, so you're back to three replicas without lifting a finger.
offline after ~15s → automatic repairDownload from any surviving replica. Decryption happens in your browser with your key, so the only place the file is ever readable is with you.
fetch any replica → decrypt locallyHow to use it
Store your own files privately, or lend spare disk to the network and earn from it. Each takes only a few minutes to start.
For everyone
For node runners
$ node server.js --token znj_… --capacity 5
Under the hood
Responsibilities are split so the machines storing your data never get the means to read it, and nobody can move funds that weren't earned.
Unlocks your vault key, then encrypts files and metadata before upload.
Wallet sign-in, payment verification and the encrypted file index.
Admits nodes, places replicas, detects failures, repairs and meters rewards.
Independent machines that store and serve encrypted replicas.
Takes the exact storage payment, holds the reward pool and pays operators. Nobody can take funds that weren't earned.
Inspect contractWhy it holds up
Files and their metadata are encrypted with AES-256-GCM in your browser before upload. Storage nodes only ever hold ciphertext.
// what a storage node actually holds a3f9e1… 48.2 KB 0x9f3ac41e77b02d1fa8e30c55b19e4f7a…
Replicas go to the least-loaded healthy nodes, spread across different operators where possible.
About fifteen seconds after a node goes silent, its replicas are rebuilt on other nodes.
Operators can retire a node safely. Its data moves to other nodes first, then it signs off.
The backend checks chain, sender, contract, call data, exact amount and the emitted event before granting storage.
Where the money goes
Most of every storage payment goes into a reward pool that only the people running nodes can earn from. The contract enforces the rules itself.
See the live contractDefault deployment split shown. The fee is fixed when the contract is deployed and capped at 20%.