In this episode, David is joined by Co-Founder of Fuel Labs and Celestia, John Adler. Fuel is the fastest modular execution layer and Celestia is the first modular blockchain network.
John and David explore how modular blockchains are shaping the future of the space, what Fuel is, why it’s different than other L2s on Ethereum, why John believes Fuel is the leading L2, and so much more.
------ 📣 Opolis | Get 1000 $WORK and 1000 $BANK https://bankless.cc/opolis
------ 🚀 SUBSCRIBE TO NEWSLETTER: https://newsletter.banklesshq.com/?utm_source=banklessshowsyt 🎙️ SUBSCRIBE TO PODCAST: http://podcast.banklesshq.com/
------ BANKLESS SPONSOR TOOLS:
⚖️ ARBITRUM | SCALING ETHEREUM https://bankless.cc/Arbitrum
❎ ACROSS | BRIDGE TO LAYER 2 https://bankless.cc/Across
🦁 BRAVE | THE BROWSER NATIVE WALLET https://bankless.cc/Brave
💠 NEXO | CRYPTO FINANCIAL HUB https://bankless.cc/Nexo
🔐 LEDGER | NANO HARDWARE WALLETS https://bankless.cc/Ledger
⚡️FUEL | THE MODULAR EXECUTION LAYER https://bankless.cc/Fuelpod
------ Topics Covered
0:00 Intro 3:56 John’s Background 5:30 Creating Optimistic Rollups 6:56 Fuel’s Design Choice 9:50 Defining a Rollup & Modular Execution Layers 18:00 More Modular L2s 18:53 Fuel Flexibility 20:36 Data Compression 21:24 Fuel VM 26:55 The Fastest 35:27 Reducing Waste & Speed 38:42 Fuel Origin & Roadmap 48:59 Fuel’s Growing Ecosystem 52:36 Where Are L2s Going? 1:00:50 Call to Action For Listeners ------ Resources:
John Adler https://twitter.com/jadler0
Fuel Labs https://twitter.com/fuellabs_
Celestia Labs https://twitter.com/CelestiaOrg
----- Not financial or tax advice. This channel is strictly educational and is not investment advice or a solicitation to buy or sell any assets or to make any financial decisions. This video is not tax advice. Talk to your accountant. Do your own research.
Disclosure. From time-to-time I may add links in this newsletter to products I use. I may receive commission if you make a purchase through one of these links. Additionally, the Bankless writers hold crypto assets. See our investment disclosures here: https://www.bankless.com/disclosures
No summary for this episode yet.
Thank you. about why Fuel is built in the way that it's built, how it's different from the Ethereum virtual machine and why the Fuel VM, the Fuel virtual machine, is new and improved and shiny and super fast and super executable and is going to be, according to John, the logical conclusion of a layer two. You'll also learn a little bit about the inner workings of Fuel beyond the Fuel VM, the other parts of the Fuel network that make it tick. And overall, just get John's philosophy onto the layer two space. Fuel is a sponsor of the Bankless podcast, But that is not why we are making this episode.
We are making this episode so we can dive all the way down into the details that make Fuel tick so we can learn more about it. So without further ado, we'll get into this conversation with John Adler of Fuel right after we talk to some of these fantastic sponsors that help you go bankless. The reality today is that five corporations control the entire world of social media. They own our names. They restrict our content. They monitor our every move. And their time is up thanks to our sponsor, Deeso. Deeso is a layer one blockchain built from the ground up to decentralize and scale social networks.
With Deeso, you can own your own identity, content, and social graph, and take it with you across hundreds of applications already built on the censorship-resistant Deeso blockchain. Deeso's storage advantages make it finally possible to build infinite state applications that can efficiently store and index large amounts of content and data fully on-chain. Deeso also offers multiple crypto-native monetization primitives for developers and creators, including social NFTs, social DAOs, social tokens, and social tipping. So in order to experience the social layer of Web3, go to deso.com and claim your username.
That's D-E-S-O dot com. If you've been listening to Bankless, you know that we're fans of the modular blockchain thesis. The idea that blockchains will separate execution from data availability and consensus, allowing all three to become the best versions of themselves. And Fuel has built the fastest modular execution layer in the industry By supporting parallel transaction execution, Fuel unlocks significantly faster throughput for the Web3 world. Fuel also goes beyond the limitations of the EVM with its own Fuel VM, which is more efficient and optimized, opening up the design space for developers.
And lastly, Fuel brings a powerful developer experience with its own domain-specific language, Sway, and a supportive toolchain called Fork. With Fuel, you can have the benefits of smart contract languages like Solidity while adopting the improvements made by the Rust tooling ecosystem. letting the fuel development environment go beyond the limitations of the EVM. If you want to learn more, there's a link in the show notes to see how you can get involved with a fuel network. In all of my years in crypto, I've never been hacked, scammed, or lost money to a thief. And a lot of that credit goes to my Ledger hardware wallet.
The Ledger Nano X and the Ledger Nano S Plus hardware wallets allow users like you and me to secure and manage all of our crypto assets and our NFTs, all with the security of storing users' private keys offline and out of reach from hackers. The Ledger Nano X is the perfect hardware wallet for managing your crypto and NFTs on the go because it connects to your phone with Bluetooth and has a nice big screen for easy transaction readings. Ledger has also upgraded the iconic Ledger Nano S and made the new Ledger Nano S device more DeFi and NFT friendly, making it the perfect hardware wallet for beginners.
Ledger has truly maximized for both ease of use and security. So discover which Ledger device is best suited for your journey by going and visiting shop.ledger.com. Welcome, Bankless Nation, to this edition of Alpha Leak, where we are talking to John Adler about Fuel Network. John, welcome to the show. Hey, David. Thanks for having me. John, you want to introduce yourself a little bit and provide some background on how you got into crypto, and we'll lead into that story all the way through to where we are now with Fuel Network. Yeah, sure. So currently, I am our guest most recently, and also currently, I'm one of the co-founders of Fuel Labs and also Celestia Labs, which are building two separate components of a modular blockchain stack which we'll dive into a bit later.
How I got into blockchain I feel like I tell this every podcast but basically my old grad school advisor when I was in grad school at UFT was really into blockchain he was involved in the early days of Ethereum and so on, so he's been around there for a while one thing he likes to show his students is this selfie he took with a Mt. Gox sign guy in Japan if you remember those like this guy was assigned like giving back or give us back our bitcoins or whatever in japan when mount gox happened and then he had a selfie with that guy so he's been around for a while he kind of introduced the students to blockchain and then since then you know that's kind of where i got exposure uh after that i guess i went to consensus to do a general layer to scalability research so things like channels plasma and so on that's also where i created the optimistic roll-up design paradigm, or I guess at the time it was called minimal viable merge consensus because it was intended to be minimally viable and not the end game.
Since then, I think we've come up with slightly better constructions such as sovereign roll-ups and so on. But yeah, and then after that, I left consensus to start Fuel Labs and Celeste Labs. That's kind of the TLDR of my journey. So you created the, you said you created the optimistic roll-up design structured? Does that mean you created what we now know as optimistic rollups? Is that what you said? Yeah, I guess you could say that. There was a bunch of competing and close design architectures floating around at the time, which should surprise no one, right? Everyone was kind of in a hodgepodge of various ideas with different parameters in terms of data availability, how to do validity, and so on.
But I was kind of the first person to at least publicly publish the exact construction that we now know as optimistic roll-ups that specifically has certain properties such as it uses fraud proofs for validity, permissionless block production to ensure state liveness, and data availability on the main chain. So combining these three properties is something that other people hadn't written about before, which is kind of odd because if you think about it, it's not exactly a complicated construction, but it's one of those things where it's obvious in retrospect. but like at the time people weren't really thinking about these kind of constructions i think it's because at the time the prevailing narrative was plasma and people didn't like the idea of posting all the data on chain because they thought it was like it was a regression compared to the quote-unquote infinite scalability of plasmas so because of that people weren't too interested in that particular avenue of research okay so uh you've been a you started as a scalability researcher at consensus you said you worked in in state channels plasma and then ultimately became uh optimistic roll-ups which means you've seen the full trajectory of ethereum scaling research since day one uh since like we started with like oh we're going to scale ethereum with state channels not realizing that that uh is limited um to where we are now with optimistic roll-ups but but you've taken optimistic roll-ups in a slightly different direction than I would say is like the status quo, where the status quo or something like arbitrage or optimism, where they are trying to be EVM equivalent.
You're going off in a new direction. Can you talk about that philosophy or design choice with Fuel and how it's perhaps different than the optimistic roll-ups that most people are familiar with? Sure. So first of all, it might be good to kind of give an intro to what Fuel is. The tldr is that it's the fastest modular execution layer okay uh fastest because uh it supports transaction throughputs uh transaction throughput along you know proportional to the cost to run a full node uh that is better than any other modular execution layer out there uh and modular execution layer because it's something that's slightly more than just a roll-up uh so we could perhaps talk about the modular execution layer part first sure and then go to the fastest part because the fastest part has like it's one word but it has like a million different cones as to why it's like that right uh so the modular execution layer for those of you who uh for those of you who aren't familiar with roll-ups uh should i maybe give like a one minute summary of a roll love it okay so a roll-up is a blockchain like any other blockchain uh and it's attached it's attached to some data layer uh and then a data layer is like a layer one like ethereum or something else yes it could be ethereum it could be bitcoin cash if you're in 2017 and you're vitalik uh it could be celestia it could be eigen layer if you want it could be it could be it you could actually have a blockchain that is its own data layer kind of like ethereum is today or like solana is right it's effectively its own data layer and we would call that kind of a monolithic but then there'll be monolithic yes With a modular blockchain, the data layer is another completely separate blockchain.
So a rollup will post its data to a data layer, and it will progress its state transition function just like any other blockchain does. And it will be able to allow users to verify that the blockchain is valid, the rollup rather, just so there's no ambiguity here. It'll allow users to verify the rollup is valid using either fraud or validity proofs, or if we have any other acute construction, to verify validity without actually fully validating the chain. Because then it's not a rollup, it's just like, it's just a blockchain. It's just like, I don't know, a sidechain or something. Right, so maybe one definition to unpack is like, a rollup is a blockchain that posts its data, as in posts its blocks, to another blockchain.
and that the fact that it's posting its own blocks to another blockchain makes it a roll-up, not its own independent blockchain. Is that a fair definition? That's a necessary but not sufficient condition. You also need additional conditions such as you would need fraud or validity proofs. And you would also need a mechanism for permissionless insertion of transactions into the roll-up somehow. Because if you don't have that, then the roll-up can be halted or it can be censored. so you need all three these three properties uh so what's a modular execution layer uh with a roll-up uh most roll-ups you don't necessarily need what's called a settlement layer uh what a settlement layer is a blockchain it could be the same as the data layer such as in the ethereum model for roll-ups the ethereum acts as both the data and settlement layers the settlement layer will verify these fraud or validity proofs thus allowing you to have a two-way bridge of funds between the settlement layer and the roll-up uh you don't technically need that for a roll-up to be a roll-up like you could have a sovereign roll-up that could be its own settlement layer that could use another settlement layer or just like use a peer-to-peer uh for verifying fraud or validity proofs but regardless uh with a settlement layer uh the settlement layer is concerned with this two-way bridge right and for a two-way bridge to work what you really need for certain VMs or certain execution systems, what you really only need is for some state root to be valid.
As long as the state root is valid, or as long as the root of something, let's say withdrawals, is valid, that is sufficient. That is both necessary and sufficient to have a two-way bridge. Now, the problem is that some roll-ups have taken this to an extreme in terms of optimization and have decided to forego everything else. So if you look at the Bitcoin design paper, right, Satoshi spends one entire section of the Bitcoin design paper talking about Lite clients, or simplified payment verification clients at the time, right? And he talks about, hey, let's put the transactions in a Merkle tree so that Lite clients can actually get a Merkle proof to their transaction being included in a block, right?
and if you didn't have light clients you wouldn't need a merkle tree like full nodes do not care about a merkle tree of transactions or even a merkle tree of state like solana full nodes the solana blockchain does not have a state root like a root a merkle root over the blockchain state all account balances and contract state that doesn't have that and full nodes solana full nodes still run but you can't have solana light clients or rather solana has a weird way of doing light clients but let's say you can't have solana light clients just as a generalization without a state root similarly if you don't have a transactions root you can't have like clients either so some roll-ups have kind of taken the notion of uh the a layer two is just a roll-up and it's just concerned with this two-way bridge and nothing else and they've optimized away things like a transactions root and they just have a transaction hash and then you can't actually have an off-chain like client to the system which is weird right because now you're running a roll-up and okay do you run like who do you trust in that case like if you think about the model who do you trust if you don't have a roll-up light client off-chain that you can run how do you know the roll-up is valid like i guess you can trust that there's some powerful computer like you know verifying it and so on uh but you run an ethereum full node because if you don't run an ethereum full node then you don't actually know the roll-up has any notion of validity or anything like that right so the trust model becomes very weird if you don't have off-chain light clients in addition to not just like the trust model of has the rollup being corrupted but the trust model of even interacting with the rollup right because then do you just trust in fura to just give you all the data honestly right there's no like merkle proofs that your transaction has been included in the block how do you know it has been right uh you just have to trust in fura completely at that point well why even have a rollup so a modular execution layer if i can use an analogy it's kind of like the difference between usb 3 and thunderbolt 3 right where thunderbolt 3 is basically for those of you who aren't familiar the usb standards due to you know the you know designed by council uh is uh you know has a bunch of optional components so you can get like a usb cable that uh doesn't include certain features like let's say display so you can get a usb cable that you say oh i can use this to connect like you know to a display but like you can't because as long as power right like a thunderbolt 3 cable has all the features similarly to thunderbolt 4 and usb4 right it is all it is all the features so you're guaranteed if you get one of these cables more expensive but has all the features right and that's kind of the analogy is that just a roll-up and just a layer 2 will be kind of like a usb3 cable you don't know what you're getting and potentially you could want to do something and you can't a module execution layer you're going to think of it like like a thunderbolt cable where it's like a roll-up that has all the features and one of the important features that it has is the ability to run an off-chain light client.
So you have the properties of a roll-up, the trust minimization, the permissionless, the trustless two-way bridge, but you also have the ability to run a light client for that roll-up. And that allows you to really have trust-minimized infrastructure. Okay, I'm going to need you to check my understanding on this. I'm going to try and regurgitate what you said and you'll correct me in some particular way. Okay, so you're saying a lot of roll-ups, and you're talking about the Bitcoin white paper and Satoshi emphasis on these light clients, emphasis on Merkle roots. And my interpretation of just what is a Merkle tree, what is a Merkle system, is a compression system.
It's a system of putting a bunch of transactions into a smaller bit of data. and by making that bit of data more manageable, you allow more people to verify it, more people to actually verify the validity of the transactions that happened. And so when you're talking about a layer two that doesn't have this like client-enabled properties or just like any sort of like system for the layer two that makes it more manageable for other people to check the validity of, you're saying that it kind of runs into the same problem that Bitcoiners previously would critique Ethereum of is like, yo, your nodes are way too big.
Only so many people can validate the chain. What's the point of having a trustless system if the ability to run a node is so goddamn difficult that everyone has to just trust Infura? So you're saying that we need a mod, rather than just a roll-up, which is the USBC model, which is some one-off solution to create a roll-up and all it does is verify the two-way bridge so you can get your assets there, but it doesn't allow users to actually verify the validity of the chain because these chains are just not optimized. It doesn't have any sort of compression tool like a Merkle tree, for example, and that means that no one can run a light client, which means no one can validate the rollup that they're on, which means they're kind of just trusting the operators of that rollup without being able to do it themselves.
And you're saying a modular execution layer has solved this problem by producing a more abstracted layer 2, a more abstracted abstraction layer between the Ethereum layer 1 or any layer 1 and the Fuel layer 2? Is that a fair conclusion? Check me where I got wrong here. Pretty fair, except the last part. I wouldn't say it has more abstractions. I would say it just has more features. Okay. Okay. More features. Everything up to that last part is good. Pretty much, yeah. It's not a bad analogy, yeah. But yeah, so that's kind of where the modular execution layer comes in. It's that we're really pushing for a system that isn't just a roll-up, and it's not just a bridge, but rather has all those features that users expect out of a blockchain today that allows trust-minimized infrastructure.
so now it seems to be following the same trajectory of just like modularity in general right so the ethereum layer one is becoming modular and i think maybe the generalized critique is that like something like optimism or arbitrum or like a roll-up as we know it is like a monolithic version of a layer two and you're trying to make a more modular version of a layer two is that also fair you can say that yes uh that's actually not a bad way of putting it in the sense that uh traditional roll-ups now they're moving towards being modular execution layers following fuels lead uh but like more these traditional roll-ups that you know su everything except for the two-way bridge you could that is not a bad analogy to think of them as more like a monolithic modular execution execution system whereas like they kind of tightly couple themselves to a very specific layer one and they say we must operate in this exact one one we must operate in this stack and nothing else okay so what kind of flexibility does fuel uh gain by this design choice by this design philosophy uh so it gains well one gains security for end users and two against flexibility so so just so just so we're clear it's not just flexibility it's also security we cover the security just just prior so in terms of flexibility uh it allows fuel to be run or deployed rather uh to those last constraints on which layer ones it can use for data availability and settlement right if you don't tightly couple yourself to a very specific stack you know this is layer one this is a roll-up if you don't tightly couple yourself then that means you're more opportunity to go in different ecosystems right so the fuel layer two can settle both its data both on ethereum and celestia and another layer one if you wanted to yes okay that's kind of what i meant about like abstraction like as in like we could extract away which data layer uh really is important to fuel so there's no there's no like layer one or data layer that fuel really calls home let's look at that again and i think a lot of large parts of our node just refer to the data layer as like da layer as opposed to ethereum right if you look at some other chains they'll call this specifically thing ethereum or they'll call it evm right in our case we've tried very hard to abstract that away not out of necessarily any ideological like concerns about ethereum which there are none but more about the more you tie yourself to any specific thing the more like weird code that you might inherit without even intending it right it prevents you from necessary it prevents you or rather it makes it harder to ensure that your code is clean and free from like weird legacy stuff sure and importantly it's that light client merkle tree aspect that we were talking about that enables this property, right?
It is the compression of all the data into like a little nice, neat bundle of data that allows for that data to be able to go onto any data availability layer. Is that correct? No, that's orthogonal. Those are two different parts. Like the fact that you can, the fact that, you know, you have the ability to run a trust. That's not the only property that, you know, there's a difference between Thunderbolt and USB analogy here, right? There's additional properties. That's a major one that I talk about because of security. But those other ones, like just building your software in a modular way, abstracting away what is the data layer and what can it actually provide, that's another property.
Okay. One of the big new things about Fuel is the Fuel VM, which is a meaningful separation from the Ethereum virtual machine, which so many roll-ups, Arbitrum again, Arbitrum, Optimism, just emulate. They recreate the EVM as close to close to the EVM as possible. This is not Fuel's design choice. So talk about the philosophy behind this design choice and kind of how it fits into the overall broader Fuel stack. Yeah, sure. So now we're getting to the fastest part. Yes, cool. And similarly to how the module execution layer has both a security component and a flexibility component, as does the fastest part, it has the fastest part, and it also has a flexibility part.
So in terms of performance period, the Fuel EVM is designed based on the EVM, actually. So if you're familiar with the contract execution semantics of the Ethereum virtual machine and some of the nuances and gouches there, you can learn how the FuelVM works in like an hour. It's very simple because it's basically the EVM, but improved is what I like to call it. It has a number of architectural changes that aren't too important, I think, to dive into. Things like it uses registers instead of a stack, which leads to higher performance and higher performance both in terms of register like a register machine like a program on a register machine being executed is faster than on a stack machine and also because it reduces gas accounting overhead uh but that's kind of like that's kind of getting a bit too much into the weeds uh the kind of interesting things that the fuel vm brings to the table in terms of performance is the fact that it can introduce new instructions that wouldn't really be introducible into the EVM without a lot of bike shedding.
Along with all the architectural changes that will emulate certain EIPs on Ethereum or that implement them in spirit. So I'll give it a few examples. One of them is memory copy, right? People would really like to have a memory copy instruction because it would just make certain operations much, much cheaper, especially custom cryptography. the current approach is you can delegate call into the identity pre-compile or sorry not delegate call i guess static call you can call into the identity pre-compile and then you know copy your data and then get it returned and then okay you have your memory copy that's fairly expensive because you know you have to call a pre-compile versus just an instruction uh and people wish that for things like custom cryptography they had a memory copy instruction why can't you implement The answer is, well, because the EIP process is very involved.
There's a lot of governance complexity in the Ethereum space because, you know, you don't want to just accept every single EIP that people propose because then the EVM would get very bloated and be impossible to maintain. And as we all know, public goods funding on clients is kind of fairly limited, which makes me somewhat happy that the Paradigm team is now choosing to maintain a Rust EVM implementation. Because now at least we can be pretty guaranteed that at least we'll have one thing in this high performance. That is also Rust, which is nice. That is maintained. And we don't have to worry about public goods funding as much.
But regardless, back to the topic at hand. So, you know, in the FuelVM, we have a memory copy. Boom. End of story. It allows you to cheaply copy a memory from one place to another. Hello, custom cryptography. Another example is transient stores. Sorry, can you... So that was like pretty technical. And for a non-technical person like me, can you just like really distill down the impact of that maybe for developers and for users, if it does impact them? It will impact people who want to build custom cryptography in the EVM and it'll impact people who want to use custom or use cryptographic primitives that aren't natively supported by the VM.
So in the EVM, you have access to, let's say, a signature verification for Ethereum's curve, but you can't really verify signatures for other curves uh one popular curve or one popular signature scheme is eddsa as opposed to ethereum's ecdsa and eddsa is used by near it's used by solana it's used by cosmos it's used by a bunch of chains but they shouldn't be using it because it's garbage but regardless they use it uh people would like to for instance construct a bridge like a i think what they have a rainbow bridge or something right they'd like to construct a bridge but to verify each eddsa signature with custom cryptography implemented in the evm is on the order of 1 million gas versus 3 000 gas for an ecdsa signature verification like that disparity is on the order of you know three orders of magnitude difference that should not be the case like maybe we're talking about a factor of two three i don't know something like that difference is what it should be not three orders of magnitude difference so and if the fuel vm people will be able to and hash cloak is actually writing.
I think they wrote a BLS signature verification in Sway, which we'll get to Sway later, but they wrote it for the field game. So you'll be able to write custom cryptography, different hashing algorithms, different signature schemes, so that you can do things like bridging to other chains and whatnot. And you can do that reasonably economically. Okay. And so that's all about just like having one transaction or all transactions on fuel just overall have like a smaller footprint on whatever data layer that it settles down to which is where we get this like fastest claim right uh among other things yes okay all right so tell us about like the uh the current state of the fuel network like uh when did it get started uh what are you guys working on right now where is there a roadmap and where are we in that roadmap Yeah, so I was about to talk about more parts about the fastest, but okay, we'll talk about this.
Oh, if we're not done talking about the fastest parts, we should absolutely talk about the fastest parts. Sure, I have a few more to add. Okay, yeah, where's next in the fastest, yeah. Okay, so there's a few other EIPs that have been implemented. One of them is transient storage. Some people from Uniswap have been pushing T-Store and T-Load, which are effectively... let's see how i can distill this uh so storage on ethereum allows you to persist things across transactions right uh and memory persists only within a particular call so if i call the uniswap contract right it has some memory and that persists only within this call uh so you have two options you either persist things across transactions or you persist things only within a call what happens if the uniswap contract calls i don't know the die contract right then the die contract doesn't have access to the memory of the uniswap contract but it'd be really nice if we had access to some some memory or some storage whatever you're going to call it that persisted across the transaction so across calls in a single transaction and that was discarded at the end so it couldn't be used across transactions but it could be used across calls that's what t store and t load are uh there's an eap for this uh and it allows you to do nice things one thing it allows you to do is it allows you to check for re-entrancy at runtime without having to use storage which is very expensive uh then you can use t-storage uh all the things you can do i mean i don't know there's a bunch of things you can do with this uh so the fuel vm has a shared memory architecture where memory is persisted across calls like this like you can go into like more like deep dive into the technicals but the essence is that it has memory that is some storage location that is persisted across calls so it already has whatever t-store would give you So you could wait whatever amount of time this EIP can wait for while it's in the back burner to be implemented, or you can just build on fuel.
And so this is part of potentially the flexibility that I was talking about. The fastest is both performance but also flexibility. In terms of performance, it might also be worth talking about the fuel protocol itself, because the fuel protocol isn't just a fuel VM. the fuel protocol is designed to run multiple instances of the vm in parallel because each transaction in the fuel system declares which contracts it will touch if you know which contracts two transactions will touch and they touch like this joint sets of contracts you can execute them in parallel because there's no like hard dependency between these two transactions so this allows us to execute transactions and therefore instances of the virtual machine in parallel and that's kind of the overarching fuel protocol so it's not just like you know a single vm that runs transactions one at a time it's more like an orchestrator that runs multiple instances of the vm in parallel and leveraging parallel transaction execution is also where we get a lot of performance gains because modern cpus haven't really increased their single core speed in like the past like 15 20 years or something like that right i remember when i was a kid i was playing Half-Life 2 on a single-core Pentium 4, and I was running at like, I don't know, 4.
2 gigahertz or something like that. I'm sure a lot of people had a Pentium 4 back in the day if you're my age. And that was like the fastest single-core processor at the time. This was like right on the cusp of, you know, dual-core processors starting to become a thing. And nowadays I have, on my desktop, my processor is what, like 4.8 gigahertz boost, right? So that's not even that much faster than 4.2 right and that was like that was like 20 20 years later uh oh geez i'm old so uh but what have processors done well my my processor has you know 30 i forget it was 32 or 64 it has a shitload of threads right and the old pentium 4 had one thread so you know that is you know almost two orders of magnitude more performance that is unused in a single core vm so with parallel transaction execution then this kind of uh unlocks the just using resources that are sitting there not being used like it doesn't require a more expensive machine it's just those resources are regardless of what cpu you buy nowadays it's going to be multi-core and it's going to have like at least a minimum of a threads unless you go really cheap and buy like you know an intel atom processor or something it's going to have at least you know a threads so you know those resources are unused currently in a single threaded vms might as well use them So the first thing that you said is that the fuel network, you have a transaction that calls two different contracts, and we can have this.
Instead of having to call memory twice, there's only, like, one persistent memory. I'm going to mess up the way that that's described, but, like, it's just, like, it sounded like just a more efficient way of accessing memory in the fuel network across contract calls. which again limited developer experience but it really just sounded like there was just less resource load per transaction in order to get a transaction done. That's a good way of putting it. One thing we like to say is that we reduce waste. It turns out that a lot of ways people want to use the EVM have to use the EVM wastefully.
It's not necessarily even that the EVM must be inherently slow and you must completely change the architecture because we didn't. The FuelVM is based on the EVM. It's that it turns out people want to use the EVM in certain ways, and the EVM doesn't have a good way of doing certain things. Therefore, people use wasteful ways of doing those things. They use workarounds, which ultimately become wasteful in terms of computational resources. Exactly. And we just provide efficient ways of doing those things. The Layer 2 era is upon us. Ethereum's Layer 2 ecosystem is growing every day, and we need Layer 2 bridges to be fast and efficient in order to live a Layer 2 life.
Across is the fastest, cheapest, and most secure cross-chain bridge. With Across, you don't have to worry about high fees or long wait times. Assets are bridged and available for use almost instantaneously. Across's bridges are powered by UMA's optimistic Oracle to securely transfer tokens between Layer 2s and Ethereum. Across's critical ecosystem infrastructure and Across v2 has just launched. Their new version focuses on higher capital efficiency, Layer 2 to Layer 2 transfers, and a brand new chain with Polygon, all while prioritizing high security and low fees. You can be a part of Across' story by joining their Discord and using Across for all of your Layer 2 transferring needs.
So go to Across.to to quickly and securely bridge your assets between Ethereum, Optimism, Polygon, Arbitrum, or Boba networks. The Brave Wallet is your secure, multi-chain on-ramp into Web3, and it's built directly into the Brave Privacy Browser. Gone are the days of managing multiple wallet extensions that put you at risk of phishing, spoofs, and tracking. With the Brave Wallet, you can securely manage your crypto assets across more than 100 different chains, including Ethereum, Layer 2s, Solana, and more, all without downloading risky extensions. The Brave Wallet is easy to set up and removes the headache of jumping between wallets and extensions.
It's lightweight but packed with great features, like built-in token swaps, buying and holding NFTs with a gallery view, and support for hardware wallets. But also much more than that, because Brave is shipping new features every single month, with a mission to make Web3 easier to navigate for its over 55 million users. Wallet extensions are a thing of the past. So get started with Brave's Web3 ready browser today and experience a decentralized web seamlessly without all the clutter. You can download the browser at brave.com slash bankless and click the wallet icon to get started. Arbitrum One is pioneering the world of secure Ethereum scalability and is continuing to accelerate the Web3 landscape.
Hundreds of projects have already deployed on Arbitrum One, producing flourishing DeFi and NFT ecosystems. With the recent addition of Arbitrum Nova, gaming and social dApps like Reddit are also now calling Arbitrum home. Both Arbitrum One and Nova leverage the security and decentralization of Ethereum and provide a builder experience that's intuitive, familiar, and fully EVM compatible. On Arbitrum, both builders and users will experience faster transaction speeds with significantly lower gas fees. With Arbitrum's recent migration to Arbitrum Nitro, it's also now 10 times faster than before.
Visit Arbitrum.io where you can join the community, dive into the developer docs, bridge your assets, and start building your first dApp. With Arbitrum, experience Web3 development the way it was meant to be, secure, fast, cheap, and friction-free. So there's something that you said in the very beginning of this, where it was like something about the relationship between the fuel stack, the fuel technology, and a full node. And it was like the fuel allows you to leverage the full resources of a full node in a way that's not very wasteful. And this is kind of the theme that I'm gathering here, is that a transaction on Fuel is minimalist in that it only uses the minimum amount of computational resources it requires to get itself executed.
And then also on top of that, you're adding multi-core, multi-threading with the Fuel VM. Is that kind of a simple way to explain what Fuel is? Yeah, that is it. It's not like anything magical, like, oh, we used to be engineers at Qualcomm and we know how to build kernels and shit on routers. This is like very simple, just reduce waste, reduce waste in terms of, you know, make transactions. You can make transactions execute faster by making them waste less. Right. You don't need like, you know, magical reengineering of anything, of hardware or anything like that. You just say, you know, waste, waste less.
And now, boom, your transaction's faster. Is there any, are there any numbers that you can put behind this? Like how many more times faster is fuel than like your typical optimistic rollup? That is hard to say without optimizations. in the sense that there's a design aspect to it, like the design of the protocol, and then there's an implementation aspect. And the implementation obviously requires optimization work that is independent of the fundamental design of the protocol. Our implementation is currently undergoing, the VM implementation is currently going optimization work. As we speak, it's been ongoing for the past month or so.
That has greatly reduced overheads. I think like on the order of 10x just off of optimization work. But until those optimizations are complete, then it doesn't really make sense to give any numbers because if the overhead is so high because it hasn't been optimized out yet, then there's not really any comparison to make. What you really should be comparing against is an optimized VLVM versus an optimized EVM. That is still a little ways away, but it'll be ready in the not too distant future. Okay. Is there some sort of like, What number are you going for, if that's fair? What number do you want to see?
Well, I mean, hopefully 100x on the same computer. 100x faster than a typical optimistic roll-up? Yes. Okay. So I know Arbitrum likes to do an add-on. Add another zero? They like to just say, I think the last number we got out of Arbitrum is that we are seven times faster than Ethereum. So Arbitrum has seven Ethereums worth of scale. I know that that measurement has offended other Layer 2s, but if you wanted to tell a normie like me, how much more scale does it have? That's a nice thing to say. So does it go and say that, okay, then fuel is 700 Ethereums? I don't know the zero. I don't know the zero.
No, I mean, I don't know the zero to the 7x. So I don't know. Something along those lines. Okay. Well, that's certainly a big number. Have we covered all the fast part of Fuel? Yes. I think we're ready to move on to your previous question about roadmaps. Maybe we could repeat it in brief. Yeah. So when did the Fuel project really get started? What is the roadmap and where are we on that roadmap? Depends what even my Fuel project. I guess I can talk about the origins of Fuel. Sure. Which is that I think it was in 2019. Yeah, I think it was in 2019 when I left ConsenSys. to start it up with Nick, and then Sam joined shortly thereafter, very shortly thereafter.
It was basically the three of us in a cave with a box of scraps subsisting off of a single small grant from the Ethereum Foundation, and we launched Fuel V1. Was it at the end of 2020? No, that seems too long. Okay, maybe we started this in 2020. The years are all fuzzy. I think we started in 2020. We launched Fuel V1 at the end of 2020. And Fuel V1 was just for payments. It was the first and currently only real optimistic roll-up. In other words, ones with A, fraud-proof, B, permissionless block production, C, posting data onto Ethereum, and D, no upgradability that exists on Ethereum today.
And it was the first optimistic roll-up, regardless of true optimistic roll-up or not, that was deployed to main end Ethereum. Right at the end of the year, December 31st. Just so we can say we deployed it in that year. a whole year before any other role. And that wasn't the end game. It was just for simple payments, but it wasn't the end game. We knew from the beginning that we wanted to build a system that allowed Ethereum to scale, not just in payments, but that allowed Ethereum itself to scale. And that meant general-purpose smart contract execution. And towards the end of that year, we had actually started working on what would become FuelB2.
We started thinking about the VM architecture. We started thinking about the language. And here's maybe some fun piece of history. We had actually talked to some people about if we had a VM interpreter in Rust that we can compile down to Wasm, if we could use an interactive verification game over the implementation rather than the protocol itself. And this turns out, we had chatted with some researchers about this, And it turns out that that's the exact approach that both Arbitrum and Optimism ended up unveiling as nice innovations in the future. What a good coincidence. So we ended up not going down that approach for various reasons, one of which is that you're tying yourself to a particular implementation.
And any weird bugs that that implementation may have, any weird inconsistencies, it also makes it harder to maintain. and one thing that's very important with these systems and this will come into play of why we built sway is that building and maintaining are not the same thing uh you can sure build a system very quickly if you you know take some general purpose thing and run it over the implementation of your vm interpreter but then how do you maintain it right then do they have to like maintain two different instances of your vm interpreter one that's you know that you can run quickly and one that you can run the IVG over.
It gets very tricky on how maintenance is done. So this also leads us to our language, right? We had also been thinking about what to do with our language. We looked into Move. We were thinking also of using the Move VM. But the Move VM is not designed to be fast. And it's not designed to be flexible. It's designed for a very particular and a very different way of reasoning about assets. And the Move language was also very immature at the time. And I'll tell you in the past two years or so since we looked at Move, I think this was at the very end of 2020. Yeah, at the very end of 2020, the language really hasn't changed that much.
Like Sway has grown from literally nothing because it was created from scratch to the most mature blockchain development language in existence, if I do say saw myself uh from nothing and sway or sorry and move has basically not changed at all in the past two years uh so it's good there's a good choice not to use it uh so in addition to you know it being immature and it following a weird different paradigm one of the reasons not to use it is that it would be an upstream dependency uh for anyone who's worked in an open source code base uh it's really nice to use if your upstream dependencies are maintained right if they're maintain then you can use them if there's a bug you ask the maintainer hey can you fix this release new version and all's good the problem is when it's not maintained then you have a choice you can either fork it yourself and maintain it yourself so now you're maintaining some code that you didn't write it's not in your style it doesn't have the same conventions uh you i mean do you completely change the style to to your conventions right and completely change how they do things to work with your conventions at that point it's like can anyone else even use it or you're solo maintaining it and if it's like a big thing uh that could be very that transition could be very expensive and it could happen at a very inopportune time so when it comes to building sure taking on a uh upstream dependency is nice and easy it makes things fast to build but again it's not just about the building it's about the maintaining and having an upstream dependency like that especially something that's like you know some software from facebook then libra then dm now it's it's like move is being forked to like different aptos is their flavor of move so has the flavor of move.
It's like, who even owns, like, is there even a single maintainer with a core move language? I don't even know at this point, right? And having an upstream dependency of that is really, really bad for maintaining your code. So we chose to build Sway instead, right, from scratch. I feel like before I talk about Sway, is it maybe good to go back to the roadmap question? I think Sway and also the fork conversation are similar. Should we also talk about fork uh sure okay i can i can also let you lead if you have a direction you want to go oh well i i was going to finish kind of at talking i was going to finish talking about you know the timeline and roadmap thing as opposed to just diving into more tactical stuff cool uh because this was more like a history lesson of you know how we got to where we are right we launched vlv1 we started thinking about vlv2 and these were some of the things we were thinking about great uh like move and then ivg and all the other stuff we ended up maybe basically building the whole thing from scratch to avoid upstream dependencies and other issues of that.
Since then, we've been building for the past two years. The organization has grown from zero contributors other than the founders. I think we made our first hire in January, end of January, something like that. Sorry? Of this year? No, of 2020. 2020, okay. No, 2021, sorry. Okay. We launched Fuel V1 at the end of 2020, and then we started building Fuel V2 in earnest 2021, January, up until now. So the past two years. Dates are hard. So, you know, we made our first hire. We've since grown to, I think, almost 70 contributors in the organization from now on, back in the beginning of 2021. So I think we've done a pretty good job building out one of the best teams in crypto.
Well, for sure, the best compiler team. and just one of the best teams, period, across our whole stack in crypto. Mostly engineers, believe it or not. Like 60 of those people are engineers. We really do need to hire more non-engineers. So if you are out there and you're a non-engineer, if you're into BD or if you're into public communication and content writing, if you're into project management or anything like that, please reach out to me after this because we always need more of those. uh so yeah and then since then we've basically been building we launched a oh sorry for the first year we built uh in stealth mode uh and then on january 2nd 2022 so this year so about 12 12 months or 11 months ago now to the date actually oh it's december 2nd so 11 months ago then we released all of our code base in public uh since then we've actually been building in public and there's an important distinction between us and potentially some other projects.
So not only is our code all open source, our entire stack, except for a couple of minor components, but those will change soon. We're also, we also build in public, right? Some other, some other projects roll up or not. We'll for instance, build entirely in private and they'll like release some blob at the end. That's not even open source. Right. Or sure. It's open source, but they don't actually build in public. They'll like, push things out you know push things out just you know boom here's something we were working on this for the past year now you know about it uh at fuel labs everything we build for the fuel protocol is built in public and it's also planned in public we don't have like a private issue tracker that people can't see like you can go on our github you can communicate with people through issues through prs and stuff and that's how we do our work so it's very part a big part of ethos uh it's not just about you know the software and the blockchain it's also about how it built because people are a very important part of our culture.
So yeah, so we made all the code public at the beginning of this year. Since then we've launched three testnets. One of them was for SwaySwap, a port of Uniswap, the hybrid of Uniswap v1 and v2, ported to the Sway language, deployed to a private devnet. Then we launched two public testnets, beta 1 and beta 2, each of these about about two months apart, that had just increasing number of features and increasing sophistication and stability and so on. I think we are gearing up for a beta 3 testnet sometime early next year, let's say. That's kind of it for the spoiler. So there'll be a few more testnets.
We're rapidly approaching a mainnet launch. What form that'll take, we'll leave to future announcements. But yeah, that's effectively how things have gone in terms of development for the past three years. So how will an ecosystem come to be on fuel? What's the idea behind that? Because if I'm understanding this correctly, you can't just copy and paste Uniswap code and deploy it to fuel. That's why you're talking about with some sort of iterated code to make it work on the fuel network. How do you expect an ecosystem to come to be on fuel? How do you expect that story to go? yeah uh it's not just how i expect an ecosystem to come it's i can describe how an ecosystem came the fuel uh we already have a burgeoning ecosystem of uh very uh excited developers that are really engaged into the project uh and the language and just in a general ecosystem uh that have you know basically they've taken a look at sway they're taking a look at the fuel vm and they're like wow there's so much better than any other chain i can get even today and there's the early days with rough edges imagine like a year from now when we've polished all those rough edges even more it's going to be insane and we already have like you know a dozen or so projects that are building on us on testnet uh we hosted a twitter space with one of them pool shark uh last night on the sway you can look at the sway lang twitter uh and it has a space from just just last night uh just last night if you're in eastern time i guess if you're in different time zones then It's not night and maybe not yesterday.
But, you know, they're building an AMM that's concentrated liquidity, liquidity, if I recall correctly. Right. We have a few other ones like an NFT marketplace and some other stuff that are being built today. So this isn't like we have to attract developers out of nowhere. It's like we already have an ecosystem of developers being built that are already here. And there's only going to continue to grow. Of course, yeah. Do you have any stats on users or daily transaction volume or any stats of adoption like that? That is something I don't have off the top of my head. I'll have to talk to our growth lead on this.
I'm sure she has a whole bunch of numbers and stuff, but that's not my area of expertise. I just do protocol design. Would data like that be something available in something like Dune Analytics, or does the fact that it's a Fuel VM make finding data on Fuel a little bit harder because it's not as easily plug-and-playable as other rollups? Yeah, it's not currently as plug-and-playable, so it wouldn't appear in Dune. That being said, it's all on-chain, and the testnets are public. Beta 2 is a public testnet. It has an open GraphQL endpoint that anyone can query. I should also point out that it's not just the fundamental protocol that has been improved over the EVM.
We also made improvements to things. We have a native GraphQL interface, so you don't have to use a third-party service like the Graph to index things and then expose a GraphQL endpoint if you're like doing or whatever, right? We also have a first-party indexer service. So if you want to build an application and then run various indexing on that, things like pools over time and user accounts over time and all this other stuff, we actually have a first-party indexing service that you can plug into our node. You don't have to use a third-party like the graph, wait for integrations, wait for all that governance and all that stuff.
you can just use our indexer boom it just works that's all like a single unified tool chain and you can get all your next thing done that you can then plug into analytics analytics websites you know of course it's not currently plug and play into dune but you know eventually why not uh there's no reason that it can't happen or there's no reason you can't just run some graphql queries against the node on yourself because again the beta 2 network is public and like you can just you can just the blockchain it's all on chain as they say right you just square of the time do you have like a attitude or philosophy as like is do you where do you think the whole entire broad landscape of ethereum layer twos is going because each layer two has its own kind of directional philosophy optimism is really focused on like their bedrock and op op stack zk sync wants to do its prover circuit with a bunch of layer threes do you have any sort of like belief as to like where the broad landscape of all ethereum layer twos will go and and i'm assuming like you think that uh fuel is kind of leading in a particular direction that you think is uh the right direction but do you have any any takes about like where uh the logical conclusion of a theorem layer twos go so i think there's two facets to that question one of them is potentially where do i think it's going to go in the short term and the second is where i think it's going to go in the long term sure so i'm pretty convinced in the short term that we're going to see two things happening the first one is convergence around the evm as a focal point as it exists today uh other than you know fuel of course uh so this this will look like what we see today we have a bunch of uh blockchains going for a bunch of roll-ups going from you know i guess we're evm compatible to okay now we're evm equivalent right uh and then they're all gonna deploy their solutions that are quote unquote evm avm equivalent uh but then the next step to this and this is still like the short term is people will want more they'll want more flexibility they'll want more speed they'll want more something right uh and we can see this already you know you have projects that talk about oh why don't we add account abstraction why don't we add native support for t-store right hey you know i'm on i don't know the roll up xyz you know let's implement t-store and get people who have been excited about it all this time to use us and people want more uh and you're going to end up i think in a weird scenario where uh well that's the long-term thing we're going to talk a weird scenario in the long-term thing okay so in terms of you know people want more people want improvements to both evm and infrastructure like rpc endpoints and stuff they'll want parallel transaction execution in a way that isn't a denial of service vector because some people are saying, hey, let's apply a parallel transaction execution to the EVM with concurrency.
That's a denial of service vector. Or rather, well, it's a denial of service vector or it does nothing, which is always the rock in the hard place. It either does nothing or it's a denial of service vector in the worst case. It is adversarial. and our Ethereum team is using this approach which is why I think they're using the wrong approach of course. Fuel is not using optimistic concurrency it's using enforced parallelism in the transactions themselves and therefore it's part of the actual consensus of the chain, it's part of the rules that there is going to be an opportunity for parallelism and then you can enforce certain payments and stuff around this if someone makes a bunch of transactions that are all targeting the same state they should pay more and so on right but you can do this as part of consensus because it's actually part of the transaction it's not just some implementation detail like concurrency is uh so what i think is going to happen uh is that you know people want more and guess what in that wanting more that is fuel right fuel is years ahead plural of any other chain in terms of building some the next step of the epm in terms of implementing these eips like t-store in terms of account abstraction, in terms of EIP-3074 for authenticated calling, in terms of flexible transactions with scripts.
All of these things, Fuel has from the beginning, right? So when people start looking for more, well, guess what? Fuel has been there for years, right? And we're years ahead of anyone else. So there's going to be no competition. There is no second best, as someone would say. So you're just saying that Fuel is the philosophy of skating to where the puck is going? Yes. Cool. and that falls into what i foresee is what's going to be some long-term consequences of this evm convergence which is that as people want more we have now crossroads it's either people are going to people are going to accept that they can't get more uh which is not good like i really wouldn't like that eventuality or people are going to say hey let's use fuel because fuel has has it has everything we want it has all the more we want and it's already implemented we don't have to wait years, right?
Has better language, better tooling, better VM, better everything. Why wait when we can just use Fuel? That's, I think, the ideal scenario, both for Fuel and myself personally, and also for the Ethereum ecosystem, I think. Because there's a third scenario, which I think is really bad, which is that each of these rollups, which, you know, a lot of them have certain financial interests and political interests, are going to start pushing through Ethereum governance changes to the EVM that benefit them. And if they don't get those changes, then they're going to start fragmenting. What is the EVM, right?
Imagine if Arbitrum and Optimism have two different ideals around some feature of Ethereum, right? Like Arbitrum really wants feature X, Optimism doesn't like feature X and thinks it should be feature Y. and an example of this is actually you know ethereum itself the evm like base layer ethereum had such a thing happen where there were two competing proposals which ironically weren't actually competing necessarily but there were two competing proposals for how to implement bls signature verification in the evm which i don't actually know why it was needed ultimately because you don't actually apparently you don't need it for withdrawals people are saying you needed it to enable withdrawals but then it didn't happen and it turns out you don't need it for withdrawals so I don't even know why it was needed.
But regardless, I think the reasoning at the time was to enable withdrawals, which we know. Even that's pretty important, right? And that's still taking a while. So there were two proposals. One of them was implement BLS precompiles. The other one was implement basic precompiles for general cryptography that people could then use to specialize at the application layer instead of at the consensus layer for BLS specifically. right uh now the bls specific ones you know maybe they're faster and cheaper but then they required you know you specifically need to know about bls the other one is more general right but it could be more expensive uh and there's like a bunch of fierce competition and governance around which one of these two should be accepted of course neither of them ended up being accepted but you know when you have a situation like this imagine if you have two roll-ups and each of them think you know one of these is better what the fuck happens to governance then especially when these roll-ups are when they say they're even equivalent like do they just stop improving their chain and fuck their users and send them all the fuel i mean i would like that right and i thought i i think that may be the ideal scenario for ethereum because then it avoids this this disaster scenario of all these roll-ups now competing with each other for ethereum governance they're not competing with each other for users they're competing each other over ethereum governance and having a war through ethereum governance for which features get implemented in the evm because they have to stay EVM equivalent.
And if they don't, then potentially an even worse scenario happens where now each of these rollups branches off and has their own flavor of EVM and fuck EVM equivalents. And then they call themselves the EVM. And it's like, well, what do you do with the Solidity compiler? Do they each have a different version of the Solidity compiler that can be used for their flavor of the EVM? Like then how do tools work and stuff, right? Like both of these scenarios are really, really horrific. And that's what I foresee post-EVM convergence, that people will want more and this more will lead to what I hope is the ideal case that people will realize fuel is that more and it is bringing scalability to Ethereum and bringing improvements to Ethereum with all the security guarantees and trustlessness and decentralization ethos and open building ethos that Ethereum really values and they'll go to fuel.
Because if not, then it's looking very grim in terms of what are the long-term consequences of roll-up teams fighting on the Ethereum governance arena for their own purposes. well john this is why i love these conversations because uh it's only developers that can actually think in these such long-term time horizon like game theory scenarios uh so uh that's definitely something that i now have to consider so so thank you for for sharing that uh well now maybe you won't sleep as well at night well there's i've never been bearish on ethereum actually being able to problem solve. But yeah, the problems do only seem to get larger and larger as we go out into the future.
If you had a call to action for listeners, developers, whoever might be listening to this episode, to help join the effort to make Fuel a success, what would you ask? I would ask that you keep an open mind and try it. You don't have to take my word for anything, but you also shouldn't take anyone else's word. Don't believe what you hear on Twitter necessarily, and don't believe anything you hear out of my mouth. What you should believe in is the code. go look on our website go look at our docs uh go play around with our tooling and our chain uh and see for yourself that there is no second best and where are all of the links to go get that done yeah so if you want to uh i mean the main portal to everything is just fuel.
network the website fuel.network uh you can also look us up on github directly like github.com fuel labs you can follow us on twitter which is at fuel labs underscore potentially potentially that might be changing soon soon alpha alpha leak uh but yeah that's kind of where you can go to kind of get started on socials and just code and stuff awesome well john thank you so much for joining me on this alpha leak episode uh speaking of alpha leaks uh and explaining to me the fuel ecosystem i appreciate it thanks so much for having me david and the bankless nation hey we hope you enjoyed the video.
If you did, head over to Bankless HQ right now to develop your crypto investing skills and learn how to free yourself from banks and gain your financial independence. We recommend joining our daily newsletter, podcast, and community as a Bankless Premium subscriber to get the most out of your Bankless experience. You'll get access to our market analysis, our alpha leaks, and exclusive content, and even the Bankless token for airdrops, raffles, and unlocks. If you're interested in crypto, the Bankless community is where you want to be. Click the link in the description to become a Bankless Premium subscriber today.
Also, don't forget to subscribe to the channel for in-depth interviews with industry leaders, ask me anythings, and weekly roll-ups where we summarize the week in crypto and other fantastic content. Thanks everyone for watching and being on the journey as we build out the Bankless Nation.