Today we're talking EVM, specifically how Mega ETH and Monad are planning to make Ethereum SUPER fast.
We answer: 1 - Which is faster, more decentralized, and more censorship-resistant? 2 - How did Monad and MegaETH build large communities before even launching a testnet, let alone a mainnet? 3 - What are their thoughts on criticism that building with the EVM is like building on quicksand? Could this eat at Solana's value proposition?
------ 🌊 KELP | Deposit ETH with Gain today https://kelpdao.xyz/gain/?utm_source=Bankless ------ BANKLESS SPONSOR TOOLS:
🐙KRAKEN | MOST-TRUSTED CRYPTO EXCHANGE https://k.xyz/bankless-pod-q2
🦄UNISWAP | BROWSER EXTENSION https://bankless.cc/uniswap
⚖️ ARBITRUM | SCALING ETHEREUM https://bankless.cc/Arbitrum
🛞MANTLE | MODULAR LAYER 2 NETWORK https://bankless.cc/Mantle 🌐 OBOL | STAKE ON DVs, SCALE ETHEREUM https://bankless.cc/obol
🗣️TOKU | CRYPTO EMPLOYMENT https://bankless.cc/toku
------
✨ Mint the episode on Zora ✨https://zora.co/collect/zora:0x0c294913a7596b427add7dcbd6d7bbfc7338d53f/54?referrer=0x077Fe9e96Aa9b20Bd36F1C6290f54F8717C5674E
------
TIMESTAMPS
00:00:00 Start 00:05:48 Intro To Monad 00:11:47 How Does Monad Fit Into Ethereum? 00:14:08 What is Mega ETH? 00:18:31 Similarites and Differences 00:21:38 Architectual Impact 00:28:58 Decentralization - Monad 00:34:56 Decentralization - Mega 00:39:43 Who's More Decentralized? 00:49:27 In Summary 00:57:24 Software Effeciency 01:06:50 Monolithic vs Modular 01:15:11 Community 01:28:37 Why Choose The EVM? 01:33:07 When Mainnet?
------ RESOURCES
Lei Yang: https://x.com/yangl1996
Keone Hon: https://x.com/keoneHD
------ Not financial or tax advice. See our investment disclosures here: https://www.bankless.com/disclosures
No summary for this episode yet.
Welcome to Bankless, where we explore the frontier of internet money and internet finance. And today on Bankless, we are exploring the frontier of the Ethereum virtual machine from two different architectures. Two different blockchains are on the show today. Monad, representing the Layer 1 camp, and MegaEth, representing the Layer 2 camp. Both are using the EVM and really turning the EVM up to 11 to see how far it can go, but with very different paths to actually getting there. On this episode, we compare and contrast each of these respective blockchains with the respective founders of each of the respective blockchains.
So some of the topics that we talk about, which one is faster? Which one is more decentralized? Which one is more censorship resistant? All of the technical properties that we enjoy talking about in the blockchain world. Also, how did both Monad and MegaEth attract such large communities ahead of actually shipping a testnet? That's right, not a mainnet, a testnet. And then also, what do they think about Anatoly's claim that building with the EVM is building through quicksand? What do they think about that? And why, of all EVMs, do they choose to build on the EVM? All of these and other topics as well.
Before we get into the episode, though, a message from our friends and sponsors over at KelpDAO, which just introduced GAIN, a new product to help you maximize your rewards on your ETH. You can deposit ETH, RSETH, or other LSTs into GAIN to access rewards from multiple Layer 2 networks, restaking platforms and other DeFi opportunities. And for those who enjoy the Pendle games, they're already live on Pendle, Balancer, and more. But that's not all. If you deposit into the Gain Vault, you also don't give up your liquidity. You receive a GE from Kelp to unlock multi-chain DeFi strategies. There is a link in the show notes to getting started today.
Ryan, what'd you think about this episode? Yeah, I think it's a relevant topic. You know, this discussion of, you know, whether Ethereum is going to find its way, how it holds up to things that maybe the SVM, the Solana community is kind of kicking up, kicking out, right, with the FireDancer client. And I think the super fast EVM, super fast Ethereum approach that both of these respective teams are trying to build is kind of like one answer to that. In particular, the most interesting part of the discussion was over this like decentralization word, like which approach is more decentralized. And of course, we all know that decentralization is just a means to an end.
It's about security. It's about settlement assurances. It's about censorship resistance. But they've both taken a different architecture to that. One is a layer one. The other is a layer two. And so this was maybe the most contentious part of this discussion when we asked the question of, okay, which approach is going to lead to more decentralization? One element I feel like we didn't discuss, which is worth more investigation, is the concept of economic security as it relates this. There's a lot of time spent on kind of technical requirements to run a node in this conversation of what is a full node.
We didn't talk as much about distribution of stake. And I think that's maybe a follow up conversation. Anyway, lots, lots jam packed in here. One disclaimer before we get in both David and I hold angel investments in monad and nothing in mega ETH. There's always a link to all disclosures at bankless.com slash disclosures. All right, guys. We're getting right into the episode. But before we do, we want to thank our friends over at Kraken. If you want a super fast trading experience, go open a Kraken account and get started. If you want a crypto trading experience backed by world-class security and award-winning support teams, then head over to Kraken, one of the longest standing and most secure crypto platforms in the world.
Kraken is on a journey to build a more accessible, inclusive, and fair financial system, making it simple and secure for everyone, everywhere to trade crypto. Kraken's intuitive trading tools are designed to grow with you, empowering you to make your first or your hundredth trade in just a few clicks. And there's an award-winning client support team available 24 7 to help you along the way, along with a whole range of educational guides, articles, and videos. With products and features like Kraken Pro and Kraken NFT Marketplace and a seamless app to bring it all together, it's really the perfect place to get your complete crypto experience.
So check out the simple, secure, and powerful way for everyone to trade crypto, whether you're a complete beginner or a seasoned pro. Go to kraken.com slash bankless to see what crypto can be. Not investment advice, crypto trading involves risk of loss. The Uniswap extension is here. The self-custody wallet created by the most trusted team in DeFi, Uniswap Labs, designed to make swapping feel effortless. This extension lives in your browser's sidebar, letting you swap, sign transactions, and send or receive crypto without ever losing your place on the internet. Plus, with human-readable transaction messages, you'll always know exactly what you're signing.
Navigate a multi-chain world effortlessly with support for 11 chains like Ethereum Mainnet, Base, Arbitrum, and Optimism. No more chain switching or token importing. All your assets are right where you need them to be. The Uniswap extension is designed to level up your swapping experience with other Uniswap Labs products as well. Easily onboard to the extension using the Uniswap mobile wallet to begin managing your assets across platforms and take advantage of smooth, seamless synergies with the Uniswap web app. So go and download the Uniswap extension today by clicking the link in the show notes.
Just another way Uniswap is helping you swap smarter. Launching a token? Don't let complex legal and tax issues slow you down. Toku provides specialized support to optimize your launch and ensure that you as a founder and your team and your investors get the most tax efficient outcomes. The Toku team understands the crypto space inside and out and will ensure your token launch is fully compliant while maximizing tax efficiency. Toku can connect you with the best attorneys if you need them to make sure that you have the best advice and Toku can help to optimize your taxes so you pay the least possible amount of taxes while still maintaining legal compliance.
With Toku's guidance, you can concentrate on building your company while Toku handles the logistics. Token launches don't have to be complicated. Talk to Toku today to get a free initial token valuation. Bankless Nation, super excited to introduce you to Keone Han, the founder and CEO of Monad Labs, the creators of the Monad chain. Keone, welcome to Bankless. Hey, thank you so much for having me. And we also have Lei Yang, the founder and CTO over at MegaEth. Lei, also welcome to Bankless. Happy to be here. okay so two brand new high performance chains coming onto the scene both leveraging and juicing up the evm to i think really uh see how far we can take the evm uh different ways of actually using the evm that i don't think we've seen be used in the ethereum ecosystem or as layer twos ever before uh and so this is kind of a new frontier uh for this tech stack that we call the evm that i i think we all want to explore a little bit here on the podcast today let's go and take some time to introduce your guys' respective projects and really what are the key aspects, the key features of your guys' respective projects as it relates to the EVM.
I think Monad was founded first, so that means we'll start with Keone and then we'll go with MegaEth second. Keone, explain to us Monad and what it's doing differently in the space of blockchains. Yeah, thank you for having me. My name is Keone Hahn, co-founder and CEO at Monad Labs. We're building Monad, which is a reimagining of Ethereum from the ground up by redesigning both execution and consensus layers to introduce four major improvements and more generally deliver a really high performance version of Ethereum, offering over 10,000 transactions per second of throughput. And Monad is doing that by introducing a completely new database that's built from scratch called MonadDB by introducing optimistic parallel execution so that many transactions can be executed in parallel by introducing asynchronous execution where consensus and execution kind of run in separate swim lanes to massively raise the budget for execution.
And lastly, through Monad BFT, which is a really performant consensus mechanism that allows hundreds of nodes that are fully globally distributed to stay in sync with each other. So overall, it's an effort to go really low level and apply systems engineering techniques to build a really performant reimagining of Ethereum. One thing I want to bring up, Keone, me about the way Monad works is I think there was a lot of excitement about Monad after the Solana virtual machine, Solana, and the parallelization of the SVM got everyone excited about parallelization. And then there was like some technical pushback from very smart people who said, it's actually not paralyzed execution that is really the bottleneck.
It's paralyzed read access of a database, to which Keone of Monad said, well, we've also paralyzed our database too. And then everyone was like, wow, that's pretty sick. Can you kind of walk us through that part of an architecture of a blockchain? Why is parallelization of a virtual machine cool? But then also, how does it boil down to needing to have parallel read access to a database, which you guys also have? Yeah, it's a great question. I think people kind of intuitively understand that parallel execution is of some benefit because our modern computers clearly have many processors and are running many tasks in parallel.
You know, I have hundreds of browsers tabs open. It's kind of a bad habit, actually. But, you know, I have a whole bunch of different browser tabs, Spotify, Discord, all these things going on in parallel. And it's a little bit crazy right now that Ethereum and other EVM blockchains all are single threaded and execute completely serially. So parallel execution is the aspect of utilizing multiple threads or multiple processors on the host to run many pieces of work in parallel. And that's one of the improvements that ultimately can unlock performance. But when you do the benchmarking and when you look at what the real costs are, actually the single biggest bottleneck for execution is not that CPU time.
it's not like you know doing math or you know like executing individual instructions the actual biggest bottleneck is state access because every smart contract depends on some residual state that's associated with that contract for example when you're making a uniswap swap you need the balances of the two assets in the pool say it's uni v2 you need to be able to look those up in order to actually execute the swap and figure out what the new balances are. And that requires reading some data from disk. So the biggest bottleneck for execution actually is state access and only parallelizing the computation without also parallelizing reads to the database would be only a small improvement relative to the much bigger improvement that could be made by also allowing the database to be parallel readable.
And that's exactly what our team has done with MonadDB, which is a completely from scratch database that's specifically optimized for the problem of storing the Ethereum Merkle tree data really efficiently on disk. It's been a big endeavor to build this database. Everyone always, you know, the common computer science advice is don't write your own database because it's a big undertaking. But in this particular case, it's really needed and really impactful because we have high value state, aka Ethereum state. We need to be able to access it as fast as possible. Keone, one last question for you before we delay in the mega ETH side of things.
And this goes to kind of the word choice you were using and the phrasing you were using. You're talking about bringing this to Ethereum, this technology to Ethereum. And so my question to you is, like, in what sense is that true? And what sense is that not true? So certainly you are bringing this to the EVM, let's say, which is a virtual machine that Ethereum uses. But correct me if I'm wrong, Monad still plans to kind of launch its own alternative layer one. So we maybe call that an alt layer one in common parlance, not as a layer two. And this gets to maybe one of the distinctions and differences.
So in what sense are you bringing this to Ethereum? What sense are you not bringing this to Ethereum. So you're not actually expanding Ethereum as a layer two. You're not doing this in mainnet. You're not doing this like you're doing this as an alternative chain to Ethereum. Is that correct? That's correct. Monad is a vanguard environment for proving out the capabilities of these different architectural improvements that our team thinks ultimately are really needed in Ethereum L1 as well. I think at the end of the day, the discourse around layer 1s and layer 2s is one that's evolved over time.
And when we first started in 2022, there was a very, very strong feeling of layer 2s that all interact with Ethereum in the same way, utilizing Ethereum both for state commitments and for data availability. You know, these are very, there's like this one pattern of how Layer 2s interact with Ethereum. Now in 2024, that spectrum of sort of how Layer 2s interact with Ethereum and to what extent they're utilizing the services of Ethereum directly has evolved as well. And our team's belief is that there are many different ways to be contributing to Ethereum overall. And by focusing on a completely orthogonal direction of Ethereum scaling research that we think is really needed and wasn't being explored, we can also make a significant improvement, a significant contribution to the Ethereum ecosystem overall.
Okay, Leigh, it's your turn. So let's talk about MegaEth. And same question to you. Could you just tell us, what's the project about? And why are you here? Why is MegaEth here? Yeah, of course. So, yeah, again, my name is Lei Yang, and I'm a CTO and co-founder of MegaEth. So I just graduated with my PhD from MIT, worked for six years on blockchain consensus, and published a bunch of papers on security, performance, network aspects of blockchain. And now building MegaEth. So MegaEth is a performance-optimized blockchain with full Ethereum compatibility. And I guess the key kind of differentiation here is that we are kind of unapologetically performance oriented and we're single-mindedly performance oriented.
And how that materializes, right? So first we choose to be an Ethereum layer 2. And the reason is really that we think it's kind of the only optimal architecture for performance engineering. performance engineering. And we are really exploiting the architecture of being a layer two by building what we call the first real time blockchain. So in other words, up to more than 100,000 transactions per second, real Ethereum transactions, not just payments, a block time of 1 to 10 milliseconds, so that's what we want to kind of achieve is really for Dapps to be kind of as responsive and as feature and I mean, logic reach as your normal VAP2 applications, while also giving all the users the same benefit that they expect from ADAPT.
That is correctness of execution, freedom of censorship, etc. So a few kind of detailed kind of technical optimizations. So first, being a layer two allows us something called node specialization, in the sense that in MegaEth, we try to cut down the redundancy of execution as much as possible to the degree that there's only one active sequencer at any given point working on executing every single transaction. And all the other nodes, while they subscribe to the state updates, while they try to keep up to date with the current blockchain status, they do not need to execute all of the transactions.
and um basically that allows us to really jack up the performance and jack up the hardware configuration of the sequencer which is executing all the transactions and also maintaining the hardware requirement of the full nodes who are only interested in getting the getting the current state and on the sequencer side we have a few optimizations um including a new data structure that is feature i mean feature-wise being the same as the merco patricia tree but being much more efficient in terms of utilizing the actual hardware like ssds and memory we are going to compile in real time the ethereum smart contracts from bytecodes down to native assembly codes down to native instructions and we are also paralyzing the execution of the ebm so yeah these are some some highlights and uh yeah and we call the end product a real-time blockchain leia i'm curious that you heard uh kioni's description of uh monad right so i'm curious your perspective on kind of similarities and differences right so and and like maybe for kind of the the layman who's sort of approaching this the layman let's call them uh crypto native so obviously a similarity that probably stuck out is you're both looking to scale the evm and parallelize execution so that's ding ding ding that's a similarity okay and then a difference uh that i think we've heard from both these projects is megaeth is uh using the layer 2 architecture so it's uh settling to ethereum it's using ethereum for data availability uh i would imagine so it's uh is that is that correct um actually that's not correct so we settle down to i mean I mean, we use Eigenlayer as the data visibility layer, but also we settle down to Ethereum.
But also, a small nuance here is that we are not pushing parallelization as kind of the flagship feature or the flagship optimization. We value single-threaded performance as much as parallelization. Ah, okay. Well, then why don't you put it in your words? So what are the similarities and differences between the projects in your words? I think you summarized the similarities very well. The same focus on performance and trying to kind of bring in the next generation of apps by giving them abundance of resources. But I think the difference here first, as I mentioned, kind of a different angle, I would say, towards parallelization.
So my hot take is that actually, if you want to build, say, if you want, say, 100 copies of Uniswap, there's enough block space in EVM and Ethereum ecosystem for you to do that. But what we actually need is brand new applications. And for these applications, our belief is that you have to get to a degree of really high single threaded performance, because that is the actual performance that a single individual application can use at the same time. So yeah, so in other words, we're kind of really pushing the frontier of single threaded performance. the kind of the optimizations i mentioned like the new data structure the the jit compilation of smart contracts um the um and also this in-memory computation technique uh that i didn't mention they are all for single-threaded performance while parallelization we viewed it as kind of the second step to to push for after um we got to a high enough single-threaded performance to enable brand new applications.
Although engineering and operation-wise, we're doing the two at the same time. Another is, I would say, kind of a sharp focus on performance. We build a layer two by choice because we believe that it's the kind of the only optimal architecture for performance that enables you to really eliminate as much redundancy in terms of execution, in terms of consensus in the blockchain as possible. So I think that's a key difference that I want to highlight. Kioni, was there anything that Leija said that sparked anything in you? I think one thing to mention is that Monad's goal and these individual architectural improvements that Monad is working on are designed to get the maximum performance out of the minimal hardware requirements.
I think it's really important from the perspective of decentralization that anyone be able to run a node with commodity hardware. And in order for that to be possible, we need to make software improvements that get more performance out of the hardware rather than strictly relying on really high hardware requirements. So I think that fundamentally, the two projects are probably just very different in the outset from the initial premise, which is like in Monad, we're just really focused on getting the most performance out of hardware so that anyone can run a full node and have access to all of the state and keep up with the network and not have to trust, but instead just verify directly.
there's something really interesting about uh having both of you guys on the same podcast which is why we wanted to do this podcast where you guys have the same goals which is a very fast evm and but like the way that you guys have gotten there are like almost polar opposites towards each other whereas uh mega eth is going for the layer two single sequencer or very low number of sequencer routes and Monad is going for a layer one blockchain with a very wide distributor validator set. And then technically speaking under the hood, you guys have architecture to match these end desires. I'm wondering, since the end goal is the same, which is having a very fast EVM, do you think that the apps that will manifest on each one of your guys' respective blockchains will also kind of be the same?
Or do you think each one will kind of have an ecosystem that will emerge differently because of the underlying architecture? I guess the question is, how does the underlying architecture, how do you think it will impact the application landscape that comes to be built on top of each respective blockchain? Or maybe it does not do that. Lei, let's start with you. Okay, so I think it would be very different because, I mean, first, we are, as I mentioned, we're single-mindedly focused on performance. So that actually allows us to reach a much lower latency and I would say higher throughput as well for our system.
And I really want to highlight the latency part because it's exactly as you mentioned, we use a single sequencer at the same time. So the sequencer can just execute the transactions in a stream fashion and it really minimizes the kind of the wait time and this block packaging time for transactions to get their feedback. In other words, we expect the kind of the turnaround for an transaction from it arriving at the sequencer to it being executed and packaged and the state being updated is one millisecond. So I would say to me, at least from my background of consensus research, this is not possible for any system where a consensus algorithm sits in the critical path of the system.
because for a consensus algorithm to really function, a message has to travel at least across all of the nodes. And if they're globally distributed, then it means that it has to fly around the world. Although at almost light speed, it still takes several hundreds of milliseconds. And even not to mention that usually you need at least two or three rounds of messaging to do that. So that goes to maybe six to 700 milliseconds. And that is your minimum latency for a layer one or even a layer two with kind of a decentralized sequencer using a consensus-based approach. So this low latency, I think, would be really useful for some applications.
For example, imagine like on-chain Minecraft, right? You do not want your avatar to kind of take a 600 millisecond wait before it can take the next move. And for really high-frequency trading, I think it would be very interesting because actually the market makers and the traders can actually choose to co-locate with our sequencer. So these kind of real-time applications, I think, would be our unique ecosystem projects. Kiyoti, same question to you. Oh, yeah. Yeah. Wondering about the decentralized Minecraft situation, because that's only going to be low latency if you happen to be close to where the sequencer is.
Yes, of course. So I would like to distinguish two parameters. One is the tick time or the block time. In other words, the fidelity or the resolution of the movements. Like every one millisecond, a movement can happen. But for the user to actually get feedback, of course, we're not really breaking physics here. So the user has to kind of the action has to travel from the keyboard of the user to the sequencer back to the user's display. However, that is already happening with any kind of online, I mean, MMORPG games. So actually that part of latency is fine. What really matters is if you bring in consensus into a critical path, you have this three round, I mean, three messages around the globe situation.
And that's 600 plus milliseconds, which is much higher than the typical latency. I mean, the raw network latency from the user to a centralized sequencer. Keoni, what's your attitude or belief about the way that the application ecosystem will come to be born on top of Monad? Is there any differences or any things that you guys are focusing on specifically? I think the beauty of the EVM is that it is really this dominant standard that has incredible network effects. There's so many libraries that are built for the EVM. There's so many applications. There's a lot of applied cryptography research all being done in the context of the EVM.
And so being fully bytecode EVM equivalent, Monad offers developers who are already building with the EVM the best of both worlds between performance and portability. and Monad continues to do that while preserving decentralization, which I think, yeah, fundamentally will just be like, you know, a bit of a crossroads between Monad and MegaEth in the sense that our team just thinks it's really important to have decentralized block production from the perspective of censorship resistance and, you know, all these other properties that the crypto community has grown to cherish and deeply value, it's really important to preserve that full consensus, even if there is an overhead from consensus that lay, as you said, is literally inevitable due to speed of light, unless we can find a way to speed up the speed of light.
Maybe said differently, Keone, if I'm understanding you correctly, you're kind of saying that there is like a certain level of responsibility that one has when one builds a layer one because of the ethos of crypto that comes alongside with it. So like, what's the point of building a layer one if you don't have censorship resistance? What's the point of being building a layer one if you can't like meaningfully decentralize your validator set? And so in addition to having some of the very strong architecture improvements from the Monad EVM in the monad db you also have to do kind of like you have to do all the things that are required in order to call yourself like a legitimate blockchain uh effort which is like all the things that we value as like the crypto industry is that kind of what you're saying yeah that's right it's um you know it really comes from the social layer as well that's um enforcing these values um you know decentralization is important from a hardware requirements perspective from a number of nodes participating in consensus perspective from a stake weight distribution.
So these are all properties that have to be evaluated for any network. And beyond that, there also needs to be a really strong social layer that reinforces those values. Can we get into that? Maybe that's a good jumping off topic. I was going to ask another question, but since you brought it up, Kioni, the D word decentralization, this is sort of a sacred word in crypto. And I imagine Lei would be saying something similar. The reason we're deploying as a layer two is because of this word decentralization and censorship resistance. So can you kind of maybe start by talking about the Monad position with respect to decentralization?
Because I think this will be sort of counterintuitive to an Ethereum audience. It's just like, hey, if you're going to try to maximize decentralization, why wouldn't you be a layer two rather than a layer one? And it appears like you are arguing the opposite, right? So I think for a typical like Ethereum, their perspective is that, okay, Ethereum has had many years of tested Lindy effect decentralization. Like that's the thing that it's best at, right? It's like not very good as an execution environment, you know, 10 to 15 transactions per second kind of sucks at a lot of things. But one thing it gets right is almost near Bitcoin level, or maybe even better than Bitcoin.
I said it. Decentralization properties, right? And so why forsake all of that and move to a layer one? Yet you were saying your design choices in Monad are optimizing for decentralization. So maybe first talk about how you view the word decentralization and why the architecture kind of like promotes that for Monad. and then I'd love to get Leita way in as well. Sure thing. I think the first thing to point out is that for any choice of sort of network parameters, we should strive to get the maximum performance from that. So if we have a network with 10,000 nodes that are fully globally distributed, where the hardware requirement is a particular level of requirement.
I think in the case of Ethereum, and it's a bit of a meme, but I'll say it anyway, you have to be able to run it on a Raspberry Pi. So certain hardware requirements, certain number of nodes, then we should strive to get the maximum performance out of that requirement. And if the requirement is a little bit higher, but still very reasonable, so in the case of Monad, 32 gigs of RAM, a 2 terabyte SSD, 100 megabits of bandwidth, and a pretty cheap CPU, we should try to get as much performance out of that level of hardware and that network setup. sorry, I forgot to also say number of nodes. So two to 300 nodes participating in consensus that are fully globally distributed.
For that parameter set, we should try to get the most performance out of that. And by the way, is that hypothetical or is that the exact parameter set? Is that basically the specification? That's the parameter set. So basically, that's kind of like a consumer-grade laptop, like MacBook Pro, sort of what you described and like sort of a you know broadband typical broadband consumer internet connection is sort of the hardware requirement and then 200 to 300 nodes yeah it's a laptop you could get at costco okay and um you think that this is and and is this decentralized enough or is it as decentralized as ethereum or how would you even kind of like have that uh like conversation or would you include other actors in the in the space as well, because of course, it's not just the nodes, the validators, they're other actors with respect to how a block is created, block builders and such.
There's an entire supply chain around this. Anyway, would you say that Monad's design parameters are going to be more decentralized than Ethereum? Or how would you even have that conversation? Right. So I think the thing that I was getting at is for a given set of parameters, we should strive to get the most performance out of that setup as possible. And the only way you can get maximum performance is through software improvements. So the improvements that our team is pioneering within Monad with this particular configuration, some of those improvements will make an improvement to a different setup that, you know, more like Ethereum L1 right now, where there are 10,000 nodes.
It's like literally a different number of nodes and the hardware requirement is a little bit different. It's still a benefit to have this new database. The new database isn't designed for a specific SSD size. It works for any SSD size. So at the end of the day, it's really just about getting max performance with very reasonable hardware requirements. And so my point is that if you constrain the network to only having one node, really um then and you don't constrain the hardware requirements at all or you allow really high ram like there are going to be potentially some different performance uh characteristics that you could get from that um maybe even just for free just from like not having to go to ssd like keeping all of the state in in memory so at the end of the day it is like no matter what the job of the team that's doing the engineering work should be to get the maximum performance out of any kind of hardware setup.
But everyone always chooses one particular starting point for the hardware and then gets the most out of it. And our view is that this is a really good anchor point where the hardware is still very reasonable and we can get a lot of performance out of it. What's your take on the DWORD decentralization? What's MegaEath's position on it um either similar or con in contrast to what we were just hearing of course so i would like to first address this kind of performance per hardware unit if i may uh point so of course mega is also working to maximize the performance per hardware um unit or per per gigabyte of ram per CPU core per gigahertz of CPU frequency.
But also, basically, all of our optimizations can be kind of neglected if we can just jack up the hardware configuration to the infinity. But unfortunately, there is no such hardware that has an infinite number of CPU cores and infinite amount of memory. Actually, it's also the limitation of even the latest generation, the top-of-the-line server hardware that requires us to also do hard engineering work to really maximize the efficiency. The word should be the efficiency, the kind of the performance per unit, like compilation, like the new data structure, right? So back to decentralization. So the point here is that actually we also have lightweight nodes.
So our full node has 8 to 6 gigabytes of memory, terabytes of SSD, but not the server grade, just the consumer grade, 4 to 8 cores of CPU. So it's kind of relatively the same order of magnitude of configuration like Ethereum execution nodes and the S-Modern nodes. But the key difference, the reason, I mean, the real highlight here is that the sequencer has to shoulder most of the work by executing all of the transactions. But being on layer two allows us to kind of maintain the hardware requirement for the full nodes who are interested in getting the latest states, the entire latest states. So that actually boosts decentralization by being on layer two.
And also we have verifier nodes who literally can run off and rest reply, no storage, and just obtains the states needed for verification and also the transactions needed for verification from the network on the fly and just kind of verify the blockchain at kind of bite size, right? So actually, we value decentralization a lot, and node specialization is our answer to Kuhn's observation that, yes, if you require everyone to use really beefy hardware, then there's no decentralization to start with because no one can afford a server and no one wants a server humming. I literally have a server next to my desk, and it's noisy as hell when I do an upgrade or when I do a reboot.
And no one wants that at their home. So we are really conscious about that, and node specialization is our answer. Wait, wait. Is node specialization just basically L1 and L2? No, no, no. So it's basically you have different kinds of nodes of different hardware configuration doing different job within a layer two system. So you have sequencer executing all the transactions. You have full nodes subscribing to the state updates. And you have verifiers who statelessly verify the chain state. But on the topic of decentralization. So although we are really conscious about it by really minimizing the hardware configuration for full nodes and verified nodes, we actually believe that decentralization is just means to an end.
What you want is, I would say, correctness of execution. You want finality. You want censorship tolerance. I don't think anyone, I mean, most important people coming from VAP2 to look for something called decentralization when they enter the crypto space. I think what they want is assurance of correctness. They want to not to trust any single entity to run their important applications. And decentralization, as we saw, which worked really well for layer ones, is just one mean to an end. And now that a layer one has been built, which is Ethereum, with really as much decentralization as one can ask, I would say, we think it's time to move on.
So Ethereum has done the decentralization part for us. And now it's time for us to really optimize for performance, piggybacking on the decentralization that Ethereum has achieved. Do we get to have one of those back and forth conversations of like, you know, let's not use the word decentralization, but let's use it as a proxy for all of the properties you just mentioned, Lei, which is like censorship resistance, settlement assurances, all of these things, right? It's like we understand decentralization is just a means to the end. But I think what listeners want to know is, okay, which of your super fast performant EVMs are more decentralized?
So is it MegaEth or is it Monad? I, you know, what's your answer to that, Lei? And then we'll go to Keone. Also, how do we even like think about that? How do we even understand that question? Yeah, very good point. Very good point. So we can try a few different angles, like hardware configuration, which I mentioned. The full nodes and the verifiers for MegaEth are on the same magnitude of, same order of magnitude of hardware configuration as Ethereum and the modem nodes that is for full nodes, MegaEth. And verifiers literally rest their pi-grade and just downloads the information of the wire as needed.
So that is hardware configurations, right? So I mean, the takeaway is that you do not need anything that is beefier than your existing Ethereum execution nodes to download the latest and also maintain the latest megaeth state. In terms of the number of nodes... Yeah, go ahead. Sorry, sorry. It was just, you keep calling them full nodes, but I mean, are they, like, is that an abusive terminology at all? Because I think pretty much everyone else in the blockchain space uses full node to mean a node that executes all the transactions, like verifies the correctness of the outcome of those transactions.
And I think what you're referring to when you say full node is like something kind of different. Yeah, I can answer that question. So if you go to, say, ethereum's website and there's instructions for syncing up a full node and actually the default option is uh i forgot it's called snap sync or or fast sync i think they change the terminology a lot but basically is the default is one that just downloads the latest um snapshot of the state and such a node does not really verify the transactions before uh kind of start to serve you uh the state which is downloaded, right? Because the logic is that it just downloads the latest copy of the state and then starts working.
And then probably it will probably optionally verify the backlog, but it may not do so. So my point or our understanding, I think it's important that we bring this up, but our understanding of a full node is one that maintains and keeps track of the latest blockchain state. Yeah, so that's our understanding. And of course, the terminology is up for debate. And it would be great if the industry can agree on the same set of terminologies. We've been arguing on what's a full node since the Bitcoin versus Ethereum. That's where I started. It'll never be fully answered. Keone, how would you define, how does your idea of a full node differ from Lay's?
Yeah, why'd you bring that up? What's your thinking there? Yeah, well, I mean, I think if you are running a node of some sort, and it's not, you know, it has to trust a centralized party, then it's not very good. Right? Like the whole point of blockchain is that we don't have to trust, we could just verify. and so that's you know whether we call it a full node or not i mean i'm i'm calling out the use of the terminology full node in the sense that like it's being compared to like other things but i think what we really care about is you know if i'm a um you know a small business owner and i'm accepting payments um and you know someone sends me a payment and i let you know the person like walk out of the store with like, I don't know, a laptop or a diamond ring or a Tesla or something like I need to be able to know that that payment actually went through.
And so the whole premise in my mind of blockchain is that, you know, that small business owner could actually literally just run a node. And when they see that payment, they verify that it actually happened. And they know that they're not just trusting like a single centralized intermediary. So that's really the nature of my question. I guess I don't care whether you're calling it full node or not, really, but I really care about the question of knowing for sure, rather than just having to trust your single centralized sequencer. Yep. So I think you mentioned that don't trust verify, right? So if I may, I want to kind of append the following to it.
So basically, don't trust verify, but even better, let someone else verify it for you, which is the case of rollups, both optimistic and zk rollups so um in the particular case that you mentioned right i i'm the seller of a laptop someone paid me on megaeth say five thousand dollars and uh i'm deciding whether i should hand over the laptop so the thing here is um the sequencer the single sequencer yes and at the moment we are trusting the single sequencer to correctly order the transaction and to execute the transaction um but the important thing here is that the single sequencer is under kind of a social and economic contract so i think the debate is really about crypto economic security so imagine that because the thing is that if the sequencer ever cheats in the sense of retracting i mean excluding the the transaction or just giving me an incorrect balance update every information every piece of information that the sequencer told me when i was deciding whether to hand over the laptop was signed by the sequencer and if the sequencer did any shenanigans here this is kind of a proof that we'll get the sequencer slashed so yes the sequencer uh may lie to me but the sequencer has to probably lose um if that is worth maybe a thousand teslas or a thousand laptops which is not not not kind of not worth it right i mean uh yeah i think this really boils down to crypto crypto economic security and i mean being um a project in the ethereum ecosystem um i myself got from so i started working i started my research in blockchain from proof of work i think it's beautiful but um then i got to know kind of proof of stake and a cryptogamic security mode more importantly day by day and i think it really it really works yep new projects are coming online to the mantle layer 2 every single week why is this happening maybe it's because mantle has been on the frontier of layer 2 design architecture since it first started building mantle da powered by technology from eigendia maybe it's because users are coming onto the mantle layer 2 to capture some of the highest yields available in d5 and to automatically receive the points and tokens being accrued by the 3 billion dollar Mantle Treasury and the Mantle Rewards Station.
Maybe it's because the Mantle team is one of the most helpful teams to build with, giving you grants, liquidity support, and venture partners to help bootstrap your Mantle application. Maybe it's all of these reasons all put together. So if you're a dev and you want to build on one of the best foundations in crypto, or you're a user looking to claim some ownership on Mantle's DeFi apps, click the link in the show notes to getting started with Mantle. The Oble Collective is up and running and is maybe one of the most important collectives that you've never heard of. OBL is bringing distributed validators, or DVs, to the Ethereum staking stack.
Distributed validators allow multiple parties of people running multiple nodes to create a single virtual Ethereum validator together. This makes participating in Ethereum consensus more accessible, more affordable, and more inclusive. It is a strict improvement to the Ethereum staking tech stack. With collaboration from Lido, EtherFi, EigenLayer, and 50 other entities and thousands of individuals, The Oble Collective is working to scale and decentralize Ethereum using DVs. And now you can get involved. Introducing the Oble Contributions Program. Visit Oble.org slash Bankless to stake on DVs, either through a partner staking protocol or at home.
Earn access to future governance and ownership in Oble while contributing to retroactive funding for projects that are actively decentralizing Ethereum. This is your opportunity to secure inclusion in one of the most important projects working to scale Ethereum's foundation for future growth. Visit obol.org slash bankless to get started. That's O-B-O-L dot org slash bankless. Arbitrum is the leading Ethereum scaling solution that is home to hundreds of decentralized applications. Arbitrum's technology allows you to interact with Ethereum at scale with low fees and faster transactions. Arbitrum has the leading DeFi ecosystem, strong infrastructure options, flourishing NFTs, and is quickly becoming the web-free gaming hub.
Explore the ecosystem at portal.arbitrum.io. Are you looking to permissionlessly launch your own Arbitrum Orbit chain? Arbitrum Orbit allows anyone to utilize Arbitrum's secure scaling technology to build your own Orbit chain, giving you access to interoperable, customizable permissions with dedicated throughput. Whether you're a developer, an enterprise, or a user, Arbitrum Orbit lets you take your project to new heights. All of these technologies leverage the security and decentralization of Ethereum. Experience Web3 development the way it was always meant to be. Secure, fast, cheap, and friction-free.
Visit Arbitrum.io and get your journey started in one of the largest Ethereum communities. Can I try and summarize the bit of conversation that we've been up to so far, just so I can make sure that I'm kind of keeping up with the issues? And I agree with you, Keone, like my definition of a full node, and I think the consensus definition of a full node in Ethereum land, at least, is that like I am a listener of the blockchain. I'm keeping a copy of the ledger, but I'm also doing my duty of verifying the validity of incoming transactions and incoming blocks. And so sometimes maybe a block comes to me and it's invalid and I reject it and I start listening for a different block coming from someone else.
And I don't actually just automatically accept that invalid block. I actually do my role of making sure that I'm adding only valid blocks with only valid blocks transactions to the blockchain. And this is how if everyone is doing this role, this is how blockchains preserve decentralization while also having correctness. And then and so what you're saying is that if you're just listening to a trusted source of these blocks, a single centralized sequencer, that actually is less of a role of what a full node does. Because if you're just automatically trusting the validity of these blocks as a full node, that makes you like less of a full node.
I think that was the point of contention that you brought up. And then Lay's response is like, well, if the sequencer is signing transactions and there's an economic bond that would result in the sequencer getting slashed a very large amount, then we are perhaps not the same full node as I was describing earlier, but there is a large amount of economic security here. And that's our new trust assumption. That's been the conversation so far. Yep. And yeah, exactly. And I would say, I think the type of node that you mentioned is kind of a combo of a full node and also a validator in Ethereum terminology.
Because usually people don't expect a full node to really sign, I mean, mine blocks. You have to be also staking. In other words, if a node does not stake, should it be called a full node? I think so. So I think kind of the type of node that you mentioned is kind of something that's much more than a full node. Yeah. Mm-hmm. Sorry, so just to verify, you said when, or Lei, you said that when, or if the sequencer were to post an invalid state root, how would they get slashed? Right. So it's basically standard optimistic and zk-proofs. So the way it works is that the sequencer, by posting the state updates, kind of accountable proof that the sequencer has set something like this, which is incorrect, right?
So later these transactions, the block, they are going to be posted to Eigen DA and the state route posted to Ethereum. And for optimistic proof, there are usually seven days for verifiers, which I meant the verifiable price, to come and re-execute those transactions. So importantly, people in MegaEth, they do re-execute transactions. The important thing is that an individual node does not need to re-execute every transaction. So this makes them lightweight. But again, people re-execute every single transaction collectively. So if they find anything that is incorrect, they submit something called a fraud proof or an optimistic proof to the Ethereum smart contract, which slashes the sequencer automatically.
the case of the zk proof it's even simpler basically the sequencer is responsible for kind of proving the state transitions in real time before in the future before even it posts the state updates so yeah that's how uh yeah that's how we verify the state roots i mean also nothing exotic here this is all standard layer two fair yeah exactly exactly exactly yeah yeah this This is not anything different about MegaEth. This is just Layer 2 101. Yeah, if I miscommunicated, I'm sorry. But yeah, as I mentioned in the beginning, it's just standard OP and ZK rollups. But just to verify, those are two different mechanisms.
So have you guys decided which one you're going to use? Yeah, we're using optimistic proofs for now. Because we believe that the ZK proof is not kind of efficient enough as of this point for our level of throughput. Oh, I see. Okay. But you were just mentioning ZK as a future, maybe, possibility. Yeah, exactly. I was trying to just introduce the validity proofs on a high level. Okay. Yeah, that makes sense. But then for the optimistic, for other people to verify, they'd also have to have a lot of RAM. And that is incorrect because I think I mentioned repeatedly that the verifier only needs to be as beefy as a Raspberry Pi.
So the secret sauce here is something called stateless verification. So again, disclaimer, we didn't come up with this idea. So it roots from Ethereum's stateless client discussion, I think a few years ago, but we are basically adapting the technology. Keone, I'm curious your take on this. So this line of discussion around full nodes and everything we we just talked about started with the prompt of, okay, Leigh, who's more decentralized? And again, we're using that word as a proxy for many things, censorship resistance, all of these features that make blockchain special. So I want to turn that same question to you.
How do you think about that question? Like, which is more decentralized? What's the path to getting there? for me decentralization means that anyone can run a full node and by full node i mean a node that has access to all the state and that executes all the transactions so monad is pioneering these different architectural improvements so that anyone could without raising their hardware requirements very much, run a node and keep up with the tip of the chain, execute all the transactions, and have access to the full state. I think that's really important to decentralization. I think that there are other architectures which trade some aspects of decentralization and censorship resistance for being able to move execution off of the layer one.
And that's interesting. I think there's a lot of merit there. But I think from the perspective of having a system with, I mentioned before, a couple hundred nodes participating in consensus, but even more than that, like thousands or tens of thousands of full nodes that have access to that full state. It's just really important that node requirements be reasonable. And then downstream, that also has an effect on the economics of the blockchain. I know this is a hot topic, but in blockchains where the hardware requirements are really substantial, it means that the cost to run a node is quite high, which then has a centralizing effect as well.
and you know we see that with some other high performance blockchains that have really high hardware requirements that it's just not economical for a small staker to actually run a node because it'd just be too expensive if it's like ten thousand dollars a year or something to run a node so i think that efficiency you know efficiency matters and efficiency has knock-on effects and it's just really important to have really high software efficiency so that we can have the most decentralized network possible. Going back to something that you said about Monad, Keone, about software efficiency is that just like one transaction should cost the least amount of just like total compute from all of the nodes around the world as possible.
And I think that's kind of like where you're spawning efficiency from. Can you talk about those knock-on effects? Like if you are optimizing for reducing the total compute costs of planet Earth to run the Monad blockchain. What does Monad get out of that? What's the juice that you can squeeze from that feature? So just to mention one thing, like I think it was actually Lei that was saying that like efficiency means like the least amount of compute expended to do something. But, you know, like that comes from like having one sequencer that does it. So yeah, like in the Monad network, If one reduced the number of nodes participating in consensus, there would be less, I guess, like in some sense, electricity expended for that.
But that's not totally like the metric that our team is optimizing for. Like we just want per unit of verification, like per full node, that cost to be as low as possible so that then it is as cheap as possible to run a full node and keep up with this entire global state that's progressing through time. So just wanted to clarify that. Sure. Maybe I'm missing something about the way MegaEth runs. I'm going to make an assumption here and yay, like shake your head violently if I'm wrong. But like since the whole idea about like mega ETH is that it goes really, really fast. Like we're centralizing all the compute.
We're centralizing all the resources in order to have like this real time server that like people ping and it goes really, really fast. And then in contrast to that, Monad is like a layer one blockchain with consensus and like individual, like hopefully solo stakers. and because of that architecture like in full nodes people who aren't staking but are still listening to the blockchain can keep up with the monad blockchain because you know the stakers have to be meaningfully decentralized and that means you have to reduce the hardware requirements from these stakers uh is your claim kioni that like because of like the more centralized sequencer that um that mega eat has that like it has like a lesser claim on decentralization and censorship resistance in comparison to monad is like a statement that you would agree with uh yeah that's a statement i agree with because of and like my logic is sound there right like because you guys have individual solo stakers you can therefore also have individual phone full nodes and then you have like kind of the complete blockchain stack to preserve like decentralization incredible neutrality and centricity resistance yep yeah yeah uh lay how would you respond to that?
So I think it's important to realize that we anchor our kind of finality, the correctness and censorship resistance on Ethereum. So instead of hundreds of nodes, there are tens of thousands of nodes that are a kind of backing that's powering the censorship tolerance guarantees. So by that definition, by the particular definition that you stated, I would say MegaEth is more decentralized. So I'm personally, I'm against kind of comparing decentralization of two products like without really clearly defining it. But in the way that you defined it, in terms of the number of nodes that provides the final guarantee of finality, correctness, and censorship tolerance, then I think it is objectively true that MegaEth is more decentralized.
Okay, cool. Because again, we're kind of cheating here, right? Because we built on Ethereum, but that's exactly, that's a conscious choice. Keone, do you have a response to this? I mean, this entire podcast quite clearly was just to bait you guys in the question of arguing over who's more decentralized. Let's just put that right out there. But what would you say? What's kind of the Monad claim on decentralization? How would you dispute what was just said there? I think it's important to be progressing toward... Well, yeah, maybe just to take a step back, In Ethereum L1 land, there's discussion right now about what improvements can we make to Ethereum itself to raise the execution throughput of Ethereum from 15 transactions per second, aka 1.
5 million gas per second, to something higher. and it's frustrating when there's the gas spikes on L1 and yeah, I just think that ultimately it's of merit for Ethereum to become more performant. It's of merit to introduce software improvements that make Ethereum more powerful. And so that's sort of like the most fundamental guiding principle in how our team was designing Monad was to make individual architectural improvements that might actually be something that could slot into Ethereum L1 itself. So I think that, you know, if we're going to sort of fall back on like, well, it uses Ethereum for some elements and not for DA also, by the way, but like using Ethereum for like settlement, um like i guess i would say all layer twos kind of can make that same claim of like we are quote unquote more decentralized than monad because we're all like using ethereum directly for settlement and i would just say like on the opposite side of the um the diagram uh it's just like you know monad is trying to introduce tech that makes ethereum more performant without requiring more hardware, which I think is good.
And then second of all, it's just that without kind of is like a more uniquely differentiated, that is a uniquely differentiated direction that I hope will be helpful to the overall effort to improve the impact of decentralized systems. Yeah, I think we can definitely agree that we're all contributing tech to the Ethereum ecosystem. But I think one small point, I think in terms of overall hardware consumption. So if we define the overall hardware kind of consumption of two chains as kind of the number of the amount of dollars that you need to buy servers and nodes to kind of let the system produce blocks correctly.
Right. Then for MegaEve is for MegaEve is one sequencer and for Monad it's several hundred full nodes. So I'm personally not sure if it's more expensive to operate and to purchase one beefy sequencer, probably thousands of dollars, versus hundreds of full nodes, I mean, Costco laptops. So just one small point. But overall, yeah, definitely. Yeah, I mean, that's kind of a puzzling line of argument for me, though, because, you know, if the monad network were only two nodes instead of hundreds, then it would be lower cost. And from that perspective, from that metric, it would. Yeah, exactly. But then the censorship tolerance and the finality, the correctness of execution of such a hypothetical and monad system will be lingering on, will be leaning on these two monad nodes while for MegaEth it's still a tenth of thousands of Ethereum nodes.
I think that's kind of an important, that's kind of an important difference. But I think you mentioned something that's very important, which is all layer tools, all Ethereum layer tools can claim so, which we definitely agree. And again, we build on layer two by choice. Yes. One thing I wanted to ask about actually, because you keep mentioning censorship tolerance, and you're choosing your words pretty carefully, which I think is interesting. Because you didn't say censorship resistance, you said censorship tolerance. Is there a difference there? Oh, so I usually use the two words interchangeably.
I think the key difference here is whether you want like real-time censorship tolerance or you want like eventual or i mean censorship tolerance with a bounded latency so um by so mega if is offering the kind of censorship tolerance um with a bounded latency by allowing those to post their kind of sensor transactions directly to ethereum which guarantees inclusion and then forces the layer I mean, forces the sequencer to include it in the layer two blocks. But also there's repercussion for the sequencer if the sequencer fails to include a transaction, right? Because of the same economic security.
So I would say it's kind of a combo of, I mean, hard delayed censorship tolerance and also crypto economic security. Right. So this is like the sort of standard OP stack. Yeah, yeah, yeah. It's not mega ETH technology. Yeah, it's just, I mean, layer two. Yeah. Cool. I just, I guess I have kind of a comment or a take just sort of getting to the conversation so far. And this is just like much higher level than what we've been discussing. But it seems to me in being sort of an observer of the Ethereum ecosystem for a while, it seems to me that both of these projects at some level are kind of an innovation reaction to Solana at some level, to kind of what a high throughput SVM looks like.
And Keone, you may say, hey, no, Monad preceded Solana in terms of thinking about this. And if that's the case, point taken. But I think that's part of the narrative attraction to it. It's like Ethereum really hasn't done very much innovation with respect to its virtual machine since inception. Like the Ethereum Foundation has not been focused there. It's been focused on other things. And so now both of your projects are like innovating the EVM and building new things, new possibilities from the EVM. And maybe, Keone, you would say like, hey, I'm like redesigning the entire database. So Monad even more so than MegaEth at this point.
And I think that's all good for Ethereum. It also strikes me that maybe Kioni, the monad approach is more the monolithic integrated type of approach, which is just like, let's put all the state and everything in the full stack, same area. So we're not moving execution and settlement and data availability across multiple layers here with multiple dependencies. It's just all put it in one spot. spot. So you are like bullish EVM and also of the monolithic religion, let's say, or integrated religion, if we want a better framing of that. Whereas mega ETH is also bullish EVM, but of the modular religion.
And you like this idea of layer twos and keeping the decentralization properties of Ethereum or maybe the ETH alignment, let's call it. So is that a fair characterization of your two projects and where you come, like both are innovating on the EVM, both good for the progress of Ethereum, especially to the extent that you're doing this in an open source way. And, you know, giving us the code in a way that others can access it as well. But Keone, your approach with Monad is more on the monolithic integrated, whereas MegaEth is kind of modular. I'm just trying to like pin down religions here, you know, because in crypto, we like to talk about architectural religions.
Gioni, what's your reaction to that? Yeah, I would say that Monad is a full stack approach where all layers of the stack are being optimized and harmonized. Ethereum itself is a full stack. Like Ethereum is amazing. There's this VM, there's consensus. It serves as a data availability layer for other blockchains. And I think when ultimately trying to make improvements to Ethereum, you would have to think about how all those pieces fit together. And that's kind of the thing that our team is tackling right now. You were talking about Solana. So I think one thing that's interesting is one of the four innovations in Monad is asynchronous execution.
the easiest way of which to describe it is by remembering the movie limitless where the premise of the movie is like the aphorism that you only use 10 of your brain like what if you could take a pill and use 100 of your brain like think about how smart you'd be and how easy life would be for you and you know in the movie there's a guy who takes the pill and of course things are great and then they become terrible because you run too fast. Yeah, exactly. Fly too close to the sun. And that's a helpful analogy because in existing blockchains where consensus and execution are interleaved, which is how Ethereum works and how almost every blockchain works, the budget for execution is actually quite small because consensus takes up most of that time.
And consensus is expensive because nodes are on opposite sides of the world. If it's a well-formulated blockchain, they're on opposite sides of the world or they're completely globally distributed. So consensus takes up most of that block time. And so execution is actually only a small fraction of that block time. In particular, in Ethereum, there's 12 second block times, but the budget for execution is actually only 100 milliseconds, which is 1% of the block time, which is like a crazy dilating effect. So with asynchronous execution, Monad moves execution out of the hot path of consensus and runs it in kind of a separate swim lane, very slightly lagged relative to consensus.
And that means that the entire block time can be allocated to execution. So this is a massive actually budget increase for execution. It's just coming from this different software architecture. so you know we've been our team has been talking about this concept for quite some time now and recently i've seen other blockchains including solana talk about you know kind of embrace like the idea of asynchronous execution and talk about ways to integrate that within these other blockchains as well so i think it's just um that's only feasible if you're designing an entire system where consensus and execution are both considered, the way that they fit together is considered, and we optimize this full stack.
So I think that that's, yeah, for sure, like Monad is aligned with the idea of trying to optimize the full system to deliver the most performance possible. You're going to confuse a lot of people when you ship the Monad product for all the narrative shillers out there, because I'm not sure whether you're the Ethereum killer or the Solana killer that, you know, we have to have a killer if we're launching an alt layer one or else, you know, We can't get the narrative off the ground. But, you know. Centralization killer. There you go. There you go. Lei, what's your reaction to kind of like my framing of this, which is like you're both EVM, Megabulls, and your project takes the modular approach versus Monad taking kind of the integrated monolithic approach.
Yep. EVM, Megabulls, we are there to enable new applications. and what our product design, as we saw, is just single-mindedly optimized for that, which is kind of allowing for better performance in terms of throughput, in terms of low latency, real-timeness, right? I don't remember kind of modular versus monolithic, the discussion coming up even once in our kind of scoping, our design discussions back in the days. so I think at the end of the day I don't I totally agree with you that yes we are on the track of um a modular approach um but I would say we're not guided by the discussion the kind of religious debates between uh monolithic and the modular it's really just because we build an we build layer two and uh yeah so yeah that's my that's my conclusion and I guess in terms of the the kind of engineering approach like we are performance we are kind of i would say if monad is like a full stack approach we are kind of a focused approach on on uh on performance and we're reading we're willing to kind of make sometimes controversial and uh and uh interesting uh design decisions but yeah here we are so if you're not willing to pick a religion uh are you willing to pick a killer you're an eath killer or your solana killer Well, centralization killer, definitely not ETH killer.
And yeah, I cannot say more. Guys, one thing that's, I think, pretty interesting about each of you guys' respective blockchains is the magnitude of the community that has risen around each one. Despite, I think, both of you not having a testnet. Raise your hand if you have a testnet. No one. We have an internal one, but nothing public. Internal testnet. Okay, so incoming soon, TM. It's actually pretty amazing that the brands that you guys have elevated for yourselves has attracted builders. So there's already people building on Monad. There's already deals going around of people building on Monad.
Same thing with MegaEth. There's this thing called the Mega Mafia. MegaEth has this hat that every single person wants in Ethereum. I wonder just how, what's it like to do community management, business development for an EVM chain? Because there are roughly, I don't know, 30, 40, 50 EVM chains that are out there. Yet somehow these two ecosystems that we have on the podcast today have done a very good job of actually building a community and started building a community of builders as well. I'm wondering, like, what's your guys' trick? How did you guys do this? What was the strategy for getting this done?
Keone, do you want to start? I think you we both have hats that you guys are about to show us yeah shows your stuff the Merck okay so the Melan deck yeah he's awesome shoulder right now it's a purple stuffed animal for you podcast listeners I can't see this I'm actually in a in a hat factory here I'm in a hat storage room, but I wanted to show you this Molandak. Yeah, the Monarch community is honestly incredible. It's just the result of amazing individuals who are really passionate about crypto, really passionate about DeFi, follow along with the lore and the memes and the fun of crypto Twitter every day.
Many of whom were not, actually pretty much all of whom were not like famous on crypto twitter or anything like that um but are just people who have been following along and found a home in the monad community and um found opportunities to contribute to take on leadership opportunities in terms of organizing initiatives contribute their art contribute um i don't know we have a lot of fun initiatives going on like um the monad run club which initially was seeking to run 10,000 kilometers collectively and hit that pretty quickly. So now they're doing, I think, 80,000, which is like the circumference of the earth.
I probably got those numbers wrong. Sorry. Or Monlingo, which is an effort to learn a new language. So people are doing Duolingo together. There's just a lot of incredible energy and it's all just driven by individuals. So I think it's similar to, it's really consistent with the ethos of crypto where individuals matter and everyone can make a difference. And also, you know, it's a environment of opportunity, both for application builders, as well as for folks that have just been are really switched on and really following along. How do you keep them engaged when only so many of them are actually like playing around with the internal Monad testnet?
So like, what are they doing in there? Like they're going on runs together, which is kind of sick. But what about just like, I don't know, more like crypto native stuff? Yeah, we've I mean, it's evolved over time. Initially, it was really just people hanging out, commiserating during the bear market. I think that a lot of things are path dependent, but it was pretty rough back there. And a lot of our really The OG members were just people who were scrolling the timeline and decided to take shelter, if you will, from the negativity. And over time, that's evolved into more specific initiatives.
But there are folks in our community who are getting job opportunities in the Monad ecosystem. For builders, it's amazing because they can meet really talented community managers or marketers or people who just have really good instincts for putting some wind in the sails of the project from a community or marketing perspective. So overall, I think it's just a very nascent but growing environment with a lot of opportunity. So inside, if you are a consumer of Monad lore, you'll notice that there's not just a Molandak. There's a few other animals as well. There's a Moland fish, another of other creatures.
I don't know how they work. Where does this lore about the Monad animals come from? Yeah, that's actually a great question. Great anecdote. when we first started opening up the community. Bill Monday, our community lead, and I spent a lot of time brainstorming, like trying to come up with the right mascot. And so I have this notion page now of prospective mascots and all of the ideas are really bad. Like every next one is worse than the previous one. And I think what it really, because we were thinking about it too hard. We were like, okay, Monad is really fast. So like, what's the thing that's fast?
Okay, like a cheetah or a car or something. Anyway, the point is we were absolutely mid curving it. And at the end of the day, the creatures that have ended up becoming like unofficial Monad mascots are all just community driven. Like, you know, a person just uploads an image and then that one through community curation, like floats to the top just through people reusing it. There's no formal voting process or anything like that. It's all just, you know, which things kind of stick in people's heads and end up recurring. And now there's a super deep lore with Melandek and Mokadel and Salmonad and Moyaki.
Yeah, I'll send you the photo later. But he's really cute, really funny, really hopeless, I would say. And he has a whole lore around him. Like he's, yeah, he doesn't have a house like all the other animals have houses. and um i don't know there's that doesn't have a house salman doesn't have a house uh that yeah i guess because he's migratory but but actually just because he he always kind of gets the short end of the stick and um in monad lore um sorry buddy there's mooch who's a fly he's french he was created by the french nads um shout out french nads um there's um spider mon who's a spider created by the Turk Nads.
He's creepy, but funny. Anyway, yeah, there's just so much like depth to, and it's just really fun. Like at the end of the day, if you're not, if you're in crypto and you're not having fun, then something is wrong. Something's wrong, yeah. And of course the Monad community is called the Nads as well. Lei, tell us about the MegaEth Apparel brand. How did you guys start this? Yeah, so we actually see a kind of an astonishing growth of our community because we literally just came out of stealth, I mean, less than half a year ago. So our thrust, our brand is called Mega Mafia. It's our kind of flagship builders program, incubation program.
So what we look for is those 0 to 1 applications that are only possible on MegaEth, a real-time blockchain, right? And so, I mean, what we're looking for are the people, are the kind of the founders who, I think actually the kind of our cohort, I think they share kind of a common personality. So they were drawn into crypto by, they probably read something on the internet saying that, kind of promising them that, hey, you can build this, you can build that decentralized and trustless application on crypto. they came to crypto realized that hey it's a lie there's not enough resource there's not enough infra to build what i wanted to do however so we are kind of offering them we're kind of telling them that that hey there's a new kind of wave of infra in particular megaeth that you should uh try to kind of redo what you what actually initially brought you into crypto the initial dream the initial chase um again right now so that's how we got to uh all most of our builders so uh we have uh like i mentioned um on-chain um minecraft we have on-chain vpn which is infinitely scalable and we have of course the the usual uh defy applications decks um products um but based on other books but not on on amms we have real-time prediction markets we have real-time real-time game shows etc so i think i'm basically wearing the mega mafia t-shirt so um yeah this is kind of our centerpiece of our community and uh um now they were talking about rabbits uh the mega bunny so there if monad is kind of mid-curving it then we're really kind of left curve in it because Because we picked Bunny really just because I'm holding a jellycat.
It's not a mega-eat jellycat. It's just a generic jellycat. I just like to hold it. So we picked Bunny really just because I love Bunny. So I was having my first chat with our co-founder and CBO Shuyao in Denver. So she said, hey, we need to pick some animal. We need to pick a mascot. And I said, hey, I go to feed the bunnies on MIT campus almost every other night. And I really love bunnies. And she basically said, that's it. And that's why we picked bunnies. I think it worked well. It's not by community choice, but I think our community love bunnies. But I think our rule, our single rule for Discord management is that if you eat bunnies, you're banned forever.
um uh but but other than that i think yeah uh i think it's been going well um so we are seeing more and more people who are kind of really interested in the tech so um probably uh some listeners may already uh saw our our tiktok i mean our short format videos um basically explaining kind of, I would say, common misconceptions and interesting and lesser-known tidbits in the crypto industry and in crypto research. Just break it down into kind of bite-sized pieces for our audience. I think that's been going well. Yeah, we do serious performance engineering, so we are also publishing a series of long-format tweets and also upcoming blog posts with kind of rigorous and more technical content for those more techie people.
Yeah, but I would say we just want applications. So that's kind of the centerpiece of our community building effort. We want people to rethink what is possible now on crypto with a real-time blockchain. So, Lay, is MEGA an acronym? In the MEGA ETH? I heard a rumor that it stands for Make Ethereum Great Again. Is that right? It does stand for Make Ethereum Great Again. But interestingly, we realized it almost a year, I think, into the inception of the company. Okay. Oh, you went with MEGA ETH first and then you realized, okay. Yeah, yeah, yeah. Exactly. It's actually one of our genius investors.
uh yeah it's just a coincidence you could always do the red caps if you if you want to go in that direction although that mean may already be taken by someone else we yeah we do have red caps so it's right on the on the kind of i'm handing it on my door so that i can wear it whenever i go out home yeah and the uh how many mega eat hats are there because i was told there were 50. um Yes, there are 50, but I shamelessly took three. So there are three at my door and also I think two red hats. How many unallocated hats are there? I think these three, so one for me and the other two are the only unallocated hats.
That's my counting. But yeah, ask Shuyang. High FTV, high flow, I guess. May I have one? We'll talk after. Yeah, ask our head star, Shuya. Okay. I already did. She said no. Oh, then unfortunately. Sad. I'm not allowed to tap into the reserve. Okay, one last question I have for you guys. Recently on a podcast we did with Justin Drake and Anatoly from Solana, Anatoly was talking some shit about the EVM. He was saying that it's just like building through quicksand. And while it's possible to like rebuild the EVM architecture to make it easier for builders, it's still really hard. And that's one of his like kind of bare scenarios for Ethereum.
I'm wondering if you guys can give your takes. Both of you guys have chosen the EVM. Why did you choose the EVM? What are your guys' takes about the future role that the EVM has in the industry? I remember in 2021, there was a chant going around in the Ethereum crowd that like the EVM is at the center of all things because even Ethereum killers were using the EVM, like Phantom, Avalanche, et cetera, five other chains that I've forgotten about because they've disappeared into history. Just what are your overall takes about building on the EVM? Why commit to the EVM? What do you guys think about it?
Where does it go from here? Keone, you want to start? Yeah, I think the EVM is actually a perfectly fine bytecode standard. There are some minor things that are a little bit quirky, like the size of the individual storage slots. 32 bytes is pretty big. But I think fundamentally, it's a perfectly reasonable, very expressive standard. And we have high-level languages like Solidity or Viper or Huff that are really powerful. so i think a lot of the hate is really misdirected or or just uninformed or just there for hot takes and it's a great standard that can get better over time through continued improvements and support for new pre pre-compiles or op codes like it's it's an evolving standard but there's actually nothing wrong with it at all and that combined with the network effects of so many application developers that have already built apps for EVM, so many libraries, so much applied cryptography research, that it's just a no-brainer, really.
Lei, your thoughts? Yeah, I pretty much agree. There's nothing that is fundamentally wrong with EVM. So interestingly, we had Vitalik at one of our events in ECC, so it was kind of oriented for students. And so one of the students asked Vitalik, hey, what's your, I mean, name, kind of, I think, three regrets of the technical choices of Ethereum. I think Vitalik didn't really mention EVM. I mean, I think he did mention that he would not start the slippery slope of precompiles, but nothing that is fundamentally wrong with EVM. And we definitely agree with him. Because and also I kind of realized that as an engineer and as a researcher, I think there's always the urge to kind of burn down everything and that start from scratch clean slate.
But there's always as CUNY mentioned, right? There's always all those ecosystem tools, libraries, research, builders, most importantly people, right? And they are already accustomed to EVM. There's a reason that Intel doesn't really come up with a new ISA instructions standard every five years. There are reasons because there is kind of accumulation of capital, of know-how into a particular tech ecosystem. So nothing that is fundamentally wrong with EVM and 100% EVM will keep flourishing. Okay. But now I'm dying to know, what were Vitalik's two other regrets? You said precompiles is one. What are the other two?
I must know. I honestly forgot. Oh no. Lost to history. We'll have to ask. Yeah, they are not. I think it's preferable. I think someone tipped it. They're not that bad. I think someone tipped it. Yeah. All right, guys. This has been great. Keone, one last logistics question. What's the future of everything that Monad has built and their open source nature? You got the Monad EVM, the Monad DB. Will these things eventually become open source? That's our plan. Any sort of timeline, or is that just something you guys will think about later? We'll think about it certainly as time goes on. And certainly before mainnet, the code will be completely open for people to read and verify.
It's really important from an audit and safety perspective. So yeah, no worries there. Okay, wait, wait. I can't believe we've gotten this far in the episode and we haven't asked the question, when mainnet? Because usually we don't do these conversations while there's just testnets. We usually wait to mainnet. We broke the bankless rule because this is such an important conversation because you guys are building this parallelized EVM thing, or I should say high-performance EVM thing. So now let's ask the question. So when mainnet? Gioni, when is Monad coming to mainnet? Our team is working really hard on it.
Can't give an exact date. My cheeky answer will be when Melandak comes out of this hat closet and doesn't see a shadow. Okay. Is that happening in February? Is that what we celebrate? All right. Lei, how about you? When may not for MegEth? Yeah, we have been pretty open. So end of the year slash early next year. Cool. End of the year slash early next year. Some new blockchains to play with coming your way, Bankless Nation. Keone, Lei, this has been just fantastic. I've learned quite a lot on this episode. So thank you guys for spending the time with us. I hope the Bankless Nation has learned a lot because I certainly have.
It's such a pleasure. Yeah, thank you for having me. Thank you so much. Bankless Nation, you guys know the deal. Crypto is risky. New mainnets will also be risky when they arrive. But nonetheless, we are headed west. This is the frontier. It's not for everyone, but we are glad you are with us on the bankless journey. Thanks a lot. Thanks for watching!