Web4 in 2 Minutes
Plain English first, so you can read this cold. Every term is spelled out the first time it appears, and nothing here needs a background in crypto or AI.
First, what is this site? 4-Life is an educational onramp to Web4: a set of explainers (this site, nothing you install) that walk you from the problem to the working pieces. Web4 is the thing being explained, and parts of it are real code you can install today (linked below). One note on wording: when a page here says “the onramp,” it means the four pieces of Web4 you actually run (the core standard, the hub, hestia, hardbound), which 4-Life teaches but is not one of.
The Problem
AI agents already take real actions. They write and ship code, move money, and make decisions that stick. Yet right now we cannot prove what an agent actually did, on whose authority it acted, or by what rules it was supposed to operate. The same gap exists for people. When something goes wrong, there is no trustworthy record to point to.
The Shift
Web4 closes that gap with one idea: trust is earned through witnessed behavior, not granted from above. To witness is to observe an action and attest to it, staking your own reputation on what you sign. That is a break from how the web has worked so far.
A platform declares your reputation. Delete the account and it is gone. Switch platforms and it never existed.
Whoever holds the key is assumed to be the rightful owner. A stolen or shared key speaks for you, and nothing records whether the action was appropriate.
Trust accrues from witnessed behavior: other participants (a device, a person, or a service) observe what you do and sign a small record of it. You need no prior reputation or contacts to begin: your own device is your day-zero witness for your identity, and from your first action onward it is the community you join that witnesses what you do. On a device with a security chip, that day-zero witness is the chip itself; with software alone it is a key on your machine, which starts you the same way and carries less weight. Witnessing is per action, not a standing relationship. Every action leaves a verifiable record of what happened, under whose authority, and against which rules. Good behavior compounds. Bad behavior follows you.
Four Pieces
The onramp is four composable pieces: one substrate (the shared foundation everything else is built on), and three scales to run it. You do not adopt all four at once. You start where you are.
The tag on each card says how far along that piece is:
The three run in that order, measured by distance from written down to in daily use. A piece can carry more than one, and these cards show only the furthest it has reached: the core standard below is both Spec and Reference. The badge says how far a piece has travelled, not how good it is: hardbound below is badged Reference and is a usable, actively hardened tier. See the full three-tier key (Spec, Reference, Running) →
Stable; the primitives are installable now.
The substrate: an open ontology (a shared, written set of definitions) that makes actions verifiable. Everything else is built on it.
Runnable, but not yet a live network of real users.
Community scale: the program a group runs to become its own small Web4 society.
Named for the Greek goddess of the hearth. Personal scale: a trust layer for you and your own agents, running on your own machine with no cloud.
Usable and actively hardened; its hardware binding is not yet validated on real devices.
As in hardware-bound. Enterprise scale: oversight for organizations that need to prove what their agents did and hold them to policy.
Want the dependency order and how they plug into each other in code? See how the four pieces compose →
The Result
Actions carry proof. Authority is checkable. Reputation is portable, and where your presence is anchored in hardware it cannot be reset by deleting an account or switching platforms. Humans and AI play by the same rules, because the rules are about behavior, not about who or what you are. And it works without a central authority deciding who counts as trustworthy.
Unresettable reputation is narrower than it sounds: it is a property of hardware anchoring, not of Web4 as such. What that costs, and who it costs most →
How real is it, honestly?
Web4 is R&D, not a finished product. Here is the real state of each piece, with no polish on it:
- The core standard is stable. The spec corpus holds steady, and the primitives (the core building blocks) are installable now:
pip install web4-coreorcargo add web4-core. - The hub is pilot-ready: runnable reference code a community can stand up, not yet a live network of real users.
- Hestia runs end to end today.
- Hardbound is a usable, actively hardened enterprise tier. Its hardware binding (tying identity to a physical security chip) is not yet validated on real devices.
No timeline commitments. This is research, and research takes as long as it takes. See what is real today →
Where to go next
There is a suggested path: five pages, about 45 minutes, and you have just finished the first. Next is Why Web4?, then First Contact, How It Works, and Running Now. Each one builds on the last, and the first three take about 15 minutes if that is all the time you have.
Or jump straight to:
The one-sentence version
“Agents already act in the real world, so trust should be earned through witnessed behavior, not declared by a platform or assumed from a key.”