MegaETH Mainnet is Live! — The Next Era of Ethereum Scaling | Lei Yang & Namik Muduroglu
Namik:
[0:00] We scaled far further than what any L1 can scale, in our opinion. We just did a stress test on mainnet, so everyone was able to do it,
Namik:
[0:09] where we did 55,000 transactions per second. That was a mixture of Univ3 transfers as well as ERC transfers. And while that was happening, we were allowing users to play low-latency games at Crossy Fluffle with zero UX trade-offs. Now, this is only possible because we've chosen to build Layer 2.
David:
[0:33] Bankless Nation, I'm here with Nomek and Leigh Yang of MegaEth. Nomek, Leigh, welcome to Bankless.
Namik:
[0:39] Thanks for having us.
Lei:
[0:40] Happy to be back.
David:
[0:41] All right, so some pretty interesting times to be a Layer 2 on Ethereum. We're quoting the day after Vitalik released his Layer 2 tweet. A big moment, to say the least. When you guys just saw this tweet rocket around Twitter, it got so big that basically everyone on crypto Twitter was commenting on this. What was your reaction to it? Nomek, I'll start with you.
Namik:
[1:02] Yeah, I mean.
Namik:
[1:03] Thanks for the question, David. I think it was honestly a validation of our point of view for a while. We're called MegaEath. We love Ethereum. I mean, I go into crypto because of ETH. So it has a special place in my heart. But the reason why Mega uses Ethereum is not because of fanboyism, but because it allowed us to build the most performing possible blockchain. Right. So Ethereum gives a guarantee of sorts, right? The guarantee is simple. It's the most decentralized or incomplete blockchain. And we take that guarantee and we say it's sufficient for us to build a hyper-performant execution environment that we believe can solve for an entire new set of use cases. And that's basically the relationship between MegaEF and Ethereum. Vitalik kind of points towards that and is like, what did I do if I was in L2 today? He says he would build a bunch of stuff which is not similar to Ethereum L1. He mentioned six things. We do 50% of them off the bat. We scale, buzzword, but it is a word. We scale far further than what any L1 can scale in our opinion, right? So we just did a stress test on mainnet. So everyone was able to do it. Where we did 55,000 transactions per second, that was a mixture of UNIV free transfers as well as ERC transfers.
Ryan:
[2:29] And while that was happening,
Namik:
[2:31] We were allowing users to play low-latency games at Crossy Fluffle with zero UX trade-offs. Now, this is only possible because we've chosen to build Layer 2. So that's one of the things we do, which Vitalik had described. We've also built an ultra-low-latency environment, something that really can't be done with a traditional consensus-based Layer 1 system. And we decided to do a bunch of unique, wacky things on the chain, which we did because the applications wanted us to. That's an example is our native enshrined Oracle of Chainlink. So when I saw the article slash tweet, I was happy because a strong ETH is good for crypto. I think if ETH doesn't do well, our entire industry, i.e. smart contract blockchains, we're all screwed. And I was kind of happy because it almost meant we can drop some of the traditional alignment games you have to use EFDA and we can try to build the most performance systems we can and hopefully capture new sections of the market. Leigh, what do you think?
Lei:
[3:33] Yeah, it's pretty much about differentiation because to us it's pretty uninteresting to try to build and replicate exact primitives provided by the layer one because then first, of course, you face the
Lei:
[3:46] question, why do I use a layer two that provides essentially the same service as the layer one? But also, it's just technically uninteresting in an interesting technical sense, in an academic sense that you are basically trying to replicate things in a much harder way in the sense that actually, I think, to the contrary of, I think, common belief, it's actually very hard to build a secure layer two. And if all you want from a layer two is kind of just adopt Ethereum security as is then I think you are better off like building an odd layer one I would say I would go as far as that
Ryan:
[4:24] Yeah, I do think in Vitalik's tweet,
Namik:
[4:26] There's definitely some validation of maybe I'll call it the barbell approach to Ethereum and to layer twos, which is like on one side of the barbell with one heavyweight, you have Ethereum. And that's going to be slow from transactions per second, but it's going to be max decentralized. And that's good for lots of use cases, including anchoring a layer two, but also slow DeFi. And that's getting faster, by the way. So that's one side of the barbell. The other side of the barbell, you have some extreme things that do things that aren't replicating what the Ethereum L1 does, but that kind of explore a frontier in a totally different domain. And so MegaEth seems well positioned on the barbell strategy in that it's just like accelerating a number of things. One in particular is just like insane scaling levels that the ETH layer one cannot do. But I want to maybe broaden this because there's so much to discuss with this Vitalik tweet, I feel like. One is just that this feels like a departure from maybe how Ethereum, how Vitalik, how the community, how even at one time Bankless thought about the role of Layer 2s. It was not too long ago, maybe three years ago, there were people like Polenia talking about how Layer 2 scale.
Namik:
[5:44] There was people like Justin Drake saying, hey, like if you're on the L1, gas fees are high, get off the L1 and go to the L2, right? And that was oft quoted. Even on Bankless, we would talk about like the scaling strategy for Ethereum was primarily L2s. And the idea was like you take everything that worked on the L1 and it's expensive and then you move it to an L2 and it should just work. In fact, Vitalik kind of acknowledges this. He says, the original vision is no longer working. Ethereum itself needs to scale. In the original version, basically, we were offloading a lot of this to L2s. And that's kind of no longer necessary because the L1 is scaling.
Namik:
[6:27] I think of this as a pivot, not a values pivot, but I'm going to use the P word, a pivot in terms of the roadmap itself, in terms of what was originally envisioned with a roll-up centric roadmap and where we are now. To me, it's a very logical pivot. We were talking about this on Bankless probably 18 months ago when we're just kind of feeling out whether this made sense or not. But there was a lot of immune system attack on the idea of this tweet. And you can even see it. I think some in the Ethereum community are like, oh, we feel disillusioned by this. This feels like a departure from what Ethereum has been saying for many years. This feels like wasted time and wasted energy.
Namik:
[7:12] That's a lot of different thoughts, but that's because there's so much to unpack, I feel like, with this post. It's like three to five years of Ethereum history.
Namik:
[7:21] Do you guys have any thoughts on what I just said? Do you view this as a pivot? Is it logical to you? Or is it more of the same of where Ethereum was always going? What do you think, Namik?
Namik:
[7:33] I think for me, it's a sad realization of like Moloch 1 almost in some ways, right? Hmm.
Ryan:
[7:41] We have to be honest,
Namik:
[7:42] Everyone has different incentives, right? Like, I remember one of these points was, there's been stage one rollups that told me they did not want to become stage two, point blank. And the reason is because it was the regulatory environment, they prefer to be more centralized.
Namik:
[7:59] And, you know, it's like, it's a bit of a shame, I would say, right? But I also acknowledge that we are to blame as well, right? There was another article that came out a few days before V's tweet, which was like, Meg E from the depth of this stage one rollup, where the entire argument in that article was, hey, like, so far, everybody who basically disregarded the traditional value sets of like following Ethereum L2 convention, they were not very serious people. Right? They were not trying to build really, really good product. While what our team did is like we were, we kind of foresaw, we forsaked some of those value propositions trying to build good UX. And so I think we're to blame as well. On my end, I think it's good that L1 is scaling. I think it is a bit of an overreaction to say that Ethereum will no longer need L2s. The reason why Ethereum is cheap now is because all activity moved to L2s. But like, you know, we will very quickly get back to a world where like, there's $200 transactions on EFAL1. So we need to scale the layer one. I don't think it's as easy as like, boom, it's done.
Namik:
[9:09] But I think Ethereum and the EF needs to take Ethereum's success into their own hands and understand that L2s are trying to build businesses or trying to
Namik:
[9:20] build products that are valuable. And I think ultimately, that's where we see PMF of institutions as layer twos, right? They like that trade-off.
Namik:
[9:30] Leigh, I'm interested in your takes on this too.
Lei:
[9:32] Right. So I think first, it's a logical, I would, yeah, it is a pivot. So yeah, it's a logical pivot. And we kind of saw it coming from the Gallego of mega ETH. So we are, I mean, we're not surprised at all. And to like the narrative about Ethereum wasting the last four or five years,
Lei:
[9:53] Quote unquote, chase the layer two roadmap, I don't think that's valid because first one has to consider I think the origin of the layer two of the layer two roadmap. I think it's really just because I think back in 2018, the hot topic about scaling is sharding, right? Remember that? And then a natural evolution of sharding is layer twos because you can basically regard each shard as a layer two today. And I think the original idea is that Ethereum would run and operate all the shards. And I think then the question comes, hey, why does it have to be Ethereum? Why don't we just delegate it to a few teams so that we get some diversity, some competition, some experimentation? I think experimentation is one of the most interesting things that came out of the Layer 2 roadmap. Because with the roadmap, I think Ethereum started to focus really building the substrate that can support experimentation. I don't think many people in the community kind of realized how general purpose the Ethereum infrastructure has become in terms of supporting consensus-less
Lei:
[11:06] Blockchains, which are layer twos, the DA, the dank sharding, the portal dank sharding, and all the upgrades and the blobs, I think they all are critical in terms of supporting the layer two infrastructure. So now that the infrastructure is done, I think it's actually fine that the layer two is kind of back at scaling itself, which I think is totally logical because you also need a good coordination layer two to synchronize all the layer twos to serve as the hub.
Ryan:
[11:34] But I really don't think like the pivot,
Lei:
[11:38] I really don't think like the energy we spend on this substrate is wasted or something because I think mega is only possible because Ethereum was chasing this layer two centric roadmap for a few years. I'm extremely grateful that it did so that we can have this interesting experiment we're working with and as well as many other experiments I think that are going to come. So yeah, I don't think it's, I don't think it's a sunken cluster in any sense. It's actually pretty good.
Namik:
[12:03] Well, yeah, I think I agree with that. I mean, layer twos have been massively beneficial to Ethereum and the layer twos alignment with Ethereum, like both economic security wide has been beneficial to them as well. So it feels like a win. It's just very interesting. I feel like sometimes, maybe this is true of all different communities in all areas where social groups have a tendency to kind of oscillate like a pendulum swing in like too far in one direction and then too far in the other. And so what was happening was there was this thought within Ethereum that L2s are Ethereum, exactly the same thing, and that they will solve all of Ethereum's scaling problems. And that was a naive perspective from the early days of the roll-up centric roadmap. And we were too far on that extreme.
Namik:
[12:52] Now, what I almost see, it's some reaction to Vitalik's tweet, is an oscillation too far in the other direction as the pendulum swings. Which is like people now saying, the L2 roadmap has failed. It's over for Ethereum. This is like, you know, five years of wasted time and energy and the project
Namik:
[13:09] is done and all of these things. Without understanding the value that L2s are bringing to the table and have brought Ethereum and all of the various ways that those have contributed to even scaling the L1 and projects like, quite frankly, LIDR and MegaEth on the horizon, really differentiating what they can do. I guess... One question I have for you, though, to distill this for the listener, because on that other side of the pendulum swings, people have said things like, well, why be an L2 at all? Like, there's no such thing as like L2s. Okay, like everything is just a chain.
Namik:
[13:47] And I don't think that's true either. But in order to get into that, I think we need to understand the security guarantees and the property rights guarantees that users actually get when they're on mega ETH. And just help frame this out. So I'm a user, let's say, I have assets from Ethereum. I move them to mega ETH, so they're sort of rooted in the security of Ethereum, okay? What do I have? What property rights do I have? Do I have, because you guys are using Eigen for DA, of course, right? So it's a different type of roll-up from that perspective. And then I'm not sure what kind of your stages are going to look like once this is all operational, what the directory there is. But like, say in a year from now, if I'm a user on MegaEth, what do I get in terms of inheriting Ethereum's property rights? Do I get censorship resistance fully? The way I would on Ethereum? Do I get the ability to exit my assets? I feel like that's just hard for people to understand right now in this chaos and swirl. So help us with that.
Lei:
[14:57] Yeah, of course. So if we're talking about a year from now, actually, you would get... Pretty much almost all the important features you would have, you would want on Ethereum with the caveat that you have to trust both Ethereum, trust as in trusting that Ethereum will not reorg beyond some certain depth, especially beyond the finality and also or sensory interactions. And plus, you have to trust EigenDA in the sense that whatever we as MegaEth submit to EigenDA, they make it available for anyone to read, and they kind of stand by the claim, right? So again, so we're listing the trust assumptions. The difference between layer one and layer two, especially our sort, is that you not only have to trust Ethereum, but also EigenDA, which I think is a pretty valid trade-off because of the immense throughput scaling you have from EigenDA. And in terms of then with those trust assumptions, the guarantees you have, First, the layer 2 cannot censor you, in the sense that
Lei:
[16:01] If your transactions are being maliciously excluded from the layer two, if you just go to the layer two to try to submit a transaction, you can always go back to the layer one and submit a transaction there. And the layer two sequence will be forced to include your transaction. So this is like the classical censorship resistance. So it's actually pretty funny because we're having this frontier stage of our main net. And we're doing a whitelisting on the RPC so that we only allow users onto the chain so that regular users, they don't make mistakes and lose money, right? I think that's a responsible thing to do. But we have always known, we always know that there is this censorship resistance bridge. It's live today, right now. There is censorship resistance. You can now submit a transaction to the layer one inbox of our chain and it'll be forced to be included to the layer two. It's been live for the whole time of the frontier stage, even if we're doing the RPC whitelisting. So I've always been a bit worried that users might just submit transactions onto the layer two through this mechanism.
Lei:
[17:05] So censorship resistance. Second, the assurance that you can always exit the layer two whenever you want. And this in part is achieved by censorship resistance because to exit, you have to submit a transaction on layer two. And if the sequencer does not allow you to do so, you go through the mechanism I just described. And then the layer two will be forced to allow you to exit by proposing a state proposal, certifying that your exit or your withdrawal is valid. And this is achieved by allowing anyone observing the layer two to provide such certification. So even if MAGIT decides to disappear tomorrow, anyone else can just come and submit those certifications and you can use this certification to claim your money from the layer one end of the layer one, layer two bridge to MegaEase, right? You can just take your money. And also a few other guarantees, for example, your chain actions will not be miscalculated.
Lei:
[18:09] It will not be errorlessly executed because there is the fraud proof system. And with that, we're actually using a ZK-based optimistic fraud proof system in the sense that if the chain, if the sequencer ever makes a mistake, anyone can just permissionlessly submit a ZK proof showing to a layer one contract that the sequencer is doing something wrong.
Lei:
[18:34] And at that stage, the sequencer is going to be slashed,
Lei:
[18:37] You can stay assured that no one can claim your money that does not belong to them, right? So these are the assurances. So censorship resistance, guaranteed correctness of execution, and guaranteed ability for you to just escape whenever you want.
Namik:
[18:52] So that's a great set of property rights, basically. And the trade-off is, if I'm willing to trust Ethereum, which I already am, and then Eigenlayer, and of course Eigenlayer, that's economically secure, then I get all of the benefit of scalability on something like MegaEath. I got to ask the question, where does stage two fit in all of this? So part of Vitalik's comment was like, okay, L1s, they're only going to, like a lot of them are only going to stay with stage one. And my understanding of stage one is basically like upgrading contracts and such. It requires a security council. What is that? It's a group of parties that can collude and they can update these contracts and update the rollup at any point in time. And so if they all did that, then they could actually yoink your funds and that's why it's different. How about in your setup? Like, you didn't mention stage two once. I mean, is stage two relevant for MegaEth? And if so, how?
Lei:
[19:49] Very interesting question. Thanks for a reminder. Yes, you also have to trust that the security console is not going to misuse your power because within a year, I mean, after a year, we do see ourselves in stage one, But actually, it's probably not good for us to claim ourselves, to label a mega ETH as a stage one slash stage two slash stage zero chain. Because I think the stages only pertain to rollups. And rollups, by definition, they have to use Ethereum DA and we use EigenDA. Sorry for being pedantic. But yes, you do have to trust the security console, which we're picking up.
Ryan:
[20:26] Very seriously. And so where does stage two come into play?
Lei:
[20:29] I think stage two basically says, get rid of the security console. Code is to govern you, like, for life. Immutability, right? There is going to be at least one part of the chain governance logic that is immutably enshrined on the layer one. Here, I mean, like, deploy a contract without a proxy, right? Just deploy the contract, and the contract as is will govern, say, how and when you can upgrade your logic and maybe you cannot maybe govern that you cannot govern the fact that you cannot upgrade your logic at all. So we call that it's a huge commitment because you are basically saying one piece of the design of the rollup of the layer two is going to be fixed forever for the lifetime of the universe, for the lifetime of Ethereum, which are equal.
Lei:
[21:16] This is a huge commitment and it's a big risk because what if you find out a bug like a thousand years from now, right? You have to correct them. But if you are a stage two roll-up then or layer two, then I think it's pretty hard for you to do this correction. I think that's why I think also in Vitalik's post I think there was kind of a realization that actually reaching stage two is a little bit harder than what people expected a few years ago because you are really making a big bet that there's a piece of code in your roll-up logic that you are never going to touch at all. So I think this is why it's pretty hard to reach stage two. I don't think it's responsible to claim that we will reach stage two within
Lei:
[22:01] a year or maybe even within two years. But I think first, it's a really interesting goal to chase after. I'm personally very interested in a form of application of software. And I think it's a big cornerstone in us reaching stage two, which means perfectly correct code. And I think with AI, it's quite interesting because I think the thing that AI does the best is the stuff that is hard to
Ryan:
[22:28] Produce, but easy to verify,
Lei:
[22:30] Right? For example, proofs of software code. Like it's pretty hard for you to prove that a piece of software code is correct. But if you kind of draft up a proof, it's actually very easy for you to verify. So I think with AI, with form of application, we are on track, but still there's a long way to go.
Namik:
[22:50] That's the crux of this to me too, is just like, it's unclear whether I as a user actually want stage two on any of my rollups, to be honest, because what's worse to me.
Namik:
[23:01] Trusting that the teams in place won't screw me over and the security council won't screw me over or trusting that there won't be any bugs in the contract. You know what would be a really bad UX is if there was some bug that froze all of my assets in a chain and like what, am I celebrating stage two at that point? Hell no, I hate this. I hate what happened. So I guess that's part of maybe the realization as part of this kind of pivot. And this is, by the way, it's not coming out of nowhere. I mean, this is just saying the quiet part out loud. Everyone has sort of already known what Vitalik was talking about here. But it's basically saying, hey, stage two is just like, it's on this horizon and it's like, many rollups, most rollups may never get there. It's unclear whether we actually want that to happen. If it does happen, it's on the five to 10 year type horizon when everything is formally verified. And so if you're just going to be a rollup and stay stage one, you may as well write like add all of these exceptional features to your layer one that like make it truly differentiated from Ethereum. I think that's kind of the logic that that's happening here is basically the recognition that no rollup is going to get to stage two on any timescale. And so you may as well stay stage one and then like make it up for incredible features that you're offering to the community. That's how I'm thinking about this.
Lei:
[24:26] Totally. Yeah. And I think when people really claim, when people literally mean by like rollups being Ethereum equivalent, it has to be stage two because in Ethereum, you don't have to trust a security console. Right. And I think that's why I think people start to realize that actually if we treat the roll-up scaling, the roll-up centric scaling roadmap as building a bunch of shards that are literally Ethereum equivalent, it's actually a very hard task. And I think five years ago, people underestimated the difficulty of this, and I think people also kind of overestimated the difficulty of ZK proving, so yeah, more efficient ZK proving. So, like it's a max, I think we've made good bets and bad bets.
Namik:
[25:07] Yeah, I think there are a few teams that are working on making, say, true roll-ups, and I think that's also exciting.
Lei:
[25:13] So I don't want to,
Namik:
[25:14] Like, you know, unvalidate all the hard work that they're doing. I think on our end, it's just like this, like very, like, at least from my perspective, like a very left-curve brain is, like, you know, we should work on, like, like, Ethereum L1 needs to scale
Namik:
[25:31] But it also can't scale in a way where it compromises its value proposition to the market. And forget, Maggie, forget L2s, right? I mean, the reason why ETH wins is obviously A is platform economics. It's here. It has a lot of liquidity. It has a lot of users. But I also think there is value in being the most decentralized to a complete blockchain.
Namik:
[25:56] And for a long time we were saying, okay, well, let's just ossify the whole thing now and not touch anything because this is sufficient and we'll just do it all in L2s and that was not the right answer, right? What the right answer was is like, okay, we need to scale the L1 but I don't think we should scale the L1 in an appropriate manner in which we lose our decentralization property. I think that's where L2s can maintain a valid proposition, right? Like if there are experiences or user flows or apps that are only performant or possible because of like the properties that come alongside not having like a distributed validator set, those should not go to like, you know, quote unquote, like all to L1s or like closed validator sets. Those should just go to their most logical conclusion, which is like these like, you know, somewhat centralized sequencer architectures that They are more centralized in like the immediate sense of resistance term of the word. Like, by no means is anyone on our team going to say that Maggie is like, more decentralized in Solana. Like that's just fake news, right?
Namik:
[27:10] Maybe many years in the future, they just become different trade-offs that become things people are willing to make, right? Which is like, hey, the guys in charge can't really rug unless they give me a chance to leave, right? A couple of days, security council, some sort of variation. But I think like the takeaway I have at least, is, hey, ETHL1 needs to scale in a responsible manner. And for that portion of the market ETH does not capture by scaling responsibly, those should be captured by L2s in the barbell thesis. And that's the way that I think Ethereum's design choices create the most value for the world. Both economic value, but also, hey, we need to get users on on blockchains or or maybe not but i think that's my gut feeling
David:
[28:02] Let's talk about that that barbell as we were talking about like really what what are l2s really good for is delivering exceptional features and there's something that was going on in the mega eth ecosystem last week that i think kind of underscores what the exceptional features that mega eth are bringing to the market uh you guys did a stress test so uh the stress test of mega eth you guys published a bunch of data about this stress test. Maybe you can kind of walk us through what was that stress test for? What were you hoping to learn? What did you learn? Anything cool that you saw or noticed? And overall, what did this test, this stress test of MegaEast capabilities do for you guys?
Namik:
[28:41] Yeah, you know, I'll start with a small analogy, right? The past couple of weeks have been like quite intense for all stakeholders, right? Market, blah, blah, blah. I mean, I remember during the stress test or a couple of days before the stress test, So someone asked me, you know, how are things going? You know, you guys are taking a while to launch, blah, blah, blah. And all very valid points. And my takeaway was kind of like, I'm actually feeling great because, you know, I can't code. I'm not a developer. And for the past two years, I just had to get on calls of Lay and the rest of the team and just like, trust me, bros. Like, this trains really fast and has like unbelievable compute and it can handle crazy levels of activity. And I'm just like, well, it makes sense on paper, but where is it? And we saw it. And that was really awesome. Like, genuinely, there was a level of, you know, obviously, this is not organic activity.
Namik:
[29:34] We made all of the transactions ourselves. But I remember, like, you know, using chains like ETH and SOL, I would, and then, you know, I would go trading and stuff. And like, when there was a lot of people playing the game, the game broke. And it's just like, you know, I couldn't do swaps. I couldn't do anything. I remember back in 21, I'd have to spend like 6% of my portfolio to exit a position during a market downturn. It's like, oh, Jesus Christ, I've spent like 500 bucks. And that's like, well, I hope I do well in the future because it's just craziness. We basically did an insane amount of transactions per second. And we did it while letting people play these games, which were like low latency games on chain. So we had Azure Xmons, who's the founder of Pseudoswap. He built a fully on-chain Pokemon game. Our team took the Crossy Road game, made it on-chain, put it onto the mainnet. And people were able to play these things while we were just doing an egregious amount of spam on the chain.
David:
[30:38] I like the egregious word. It's true.
Namik:
[30:42] Just inappropriate levels.
David:
[30:44] Inappropriate amount of transactions.
Namik:
[30:47] The block explorers,
Ryan:
[30:49] Died.
Namik:
[30:50] They died. They were like, please stop doing this. But yeah, it was cool. It was genuinely cool. And it made me feel like MegaEath makes sense. And we're seeing why it makes sense. And we did this while also having fees like five, six times lower than chains like MegaEath that use EFDA or like old L1 chains that were just way more expensive. So it felt great from a non-technical point of view. It felt like what we're doing makes sense and people could feel it.
Namik:
[31:20] But maybe they have some actual data.
Namik:
[31:23] Well, actually, before we get to lay, can you give us some numbers for people who weren't watching this stress chest? And maybe you can convert this to, you know, amount of gas, like giga gas, you know, estimates or transactions per second. Yeah.
Namik:
[31:36] Yeah. You guys can go on stress.megaeve.com, right? And we have like the retroactive information there. We had 11.4 billion transactions in seven days. So that's more than like any other 11.4
David:
[31:50] Billion transactions in seven days.
Namik:
[31:52] Yeah. Yeah. Average TPS was 15.5 K per second. We had a peak TPS of 55 K. The average mega gas was 1.6. So
Ryan:
[32:07] Yeah, it was pretty cool.
Namik:
[32:08] Wait, wait, average megagas was 1.6 thousand. 1.6k, yes. 1.6 gigagas then.
Lei:
[32:14] 1.6
Namik:
[32:15] Gigagas, yes. Yeah, my bad.
Namik:
[32:17] And then, so how, you know, we've all seen numbers from like test nets before, right? Or like, I'm running these things locally and I achieved, you know, a billion transactions per second, whatever. How closely does this environment emulate what we will actually see post-launch? Because that's kind of the benchmark, right? You guys show these numbers in, you know, kind of pre. That's one thing. But can you sustain these numbers?
Lei:
[32:45] I would say yes, because if we flip-flash switched, it's exactly the thing we're going to run in mainnet. It's like the same server, same IP address, same configuration, same admin keys. So exactly the same. Everything is the same. I feel bad because we're kind of spamming the chain a bit too much.
David:
[33:02] This was a mainnet stress test, not a testnet stress test.
Lei:
[33:06] Totally, yes, exactly the mainnet.
Namik:
[33:08] We spent, I believe, 200 ETH a day, which we recycled, right? We're getting the ETH, so don't worry, we didn't go bankrupt. But it was all real.
David:
[33:18] You guys are just taking ETH from one pocket and putting it into another pocket.
Namik:
[33:20] Bingo, bingo. But yeah, so like when users use the chain, they have to use pay ETH. Now, it was very low, it was very cheap, so it's totally fine. And effectively, it was the same as mainnet, right?
Namik:
[33:32] It is mainnet. Wait, wait, with a 200 ETH per day, what's that going to? Is that all the cumulative average token transfers of 0.0001 cent just adding up when you multiply that? It's like equates to 200 ETH per day?
Namik:
[33:44] Yeah. Approximately. Wow.
David:
[33:46] We're talking about the gas fees, right? So like 200 ETH per day of gas fees to make the 11 billion transactions happen.
Namik:
[33:54] Exactly. Yep.
David:
[33:54] Yeah. How was 200 times whatever the current price is? What was the total economic cost of the 11 billion transactions?
Namik:
[34:02] Yeah.
Lei:
[34:02] Economic cost as in the cost basis or?
David:
[34:05] Yeah, just like how much did sending 11 billion transactions on mega ETH over seven days, how much did that cost?
Lei:
[34:11] Yeah, so the token transfer is what, 0.01 cent per transaction and we can do a quick calculation.
Namik:
[34:19] I mean, 200 per day times the sad current price of ETH is, you know, 400K per day, something around that.
Lei:
[34:26] $1 million, I would say.
Namik:
[34:27] $1.4 million.
David:
[34:29] $1.1 million over seven days?
Lei:
[34:30] I think so. Let me check. So three zeros, one B, K, 11.4, yes, 1.14 million, yes.
David:
[34:37] Leigh just did that and said, I would never be able to do that.
Namik:
[34:39] There's a quant joke somewhere here I'm not going to make.
David:
[34:44] How does that compare to other chains?
Lei:
[34:47] I think, so we have actually a comparison. I think we are among the cheapest to connect on. And I think I do want to highlight something, which is it's actually pretty easy for you to build a chain and run a chain that is cheap when no one's actually using it or when the number of users is small, but it's actually pretty hard for you to sustain that low transaction cost when you are pushing to, what, on average, 15.5K transactions per second. It's all market dynamics, right? Because if your chain can only sustain, say, 1,000 TPS, then the moment the demand goes beyond 1,000 TPS, then the top payers are going to decide the gas price. But in our case, because the chain has, actually the chain has more capacity, We really worried about like breaking our infrastructure partners. So we didn't really go full throttle. But, and that's the reason even at 15.5K transactions per second, yeah, like the base fee, the gas fee never fluctuates.
David:
[35:44] Leigh, a lot of this, a lot of the stress tests, I feel like it's just downstream of a lot of your just academic work. Like I feel like this stress test is also a stress test of Leigh's knowledge and his PhD in computer science. White paper. Yeah. Yeah, so like, how do you feel as just like kind of like your personal journey like downstream of this test test? What does this trust test mean for you?
Lei:
[36:06] It's amazing. And also, by the way, all the credit goes to our mastermind, Elon, who holds a real PhD in computer systems. My expertise was more like ConsenSys, which unfortunately is not used in MegaEath. But anyway, all the credit goes to him.
Lei:
[36:22] Yeah, I personally feel pretty excited because I'm just very motivated by all the DMs flowing in, telling me that, oh, my God, the chain is real. Yeah, it is real. It's been real for a year. But yeah, anyway, I'm just very happy that I think it's a nice, I also feel pretty much reassured because we now have like a real end-to-end stress test. I think you guys were asking perfect questions like, hey, what's the setting of this stress test, right? And I feel pretty comfortable right now because it's exactly the same service that we're going to run our mainnet on. I mean, it's the exact same deployment. We're not going to do any redeployment or anything. It is the mainnet. So it's a great validation. I think it's
Ryan:
[37:05] Lets me sleep better at night.
Lei:
[37:08] And also, I think it kind of stress tested our downstream infrastructure partners, because I think it highlighted some issues with the infrastructure. I think some of them, I think the blog explorers, they failed to keep up. And we're now literally working on new RPC methods tailored to make them make their lives easier, where they try to handle such low spikes in the future when it goes like really public. And we're also working with our app teams, the mafia, because they also run indexers, they post-process those transactions, and it also helped them identify the potential bottlenecks in their pipelines. So I think it's, in general, I think it's extremely meaningful exercise for the entire ecosystem. I'm just very happy.
David:
[37:52] What's the secret sauce that MegaEath has that really unlocks this throughput? Like, what is the unique thing that MegaEath has that other blockchains doesn't have that allows 11 billion transactions over seven days.
Lei:
[38:05] Right, right. So I think, yeah, we have been talking about a lot of our organizations, for example, parallelization, JIT compilation, and the peer-to-peer network improvements. But I think something we have not been talking a lot about is our new state tri design. We call it SOT, small authentication, large tries. So think of it as a direct replacement of Ethereum's Merkle Patricia try or commonly known as the Merkle tree. So the thing is with any EVM chain or with any chain that you want and hope to like settle onto ethereum as a layer two you need a tree that authenticates to the entirety of the chain state and here chain state is basically the the list of balances the list of account nonces how much money each person has how much erc20 tokens each person has right so these states need to succinctly go into a single hash and this process is what we call managing or and updating the state try And before our optimization,
Lei:
[39:13] State try management takes more than 90% of block building. In other words, if you spent seven days processing those 11.4 billion transactions, you would spend 70 days on managing the state try. So in other words, you are kind of only spending 10% of the time running the transactions and 90% of the time like doing post hoc management. it. So what we did, I think, which is pretty interesting compared to what other chains have been doing, is we completely redesigned the data structure. And I think many teams have kind of identified this bottleneck after we did. And I think what they did was they tried to optimize the database that stores this state tribe, but I think not many of them has tried to really just revamp and redesign the data structure itself, right? So there's a difference between the the mathematical structure and also the physical database that holds these data, right? I think most people are like rearranging the data in the physical medium, but for us, we just completely redesigned the mathematical structure.
Ryan:
[40:23] What we optimized for was,
Lei:
[40:26] Okay, so many people are trying to improve the database, but our goal has always been that, let's just get rid of the database. So I think something that's very unique about our state try is it takes so little space that you don't have to constantly update your database, right? Because you don't have to store it in a database. You can just fit it in the main memory of your computer, which usually goes at most maybe 128 to 56 gigabytes, and that's it. So it alleviates the potential bottleneck of constantly reshuffling data from the state tri to the database completely. And now it's just a very quick memory read. So I think this, I would say, is one of the secret sauces, like just a complete revamp of the Ethereum, Merkle, state-tri data structure.
Namik:
[41:15] Leigh, you've done this in a way that still preserves full EVM compatibility?
Lei:
[41:20] Very good question. Extremely sharp question. So I think there are too many words to describe, too many terms to choose from. So I would not claim Ethereum compatibility because I think someone kind of commented on me. But what we achieved was, okay, so you can port whatever, you can just deploy whatever bytecode you have on any other chain as is. It runs on Ethereum. The only difference here is we're tweaking the gas model. So some opcode runs a bit cheaper. Some opcode runs a bit more expensive. And second, the state root is now computed differently. So in other words, for the same state, you can imagine as for the same list of accounts and for the same list of balances, the state root, the hash that exists in the block header will be different from what it would be if Ethereum may not. But the good news is almost, I would say, no application depends on the particular way to compute the state root. Yeah, so I would say it's compatible because it's bytecode level compatible, but people may disagree. So I describe what I can describe.
David:
[42:29] Okay, so with this optimization, with this trust test, we learned that MegaEth can sustain 11 billion transactions over seven days for the low, low cost of $2 million, or $1.1 million, which tells me that chain fees is not a viable business model for MegaEth. I don't think it's cool that you guys can do 11 billion transactions per second. I don't think you guys are getting to a sustained level of organic 11 billion transactions per second anytime soon. So that implies that economic sustainability for the mega-eats system is not going to come from chain fees. So if it's not going to come from chain fees, where is it going to come from?
Namik:
[43:11] Yeah, so I can take this one. I think that the general thinking was... There's this fundamental misalignment of interests, right? Because as MegaEath, as
Lei:
[43:25] We get more
Namik:
[43:26] Users and our blog space becomes, I could say, more valuable, we want to charge more fees because, you know, vendor lock-in, we can make more money, right? But I think that's actually short-term thinking because the way Mega grows is by letting everyone come and use Medi for as cheap as humanly possible. I think that's one of the main reasons why Solana was actually able to provide such a good value proposition for users, right? Like, you know, Pump was initially in the Blast ecosystem, but the second there's like a thousand people launching meme coins on Blast, right? Blast maybe would get expensive. Again, I don't remember the exact Blast configuration, but that's more or less what happens if you use like, you know, EFDA and a couple other statements, right? But yeah, I think our opinion was, hey, we want to be as cheap as possible. I want to get like cheaper over time so we can get more users as opposed to get less users as we become more successful. And in that scenario, we basically said, well, we need to more or less find a way to make gas consistent and run it at cost, right? Not really make any money on it. I think the second point is like, well, okay, how do we make money as a chain, right? You know, I think like the error of like, you know, launch a token for the sake of having a token and just like, that's done. So you kind of need to build some sort of like real business model. And we kind of came down to stablecoins.
Namik:
[44:51] At least that's what we have now. We plan on building more first-party applications in the future. But a general thinking is, hey, we have worked on, you know, stable core. We've worked on building a bunch of apps or facilitating a bunch of founders to build cool apps. How do we find a way to have like a win-win where we can, you know, earn off of their success, right? Without necessarily like, A, hurting their users by having fees that are expensive. Or B, you know, in any way, shape or form, messing with their economics. And the answer there is the hidden tax of Tebow yields that come in stablecoins, right? Everyone who has a dollar on chain, right, especially after Genius, is not getting the yield for that dollar. So if you're holding USTT or USDC, right, on like Ethereum L1, someone somewhere is internalizing a Tebow yield, right, on your behalf. What we basically said is, hey, we're going to have this native stablecoin, USDM. And when applications use USDM, we earn the Tebow yield for that. That goes into the Maggie EVE balance sheet, let's say. And what that does is it allows
Lei:
[46:06] Us to grow...
Namik:
[46:09] The chain reinvest into the chain in a way that doesn't necessarily harm end users you know one can argue that end users should be getting their yields right but i think then you just have to ask yourself well what kind of reasons are people coming onto your chain for right someone who's stable coin farming should not be stable coin farming on mega eve right they should not be parking their stable coins on that eve they should be doing that on efl one efl one is more secure than Mega, right? You're coming on the Mega because there's cool apps on Mega. You're coming on the Mega because you want to do something unique on Mega. And then having to deal with this hidden tax, which you wouldn't have been earning anyways, I think is a very reasonable trade-off. So the way Mega makes money is via these table yields. It doesn't hurt apps. It doesn't hurt users. And in fact, it's the opposite. If the app becomes more successful,
Namik:
[46:58] Mega is able to earn more money and users are able to maintain cheap fees. So we think it's almost like symbiotic relationship again i think for better for worse we keep experimenting and trying new things with mega both on the tech side as well as bd side maybe it'll be a complete failure i hope not but it's possible just our general thinking is there's this famous like einstein quote i think which is like definition of madness is to try the same thing twice and expect a different result and
Ryan:
[47:26] We just kind
Namik:
[47:26] Of came to the conclusion well we have to try new things because i Well, what else are we doing here, right? So yeah, that's the way we're thinking about economics.
Namik:
[47:35] I think it makes sense, right? It's sort of a TVL or AUM type of revenue structure, right? That's passive, that's in the background, that still provides a user's value, but with less friction. There is one other leg of maybe a three-legged stool of where L2s and even chains in general can charge, let's say, for their service, which is block ordering. So MEV. And this is, if you look at kind of Solana, for instance, this is how Solana generates the revenue that it generates. What about MEV? Is that like off the table from you guys? Like you'd be perfectly positioned running the sequencer to collect that. Base collects it. You know, a lot of the L2s collect it today. Why not mention that? And like, is that a factor in the revenue model?
Lei:
[48:21] Yeah, it is. And yeah, we actually have thought a lot about it because me personally, and I think the team by extension fundamentally disbelief is microscopic auctions. And microscopic auctions basically is what Ethereum layer one
Lei:
[48:38] Style, tip-based, priority fee-based ordering, because you can kind of think of it as for every block you are literally doing an auction and from the person, from the people who pay the most to the people who want to pay the least, you kind of order the transactions, right? It's literally like every single block, every 12 seconds, you are running an auction to decide what's the block ordering on a layer two, sorry, on Ethereum layer one. But I think what it fundamentally breaks for us is because our block interval is so small, because in our case, the blocking interval is 10 milliseconds at the micro block, sorry, at the mini block level. It's not constructive to imagine that people can run auctions at such latency because, say, I'm a trader in New York and the sequencer is, literally is, in Tokyo. Then it takes me about 60, almost, I think, 100 milliseconds to even have my intention of how much I want to pay for this block transmitted to the Tokyo sequencer. So running auctions at this kind of fine granularity completely breaks down. So what we are trying to achieve, what we're trying to do here, I think we call it the proximity market, is instead of microscopic auctions where you have to panamically
Lei:
[50:03] Pick your ordering preference every block. You do it on a much coarser granularity, like every month or every week, every quarter or so. So you run those options at this kind of interval and decide a bunch of people that will have the seat to co-locate with the sequencer. And once you do that, then they can take whatever algorithm they want to run and run them on these seats, which are basically virtual machines that are right next to the sequencer. So the quotes we get from our cloud provider is down to one millisecond. And if people want to optimize, they can even get down to a hundred or even tens of microseconds, which I think is right there with NASDAQ level high frequency trading. Yeah. So this is kind of how we
Lei:
[50:55] Want to collect quote-unquote MEV, but also I think for us to collect part of the MEV, we really want to redistribute it to the community. We really want to reinvest in the ecosystem, but that's kind of a topic that NAMIC should highlight. But I think just on the technical design, our goal is to have just kind of semi-long-term auctions every week, every month to decide who can co-locate with the sequencer. And also it helps incentivizing people to move next to the sequencer. Because the reason for you to have a 10 millisecond block interval is for you to build efficient liquid markets, right? What's the need of, what's the purpose of 10 millisecond block interval if people are, if those really high-faceted traders, which are really the people who are responsible for market liquidity, are going to stay at the opposite side of the world and just remotely market make, right? They should come to the sequencer. So this, I think, is both an incentive structure and also I think a more practical way for us to have like efficient priority allocation when you have real-time trading.
Namik:
[52:00] Yeah, what's fascinating about that design is, I guess it's maybe also in the spirit of seeing the quiet part out loud, right? And just creating a mechanism for handling this because when you look at very high TPS chains and including very high block time chains, you could see it sort of collapsing to that sort of thing anyway at the social layer. Like sometimes I look at Solana and the amount of co-location that is happening. Yes, it's Amsterdam. For those that don't know, Amsterdam is a massive hub that many of the Solana validators are located in. It's kind of like, I don't know enough to say it's like what percentage of the network it is, but it is the place if you want to collect the max MEV. And so you see a lot of validators, people running Solana infrastructure co-located there.
Ryan:
[52:49] But they don't really talk about that so much, right?
Namik:
[52:51] It's not advertised in the marketing material, right? So whereas with MegaEath, you're just sort of saying the quiet part out loud, which is like, and designing a mechanism for it, which is to say, hey, it's really valuable to be co-located next to a sequencer. It just is.
David:
[53:06] And also explicitly selling it.
Namik:
[53:07] Yeah, and here's a transparent way to actually like take a Moloch type problem and sort of auction it at some level. Of course, listeners can imagine different ways that this type of thing can go wrong, but at least you're taking a step of making it transparent, auctioning it, and creating a mechanism to feed this back to the community. And there's something I really like about that, actually.
Lei:
[53:28] Yeah, the transparency part is really important because I think as an independent trader, I think our mechanism could actually empower more independent, curious traders because as an independent trader, you definitely don't know how to navigate the maze of which VPS, which server provider I should use to get the minimum latency to a Solana or to a chain validator right so
Namik:
[53:47] I yeah i think it's simply like you know these are controversial decisions but we think they make sense because it goes back to mega token holders right like if the bottom line is that we're trying to build systems of value like mega token holders i think it's like fair it's decentralized in its own way it basically like turns these private value capture
Namik:
[54:11] And turns them into almost like a public goods of sorts. So the value goes back to every stakeholder. The reason why it's not worth mentioning because you need users, right? Like no one's going to participate in proximity markets unless people are using Mega, unless there's apps that people want to participate in. There's a reason why David and Ryan are on Mega Eve, not because they feel guilty after a podcast episode of us, but because there's something you want to do. And that basically means that, Like, realistically speaking, I don't think proximity markets are going to be this amazing story in the first day of Mega being live, because we're going to do a lot of the hard work of making sure that all of our apps go live.
Namik:
[54:50] We find PMF of some of these applications. And over time, people actually want to co-locate with the MegaEve sequencer. And when that happens, instead of telling them like, oh, yo, send some money to a bank account and you can sit next to a mageef in tokyo or wherever we are at the time uh we've rebuilt a system where you're like this is how much it costs based on everyone else denominated in tokens and mega tokens and you create structural economics and benefits anyone who's choosing to hold the token so we just think it's a bit more of an honest approach again well let's see what happens
David:
[55:26] I do appreciate just the understanding that the whole point of MegaEath is to collapse the business model of selling block space, which forces you guys, it's a forcing function to get a little bit more creative about how to capture value. And so, you know, creating USDM, selling co-location. Is there anything else? Is it kind of just like as good ideas come in, we'll throw spaghetti at the wall and see what sticks? or like is there, do you guys have like a third or fourth product lined up or any thoughts there?
Namik:
[55:57] Yeah, I mean, I think that like our general opinion is like, hey, let's look at the EVM and say end to end, where are there problems that we can rebuild from first principles? So Elon and Leigh did that, or at least they tried to with MedEve, right, as a blockchain. And they've built like an unbelievably high-performing blockchain, right? What we're doing as, you know, Mega, as we move forward is continue to make MagEV really good, but then also try and identify additional bottlenecks within the EVM or just the general, like how we understand blockchains to be today and try to build first-party applications to solve for those problems, right? So, you know, I think we're really interested in like, a lot of that design space. A lot of it is to be announced over the following months. But yeah, I think our general opinion is we've built this great blockchain, we've facilitated applications on this chain, and we're going to continue to facilitate applications on this chain. It's been two years. We have a few apps that we think will be exciting. There's been a lot of drama about apps on MegaEve, and there'll be lots of drama in the future about apps on MegaEve, right? We will not stop trying to have cool applications on the chain. And we're not going to stop trying to work with those applications on doing something that's unique. And anytime we progress into building first party applications or first party experiences, we think it's because it's net positive for MegaEth and MegaEth token holders as a general group.
David:
[57:24] Let's talk about MegaEth's app strategy because the other thing that I think is refreshing about MegaEth is like back in the old days of blockchains, there was no app strategy. It was like credible neutrality, like don't touch the app layer. Whatever emerges on the app layer is great, but we don't want to have a hand in that. And MegaEth has kind of just taken a very different approach, which is like, no, no, no, no. We are going to directly foster our own app layer as aggressively as possible, which I find refreshing. Now, Mike, maybe you can kind of just like walk us through what the MegaEath philosophy is with like incubating its own app ecosystem. For sure.
Namik:
[58:01] If an app, like the general thinking is like, we cannot end up in a situation where we just have a bunch of repeat applications that exist on every other chain. And there's two reasons. First, like, well, why would anyone come and use the chain if it's the same apps, right? So that's a basic one. But then the second one is like, okay, like, what is the point of us spending the past three years of our lives trying to build this thing if there's literally nothing new that can exist on this chain? It's just like, I'm not smart enough to be able to just enjoy the complex technical problems that Leigh is facing. And that's how he enjoys his life. But like, we need to, this thing needs to exist for a reason, right? So what we did is we basically just started trying to find founders and convince founders to quit whatever they're doing, take the entrepreneurial plunge, and build cool shit, to be frank. Is everything cool? No.
Namik:
[58:51] Something's really cool? Sure. Did some founders not be able to, like, did they go bankrupt before they were able to go live? Yeah. Did some founders decide there's another chain or another opportunity that's more enticing? Totally. So all of these things have happened, but we are, you know, cautiously optimistic and we're quite excited because at the end of the day, we're going live with applications, which we think are cool. And we have a bunch of unique flows that like I have not had in my life, let alone in crypto, that will be on MegaEve in the months that follow. Right. So like the general opinion is that, you know, we should find founders. We should work with these founders to build unique apps. We didn't have a chain until, you know, well, we'll have a chain like five days from now. But like for the longest, for the vast majority of the history of Megateep, there was no chain for these app founders to use. So it naturally created like this question, like, okay, like, you know, we want to do this, we're excited, but there's like fundamental bottlenecks. We aren't able to iterate as fast as we'd like. Bunch of dependencies that we're not aware of. But what I'm really excited for is now that we, and we were still able to push through and get a bunch of cool apps.
Namik:
[1:00:04] Some of, you know, depends on what you like, gaming, consumer DeFi, lending. I can start naming you apps if that's what you like. But what I'm really excited about is the fact that we will have a mainnet and we will be able to double down on getting way more unique people to try to build unique apps. Because my general opinion is that we have a massive brain drain issue in crypto, right?
Namik:
[1:00:25] Unless you're in Megif, because, oh, sorry, unless you've come to crypto because of deep, deep, genuine interest in distributed systems or systems design, right?
Namik:
[1:00:35] I came into crypto because of the, I don't want to be a pun, but the promise of going bankless, right? I came into crypto because I did not like the idea of having to deal with like a sovereign who has control over me. I like the idea of permissionless systems, peer-to-peer networks. I think a lot of those founders that could have come and built awesome apps couldn't do it last cycle because the UX was garbage. And this cycle, they just left to AI, right? And that's just kind of like a really shitty situation for crypto applications. And like, maybe the answer is it doesn't actually matter. We just need something like Aave, which is global lending and we can call it today. But I think there's a massive design space which just hasn't been explored. Its founders have been, they're not here anymore. So we have to do proactive work. We can't be credibly neutral because that implies that there's abundance of developers, there's an abundance of founders, and they'll all build stuff and you don't want to pick winners. My bigger fear is the developers are gone. It's scarce. No one's motivated to build anything. And you actually can't be credibly neutral because if you do that, we just don't end up with any more apps. We have to go in and we have to like try things, even if it ends up backfiring on us, right? And it's backfired on Mega in a couple ways, don't get me wrong, because the alternative is worse, which is we end up with nothing for sure. I don't know. That's kind of like a bit of a doomer point of view maybe, but that's kind of like how we approach the problem with Mega.
David:
[1:02:05] Yeah. Yeah, well, I mean, I appreciate like the level of just like agency and personal responsibility that
David:
[1:02:11] you and just the MegaEath team feels about growing and incubating apps. There is something resonant about having this app that can do 11 billion transactions over seven days at essentially zero cost per transaction while also having this like incubator accelerator arm of it as well. The mega mafia, do you consider that to be an accelerator? And like how, if that, because like you guys have this like AUM business with USDM And so you guys are incubating apps that help grow the AUM of your business model. So like, it's kind of an accelerator. So like, how do you think about it in terms of just like the value capture of the whole system?
Namik:
[1:02:54] Definitely. So there's real answers to all we figured it out over time, right? The first thesis of Mega Mafia was just like, hey, let's just go find founders. You know, let's just get them to build stuff and let's just go live with a bunch of apps, right? And then, you know, the apps took a while to build. Mega took a while to build. and we had more time and we're like, okay, well, we should get like more apps to build on MEGA ETH. And the thesis was always, look, we're not going to take anything from the applications. That was initial thesis at least, right? We're not going to ask them for any equity. We're not going to give them any dollars either. Like we don't give them money. They don't give us tokens, nothing. It was just like a trust me, we're agreement to build on MEGA, right? You know, I would say over time, and I think the reason why that was fair is because of no chain existence.
Namik:
[1:03:39] Right. Like, I can't force you to come in like, you know, yeah, sure. We'll fly you to like a country and we'll sit together for a month and work together. But realistically speaking, I think it's just wrong to force someone to like agree to build on a chain that does not exist. Like, dude, what if the chain doesn't work? That's not very nice. But now that the chain's live, right? I think we're going to ask ourselves again from first principles, how does a megamalfia work? Right now, the ask is to use USDM, right? And we've worked with a few of the key mafia applications, and we've even worked on helping source some liquidity and try and make sure that they have just a minimum MVP amount of motion to be able to succeed and at least see if their PMF works. The ask on our side is just use USDM. As Mega goes live in a few days from now, I think we'll have a great opportunity to say, look, we actually have the chain. Let's figure out what's like 10 things we want to see exist on Mega. Let's find 10 people to build those things.
Namik:
[1:04:38] And then let's have them use USDM for sure. Let's potentially look at investing in some of these founders, depending on how mega is going, and becoming potentially even more opinionated. I think the general problem we have is there's just not enough founders in crypto. And I'm less worried about isolating founders than not even having founders. Now, the edge case here is what if the next meow, right? Founder of jupiter doesn't want to come to join mega mafia and are we like you know making them not want to build on mega that would suck it's something i think about a lot and i think the hope is that like hey this this chain's very performant and you know they myself were all still available if you have any issues to work and power through and like you want to build something amazing, build something amazing. I just think that like the day of being hands off is really over. And I do this, and I think our thinking is that we don't really have a choice here but to try and force function apps. For better or for worse, it could not work.
Namik:
[1:05:46] One other possibility here that has more recently risen to my attention here is that the next billion users might actually be AI agents. And so if that's the case, then it could be that AI, DevEx, is a thing that blockchain teams really need to think about. Well, one thing that's been interesting to me and sort of a bit of a realization is if you think, if you believe, as I do, that some of the reason we haven't had more crypto adoption has been the UX is terrible. The UX is really hard in crypto.
Namik:
[1:06:18] That's only true for humans. Actually, all the UX problems we have are actually benefits for little software agents, right? So the clunky MetaMask telling you some transaction, you have no idea what you're about to click. Guess who understands that perfectly? In like clear English language, like it could not be more clear to a software agent what exactly is happening here. There's no confusion. It's very specific. It's very specified. It's software. It's software, talking to software. And so if you believe that, that all of the bad UX for humans becomes actually good UX for agents and you have abundant cheap block space and you have these agents like starting to come online. I mean, we've seen all the kind of the open claw stuff happening. Well, maybe we should start really prioritizing agent users in some of our blockchain's experience. I know this is still somewhat early and like, who knows? There's a dependency here. Namik, you said we lost some of our best devs to AI. Yeah, that's true. But we might actually gain some of our best devs from AI now in this agentic part of the cycle. You have any thoughts there?
Namik:
[1:07:23] This is a late question. I don't talk about things I don't know. He actually...
Namik:
[1:07:29] What do you know about this? Yes.
David:
[1:07:30] Yeah.
Namik:
[1:07:31] Yeah.
Ryan:
[1:07:33] Right.
Lei:
[1:07:34] So it's quite interesting. I think to help agents, you need the block space to be sufficiently cheap so that they can try and error. I think something that's very interesting that agents have immense amount of energy, I mean, unlimited amount of energy to do that humans do not are just try and errors. Like I get angry if MetaMask does not work on Megate for like after two tries, I just throw my phone out. But agents don't care exactly as you mentioned. So I think being cheap enough for agents to work with. Second, some inherent features. So one feature we have been talking about, what I've been thinking about is one, you can just imagine this user flow, right? A user wants to achieve something, right? Hey, I want to swap a thousand US dollars for what? 0.5 ETH. I hope it's not 0.5, but it seems that it's the case. But so I want to swap a $1,000 for 0.5 ETH, okay, and just agent, figure out, like, whatever, just get me $500. Sorry, get me 0.5 ETH, right? So now the agent will kind of try to use different paths, different DAXes, different aggregators. So it's almost like intent protocols. I think with agent, you almost have your own intent solver.
Lei:
[1:08:50] So then the thing is, as a user, I would worry, hey, what if the agent just goes crazy, right? There's always the possibility. I think the thing with any human in the loop, but now agent in the loop system is that there's always the possibility of just random errors. So I want to guarantee, I want to kind of govern the, I want to sandbox the behavior of the agent. So something we're thinking about is what if the blockchain can, as a built-in primitive, lets user describe either in natural language or in very simple like drag and drop user interface,
Lei:
[1:09:21] Describe what the transaction should achieve in order to be successfully included on the chain. In the sense that me as a user can literally just type in the whatever interface I use saying that, okay, this transaction should at most deduct a thousand US dollars from USDC, for example, from my account and should at least give me back 0.5 ETH. As long as this case is hit, I don't care what transaction it is, right? Just agent go wild. Then the agent can just literally go wild. And I have my peace of mind knowing that whatever the agent do, I don't really care. I at least got 0.5 Ether back and I spent at most $1,000. I think this is something that can be very useful and we're just very actively brainstorming similar features we can help agents like this. I think there's a great parallel to draw between software programming agents like the agents that you run on your desktop and the agents that run on a chain or uses the chain because I think sandboxing and just establishing this trust boundary is always the hardest part. And I think as an, I would say, infrastructure company, I think this is what we should focus on. Of course, we should also try to build our own agents, whatever, but I think there are a lot of interesting stuff that we can actually meaningfully do to make agents' lives easier.
Ryan:
[1:10:41] So, yeah.
David:
[1:10:42] Let's talk about the mega token. Over the arc of mega ETH history, I understand like you guys have just had a pretty like opinionated strategy with mega token. You guys did the NFT sale. You guys had the public sale on Echo. And overall, it's been kind of a departure from what I think the rest of the market has kind of treated their token in the past. There's no airdrops here. There's just like kind of a unique, fresh strategy with what it takes to get the mega tokens into the hands of people. Talk about your guys' strategy here.
Namik:
[1:11:17] Yeah, I think that the general idea was like, I remember last cycle, there were like many, like there was like price discovery happening in public markets, right? Like that's just the truth of the matter. I think it was pretty awesome. I think in, and then we learned about a lot of issues There's like the low float, high FDB issue, right? Like, you know, the number that you see on the screen, right? That kind of changes, but the number stays the same. So, you know, we learned a lot of things. And a lot of people saw like a lot of money being made. So private markets decided to like, you know, bid a ton, right? So a lot of price discovery moved to private markets. And the end result was like, you know, public participants weren't necessarily getting equal access to assets, right? So I think that was a problem that we saw. And we thought that it was just not ideal because, you know, you'd... Crypto is unique because a lot of users in crypto want to be owners as well, right? And I think this is not necessarily the case with like most industries. In most industries, you like, for example, like, you know, in like tech, right, just because I own it, like I own an iPhone, right? I don't have any Apple stock. It's not because I think Apple's bad or anything.
Namik:
[1:12:43] I just don't have Alistar because, you know, I have crypto. But anyways, so, and I think it's totally fine. That's not exactly the case in crypto where people have historically been like, I want to be an owner in the applications I use. It's just, it felt very unfair. So basically what we did is we said, hey, you know, we did this, we raised some money from like, you know, Dragonfly. Funny enough, like the founders of Ethereum, Vitalik and Joe also participated in the round. And a year later, we basically said, you know what, we just want to give the exact same terms to Echo users, right? And if they want to participate, they can participate. If not, they don't have to. Saw that very quickly. I think like 80% of Echo users try to participate, broke a few records on the Echo platform. And we were like, oh, wow, we're onto something. Like, this is cool. I think there's a way to get people to be, to probably use the chain. They get equal access. And we basically just doubled down with that thesis all the way until most recently when we disowned our sale where we started a million dollar valuation. We capped the 999 mil because we didn't think it was fair to buy it Unicorn Val from Mega. And yeah, it ended up, you know, oversubscribing by like 25X or something. Obviously, you know,
Namik:
[1:13:52] Bitcoin was not at 70k. And yeah, that's basically been the thesis. The thesis has been for better or for worse that we don't necessarily think airdrops make sense. We think that like, if the potential users want to be owners, they can be owners. And we basically gave them access and we tried to have price discovery be accessible to, you know, participants who aren't just VCs. Yeah, let's see how it pans out when the time comes. But we do think that, I mean, I'd personally rather have like 10,000, 15,000 crypto users as an investor base. They love crypto. They understand why this industry needs to exist, as opposed to like a couple of big VCs that are great, but it's just like two free people. Less momentum, I'd say. Reddit did something similar, actually, with their mods. Power users of Reddit were able to invest in the pre-IPO for Reddit, but maybe we should get rid of that one. Securities laws. Whatever. Mm-hmm.
David:
[1:14:51] Okay, guys, so this episode is coming out the day of Mainnet release. So, hey, congrats on getting Mainnet out. We're recording this before,
David:
[1:14:58] so we're assuming Mainnet comes out on Monday. What does the next short-term bit of time look like for you guys? What does an actual Mainnet release look like for you guys? Is there like a war room that you guys are in, and what does the following weeks and months look like?
Namik:
[1:15:11] We're next to each other. We're in different phone booths. So we're working.
Namik:
[1:15:15] You guys have centralized sequencers then, even at the human level.
Namik:
[1:15:18] Huh? Bingo, bingo. I think the goal is apps, right? Like we want to get some of these apps live and we want people using some of these apps and seeing what's special. We want to kickstart the USDM application flywheel. And as that started work, we want to start building more unique applications that leverage MegaEath's block times and capacity capabilities.
Namik:
[1:15:43] Very good. We're excited to see what MegaEath does in the future. Good luck on mainnet. And I do think that this is the beginning of a second era, maybe, of layer twos. Not saying the main net release of MegaEth, but you're certainly in that second cohort of layer twos that have looked at the layer twos previous cycles and kind of done things a little bit differently. So it's a second generation. It's very exciting to see launches like this. And we wish you much success. Bankless Nation, of course, gotta let you know, none of this has been financial advice. Other than we know MegaEth transactions are gonna be cheap, cheap, cheap. You lose what you put in, but we are headed west. This is the frontier. It's not for everyone, but we're glad you're with us on the bankless journey. Thanks a lot.