Join us to learn everything about IPFS’s content addressing and content routing subsystems, its content exchange strategies, and how IPFS deals with dynamic, mutable content.
Watch the tutorials to acquire all the background you need in order to start your project on IPFS and the Web 3.0 stack and get involved in the discussion.
All the material on this page is free to use for your own course, talk, or university module.
Web 3.0 joins blockchains, the semantic web, and the distributed web in one package that will revolutionize the way we do networking! In this module, you’ll hear about:
The content routing system of IPFS is the part of the architecture that discovers content in the network. It is a key part of the architecture, and the one with the largest number of open research questions. In this module, you’ll hear about:
Almost there! You’ve learned how IPFS addresses and discovers content and, with this, your client is ready to receive its first bits over the IPFS network! In this module, you’ll understand:
This module answers all your questions on how IPFS can be used for dynamic real-time applications. In this module, you’ll hear about:
libp2p is the Web 3.0 framework of choice for decentralised process addressing. In this module, you will hear about libp2p’s modular and composable building blocks for P2P networking applications and innovation, which include:
InterPlanetary Linked Data (IPLD) is the data layer for content-addressed systems and the Web 3.0. It is a suite of technologies for representing and traversing hash-linked data. In this module you’ll understand:
drand is a distributed randomness beacon. It provides publicly-verifiable, unpredictable, and bias-resistant random numbers as a public service. In this module, we’ll walk through:
We can deliver the course to your lab live with extra features, plenty of time for Q&A, and a top-notch hands-on component! Just fill in the form.
Ask your question, submit your protocol improvement idea, or just let us know about related projects you're working on through our Github Discussion Forum.