IPFS - The Permanent Web

A five-in-five talk I delivered at RESTFest 2014.

Transcript

1. IPFS
 The Permanent Web Joel Clermont
 @jclermont “Interplanetary” conveys the breadth of the scope If you’re going to build a global filesystem, why not add other planets too? A bit of a “mad scientist” idea
2. = BT + git + Web
3. = DHT + BT + git + SFS +Web
4. = DHT + BT + git + SFS +Web global one massive BT swarm literally one global (interplanetary) file system
5. = DHT + BT + git + SFS +Web global, content-addressed every object has an address just like how git works with hashes (it’s a multi hash, not tied to one algorithm) content is immutable
6. = DHT + BT + git + SFS +Web global, content-addressed, versioned versioning falls out of immutability changing a file automatically creates a new object with a new hash arbitrary large files, most people avoid large binaries in git
7. = DHT + BT + git + SFS +Web global, content-addressed, versioned,
 peer to peer file system basic operations: put(k,v) and get(k) => v anyone can serve that item, DHT routes you 20 hops for 10 million nodes BitSwap exchange protocol - different approach than BT tit-for-tat
8. Use Cases • Permanent Web • CDN • locally mounted file system • versioned package manager links don’t die CDN - integrity verification and encryption supported /ifps, with sync properties (dropbox, btsync), can even boot VMs from it package manager for ALL software
9. No More Time!! • Trust" • Performance" • Fairness" • Naming" • Data Structure" • Encryption" • Incentivization
10. Your Homework read the paper
 get the code" discuss in IRC ifps.io only 11 pages Node and Go implementations