What TON Storage delivers
- Distribute large files without placing data on-chain
- Prove that a storage provider still holds a bag through on-chain proofs
- Attach bags to TON DNS domains for human-readable access and TON Sites
- Run private or public providers that charge for storage
Core pieces
- Bag of files: a torrent-like package. Its Merkle root (the bag ID) uniquely identifies the bag. The meta file (
.bagequivalent) contains torrent info and header data. - storage-daemon and storage-daemon-cli: download, seed, and manage bags. The CLI controls a running daemon.
- Storage provider contracts: smart contracts that accept paid storage requests, manage balances, and verify proofs.
- Networking: data travels over ADNL using RLDP. Each bag uses its own overlay network, and peers are discovered through TON DHT.
TON Storage reuses torrent-style terms (torrent, bag, pieces) but transports data over ADNL/RLDP instead of BitTorrent.
When to use TON Storage
- Host static TON Sites directly from TON Storage
- Distribute application assets, media, or snapshots with verifiable integrity
- Operate a paid storage service with proof-of-storage guarantees
Next steps
- Run the daemon and work with bags: Storage daemon
- Operate or consume paid storage: Storage provider
- Common flows and DNS records: TON Storage FAQ