Sabitlenmiş Tweet
you are reading about a web3 project,
things are going well,
and then you hit a word.
“Sequencer”, " Delta-Neutral”, “Intent solver”.
you don’t understand what it means, but you don’t stop.
something shifts, you are now skimming, hoping that context will fill in the gap but it usually does not.
if you’ve ever interacted with a web3 project before, then you’ve definitely experienced this.
that moment is not a failure of your intelligence but a failure of resources because they are shallow or assume you already have an engineering background.
that gap in understanding is exactly why you cannot evaluate protocols, read whitepapers critically or tell a well built system from a fragile one.
there needs to be a bigger shift towards collective user-friendly education because the more you know these concepts for what they are,the more you can flow, decode and evaluate web3 projects.
this is why i’m starting an educational series called “Know Your Infra”
the Know Your Infra Series is part of the shift towards user friendly education.
this is a series about the infrastructure behind the applications you use, fund, build, and write about in Web3. Not just the apps themselves, but the systems underneath them.
why Infra?
because those technical terms are mostly infra & these infra layers determine whether a protocol is fast or slow, secure or fragile, scalable or stuck, trustless or quietly centralised in ways most people never notice.
that is what this series will focus on.
every week, expect simple and healthy explainers that break down concepts, introduce key projects, answer real problems or questions and create a working mental model you can always refer to.
who is this for?
~ anyone who engages with crypto seriously but does not have an engineering background.
~ developers moving to other ecosystems.
~ investors and analysts who evaluate projects but want to stop nodding through the architecture section of whitepapers.
~ writers and researchers who want to go deeper.
~ community members who want to actually understand what they are participating in.
Why this is not is hype.
I’m not here to glaze up any project and tell you if their token price will pump. I’m analysing systems, why it was built a certain way, its tradeoffs and possible opportunities.
we will start with the fundamentals, why projects can have different architectural designs down to other narrative specific infrastructure, etc.
since this is for my community, some topics and case studies may be open to community suggestions.
by the time you have read through this series, you will have the kind of background that makes you research faster, make conversations around how apps work and possibly vibecode your ideas too. you will not need to start from scratch every time you open a whitepaper.
the pilot episode drops this week. Turn on notifications so you do not miss it.
English
