Sixty days ago, I didn’t know the difference between a hot wallet and a cold wallet.
Now, somewhere around Day 60 of writing every single day, that feels like a completely different starting point.
I knew Bitcoin existed. I knew NFTs had created some kind of cultural moment. I had a vague sense that “blockchain” meant something important.
That was it.
If you want to keep up with this journey as I continue building and learning in Web3, you can follow me on X, on Medium, on Future, and join the Web3ForHumans Telegram community.
What 60 days actually is
Sixty days is not enough to become an expert.
I can explain how zero-knowledge proofs work conceptually, but I cannot implement one. I understand why EigenLayer matters for the security economy, but I wouldn’t audit an AVS. I know how gas optimization works in theory, but I wouldn’t deploy a high-stakes contract without a review.
That’s important to say clearly.
Because what 60 days actually gives you is something else.
It removes the fear of terminology. It makes whitepapers readable. It lets you follow conversations without feeling lost. It gives you enough context to form opinions.
That shift from not knowing what you don’t know to knowing exactly where the gaps are is bigger than it sounds.
The articles that surprised me
The article I thought would perform best was the DeFi one. It had a clear topic, obvious demand, and simple framing. It got 69 views.
The one that actually worked was the storage piece, Where Blockchain Data Actually Lives, which I wrote quickly because I was behind schedule and framed as a “war” without thinking too much about it. It ended up at 306 views.
Over 59 days, I learned Web3. At the same time, I learned that I’m not great at predicting what people want to read, and that consistency matters more than trying to get one article right.
The community
Web3ForHumans started as a Telegram group I created so I could share updates without spamming people I knew.
It now has 45+ members.
People share articles, ask questions, and occasionally point out where I’m wrong. I didn’t grow it intentionally. I didn’t run any campaigns. I just wrote every day, mentioned it, and let it grow slowly.
That’s probably the most honest signal I have. People don’t join a Telegram group about Web3 unless something is working.
What I’m carrying forward
The work I did with Bitquery showed me something this series didn’t.
Writing for developers and writing for beginners are completely different skills. The structure, the depth, and the expectations all change. Being able to do both is something I didn’t expect to gain from this.
The series itself taught me something simpler.
Consistency compounds.
The views on Day 5 didn’t matter. The views on Day 35 didn’t come from one article. They came from showing up repeatedly.
A single article doesn’t build anything. A body of work does.
What comes next
The series ends here.
The writing doesn’t.
I’ll keep posting on Medium and Forem. Same tone, same style, just going deeper. Some pieces will be technical, some will be about data, and some will be about things I’m building or trying to understand.
Substack is something I’m taking more seriously now. One piece a week, more reflective, more long-form, and less structured around explaining a single concept.
The Web3ForHumans Telegram stays open. That’s where the conversations are happening.
And the dashboard project I mentioned earlier in the series is still being built. Slowly, publicly, and not in a straight line.
If you’re about to start Day 1
The hardest part isn’t the terminology. It’s the first couple of weeks where everything feels connected and nothing makes sense yet.
Push through that.
By Day 10, things start to form. By Day 30, you start having opinions.
After that, it becomes less about learning everything and more about choosing what you want to go deeper into.
Follow your curiosity instead of trying to go in order. And write, even if it’s not public, because writing forces you to see what you don’t understand.
I started this not knowing what a wallet was.
Now I’m writing about the major pieces of Web3 and the infrastructure behind it.
That’s not a transformation story.
It’s just a data point.
And the only reason that data point exists is because I showed up for more than 60 days.
Thank you
If you’ve read even one article from this series, thank you.
If you’ve been here since the early days, when the views were in single digits and the explanations were still rough, I appreciate it even more.
And if you’ve ever messaged, commented, or pointed out something I got wrong, that probably helped more than you think.
If you want to keep following what comes next, you can follow me on X, on Medium, on Future, and join the Web3ForHumans Telegram community.
Top comments (0)