Transcript preview
Preview only
This podcast is strictly informational and educational and is not investment advice or a solicitation to buy or sell any tokens or securities or to make any financial decisions. Do not trade or invest in any project, tokens, or securities based upon this podcast episode. The host and members of Delphi Ventures may personally own tokens or art that are mentioned on the podcast. You're now plugged in to the Delphi podcast podcast. Hello, everybody. Welcome to an episode of the Delphi Digital podcast. My name is Cedars. I am coming on the pod now on Tom's pod. I'm the the head of research at Delp
Around 6 months.
Around 6 months. Okay. Yeah. So, yeah, you've definitely been into a lot of these technical pieces. First one with the Bitcoin roll ups. Right? And this one now. So just, like, what made you kinda, like, wanna dive into Solana roll ups? And, like, when did it kinda start getting put on your radar that this was something that had, like, some real kinda, like, traction behind it?
So I think, generally, the separation of SVM, from the validator client by Anza was one of the main developments that I started watching this space. Before that, I was just, like, taking a look at, the banking banking stage improvements in the scheduler, which were, like, more focused on making the l one more, improved. Right? But this was the first instance in which there was some some kind of separation of SVM, from the validator. And, not just that the SVM, along with the RPC and, scheduler are going to be decoupled. So I I kind of saw that validator is getting split apart, into a a couple
May maybe just to, like, go back on the SVM thing. So Mhmm. Before so Enza kinda splitting that out. This made it now easy for anybody to kinda just go grab that, and work with it. I guess in the past, they would have to take, like, the whole collective Solana code base and kinda, like, reconstruct it. I think Solana is, like, probably one of the most misunderstood code bases out there. It's, like, my understanding that there's, like, 20 people in the world that understand SVM. And then, you know, so long as consensus mechanism isn't formally verified or anything, and so it's very confusing. S
Yeah. That's right. Because earlier, the code base was, like, very intertwined with each other. So, if anybody wanted to use the SVM by itself, there was nothing like SVM, that was separated in the code base. So they just had to use the entire code base, and take into consideration, you know, all the dependencies, with respect to the consensus and so on. So they couldn't make any kind of customizations as such, if they wanted to without, you know, being tied down by the consensus. Yeah. Separation kind of makes it very easy to just work with the SVM, which is, yeah, one of the most battle test
makes sense. I think, you know, people talk about how, you know, we're all converging and building the same thing in the long run, which is, you know, definitely truth to it. But the path you take there also matters a lot. Like, if I think about why Cosmos ecosystem has mostly failed, which I think it's fair to say that it's mostly failed at this point. I think that they can I think, like, the Cosmos thesis of app chains is actually going to be correct in the long term? I think the the the challenge is that they never had this, like, one, you know, central hub, that you had general purpose con
I think, you made a great point there that, you know, building an SVM on top of SVM doesn't make any sense, especially because I think Anatoli and others have also pointed out that if there is contention
Keep exploring with a free account.
A free account preserves the short preview. Upgrade to Pro for the full transcript and episode chat.