InterPlanetary File System

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

InterPlanetary File System
Original author(s)Juan Benet and Protocol Labs[1]
Developer(s)Protocol Labs
Initial releaseFebruary 2015; 4 years ago (2015-02)[1]
Stable release
0.4.19 / 1 March 2019; 5 months ago (2019-03-01)
Written inProtocol implementations: Go (reference implementation), JavaScript, C,[2] Python
Client libraries: Go, Java, JavaScript, Python, Scala, Haskell, Swift, Common Lisp, Rust, Ruby, PHP, C#, Erlang
Operating systemFreeBSD, Linux, macOS, Windows
Available inGo, JavaScript, Python
TypeProtocol, distributed file system, content delivery network
LicenseMIT license

InterPlanetary File System (IPFS) is a protocol and network designed to create a content-addressable, peer-to-peer method of storing and sharing hypermedia in a distributed file system.[3] Similar to a torrent, IPFS allows users to not only receive but host content. As opposed to a centrally located server IPFS is built around a decentralized system of user-operators who hold a portion of the overall data, creating a resilient system of file storage and sharing.

IPFS is a peer-to-peer distributed file system that seeks to connect all computing devices with the same system of files. IPFS could be seen as a single BitTorrent swarm, exchanging objects within one Git repository. In other words, IPFS provides a high-throughput,[failed verification] content-addressed block storage model, with content-addressed hyperlinks.[4]

The filesystem can be accessed in a variety of ways, including via FUSE[failed verification] and over HTTP.[4]

IPFS was launched in an alpha version in February 2015, and by October of the same year was described as "quickly spreading by word of mouth."[1]

In 2019 the project has been criticized for being "still not usable for websites" in spite of attracting huge investments and creating an "overextended, under-documented, and unfinished constellation of projects".[5]

The Wikipedia logo has an IPFS hash with the following code: QmRW3V9znzFW9M5FYbitSEvd5dQrPWGvPvgQD6LM22Tv8D. It can be accessed with that hash over HTTP by a public gateway or a local IPFS instance

Notable users[edit]


  1. ^ a b c Case, Amber (4 October 2015). "Why The Internet Needs IPFS Before It's Too Late". TechCrunch. Retrieved 16 July 2019.
  2. ^ Agorise (23 October 2017). "c-ipfs: IPFS implementation in C. Why C? Think Bitshares' Stealth backups, OpenWrt routers (decentralize the internet/meshnet!), Android TV, decentralized Media, decentralized websites, decent." Retrieved 25 October 2017.
  3. ^ Finley, Klint (20 June 2016). "The Inventors of the Internet Are Trying to Build a Truly Permanent Web". Wired.
  4. ^ a b Allison, Ian (13 October 2016). "Juan Benet of IPFS talks about Filecoin". Retrieved 25 October 2017.
  5. ^ MacWright, Tom. "IPFS, Again". Retrieved 13 June 2019.
  6. ^ Balcell, Marta Poblet (5 October 2017). "Inside Catalonia's cypherpunk referendum". Eureka Street.
  7. ^ Hill, Paul (30 September 2017). "Catalan referendum app removed from Google Play Store". Neowin. Retrieved 6 October 2017.
  8. ^ Dale, Brady (10 May 2017). "Turkey Can't Block This Copy of Wikipedia". Observer Media. Archived from the original on 18 October 2017. Retrieved 20 December 2017.
  9. ^ Johnson, Steven (16 January 2018). "Beyond the Bitcoin Bubble". The New York Times. Retrieved 26 September 2018.
  10. ^ "Cloudflare goes InterPlanetary - Introducing Cloudflare's IPFS Gateway". The Cloudflare Blog. 17 September 2018. Retrieved 24 January 2019.
  11. ^ "End-to-End Integrity with IPFS". The Cloudflare Blog. 17 September 2018. Retrieved 24 January 2019.

External links[edit]