Why Bsafe
Bsafe is a decentralized storage network. Your files are encrypted on your device, then spread across independent node operators who are paid by a public contract. No single company owns the disks your data lives on.
Bsafe is built in layers. The ones that hold your data, your money and your keys don't depend on any single company, and network services tie them together.
Anyone with spare disk
Every file is copied to three nodes, owned by three different operators whenever the network has them. Nodes join with a single-use token, prove their identity with their own key and can leave at any time. No company owns the disks.
The StorageIncentive contract
Storage payments go into a public contract on Ethereum. Most of each payment lands in a reward pool that only node operators can be paid from, and the contract caps every payout at what the pool holds.
Your browser
Files and their names are encrypted in your browser before they leave it. No server and no node ever needs your plaintext.
The coordinator
Admits nodes, picks where copies go, watches every node's health, rebuilds lost copies and settles rewards. It routes only encrypted data, and the contract stops it from paying out more than the pool holds.
The backend
Signs you in with your wallet, checks every payment against the chain, and keeps the encrypted index of which nodes hold which copy.
You shouldn't have to take our word for anything. These are the parts you can check for yourself.
StorageIncentive's source is verified on Etherscan. Anyone can read the price, the fee, the pool and every payout.
Live contract stateKeys are derived and files sealed by JavaScript running in your own browser tab. Inspect it, or watch the network tab: only ciphertext leaves.
Security modelOperators run open-source code. It accepts requests only from the coordinator and stores bytes it can't read.
Run a nodeUploads unlock only when the chain, the contract, the call, the exact amount, the confirmations and the purchase event all match.
How payments are checkedYour files are sealed in your browser before they go anywhere. Every layer of the network sees less than you do.
Your browser builds a fixed message that includes your wallet address.
The message hash is stretched into a 256-bit unlock key, on your device.
A random 256-bit key, made once in your browser and stored only wrapped under the unlock key.
Every file and its name is sealed with a fresh IV. A single changed byte breaks the seal.
Assume any one part is compromised. Here is exactly what an attacker gets, and what they still can't do.
If an attacker controls
If an attacker controls
If an attacker controls
If an attacker controls
Three copies on three independent nodes, watched every five seconds and rebuilt automatically. Here is how the network handles failures.
Detected within about 15 seconds. Every copy it held is rebuilt on another node from a healthy replica.
The third copy keeps serving your file and seeds the rebuild of the other two.
AES-GCM rejects it on download, and the file is read from another copy.
Its copies move to other nodes before it shuts down. Nothing is dropped.
They hold only ciphertext, and the other copies of every file sit with different operators.
Cloud drives keep your files and your keys. IPFS shares freely but forgets. Storj is private and durable but bills like a cloud. As understood at the time of writing; check each project's own docs.
| Bsafe | Cloud drives | Storj | IPFS | |
|---|---|---|---|---|
| Who holds the disks | Yes:Independent node operators | No:One company | Yes:Independent operators | Yes:Anyone who pins |
| Encrypted before upload | Yes:In your browser, names too | ~Partly:At rest, with the provider's keys | Yes:Client-side | No:Public by default |
| Stays stored on its own | Yes:3 copies, auto-repair | Yes:Provider-managed | Yes:Erasure coding, auto-repair | ~Partly:Only while pinned |
| Sign-in | Yes:Wallet signature | No:Email and password | ~Partly:Account | Yes:None |
| Payment | Yes:Once, on-chain | No:Subscription | ~Partly:Monthly usage | No:Not built in |
| Operators paid by | Yes:A public contract, in ETH | No:n/a | ~Partly:Storj, monthly, in a token | No:Nobody |
| Self-repair speed | Yes:About 15 seconds | ~Partly:Provider-managed | Yes:Automatic | No:None |
Where the network is heading. Directions we are working towards, not promises.
Derive vault keys straight from a wallet signature, binding your files even more tightly to your wallet.
Regular challenges where every node proves it holds its copies, with rewards tied to passing them.
Operators lock $BSAFE as a bond that can be slashed for proven data loss. The contract is written and ready for the token.
Export and hold your own encrypted index, wherever you want it.
Node admission and reward rates published on-chain for anyone to check.
Several independent coordinators working side by side across the network.
The same durability as three full copies, using less disk.
Go deeper