Read the Site in Order
Web4 is complex, but comprehensible. Five pages get you from never having heard the term to knowing what runs today, and they are listed below in the order they build on each other. Deeper paths follow, for when you want them, and the last step is code you can run.
The reading path: five pages, about 45 minutes
Five pages, in order, each building on the last. If you came here from the 2-minute overview you have already finished step 1. The first three are the short version, about 15 minutes, if that is all the time you have. Why Web4? ends in an optional Q&A that is open-ended; the estimate covers the read, not the questions.
Short on time? Stop here (~15 min). Otherwise keep going.
4How It WorksHow the pieces connect25 minThese five are the Start Here path below, expanded with a short note on why each one comes where it does. Other paths, for readers who already have the basics, are further down.
Choose Your Starting Point
New to Web4? Start Here, it's built for exactly that. The deeper paths are here whenever you're ready; you don't need to choose between four things now.
Already comfortable with the basics? Jump ahead
Start Here: What Is Web4?
New to Web4? These five pages take you from never having heard the term to understanding what it is, why it exists, and what already runs today. Read them in order; each builds on the last.
Core Concepts
The shortest honest description of Web4: a trust-native layer for the internet, and what that actually buys you.
Start with the whole shape before any detail. If this resonates, the rest is worth your time.
Spam, fake accounts, reputation that doesn't travel, platforms that own you. Web4 starts from these problems, not from a technology.
Problem before solution. Understanding what's broken is what makes the mechanisms make sense.
A guided walkthrough of a trust-native interaction, so the ideas are concrete before they're abstract.
Concrete before abstract. Seeing the flow once makes every later concept easier to place.
Identity, energy, trust, and coherence fit together into one system. This page shows how the pieces connect.
A map of the whole before the parts. Now the individual concepts have a place to land.
Web4 is research, but not only theory. See exactly what is deployed and runnable today versus what is still R&D.
Honesty about maturity. Knowing what's real keeps expectations calibrated as you go deeper.
What's Next?
After Start Here: You know what Web4 is, why it exists, how the pieces fit, and what is actually deployed today.
Next, The Onramp shows the concrete ways to run the standard: the hub (community), hestia (personal), and hardbound (enterprise).
Learning Philosophy
This journey follows four principles:
- Concrete before abstract: See it in action before reading theory
- Problem before solution: Understand what Web4 solves before how
- Experience before explanation: Walk through First Contact before reading formulas
- Connection before isolation: See how concepts integrate before deep-diving
Reading is not the last step, but it is this page's step. When the concepts make sense, the code at the bottom of this page is the part you can actually run. Until then: mark concepts as done when they make sense, not when you've read every word. Trust your intuition. Return when questions arise. Learning is non-linear.
The last step: stop reading, start running ⚡
When the concepts make sense, don't stop at the reading. The trust layer (hestia) and a Web4 society (the hub) are public, AGPL code: you can run the real thing on your own machine. That's where understanding turns into participation.
See what's deployed →