Oct. 7, 2023
Open Source and Building on Solana with Mert Mumtaz, Co-founder & CEO of Helius
This week on the podcast, Alex Kehaya welcomes Mert Mumtaz, Co-founder and CEO of Helius, the leading developer on Solana specializing in APIs, webhooks, and RPCs for building scalable and reliable Solana applications. They take a deep dive into open source development and how to navigate on-chain data using Helius' robust infrastructure efficiently.
Alex and Mert analyze crypto's slow yet steady growth, the rise of NFTs, and how Solana and L2s are redefining the crypto infrastructure. Mert shares his insights into the challenges crypto faced in its early days. They also briefly explore the roles of AI, AR, and VR in the crypto game, emphasizing the need for more talented founders in the space to build products that meet the demands of the crypto market.
Host - Alex Kehaya
Producer - Shawn Nova
Chapters
00:04 - Web 3 and the Future Explained
08:28 - Opinions on Open Source in Crypto
15:19 - Open Source vs. Proprietary in Crypto
24:49 - Challenges and Opportunities in Crypto Infrastructure
34:33 - Crypto Advocacy and Connecting Builders
Transcript
WEBVTT
00:00:04.427 --> 00:00:08.013
Welcome to the Index Podcast hosted by Alex Kahaya.
00:00:08.013 --> 00:00:13.528
Plug in as we explore new frontiers with Web 3 and the decentralized future.
00:00:16.100 --> 00:00:26.007
Hey everyone and welcome to the Index brought to you by the Graph, where we talk with the entrepreneurs building the next wave of the internet.
00:00:26.007 --> 00:00:35.927
I'm your host, alex Kahaya, and today we have Mert Muntaz, founder and CEO of Helius, the leading developer platform building on Solana.
00:00:35.927 --> 00:00:37.332
Thanks so much for being here.
00:00:37.332 --> 00:00:42.131
Super excited to have you and following you for a while on Twitter and just love the impact that you've been having on the space.
00:00:42.131 --> 00:00:49.770
Maybe just jump right in and tell me a little bit about your background and, for people who don't know you, how you got to Helius and what you were doing before that.
00:00:51.101 --> 00:00:57.253
Sure, first of all, thanks for having me, in terms of my background relatively boring, I would say.
00:00:57.253 --> 00:01:06.134
I was born and raised in Istanbul, turkey, and moved to Canada around grade seven, grade eight, right before high school.
00:01:06.134 --> 00:01:10.090
I was always super interested in math and engineering.
00:01:10.090 --> 00:01:14.359
Actually, at one point I wanted to be a garbage man when I was a kid.
00:01:14.359 --> 00:01:17.028
Like riding on the back of those garbage trucks seemed fun to me.
00:01:17.028 --> 00:01:20.197
So definitely some interesting career aspirations.
00:01:20.278 --> 00:01:23.359
Early on I went to Queens University to do engineering.
00:01:23.359 --> 00:01:31.439
I did a double degree in applied math and communications engineering communications being satellite signals, computing systems, stuff like that.
00:01:31.439 --> 00:01:36.879
I initially wanted to do a PhD in physics or math and just go the super theoretical route.
00:01:36.879 --> 00:01:40.039
I did a internship at Blackberry.
00:01:40.039 --> 00:01:42.459
So when Blackberry was a thing, I worked there.
00:01:42.459 --> 00:01:58.890
I was on the cloud team managing the cloud that manages BBM or that BBM uses, and I really fell in love with the entire process of building these infrastructure pillars that benefit other developers and they can build other structures on top of.
00:01:58.890 --> 00:02:02.245
And that was super fun for me and I was kind of red-pilled.
00:02:02.266 --> 00:02:15.829
I guess I did a complete 180 from pure theoretical math and physics to pure practice and pragmatism and right after graduating I worked at a few banks, so Canada was run by like an oligopoly of five banks.
00:02:15.829 --> 00:02:25.031
I worked at three of them building financial infrastructure, trading, desk infrastructure, low latency stuff, atm withdrawal systems, payments cybersecurity even.
00:02:25.031 --> 00:02:29.830
And then I worked at a startup that got acquired by Shutterstock.
00:02:29.830 --> 00:02:52.022
And then I worked at a startup called ClearCo, which became one of the only unicorns in Canada, and right around that time, when I was building payment systems for entrepreneurs at ClearCo, I noticed a lot of inefficiencies between sending payments internationally and the systems that we were using.
00:02:52.022 --> 00:03:04.406
They actually take multiple hops in jurisdictions if I wanted to send money from here to Australia, here being in Toronto and I suggested because I was also from there with crypto at the time in Salam, hopefully.
00:03:04.806 --> 00:03:07.092
I'd say you're pretty familiar with crypto.
00:03:08.240 --> 00:03:12.692
So I suggested using USDC and people were kind of like, well, crypto is kind of a scam.
00:03:12.692 --> 00:03:16.741
And whenever I talk to people about crypto, it's essentially like can I mine what?
00:03:16.741 --> 00:03:19.668
Can I mine some free money using crypto and stuff like that?
00:03:19.668 --> 00:03:20.531
So you just have this.
00:03:20.531 --> 00:03:29.530
I think the asymmetry between truth of what these systems enable and what was realized by the public was quite significant still is, anyway.
00:03:29.530 --> 00:03:34.088
So I didn't like the answer that we're not using a better tech just because people perceive it to be a scam.
00:03:34.721 --> 00:04:08.501
So a few weeks after I got a job at Coinbase this is before they went public, so they were still kind of a startup at that point so got to work on a lot of cool things at Coinbase platform APIs, payment systems, transaction histories, balances, npc wallets, stuff like that and I was there for slightly over a year and by that time I was also doing a lot of research into different blockchains, whether it be Avalanche, polygon, cosmo, solana, and Solana I think mostly due to my signals and communications background really resonated with me.
00:04:08.501 --> 00:04:13.310
It seemed to be my mental model around.
00:04:13.310 --> 00:04:26.072
This was essentially, maybe Ethereum and Bitcoin are more proof of concepts, where it's super theoretical and research driven and the core team has PhDs and Vitalik is a super smart theoretical dude.
00:04:26.072 --> 00:04:46.658
But then you see Solana it's like these hardcore Qualcomm engineers and people who used to work at Bell Labs really optimizing the living shit out of the hardware that they're working on and really squeezing the juice out of these machines and pushing the frontier of distributed systems, and that really resonated with me how practical it is.
00:04:46.658 --> 00:04:54.985
And people say Bitcoin is like immutable money and Ethereum is maybe immutable, programmable ultrasound money, and Solana is more like censorship resistant radio.
00:04:54.985 --> 00:04:56.391
It's kind of a different thing.
00:04:56.391 --> 00:05:07.012
It's like it optimizes for real time peer to peer communication speeds essentially, and that's something that, with my background, I just really appreciated.
00:05:07.254 --> 00:05:14.163
And obviously the developer community and stuff kind of added that flywheel effect, like when I used to build on Solana, I used to build some boss or threads.
00:05:14.163 --> 00:05:23.651
People within the ecosystem would kind of hype me up or chat about it and there'd be hackrouses and the community was super solid.
00:05:23.651 --> 00:05:48.908
It still is super solid and so if you take kind of the pure rock, performance oriented engineering culture a super solid community and you combine those things, that's really what attracted me to Solana and obviously, being an engineer myself, I noticed a lot of inefficiencies with the current system of reading data on slanted, say so, rpcs, api's, indexes, etc.
00:05:48.908 --> 00:05:58.706
And I said I decided, okay, well, you know that this is a pretty big problem and I believe the market will get bigger for this as crypto takes off, so this is a good time to start a company around it.
00:05:59.454 --> 00:06:05.889
At first, we just shipped human readable API's, so the goal was to make everything human readable.
00:06:05.889 --> 00:06:08.444
We did a pretty good chunk of that.
00:06:08.444 --> 00:06:15.026
We have like pretty much 100% coverage for NFTs right now and SPL programs and Jupyter Swaps etc.
00:06:15.026 --> 00:06:36.398
But then along the line, like, we noticed customers complaining about a lot of things like their RPCs and maybe their data lakes and stuff like that, and so we started really focusing really hard on the lower level of the infrastructure stack, on Solana, and basically now we're on a mission to accelerate the adoption of crypto power software and products at Helios.
00:06:36.398 --> 00:06:45.334
So we want to build tools such that developers, if they're considering building in crypto, you know they look at Solana and Helios like, okay, wow, that's great developer experience.
00:06:45.334 --> 00:06:46.759
This is the chain I'm going to use.
00:06:46.759 --> 00:06:52.382
This is a product I'm going to use to build the applications that will get me users so I can focus on my product.
00:06:53.425 --> 00:06:57.619
So, and here we are- you tapped into a lot of things that I find interesting.
00:06:57.619 --> 00:07:01.278
One I totally agree with the direction you guys are taking, like the high level.
00:07:01.278 --> 00:07:02.403
There's a huge need there.
00:07:02.403 --> 00:07:14.153
There will probably be several developer platform firms that become multi-billion dollar businesses because the need is going to be so huge, just to make it easier to build, and this speaks to just where the space is today.
00:07:14.252 --> 00:07:15.678
Right, it's still super early.
00:07:15.678 --> 00:07:20.194
I mean, even two years ago, when we started Olaplex, there were no indexers.
00:07:20.194 --> 00:07:22.786
Like there's not a single way to index NFT data.
00:07:22.786 --> 00:07:27.081
We built something from scratch that was open source, but, man, I wish we hadn't had to do that.
00:07:27.081 --> 00:07:31.201
Like we invested a ton of resources in that and we only built it because we had to.
00:07:31.201 --> 00:07:35.218
We weren't trying to build a business offering indexing as a service to customers.
00:07:35.218 --> 00:07:39.848
It's a very specialized tool that needed to be built.
00:07:40.596 --> 00:07:43.081
And the other thing is like, what attracted you to Solana?
00:07:43.081 --> 00:07:45.747
It's this very close to the same reason.
00:07:45.747 --> 00:07:48.625
I mean, articulated a little differently that I joined.
00:07:48.625 --> 00:08:00.899
I started in crypto in 2016 and I saw the same thing like really research, heavy academic feeling projects that were really not building open source either.
00:08:00.899 --> 00:08:02.987
They were more doing things.
00:08:02.987 --> 00:08:13.886
They would open source it later they weren't like building in the open and when I met Toley for the first time, he was shipping day one like testnet open source, and that was really inspiring.
00:08:13.925 --> 00:08:28.439
Most people were afraid to do that back in 2017, 2018 because they're all worried about competition and so they had this real practical approach of just shipping high quality product and developing a business and not just sitting around researching it in a closed firm.
00:08:28.439 --> 00:08:33.640
Basically, I would love to hear your opinion on open source in general, on Solana and in crypto.
00:08:33.640 --> 00:08:36.472
What are your thoughts on building open source business models?
00:08:36.472 --> 00:08:47.260
And I consider Healy is to be primarily a business built on open source software, offering indexing, rpc services, and I think people kind of don't understand that how you can build a business using open source software.
00:08:47.260 --> 00:08:52.043
A lot of people keep their stuff closed source for that reason, so I would love to hear your thoughts, just in general, on that.
00:08:52.846 --> 00:09:01.471
So it's a good question and there's actually a prime example of something that's open source and we're working on right now, which is compression right.
00:09:01.471 --> 00:09:21.163
So for those who don't know, there's something called compression on Solana now which lets you essentially mint a lot of NFTs for cheaper than before, so more technically, but you get to trade off state space or account space and you get to put it on the ledger and then you get to link those.
00:09:21.163 --> 00:09:27.303
We have a miracle tree with the root hash to guarantee the integrity of data and the way it works is so.
00:09:27.303 --> 00:09:56.241
Solana labs had the the white paper on on how this would work and then I think they gave a request for comment or a proposal to Metaplex and Austin there built a lot of the early parts of the system and this was all done open source and us being Healy is an untried and also really collaborated with them very heavily and we still do and just tackling different parts of the systems and really kind of collaborating as as an ecosystem to push the system forward.
00:09:56.241 --> 00:10:04.192
I think that's probably one of the best examples of open source that I'm aware on Solana, because now we have this thing called digital asset standard API.
00:10:04.192 --> 00:10:19.517
It's the digital asset DAS that's API is what we call it and now it's like developers now, instead of having to use API's that give them, for example, vendor risk or, you know, centralization risks, closed source, etc.
00:10:19.517 --> 00:10:29.765
You now have this DAS API system, which is open source, and you know we have our own fork of it at Healy is, and I'm sure Triton does as well, and then Metaplex has their own version.
00:10:29.765 --> 00:10:35.279
But there's things that are similar between them we collaborate on and people say, okay, you can't build a business on top of that.
00:10:35.279 --> 00:10:36.004
But it's not true.
00:10:36.606 --> 00:10:39.078
The compression stuff, for example, I've done a lot of work with.
00:10:39.078 --> 00:10:43.254
We provide extremely solid support around compression, right.
00:10:43.254 --> 00:10:44.399
It's a very difficult system, right?
00:10:44.399 --> 00:10:49.039
Just just just because the code is there doesn't mean you're going to be able to understand how to run it.
00:10:49.039 --> 00:10:55.504
For example, if I told you exactly how a Ferrari is constructed and gave you all the names of the pieces, are you going to be able to put it together?
00:10:55.504 --> 00:10:59.162
It's like you know it's going to take some work for you to do that.
00:10:59.162 --> 00:11:07.416
It's not that easy, and so the source being there is super crucial, especially in a field like crypto, where you want to minimize trust.
00:11:08.258 --> 00:11:14.220
The business models around that in crypto are actually, like I would say, relatively unexplored, especially with the rest of protocols.
00:11:14.220 --> 00:11:16.966
Like if you put it on chain and then maybe there's fees.
00:11:16.966 --> 00:11:18.861
I don't have the answer there.
00:11:18.861 --> 00:11:29.179
But for an infrastructure company like us it's actually quite easy because there's open source and then you just provide white glove service around it, right, you really understand the system, you do the work.
00:11:29.179 --> 00:11:35.475
Right, you do the work, you chew the glass and, for example, we actually had an incident this morning where some team had an issue with compression.
00:11:35.475 --> 00:11:43.032
We had so much experience working with it that we were able to essentially give them Time in exchange for money, right, like.
00:11:43.032 --> 00:11:48.354
They also could have done this, but they want to save time and ship products and so we help them with support.
00:11:48.354 --> 00:11:57.263
And then, obviously, like marketing and stuff and Building other integrations on top of that that that feed off the open source engine are all good and well.
00:11:58.431 --> 00:12:07.082
You know, my thoughts on open source for infrastructure are pretty clearly like it's a super solid thing to do, like, for example, mongo, does this red hat you go by?
00:12:07.082 --> 00:12:09.090
Those business models I think are pretty great.
00:12:09.090 --> 00:12:16.312
I'm not like an open source maxi, because I just don't know enough about it to be a maxi about it, right, like, I think like.
00:12:16.312 --> 00:12:20.623
So in the context I'm coming at this from is more the protocol level.
00:12:20.623 --> 00:12:24.298
So with infrastructure stuff, I think open source makes a ton of sense.
00:12:24.298 --> 00:12:40.740
With DeFi protocols and just protocols in general, like maybe Metaflex and Revenue generating operations on chain, it seems this open source which is not open source discussion is relatively unsettled, like some people say.
00:12:40.740 --> 00:12:46.113
For example, metaflex right Like Metaflex has this license such that you can fork it but you can't change the fees.
00:12:46.113 --> 00:12:48.259
And so is that really open source?
00:12:48.259 --> 00:12:50.513
Technically, not by definition, it's not open source.
00:12:50.513 --> 00:12:52.399
It is source available was better than nothing.
00:12:52.399 --> 00:12:56.210
But I don't know the answers there, if that makes sense, because I haven't built a protocol myself.
00:12:56.952 --> 00:12:59.765
I have some pretty strong opinions about this, as you're aware.
00:12:59.765 --> 00:13:03.184
Number one I think the examples you gave for infrastructure is just.
00:13:03.184 --> 00:13:16.572
It's not a new Thing, but not a lot of people realize that right like a huge part of the internet runs on open source software and the infrastructure Providers are providing services that use it, and there's a multi-billion dollar business opportunity there, I think.
00:13:16.572 --> 00:13:18.615
For for protocols it is.
00:13:18.615 --> 00:13:22.484
It is a bit different, and there's got to be a lot of experimentation.
00:13:22.484 --> 00:13:29.178
For me, though, with the Metaflex issue, it was more about Transparency around the license and the fact that it was.
00:13:29.178 --> 00:13:43.033
It was a GPL license and then they changed it without Notifying customers, and for a developer like somebody building a business on top of a software that you think is open source and forkable, to have that change is a big problem, introduces risk.
00:13:43.033 --> 00:13:46.447
When there's a fee structure that you don't know what the fees are going to be later on.
00:13:46.447 --> 00:13:49.053
They can change it kind of Whenever, and what's that going to do to my business?
00:13:49.053 --> 00:13:58.261
You know you have to trust that whoever's in control of those smart contracts is gonna, you know, not introduce a fee structure, that that that breaks the business model for you.
00:13:58.261 --> 00:14:08.856
That's a real issue, I think, and I think there are always ways to monetize the like layer one, and then I would say, like Metaplex, which is smart contract on top of Solana.
00:14:08.856 --> 00:14:14.179
You know, you can probably Find ways to monetize that that aren't a fee in the contract.
00:14:14.179 --> 00:14:16.994
If that's what you want to do, it's fine to do that.
00:14:16.994 --> 00:14:23.049
As long as you're transparent about that from from the start, you know, and then if people can choose to use it or not, that's great.
00:14:23.270 --> 00:14:34.056
I think that's one of the biggest issues is we need diversity of protocols that are usable on Solana, so that some you know, and I know that, like Genesis go released one recently and there's a couple other ones being worked on.
00:14:34.056 --> 00:14:58.475
But the flip side of it, the big, other big issues I love that you guys are collaborating with them and others on like compression, for example, and I wish that we could, that we just didn't have to have multiple standards, like it would be nice to the power of many people working on the same protocol and Ensuring it's secure, ensuring there's the know-how to use it, and like offering the services that you guys offer to the ecosystem and that other people are also competing against you to offer.
00:14:58.475 --> 00:14:59.499
I think that's important.
00:14:59.499 --> 00:15:06.481
That creates a safe, competitive Marketplace and it's a great example of how open source can work really really well.
00:15:07.172 --> 00:15:09.620
So you know I would like to see that continue and it will.
00:15:09.620 --> 00:15:12.831
I mean, the reality is it's gonna take a while to replace something like Metaplex.
00:15:12.831 --> 00:15:17.643
They have a lot of a pretty big moat around the infrastructure required to even use their tools.
00:15:17.643 --> 00:15:19.673
Those are kind of my thoughts.
00:15:19.673 --> 00:15:21.658
I don't know if you have other ones related to that.
00:15:22.399 --> 00:15:29.389
I certainly empathize and Mirror your sentiments on the license being changed kind of maybe none the most transparent way.
00:15:29.389 --> 00:15:33.158
I wasn't aware of it and in fact totally wasn't aware of it.
00:15:33.158 --> 00:15:37.754
If people followed you know, people listening followed along on Twitter, I think.
00:15:37.754 --> 00:15:46.340
Not sure who first posted it it might have been Mike or Tracy from Genesis and Totally saw it and he didn't know and he said he was pissed.
00:15:46.400 --> 00:16:00.957
And I don't think I've ever heard totally said he was pissed about anything ever and and I don't know ever, and that's the that's the CEO of Solana, by the way like guy goes to a lot of fun and so it's definitely a very nuanced and interesting topic.
00:16:00.957 --> 00:16:13.484
And so, like I don't know if I were to sum up my thoughts on this and you're much more of an expert on open source, I would say, for infrastructure plays, like, like, like Helios databases you know stuff like that in general.
00:16:13.484 --> 00:16:29.490
Totally like, open source is a great way to collaborate and build and collaborate and and push what's possible on these systems, and then you can, you can definitely monetize it properly, like you don't have to add a tax to the protocol, which is kind of where it gets interesting right.
00:16:29.490 --> 00:16:33.561
Like there was the uniswap versus sushi swap thing that happened some time ago.
00:16:33.561 --> 00:16:40.770
There was, you know, a curve and then saber, and then curve was like throwing shit a saber, and obviously saber turned out to be other Things as well.
00:16:41.332 --> 00:17:00.278
I don't think there's clear consensus on this and I think it's gonna be like a fighting topic for some time and we need people who advocate for open source To be more vocal, to be more articulate and to really push their message and say like, hey, this is why it's better, like one corporate example we can, we can kind of look to is Microsoft right?
00:17:00.759 --> 00:17:20.796
Microsoft was traditionally Extremely close source, like giant evil Corp kind of type, and then now, more recently, with their acquisitions over the past you know, I don't know how long, but let's say five, six years at least, seven years at least they've been more and more friendly to open source and They've been much more successful as a result of that.
00:17:20.796 --> 00:17:34.123
And so you know People listening this if you're concerned that, like you're gonna be successful because you're open source and maybe your comparison will steal stuff, I think that's especially in a space like crypto, where the market is super small.
00:17:34.123 --> 00:17:36.089
I think that's mistaken.
00:17:36.089 --> 00:17:44.931
Personally, for infrastructure plays, at least For protocols since I haven't built a protocol myself, I don't feel qualified to comment on that.
00:17:45.505 --> 00:17:55.652
I think at the protocol level it's all about adoption and the best way to get adoption is to build something that's easy for developers to contribute to and to use, and I think that that means you need to be open source.
00:17:55.652 --> 00:18:03.374
And because in our space, trust and transparency is so important, like it's about a value system, it's like, hey, do I have control of my destiny?
00:18:03.374 --> 00:18:16.492
That's number one when I'm building in Web3, for me, if I don't have control over my destiny, that's a problem, because then we're getting into centralization and kind of going back to the model that I think all of us are trying to dig ourselves out of.
00:18:16.492 --> 00:18:18.451
It's really about a value system.
00:18:18.451 --> 00:18:20.432
Now, what kind of businesses can you build?
00:18:20.432 --> 00:18:30.214
There have been some successful businesses that are protocols, that have introduced fees, like yearn, like yearn finance, I think did a really interesting job doing that.
00:18:30.214 --> 00:18:35.189
I think a lot of DeFi actually has figured out how to capture some value from their protocols and leave them open source.
00:18:36.105 --> 00:18:40.169
The Uniswap and SushiSwap case is pretty interesting for people who don't know.
00:18:40.169 --> 00:18:46.892
Uniswap was open source I can't remember the license that they had and then they got forked by SushiSwap.
00:18:46.892 --> 00:18:55.094
They got copied and SushiSwap took a lot of volume and became quite big and it was literally just a clone, an exact clone of Uniswap.
00:18:55.094 --> 00:18:55.876
It was my understanding.
00:18:55.876 --> 00:18:58.252
I might be getting some stuff wrong, so just cut me off if I am.
00:18:58.252 --> 00:19:14.951
And then I think that Uniswap after this updated their license to be something that's like source available and not open source for a period of time, like two years, and then their whole plan was to release better things in that timeframe and then anybody can copy their old stuff, but they wouldn't be able to copy the new stuff.
00:19:14.951 --> 00:19:19.450
I was kind of like anti that in the beginning, but I think it's worked.
00:19:19.450 --> 00:19:26.111
They've created the value you want to see created and they're still source available so you can trust the code and look at it.
00:19:26.904 --> 00:19:28.029
I'm kind of coming around to it.
00:19:28.029 --> 00:19:44.051
Everything I've built has been GPL license, like all of Olaplex's technology is GPL license, and that's because I'm very interested to see if we can successfully build a business that is full stack, open source and forkable, and so it's a big kind of experiment for me.
00:19:44.051 --> 00:19:44.713
We've seen that.
00:19:44.713 --> 00:19:49.167
I mean WordPress is an example of a full stack, open source piece of software.
00:19:49.167 --> 00:19:52.411
That's been huge and it powers like 30% of the internet.
00:19:52.411 --> 00:19:54.069
So I think it's possible.
00:19:54.069 --> 00:19:59.398
But TBD with all these new paradigms that we have in crypto.
00:19:59.398 --> 00:20:05.450
It is something I spend a lot of time thinking about in my job just because I'm passionate about it.
00:20:05.450 --> 00:20:10.073
I recognize that I am a bit of a zealot, so I try to keep an open mind.
00:20:10.505 --> 00:20:11.648
It's definitely an interesting conversation.
00:20:11.648 --> 00:20:19.076
This is probably one of my weakest areas in terms of just having clear values to articulate.
00:20:19.076 --> 00:20:36.188
I can see both sides of this argument and there's an argument to be made for crypto, and actually this brings up a good point, which is that I would bet that Solana would have taken off more if the culture was a bit more oriented towards open source.
00:20:36.188 --> 00:20:44.788
I've seen a non-trivial amount of people from Ethereum not being a fan of Solana purely due to the code being proprietary.
00:20:44.788 --> 00:20:53.913
I don't know if I remember correctly, but something about phantom being closed source versus MetaMask being open source, and that was actually a big deal for some people.
00:20:54.246 --> 00:20:56.614
And MetaMask is way worse UX.
00:20:56.614 --> 00:21:11.010
But when you have an ideologically driven movement, it's not clear if the better UX wins, which is super different to web 2, which you obviously need the best product, the best street cards.
00:21:11.010 --> 00:21:12.849
I wonder how much damages cost.
00:21:12.849 --> 00:21:19.172
And it's interesting because, totally like you said, he's a massive open source maxi, probably more so than anybody else I know.
00:21:19.172 --> 00:21:19.946
I'm encrypted.
00:21:19.946 --> 00:21:25.384
To be honest, I think his bio is even wartime open source software.
00:21:25.484 --> 00:21:25.948
I love that.
00:21:26.984 --> 00:21:35.511
So maybe there's an argument to be made for similar to a real world analogy of governments and corporations where all the public stuff needs to be public.
00:21:36.265 --> 00:21:55.069
I'm using these roads to understand that these roads will be always available to me, which is kind of why the MetaFlex situation was so annoying, because it's like maybe a corporation gets a subsidy from the government to build roads that everybody uses, but then now the roads have taxes and I'm like, wait a minute, this isn't a public good then.
00:21:55.924 --> 00:22:03.510
So I kind of don't understand what's happening, and so in that case I think open source clearly should win and needs to win for public goods.
00:22:03.510 --> 00:22:28.387
Then there's the argument to be made for these corporations and capitalism and you want to monetize your knowledge and secrets and you can do it in infrastructure super clearly, like I said with Healy, it's because the knowledge is your expertise in how to use that system and the integrations around that and we can give people advice on how to use it and set it up and maintain for them, because cloud and maintaining hardware is just difficult work.
00:22:28.387 --> 00:22:36.527
But if it's something like Uniswap and SushiSwap, where somebody literally just clicks the fork button, the plaza's different front end and makes a lot of money from that.
00:22:36.527 --> 00:22:46.292
I can kind of see Haydn's point of view in that too, where it's like wait a minute, I did all this work, but now I'm getting vampire attacks with crypto incentives and tokens.
00:22:46.292 --> 00:22:48.596
I don't think there's a clear answer there.
00:22:48.596 --> 00:22:49.058
It's super obvious.
00:22:50.145 --> 00:22:51.672
Ok, so you're talking something really important.
00:22:51.672 --> 00:22:55.188
When I talk to founders and I'm afraid to open source like explain this to me.
00:22:55.188 --> 00:23:03.893
The biggest thing that they're afraid of is competition and I think nine times out of 10, it's really hard for somebody to out execute you.
00:23:03.893 --> 00:23:11.134
It's really about execution and not about how fast can they copy your code, and we've seen this in the traditional closed source SaaS world.
00:23:11.134 --> 00:23:16.865
You'll see competitors pop up all around a successful software as a service business and they don't have access to the source code.
00:23:16.865 --> 00:23:19.607
That doesn't stop them from copying the entire business.
00:23:19.607 --> 00:23:42.589
However, crypto is a little bit different in that the liquidity like especially in DeFi and the example that you just made like liquidity can move permissionlessly very fast from one platform to another and that those vampire attacks like I mean it is crazy how fast like you can go to zero liquidity from one platform to another.
00:23:42.589 --> 00:23:45.252
It's like how do you build a moat and protect against that?
00:23:45.252 --> 00:23:46.549
And it's not easy.
00:23:46.549 --> 00:23:51.690
So I want to switch gears a little bit, because you talked about this a lot and I want to hear your opinion, at least on Twitter.
00:23:51.710 --> 00:23:58.674
I've seen it the future of adoption in our space and building applications at scale that real people want to use.
00:23:58.674 --> 00:24:02.415
I think that's a really big problem that still needs to be solved.
00:24:02.415 --> 00:24:05.314
We've been talking about it since I joined crypto in 2016.
00:24:05.314 --> 00:24:11.071
And a lot of I think what's prevented us from achieving that Product Market Fit has been the infrastructure piece.
00:24:11.071 --> 00:24:16.875
But I think we're almost through there on the infrastructure side of things, where people can actually quickly build applications.
00:24:16.875 --> 00:24:18.210
So what's your opinion?
00:24:18.210 --> 00:24:18.968
Like, where are we?
00:24:18.968 --> 00:24:25.273
Can people build apps that are going to get Product Market Fit and cross the chasm into massive adoption?
00:24:25.273 --> 00:24:27.953
What ideas do you see out there that might actually work?
00:24:27.953 --> 00:24:31.815
Or like how are we as a group going to achieve that?
00:24:31.815 --> 00:24:33.833
Because I feel like we haven't quite yet.
00:24:33.833 --> 00:24:40.429
You know there's been some breakout use cases, but nothing that's going to get us yet where we want to be, which is like billions of users.
00:24:41.853 --> 00:24:42.013
Right.
00:24:42.013 --> 00:24:48.169
So there's an interesting story here and I've been thinking about this specific problem quite frequently.
00:24:48.169 --> 00:25:02.267
So when crypto first released and when I say crypto I mean Ethereum in this context, smart contracts it wasn't super clear what you would be able to do with blockchains.
00:25:02.267 --> 00:25:11.432
And then certain memes came out, like a blockchain is just a slow database, like you don't need to use a blockchain for that, right.
00:25:11.825 --> 00:25:20.349
There was a pretty long period of time and it's still kind of pervasive today, which is that why do you need a blockchain for building that app?
00:25:20.349 --> 00:25:20.632
Right?
00:25:20.632 --> 00:25:26.107
Like blockchains are useless, maybe you don't need them to just slow computers, inefficient, et cetera.
00:25:26.107 --> 00:25:26.851
Why would you want this?
00:25:26.851 --> 00:25:37.871
And so then NFTs came around and some other use cases came around where, okay, these are actually being used and there's demand from real people.
00:25:37.871 --> 00:25:45.529
They're using it for their daily life and for whatever it might be trading, community forming, p2p payments, et cetera.
00:25:45.529 --> 00:26:00.992
And then we ran into the issue because Ethereum wasn't ready of scalability right Now you was getting these crypto chattis happened and you had very high gas fees pricing people out, and then you had clunky UX and all this stuff.
00:26:01.244 --> 00:26:13.953
Yeah, and just to quantify high gas fees, we're talking like thousands of dollars sometimes, like I remember back in the DeFi summer period and like when NFTs on ETH were exploding, just doing some insanely expensive trades.
00:26:14.744 --> 00:26:21.027
Exactly, and so we had this phase transition from blockchains are useless and they're just slow.
00:26:21.027 --> 00:26:25.032
Databases to blockchains are useful, but the infrastructure is not there.
00:26:25.032 --> 00:26:34.326
Okay, now, with the advent of Solana and even some of these L2s, the infrastructure isn't the bottleneck anymore not in my view.
00:26:34.326 --> 00:26:41.568
Okay, I think you can build a visa scale payments network on Solana right now.
00:26:41.568 --> 00:26:43.830
I'm actually quite confident of that.
00:26:43.830 --> 00:27:00.315
If a team got together to build this global settlement network, let's say that is gonna take on visa and this is just coming from a purely technical perspective, not a political or product and stuff like that the network itself is technically capable of handling that.
00:27:00.315 --> 00:27:02.912
Okay, and I'm super confident of that.
00:27:02.912 --> 00:27:05.191
Okay, so what's the issue then?
00:27:05.191 --> 00:27:13.848
Right, because so now we've we went from phase transition from blockchains are maybe not useful to blockchains don't scale to blockchains scale, but there's no useful apps.
00:27:13.848 --> 00:27:17.971
Okay, and then now a lot of people have it's updated, their mental model for that.
00:27:17.971 --> 00:27:25.332
In my view, they still think and this is especially prominent with VCs they still think that the infrastructure is holding us back.
00:27:25.332 --> 00:27:36.732
Right, they think, oh well, there's not useful apps because Ethereum gas fees or because you need rollups to have better UX, direct off-ramps from Coinbase and stuff like that and it's like no, no, no, no, you can scale.
00:27:36.732 --> 00:27:46.173
You can build scalable blockchain based or blockchain based consumer apps or whatever on Solana or even on some of these L2s right now.
00:27:46.173 --> 00:27:47.529
Like it can happen.
00:27:47.529 --> 00:27:50.368
I mean, you can look at Steppen, right, steppen's built on Solana.
00:27:50.368 --> 00:27:51.508
It works pretty well.
00:00:04.427 --> 00:00:08.013
00:00:08.013 --> 00:00:13.528
00:00:16.100 --> 00:00:26.007
00:00:26.007 --> 00:00:35.927
00:00:35.927 --> 00:00:37.332
00:00:37.332 --> 00:00:42.131
00:00:42.131 --> 00:00:49.770
00:00:51.101 --> 00:00:57.253
00:00:57.253 --> 00:01:06.134
00:01:06.134 --> 00:01:10.090
00:01:10.090 --> 00:01:14.359
00:01:14.359 --> 00:01:17.028
00:01:17.028 --> 00:01:20.197
00:01:20.278 --> 00:01:23.359
00:01:23.359 --> 00:01:31.439
00:01:31.439 --> 00:01:36.879
00:01:36.879 --> 00:01:40.039
00:01:40.039 --> 00:01:42.459
00:01:42.459 --> 00:01:58.890
00:01:58.890 --> 00:02:02.245
00:02:02.266 --> 00:02:15.829
00:02:15.829 --> 00:02:25.031
00:02:25.031 --> 00:02:29.830
00:02:29.830 --> 00:02:52.022
00:02:52.022 --> 00:03:04.406
00:03:04.806 --> 00:03:07.092
00:03:08.240 --> 00:03:12.692
00:03:12.692 --> 00:03:16.741
00:03:16.741 --> 00:03:19.668
00:03:19.668 --> 00:03:20.531
00:03:20.531 --> 00:03:29.530
00:03:29.530 --> 00:03:34.088
00:03:34.721 --> 00:04:08.501
00:04:08.501 --> 00:04:13.310
00:04:13.310 --> 00:04:26.072
00:04:26.072 --> 00:04:46.658
00:04:46.658 --> 00:04:54.985
00:04:54.985 --> 00:04:56.391
00:04:56.391 --> 00:05:07.012
00:05:07.254 --> 00:05:14.163
00:05:14.163 --> 00:05:23.651
00:05:23.651 --> 00:05:48.908
00:05:48.908 --> 00:05:58.706
00:05:59.454 --> 00:06:05.889
00:06:05.889 --> 00:06:08.444
00:06:08.444 --> 00:06:15.026
00:06:15.026 --> 00:06:36.398
00:06:36.398 --> 00:06:45.334
00:06:45.334 --> 00:06:46.759
00:06:46.759 --> 00:06:52.382
00:06:53.425 --> 00:06:57.619
00:06:57.619 --> 00:07:01.278
00:07:01.278 --> 00:07:02.403
00:07:02.403 --> 00:07:14.153
00:07:14.252 --> 00:07:15.678
00:07:15.678 --> 00:07:20.194
00:07:20.194 --> 00:07:22.786
00:07:22.786 --> 00:07:27.081
00:07:27.081 --> 00:07:31.201
00:07:31.201 --> 00:07:35.218
00:07:35.218 --> 00:07:39.848
00:07:40.596 --> 00:07:43.081
00:07:43.081 --> 00:07:45.747
00:07:45.747 --> 00:07:48.625
00:07:48.625 --> 00:08:00.899
00:08:00.899 --> 00:08:02.987
00:08:02.987 --> 00:08:13.886
00:08:13.925 --> 00:08:28.439
00:08:28.439 --> 00:08:33.640
00:08:33.640 --> 00:08:36.472
00:08:36.472 --> 00:08:47.260
00:08:47.260 --> 00:08:52.043
00:08:52.846 --> 00:09:01.471
00:09:01.471 --> 00:09:21.163
00:09:21.163 --> 00:09:27.303
00:09:27.303 --> 00:09:56.241
00:09:56.241 --> 00:10:04.192
00:10:04.192 --> 00:10:19.517
00:10:19.517 --> 00:10:29.765
00:10:29.765 --> 00:10:35.279
00:10:35.279 --> 00:10:36.004
00:10:36.606 --> 00:10:39.078
00:10:39.078 --> 00:10:43.254
00:10:43.254 --> 00:10:44.399
00:10:44.399 --> 00:10:49.039
00:10:49.039 --> 00:10:55.504
00:10:55.504 --> 00:10:59.162
00:10:59.162 --> 00:11:07.416
00:11:08.258 --> 00:11:14.220
00:11:14.220 --> 00:11:16.966
00:11:16.966 --> 00:11:18.861
00:11:18.861 --> 00:11:29.179
00:11:29.179 --> 00:11:35.475
00:11:35.475 --> 00:11:43.032
00:11:43.032 --> 00:11:48.354
00:11:48.354 --> 00:11:57.263
00:11:58.431 --> 00:12:07.082
00:12:07.082 --> 00:12:09.090
00:12:09.090 --> 00:12:16.312
00:12:16.312 --> 00:12:20.623
00:12:20.623 --> 00:12:24.298
00:12:24.298 --> 00:12:40.740
00:12:40.740 --> 00:12:46.113
00:12:46.113 --> 00:12:48.259
00:12:48.259 --> 00:12:50.513
00:12:50.513 --> 00:12:52.399
00:12:52.399 --> 00:12:56.210
00:12:56.952 --> 00:12:59.765
00:12:59.765 --> 00:13:03.184
00:13:03.184 --> 00:13:16.572
00:13:16.572 --> 00:13:18.615
00:13:18.615 --> 00:13:22.484
00:13:22.484 --> 00:13:29.178
00:13:29.178 --> 00:13:43.033
00:13:43.033 --> 00:13:46.447
00:13:46.447 --> 00:13:49.053
00:13:49.053 --> 00:13:58.261
00:13:58.261 --> 00:14:08.856
00:14:08.856 --> 00:14:14.179
00:14:14.179 --> 00:14:16.994
00:14:16.994 --> 00:14:23.049
00:14:23.270 --> 00:14:34.056
00:14:34.056 --> 00:14:58.475
00:14:58.475 --> 00:14:59.499
00:14:59.499 --> 00:15:06.481
00:15:07.172 --> 00:15:09.620
00:15:09.620 --> 00:15:12.831
00:15:12.831 --> 00:15:17.643
00:15:17.643 --> 00:15:19.673
00:15:19.673 --> 00:15:21.658
00:15:22.399 --> 00:15:29.389
00:15:29.389 --> 00:15:33.158
00:15:33.158 --> 00:15:37.754
00:15:37.754 --> 00:15:46.340
00:15:46.400 --> 00:16:00.957
00:16:00.957 --> 00:16:13.484
00:16:13.484 --> 00:16:29.490
00:16:29.490 --> 00:16:33.561
00:16:33.561 --> 00:16:40.770
00:16:41.332 --> 00:17:00.278
00:17:00.759 --> 00:17:20.796
00:17:20.796 --> 00:17:34.123
00:17:34.123 --> 00:17:36.089
00:17:36.089 --> 00:17:44.931
00:17:45.505 --> 00:17:55.652
00:17:55.652 --> 00:18:03.374
00:18:03.374 --> 00:18:16.492
00:18:16.492 --> 00:18:18.451
00:18:18.451 --> 00:18:20.432
00:18:20.432 --> 00:18:30.214
00:18:30.214 --> 00:18:35.189
00:18:36.105 --> 00:18:40.169
00:18:40.169 --> 00:18:46.892
00:18:46.892 --> 00:18:55.094
00:18:55.094 --> 00:18:55.876
00:18:55.876 --> 00:18:58.252
00:18:58.252 --> 00:19:14.951
00:19:14.951 --> 00:19:19.450
00:19:19.450 --> 00:19:26.111
00:19:26.904 --> 00:19:28.029
00:19:28.029 --> 00:19:44.051
00:19:44.051 --> 00:19:44.713
00:19:44.713 --> 00:19:49.167
00:19:49.167 --> 00:19:52.411
00:19:52.411 --> 00:19:54.069
00:19:54.069 --> 00:19:59.398
00:19:59.398 --> 00:20:05.450
00:20:05.450 --> 00:20:10.073
00:20:10.505 --> 00:20:11.648
00:20:11.648 --> 00:20:19.076
00:20:19.076 --> 00:20:36.188
00:20:36.188 --> 00:20:44.788
00:20:44.788 --> 00:20:53.913
00:20:54.246 --> 00:20:56.614
00:20:56.614 --> 00:21:11.010
00:21:11.010 --> 00:21:12.849
00:21:12.849 --> 00:21:19.172
00:21:19.172 --> 00:21:19.946
00:21:19.946 --> 00:21:25.384
00:21:25.484 --> 00:21:25.948
00:21:26.984 --> 00:21:35.511
00:21:36.265 --> 00:21:55.069
00:21:55.924 --> 00:22:03.510
00:22:03.510 --> 00:22:28.387
00:22:28.387 --> 00:22:36.527
00:22:36.527 --> 00:22:46.292
00:22:46.292 --> 00:22:48.596
00:22:48.596 --> 00:22:49.058
00:22:50.145 --> 00:22:51.672
00:22:51.672 --> 00:22:55.188
00:22:55.188 --> 00:23:03.893
00:23:03.893 --> 00:23:11.134
00:23:11.134 --> 00:23:16.865
00:23:16.865 --> 00:23:19.607
00:23:19.607 --> 00:23:42.589
00:23:42.589 --> 00:23:45.252
00:23:45.252 --> 00:23:46.549
00:23:46.549 --> 00:23:51.690
00:23:51.710 --> 00:23:58.674
00:23:58.674 --> 00:24:02.415
00:24:02.415 --> 00:24:05.314
00:24:05.314 --> 00:24:11.071
00:24:11.071 --> 00:24:16.875
00:24:16.875 --> 00:24:18.210
00:24:18.210 --> 00:24:18.968
00:24:18.968 --> 00:24:25.273
00:24:25.273 --> 00:24:27.953
00:24:27.953 --> 00:24:31.815
00:24:31.815 --> 00:24:33.833
00:24:33.833 --> 00:24:40.429
00:24:41.853 --> 00:24:42.013
00:24:42.013 --> 00:24:48.169
00:24:48.169 --> 00:25:02.267
00:25:02.267 --> 00:25:11.432
00:25:11.825 --> 00:25:20.349
00:25:20.349 --> 00:25:20.632
00:25:20.632 --> 00:25:26.107
00:25:26.107 --> 00:25:26.851
00:25:26.851 --> 00:25:37.871
00:25:37.871 --> 00:25:45.529
00:25:45.529 --> 00:26:00.992
00:26:01.244 --> 00:26:13.953
00:26:14.744 --> 00:26:21.027
00:26:21.027 --> 00:26:25.032
00:26:25.032 --> 00:26:34.326
00:26:34.326 --> 00:26:41.568
00:26:41.568 --> 00:26:43.830
00:26:43.830 --> 00:27:00.315
00:27:00.315 --> 00:27:02.912
00:27:02.912 --> 00:27:05.191
00:27:05.191 --> 00:27:13.848
00:27:13.848 --> 00:27:17.971
00:27:17.971 --> 00:27:25.332
00:27:25.332 --> 00:27:36.732
00:27:36.732 --> 00:27:46.173
00:27:46.173 --> 00:27:47.529
00:27:47.529 --> 00:27:50.368
00:27:50.368 --> 00:27:51.508