Part 01 — Paradigm Shift
v0.0.1A decentralized file system that maps Unix semantics onto blockchain, encrypts everything by default, and enables trustless data commerce through atomic swaps.
Get Started
# Install from source $ go install github.com/bitfsorg/bitfs/cmd/bitfs@latest # Initialize wallet $ bitfs wallet init # Upload your first file $ bitfs put ./hello.txt /my-files/
Part 02 — What is BitFS
Unix filesystem on blockchain — inodes, directories, symbolic links, all as native transactions.
Every file encrypted by default using deterministic ECDH. No key management headaches.
Local transactions + Merkle proofs. Never queries the blockchain directly.
Part 03 — Architecture
BitFS separates concerns into distinct layers — ownership lives on-chain, logic runs locally, and delivery scales through an incentivized network.
Decentralized CDN. A BSV-homomorphic chain that incentivizes data retrieval across a global network of nodes. Separate product at metanet.org.
Local-first control plane. Manages encryption, transaction construction, SPV validation, and the Unix filesystem abstraction. Your keys never leave your machine.
Immutable ownership layer. Stores Metanet DAG transactions, payment channels, and HTLC atomic swap contracts. Unbounded scaling for data at rest.
Part 04 — Key Features
01
Trustless buy and sell. Hash time-locked contracts ensure fair exchange without intermediaries. If either party fails to act, funds return automatically.
02
ls,
cat,
put,
get
— familiar commands for a revolutionary filesystem. Agent-first design means every operation is scriptable.
# Navigate like any Unix system $ bitfs ls -la /shared/docs/ # Pipe, redirect, compose $ bitfs cat /notes/draft.md | wc -l # Upload with encryption $ bitfs put --encrypt ./file.pdf
03
Human-readable addresses. Send files to user@bitfs.org instead of cryptographic hashes. Built on the Paymail protocol for seamless identity resolution.
04
Hierarchical key derivation for fine-grained file permissions. Share access to a directory without exposing parent keys. Revoke by rotating a single derivation path.
Part 05 — In Practice
# Upload and encrypt a file $ bitfs put --encrypt ./report.pdf /shared/docs/ encrypted → tx:a3f8...c2d1 [2 inputs, 3 outputs] # List with Merkle proofs $ bitfs ls -l --spv /shared/docs/ -rw-r-- 42.3K report.pdf [spv: verified] -rw-r-- 1.8K notes.md [spv: verified] # Trustless sale via HTLC $ bitfs sell --htlc /shared/docs/report.pdf --price 0.001BSV htlc published → hash:7b2e...f194 expires: 144 blocks
Part 06 — Deep Dive
Explore the full technical design — from Metanet DAG construction to Method 42 encryption, HTLC protocols, and the Metanet Chain incentive model.
Part 07 — Ecosystem
BitFS stores your files.
Metanet delivers them to the world.
Think of BitFS as the filesystem and Metanet as the delivery network. Together they form a complete decentralized storage-and-retrieval stack — analogous to how IPFS and Filecoin complement each other, but built on Bitcoin.
Visit metanet.orgDecentralized encrypted file system. Unix CLI, Method 42 encryption, HTLC atomic swaps. Your keys, your data.
bitfs.orgDecentralized CDN powered by the Metanet Chain. Incentivized retrieval, global node network, MNT token economics.
metanet.org