Before you start
The Internet is the network connecting devices. The Web is one service built on it: documents and applications linked through URLs and opened in a browser. A domain makes an address recognizable; a website is the content and functionality at the destination.
There are not three separate Internets. An information page, a shop with customer accounts and an application with a wallet can run in the same browser, or within the same project. These labels help explain who publishes, who changes the data and who controls an action.
Three models at a glance
| Aspect | Web1 | Web2 | Web3 |
|---|---|---|---|
| Typical experience | Read pages and follow links | Publish, book and collaborate | Also use on-chain state or assets |
| Website name | Usually DNS | Usually DNS | DNS, blockchain name or both |
| Where data lives | Files published by the author | Application databases and services | Some on-chain; files and services elsewhere |
| Who can change it | Author or publisher | Users under application permissions | Authorized accounts and system rules |
| Wallet required? | No | Usually not | Only for features that require it |
| Key limitation | Author-managed updates | Reliance on operators and services | Compatibility, keys, costs and hybrid dependencies |
The name is not the website
Think of a shop: its name is the sign, resolution tells you where to go, hosting stores the digital storefront, and the application runs the operations. Buying the sign does not build the shop. Likewise, a domain does not automatically include a website, email or payments.
One path, five lessons
The evolution of the Web
Reading, participating and verifying are different ways to use the Web. New approaches do not erase what already works.
Open the lesson 02 · LessonDNS and blockchain domains
Separate the name, the registry, its controller and its destination. These are four different questions.
Open the lesson 03 · LessonPublish and connect a website
Start with what your visitor needs to do. Choose the domain and technology around that purpose.
Open the lesson 04 · LessonCompatibility and limitations
A name may work in one application and not another. Check resolution, content and actions separately.
Open the lesson 05 · LessonCase studies and workshop
Study documented examples, then apply the method to three learning scenarios. Every design choice has a purpose and a limitation.
Open the lessonChoose your first step
I want to publish a portfolio
Start with static pages and HTTPS access. Choose a memorable name. Add a Web3 domain when you have a compatible route and a clear purpose.
Open the lessonI want to build a service with accounts
Map data, roles and permissions. A database and backend may fit. The site name does not determine how private data is protected.
Open the lessonI want an on-chain verifiable feature
Define exactly what should be verified, by whom and with which dependencies. Study wallets, records, networks and limitations before building it.
Open the lessonThe words you need
- DNS
- A system that resolves domain names to records used to reach services.
- Resolver
- Software that looks up and interprets records in a naming system.
- Wallet
- An interface for managing accounts and authorizing blockchain operations.
- Minting
- Creating or assigning a token in a blockchain registry.
- CID
- A content-derived identifier used by IPFS.
- Pinning
- Keeping content on an IPFS node to help maintain availability.
- Gateway
- A service exposing another network through an interface such as HTTPS.
- Smart contract
- A program executed on a blockchain under defined rules.
- RPC
- An interface used by applications to read data or submit requests to a node.
- dapp
- An application with a component that uses a decentralized network.
Check your understanding
Answers to common questions
Are Web1 domains technically different from Web2 domains?
No separate technical category exists. Both generally use DNS domains such as .com or .it. The distinction is mainly about the website and its features, not its extension.
Does a Web3 domain make my website decentralized?
No. A blockchain-registered name can point to an ordinary server or distributed content. The name, hosting, data and application must be assessed separately.
Do I need a wallet to read this guide?
No. You can learn, visit HTTPS pages and plan a website without a wallet. A wallet is needed for operations that require a blockchain account and a signature.
Is Web3 the same as the Semantic Web?
Web 3.0 has also been used to describe the Semantic Web, which structures data for machines. In this academy, Web3 mainly refers to blockchain-based systems; the terms are not necessarily interchangeable.
Sources and further reading
Primary documentation consulted for this guide. Product, network and integration support can change: check current requirements before configuring a service.