like this

Many brothers have recently private messaged me asking how to learn Web3 knowledge. Today I will share my suggestions in a unified manner. If there are any mistakes or omissions, brothers are welcome to leave comments and correct me🫡
I recommend that newcomers learn Web3 knowledge in two stages:

Stage 1: Build a foundational understanding of the industry
This involves understanding the basic concepts, tracks, and projects of Web3. Through some simple practices, you will gain a preliminary understanding of Web3, specifically including:
1. Acquire basic Web3 survival skills:
> Create your Web3 identity
> Install a wallet (MetaMask / Phantom)
> Manually back up your seed phrase (do not screenshot)
> Learn to switch networks (ETH / Solana)
Standard completion:
You know that wallet ≠ exchange
You can explain what private key risk is

2. Learn the most basic operations
> Transfer funds (wallet → wallet)
> Authorization (What is Approve)
> Check transactions using block explorers (Etherscan / Solscan)
Standard completion:
You can understand whether a transaction was successful or failed

2. Learn to understand projects, not just prices
1. Break down projects
Pick any project at random and answer these 4 questions:
> What problem is it solving?
> Why must it use a Token?
> What is the Token used for?
> Who is driving this project?
Standard completion:
You can explain a project clearly in 3–5 sentences

2. Establish Web3 information sources
Follow 20 high-quality accounts, such as founders/builders/researchers/real traders
Standard completion:
The information you see is not “pump signals,” but logical discussions

3. Participate with low risk, not gambling from the start
1. Start real interactions (small amounts)
> Use 3–5 protocols
> Each interaction amount < $10
> Record what you did
Standard completion:
You understand what real experience in DeFi / NFT / Meme is

2. Engage in early opportunities
> Testnets
> Airdrop tasks
> New product experiences
Standard completion:
You begin to accumulate on-chain behaviors.

The purpose of the above learning stages is to help you master basic Web3 operations, understand fundamental Web3 concepts, and project operation logic. Only then can you move on to the next stage.

Stage 2: Choose a direction and start meaningful learning
It is recommended to focus on only one area and go deep. Suggested directions include:
Community Operations / Social Media Operations / Content Operations / Business Development / Product

Community Operations
You need to understand what this area is doing: it’s about retaining users, encouraging activity, and building consensus.
Essentially: Relationship + Order + Emotional Management
You can first join 5–10 project Discord / TG communities to observe:
> What do admins do daily?
> When is the community most active?
> How are conflicts handled?

Then analyze a real community operation case, focusing on:
> How do newcomers join?
> Why do veterans stay?
> Are there levels / permissions / roles?
> How are levels / permissions / roles designed?
> Are incentives based on Token, identity, or information?
The core is to understand how they design user acquisition, retention, user growth systems, and incentive mechanisms.
You can analyze several communities and share your insights on X. You can also participate in communities you’re interested in to gain practical experience.

Social Media Operations
This area is about communicating the project to people who haven’t joined yet.
You can analyze 20 successful accounts, observing:
> Content types (project updates / opinions / news / emotions / memes)
> Posting frequency
> Interaction methods (replies, retweets)

Don’t focus on follower count; look at engagement density, then imitate:
> One post per day
> Start by mimicking structure, then develop your style
> Don’t chase viral, focus on consistency

How to tell if you’ve entered the beginner stage? Check if your account has stable interactions, and whether followers and traffic are growing.

Content Operations
This area mainly involves explaining complex concepts clearly.
Start with “breaking down projects,” for example:
> What does the project do?
> What is the narrative?
> What is the purpose of the Token?
> Where are the risks?
You can write project overviews / in-depth analyses / opinion articles / market reviews. Use output to drive learning; if you can’t explain clearly, it means you haven’t understood.
Aim for 3 articles per week, not necessarily long, but complete, and post on X / Notion / Mirror. To judge whether your content is influential, see how many people cite your work.

Business Development (BD)
This area focuses on resource integration and partnership implementation.
So you need to learn:
1. How to find people?
Use X / Discord / TG to find project founders / BD / DevRel
2. How to introduce yourself
3. How to propose collaborations
4. How to negotiate
5. How to follow up on collaborations

It’s recommended to attend more online and offline events, actively build networks and connect with project teams. These relationships and resources are the foundation for your continuous growth in this area. Also, if your English isn’t good, improve your listening, speaking, reading, and writing skills first. Additionally, you should have a deep understanding of the industry; otherwise, if someone mentions a term or project name you don’t know, it will make you seem inexperienced.

Product
This area involves transforming needs into interactive functions, essentially solving user problems. If you lack experience as a product manager in the internet industry, it’s personally recommended not to consider this direction. If you are a product manager in a traditional industry but unfamiliar with Web3 products, you can consider:
1. First choose one or two tracks you are most interested in
2. Find the top five projects in that track
3. Conduct product research on each project, starting from user pain points and needs to solutions, deeply understanding their core features, target audience, and solutions
4. Understand the underlying protocols supporting these features, which extensions they support, and which they don’t. Pay close attention to updates in the underlying protocols within these tracks.

That’s my personal advice. Brothers are welcome to point out gaps and discuss with each other. Hope it’s helpful, and don’t forget to follow🫡