Open Source Isn't Optional | Vitalik Buterin and Demian Brener at Convergence 2025
📅 Dec 23, 2025OpenZeppelin27 MIN101 VIEWS26 SEGMENTS · 2 SPEAKERS
Open Source Isn't Optional: Why Crypto's Future Depends on Public Goods
From Ethereum's origins to its 10th year anniversary, open source has been foundational to blockchain's credibility, security, and permissionless innovation. But today, venture capital, competitive pressure, and sustainability challenges are pushing projects toward closed systems. In this conversation from Convergence 2025, Vitalik Buterin and Demian Brener explore why crypto must remain radically open or risk becoming the centralized systems it was built to replace—and how we fund public goods without compromising core p...
Questions asked in this interview
9
0:18So how do you see the two worlds converging, financial institutions with the crypto builders, and how do we make sure that things are radically open and we build with the values that got us here?
4:40How do you think it will play out in terms of which layers of the stack, if anything, is to be open or not, and where does monetization come from?
7:17What do you think are the critical standards that need to be worked on by companies like OpenZeppelin and the real community that are important to onboard more developers and more adoption?
10:56... in terms of funding for this open infrastructure, and in particular, if everything is open source, how do you find the competitive advantage, and how can the builders of this infrastructure monetize and build sustainable businesses?
14:51Are there any specific areas that you think are underdeveloped or underinvested that you would like the developers here and in the community to be paying more attention to?
19:18Can you talk a little bit about the distinction between public goods and open source?
22:23What do you think an open financial system, an open internet based on open standards, permissionless, private, well-governed, and aligned with the core values of Ethereum, what does it look like?
25:14And do you see Ethereum playing a role there?
26:18Any final message that you want to send the community here?
Ethereum crosses 10 year anniversary recently. Congrats for that. We're at a very special moment in the industry. We see a lot of adoption not only from the cryptonative projects but also from financial institutions getting into the space, where they have a different set of requirements, different set of behaviors and needs, and they're all trying to build on chain. So how do you see the two worlds converging, financial institutions with the crypto builders, and how do we make sure that things are radically open and we build with the values that got us here?
Yeah, I think one of the most interesting things over the last few years is definitely how quickly this space has been getting mainstream, both in terms of user adoption and also institutional adoption. There have been institutions doing blockchain things 10 years ago, but at that time realistically it was at best experiments and proof of concepts, and at worst it was companies and governments virtue signaling to show that they're not completely behind the times. Blockchain was the cool new thing, they had to be cool and new. Since then we've seen the space mature, and people's understanding of the space mature. Now we're seeing a lot of stablecoin projects launching, people using and talking about prediction markets in a very mainstream way. The number of people using crypto for payments and savings continues increasing. These trends are good because they bring adoption and put capital in the hands of people building the infrastructure. But at the same time, there's a dilution of principles that's really important to guard against. It's a process that happens slowly. You start off by adding one extra server in the middle for convenience, then you add a multisig for security, and then you never actually decide to take the multisig out, and years later the multisig gets hacked. You switch over to a proprietary license to protect against some competitor you get scared of in the short term, and two years later that competitor completely disappears, but now your project, instead of being part of the public commons, is something that's tightly bound to one particular group's interests, and no one else is empowered to take it and move it forward themselves. These things happen in stages, and it's important to notice it. I think it's really important to grow and nurture this core of the ecosystem that really believes in censorship resistance, open source, privacy, security, all the core values of the ecosystem, and not just by talking about them as abstract things, but by really making sure that those are the concrete bedrock that everything else is built on top of. Our ability to have an ecosystem that is open, where people are free to build on top of each other, where people are actually able to verify the software that they are running and depending on, continues to be a reality where it is, and becomes a reality once again in those areas where it stopped.
We're seeing a lot of vertical integration in the space. Now protocols launching their own chains, also launching their front ends. Some institutions launching their own chains, experimenting with protocols. You've been advocating for full stack openness. But these teams are trying to grow, they need to monetize and expand their ecosystems. How do you think it will play out in terms of which layers of the stack, if anything, is to be open or not, and where does monetization come from?
I think often the biggest players in an ecosystem have this incentive to become closed walled gardens and try to keep the growth internalized to themselves, and be able to use that to extract more over time. But realistically, if you're not in the top two or three in any particular space, then openness is actually the most pragmatic strategy, even from a profit maximizing perspective. The reason is because openness enables you to gain the economies of scale that you need to compete with the big guys. If you are not a big guy yourself, there is no other solution. If you go at it alone, you have a team that is less powerful, with a smaller number of developers, less able to get top quality talent for every individual layer of what you're doing, and the people who are bigger are going to do it better. If you and the other smaller players can cooperate, work together on shared libraries, work together on open standards so that you can interoperate with each other and build as part of one shared ecosystem, that is the way you actually gain access to that same level of scale and those economies of scale, and you're able to be successful. So I think one of the most important tasks for us is to help more of the smaller companies and participants in every space work together through openness to be able to build a playing field where they can all be successful.
You mentioned open standards, mentioned shared libraries. We've been doing that at OpenZeppelin for the past nine years. Started with Solidity, then expanding to different languages and ecosystems. What do you think are the critical standards that need to be worked on by companies like OpenZeppelin and the real community that are important to onboard more developers and more adoption?
13 more exchanges in this transcript
Sign in free to read the rest of this interview. No card required.
Buterin, V. (2025, December 23). Open Source Isn't Optional | Vitalik Buterin and Demian Brener at Convergence 2025 [Interview transcript]. OpenZeppelin. CEOInterviews.AI. https://ceointerviews.ai/interview/606214/