People ask me what I do, and I never have a short answer. Investor is true. Builder is true. Some weeks I mostly run infrastructure, vote on proposals, or test apps that are not ready yet. No single word covers it.
I started this essay a few years ago and left it unfinished. The question behind it has not gone away. Who actually shapes Web3, the part of the internet built on blockchains, when the work is split across so many different roles, and so often held by the same person?
Not only the people writing the code. Not only the loudest accounts. Often it is one person who invests, uses, operates, votes, and builds, and has no good name for any of it.
More than one role
For many of us, blockchain is already a daily routine. Checking charts. Swapping one token for another. Lending, borrowing, and providing liquidity. Moving assets between chains. Buying and selling NFTs. Showing up in community chats, reading block explorers, building apps. The list goes on.
That takes time, attention, and capital. Some of it is useful. Some of it is mostly a chase for rewards.
I watched DeFi, DAOs, and NFTs grow up alongside online friends I have never met in person. Open finance apps, groups that run a shared treasury by vote, digital ownership. It changed how I think about work. In a single week, someone like me may allocate capital, stress test a product, write about it, teach a newcomer, vote on a change, keep a node online, and ship a fix to an app other people rely on.
Money is often how people arrive. For many who stay, something else settles in: a sense that the space matters. The usual labels do not fit. Solo founder fits some days and misses others. Crypto bro is a joke, a stereotype, or a dismissal. Neither explains the work.
Wide focus
Developers are recognized for what they do, and many of them also invest, test, vote, and operate. The point is not coders versus everyone else. It is that a lot of shaping happens across a wide field: many versions of the same kind of app, many chains, the bridges between them, and the rules about who gets what and when.
The overlap in practice
The same person can wear all of these hats in one month.
Users
You find where a product breaks, explain it clearly, come back after the fix, and help the next person. Using a product is not cofounding it. Feedback that changes a roadmap gets closer.
Governors
Many protocols are changed by token holder votes after the code is live. Governing means reading the proposal, asking what fails if it passes, voting with a reason, and changing your mind when facts change. It can also fail, through low turnout or a process that looks open while a few large wallets decide. Showing up anyway is part of keeping these systems accountable.
Operators
This is the least visible role and often the most foundational. A blockchain is only as real as the machines that run it. Someone runs the nodes that keep a copy of the chain and check every block against the rules. Someone runs the validators that propose and confirm blocks on proof of stake networks, with their own tokens locked up as a stake. Break the rules and part of that stake can be destroyed. That is called slashing. Someone runs the mining rigs that secure proof of work networks like Bitcoin, paying for hardware and power up front.
None of that is passive. Upgrades land on deadlines. Disks fill up. A validator that goes offline misses rewards and pays small penalties. One that signs twice by mistake, often from a backup machine running the same key, can be slashed. Operators read release notes most people never see, at hours most people sleep through.
Staking reaches far beyond professional operators. Many holders delegate to a validator instead of running one. Choosing well still takes work: track record, fees, how concentrated the network already is, how long funds stay locked when you want them back, and on some networks, whether you share the penalty when your validator gets slashed. A healthy network needs many independent operators, not a handful of big ones.
Self-custody
Holding your own keys is becoming a job of its own. There is no bank to call. You are the security team: hardware wallets, a recovery phrase backed up where fire and floods cannot reach it, maybe a multisig that needs several keys to move funds. You check every address, and every permission you grant an app, before you sign, because phishing never stops.
You are also the finance team. Where assets sit, how much risk each position carries, what happens to them if something happens to you, which records the tax office will want. And the tools keep changing, so the learning never ends. For many of us this is part-time work at minimum. For some it is full time.
Builders and investors
Builders ship anything from a script or a guide to a full app that people trust with what they own. As investors, we look for a live product, audits where they exist, and token design that does not feel like a trap, and we get more technical than we expected just to check the claims. At our best, together, we help bridge development and adoption. We also miss. Conflicts of interest are real when your holdings, your reputation, and your vote sit in the same wallet.
Years ago I ran onchain funds on Enzyme and sent the team detailed feedback, the kind of unpaid testing many of us keep doing.
Still, a lot of what feels easy today was once held up by people who used the hard version, complained usefully, and stayed long enough for the next version to exist.
So, what do you do?
Here is the answer I want to be able to give.
I help test and run networks that move value online without a middleman. I put capital behind projects I believe in, after checking their claims. I run some of the infrastructure that keeps those networks going. I vote on how they change. I guard my own keys, which makes me my own bank, security team, and back office. And I build apps when something is missing.
That is a lot for one line on a form. Most new fields go through this. Social media manager and data scientist were not job titles until enough people had already been doing the work for years.
So how should we define this role going forward? I do not think the answer is one more clever title. It is a clearer description of the work, and a fair way to judge it. Some of it is foundational. Networks do not run without operators. Protocols do not improve without users who report what breaks and voters who read the proposals. Good projects do not get funded without people willing to do the homework. Some of it is just noise. The useful line is between the two.
A simple test helps. Did the participation leave clearer information, safer defaults, or stronger shared tools than it found? If yes, it shaped something. If not, it was still activity. Activity is not the same as contribution.
“The people shaping Web3” is not a club or a resume line. It describes what a lot of us already do. If you are one of them, the next time someone asks what you do, you are allowed to give the long answer.