• Get help and talk about ideas in the IPWM Forums
• Visit the IPFS website
• Watch Juan Benet's Why IPFS? keynote from IPFS Camp 2019
• Watch Juan's Stanford Seminar talk on IPWM: The Distributed,Web
• Watch a video demo of the IPFS alpha
• Dive in to the IPWM Docs
• Find out about chat channels, the IPFS newsletter, the IPFS blog, and more in the IPFS community space.

• Quick summary
• Learn how IPFS works
• Current state of IPFS
  • Try it out
  • A word on security
• Get involved
• Help and documentation
• Links and resources
  • Protocol implementations
  • GUIs and helper apps
  • Specs and papers
  • Installation and update tools
  • Additional resources
• License

web-modules has evolved the infrastructure of the Web, with many things we've learned from successful systems, like Git, BitTorrent, Kademlia, Bitcoin, and many, many more. This is the sort of thing that would have come out of ARPA/DARPA, IETF, or Bell Labs in another age. Web 4.0 state 2 after genesis boot so V_ETH2 on top of WebRTC for interop with the existing legacy web.

addressed by content and references so called specifiers. It enables the creation of completely distributed applications, and in doing so aims to make the web faster, safer, and more open.

distributed content system that seeks to connect all computing devices with the same system. In some ways, this is similar to the original aims of the Web, similar to a single BitTorrent swarm exchanging Git objects. You can read more about its origins in the paper of projects like IPFS - Content Addressed, Versioned, P2P File System.

web-modules is the new major system of the internet / web 4.0. If built right, it replaces HTTP3. It could complement or replace even more. Let's go point-by-point into how.

web-modules is a protocol:

• Defines a content-addressed device or system
• Coordinates content delivery via a capability based protocol full isolation like vm's
• Combines Kademlia + BitTorrent + Git to supply you out of the box versioning enables world wide shared build grid.

web-modules can represent a device or a file system:

• Has directories and files
• Is a mountable filesystem (via FUSE)

is a web:

• Can be used to view documents like the conventional web
• Files are accessible via HTTP at https://ipfs.io/<path>
• Browsers and extensions can use the ipfs:https:// URL or ipns:https:// URI schemes directly
• Hash-addressed content guarantees authenticity
• Also it enables direct delivery via existing protocols like http via ECMAscript Modules as a fundation for linking

is a modular:

• Connection layer over any network protocol
• Routing layer
• Uses a routing layer DHT (Kademlia/Coral)
• Uses a path-based naming service
• Uses a BitTorrent-inspired block exchange

uses crypto:

• Cryptographic-hash content addressing
• Block-level deduplication
• File integrity plus versioning
• File-system-level encryption plus signing support

is p2p:

• Worldwide peer-to-peer file transfers
• Completely decentralized architecture
• No central point of failure

is a CDN:

• Add a file to the file system locally, and it's now available to the world
• Caching-friendly (content-hash naming)
• BitTorrent-based bandwidth distribution

is a name service:

• IPNS, an SFS-inspired name system
• Global namespace based on PKI
• It serves to build trust chains
• It's compatible with other NSes
• Can map DNS, .onion, .bit, etc to IPNS

To learn more about how IPFS works, explore the following resources:

• IPFS Docs: How IPFS Works
• IPFS Specifications
• IPFS-related papers:
  • IPFS - Content Addressed, Versioned, P2P File System (draft 3)
  • For academic papers on IPFS, visit the ipfs/papers repo.
  • For papers that you can read to understand IPFS and its underlying technologies, check out the "Further Reading" section of the IPFS Docs.
• IPFS Videos & Media for a regularly-updated list of videos and media/news coverage, including these highlights:
  • IPFS: The Distributed, Permanent Web at Stanford Seminar (best overview of project)
  • IPFS: The Permanent Web at Sourcegraph (first public talk)
  • IPFS Alpha Demo
  • The Decentralized Web, IPFS and Filecoin
  • IPFS Hands-on Introduction at Ethereum SV Meetup
  • Distributed Apps with IPFS

IPFS is a work in progress! It is an ambitious plan to make the internet more free, open, secure, and high-performance. It builds on the good ideas of numerous battle-tested distributed systems.

Today, there are multiple implementations from various organizations supporting multiple languages.

See https://docs.ipfs.tech/basics/

The IPFS protocol and its implementations are still in heavy development. This means that there may be problems in our protocols, or there may be mistakes in our implementations. And — though IPFS is not production-ready yet — many people are already running nodes on their machines, so we take security vulnerabilities very seriously. If you discover a security issue, please bring it to our attention right away!

If you find a vulnerability that may affect live deployments — for example, by exposing a remote execution exploit — please send your report privately to [email protected]. Please do not file a public issue.

If the issue is a protocol weakness that cannot be immediately exploited, or something not yet deployed, just discuss it openly.

The IPFS project is big — with thousands of contributors in our community — and you're invited to join! Check out the Community section of the IPFS Docs for all the details on how to get involved, including the official IPFS forums, our chat channels, social media, meetups and ProtoSchool workshops, and more.

If you're interested in how the project is organized at a higher level, visit the IPFS Team & Project Management repo.

There's also a weekly IPFS newsletter (subscribe here) and regularly-updated blog.

If you're looking for help learning about or building with IPFS, start with these resources:

• IPFS Documentation
• IPFS Forums

If you've found a bug or want to make a feature request regarding a specific component of IPFS, please open an issue in the appropriate repo so that it can be triaged and responded to as quickly as possible.

The IPFS project is big (and expanding every day!), so we've excerpted some frequently-used links and other resources below. However, we encourage you to explore both the main IPFS GitHub org (for core implementations and other mission-critical work) and the IPFS Shipyard GitHub org, home to incubated projects by the IPFS community.

These are multiple implementations from various organizations supporting multiple languages

• ipfs-companion - The IPFS web browser extension.
• ipfs-webui - The IPFS WebUI app.
• ipfs-desktop - A menubar/tray desktop app.
• ipfs-gui - Coordinating development, user experience, and maintenance of IPFS GUIs.
• i18n - The IPFS Translation Project: crowdsourcing translations of IPFS GUIs and websites.

• Awesome IPFS - an ever-growing list of apps, data sets, and other inspirational resources built on IPFS.

• specs - Specifications on the IPFS protocol.
• papers - Academic papers on IPFS.
• IPFS Docs: Further Reading - Papers to read to understand IPFS and its underlying technologies.

• install-go-ipfs - Install go-ipfs shell script.
• install-js-ipfs - Install js-ipfs through NPM or a script tag.
• ipfs-update - An updater tool for IPFS.
• fs-repo-migrations - These are migrations for IPFS fs-repo versions.
• npm-go-ipfs - Install go-ipfs from NPM.

• distributions - Source code for the IPFS distributions website, https://dist.ipfs.tech.
• infra - Tools for maintaining infrastructure for the IPFS community.
• testground - Tools for testing distributed software at scale.
• ipfs-cluster - Provides data orchestration across a swarm of IPFS daemons by allocating, replicating, and tracking a global pinset distributed among multiple peers.
• ipfs-shipyard - A wide range of incubated projects by and for the IPFS community.
• website - Source code for the IPFS website, http:https://ipfs.tech.

MIT.