Protocol
Ethereum's base layer: how blocks get made, validated, and upgraded.
How we map Ethereum
Every talk in the archive lives somewhere on this map: 20 topics, 109 subtopics, 14 of them at home in two places at once, and a reason behind each one. Click anything to start watching. The map itself is open source, CC BY 4.0, free for anyone organizing Ethereum content.
Layer 2s
Rollups and the networks that scale Ethereum beyond the base layer.
Privacy
Cryptography for private and provable computation.
Security
Keeping contracts, protocols, treasuries, and keys safe.
Developers
Tools, languages, and infrastructure for building on Ethereum.
Wallets
How people hold keys, sign transactions, and prove who they are.
DeFi
Onchain markets, credit, and trading.
Stablecoins
Digital dollars and the rails that move them.
RWA
Real-world assets, institutions, and physical networks coming onchain.
Prediction Markets
Trading on outcomes and aggregating information.
Tokenomics
Designing incentives and token systems.
AI
Where AI systems and Ethereum meet.
Social
Decentralized social protocols and the consumer apps built on them.
Art & NFTs
Onchain art, collectibles, and creator economies.
Gaming
Onchain games and their economies.
Governance
How onchain organizations decide and execute.
Public Goods
Funding what the market will not.
DeSci
Decentralized science: funding, owning, and publishing research onchain.
Community
The people, history, and culture of Ethereum.
Policy
Law, regulation, and compliance.
The thinking
Less is more
Every subtopic had to pass one test: would a viewer actually filter by this, or does the topic alone already tell them what they need? Anything that existed to make a category look complete was cut; anything that needed a written rule to tell it from its neighbor was merged with that neighbor. The draft before this one had 183 subtopics. A topic with three is fine.
No project names
Projects rise and fall; the map should not go stale with them. So no company names, project names, or token tickers appear in any topic or subtopic, and search fills the gap with aliases: type DePIN and you land on Physical Infrastructure, Perps takes you to Derivatives, ENS takes you to Naming. The names stay durable, the vocabulary stays searchable.
Shared subtopics
Fourteen subtopics live under two topics at once. Account Abstraction is protocol engineering and it is the future of wallets; splitting it in two would make you check both shelves. Each shared subtopic keeps one definition and one canonical page under its home topic, and it never counts twice. Information architects call this a polyhierarchy, and it is the honest way to file things that genuinely belong in two places.
What is deliberately not here
Level, format, event, language, and year are not topics, because they cut across every topic. They live as filters instead: beginner DeFi talks from Devcon in Spanish is four filters combined, not a category. Keeping those axes out of the tree follows the Baymard Institute's findability research, which finds filter groups work best small and warns against splitting one category plus a filter into many sibling categories.
Checked against the real world
Before freezing the map we verified it against the tracks of Devcon, Devconnect, EthCC, ETHDenver, and ETHGlobal, the categories of the Devcon archive, the sector maps of the major research firms, and the Ethereum Foundation's protocol priorities. Every current conference track lands cleanly on these twenty topics.
Take it with you
The whole taxonomy, its definitions, its aliases, and the reasoning are published at github.com/ethereumtv/taxonomy under CC BY 4.0. If you run an archive, a newsletter, or an event and need a map of Ethereum, it is yours.