Sealed before it travels
Every file, and its name, is encrypted with AES-256-GCM inside your browser. Servers and nodes only ever hold ciphertext.
Bsafe
A vault where the lock is on your side. Files are encrypted in your browser, copied to three independent nodes, and paid for by a contract anyone can read.
256-bitAES-GCM
3×replicas
~15 sto notice a failure
01 — Principles
Built so you don't have to trust anyone with the contents.
Most cloud drives keep your files and the keys to them. Bsafe moves the key to your device and the storage to a network of operators who only ever see scrambled bytes.
Your wallet is the login
Sign one message and you are in. No email, no password, no account that a company can freeze.
Copies that repair themselves
Each file lives on three independent nodes. If one disappears, the network rebuilds the missing copy within seconds.
One payment, no meter
Pay once, on-chain, per wallet. The contract sets aside most of it as a reward pool for the people holding your data.
Anyone can host
Run the node software on spare disk, join with a one-time token and earn ETH for space, bandwidth and uptime.
Payouts enforced by code
A public contract pays the node operators. Nobody can pay out more than users paid in, or take back what an operator earned.
02 — The life of a file
From your disk to the grid and back.
Scroll through what happens to a file, step by step.
Sign in. Type nothing.
Your wallet signs a one-time login message and your browser unlocks a vault key that lives only in this tab. There is no password to lose and no inbox to phish.
wallet signature → session · vault key unlocked locallySeal it on your side.
The file and its name are encrypted with AES-256-GCM before a single byte leaves your device. Everything downstream handles noise.
plaintext never leaves the browserSpread three copies.
The sealed file is written to three independent nodes, run by different operators wherever possible. No one machine holds the only copy.
replication factor 3 · least-loaded placementA node dies. The grid mends.
Nodes report in every few seconds. When one goes quiet, the coordinator copies its replicas from a healthy node onto a new one, restoring three copies without you.
offline after ~15 s of silence → automatic repairTake it back.
Download from any surviving replica. Your browser decrypts it locally, so the readable file only ever exists on your device.
fetch any replica → decrypt locallylive diagram
03 — Two ways in
Store files. Or host them.
For everyone
Keep what's yours
Connect a wallet, pay once and drop files in. They come back from any browser where you sign in with the same wallet.
- No password, no recovery email
- Names and contents unreadable to the network
- Delete a file and every node removes it
For operators
Put spare disk to work
Start a node with a one-time join token. You earn for the space you hold, the data you serve and the hours you stay online.
- Works behind a home router with a built-in tunnel
- Claim and withdraw ETH from your own dashboard
04 — The numbers
No fine print in the fine print.
The parameters that matter, as the code uses them today.
| Encryption | AES-256-GCMA fresh random IV per file. File names and metadata are sealed the same way. |
|---|---|
| Replication | 3 copies per fileSpread across different operators first, then by lowest load. |
| Failure detection | About 15 secondsNodes report every 5 s. Silence triggers automatic re-replication. |
| Largest file | 50 MBFiles are encrypted whole in the browser. |
| Payment | Once per walletVerified against the chain before any upload is accepted. |
| Operator pay | ETH, on demandClaim from the reward pool, then withdraw whenever you like. |
| Network | Ethereum MainnetChain ID 1. |