Alex Gluchowski is the Co-founder and CEO of Matter Labs and the creator of zkSync. Anthony Rose is the head of engineering at Matter Labs and has a background in software and machine learning. Prior to joining Matter Labs, Anthony spent a number of years in the industry building teams at SpaceX.
In today’s episode, the four talk about zkSync’s massive announcement, they’ve launched their zkEVM to mainnet! They also delve into the engineering challenges, what zk unlocks, the difference between zkEVM vs Optimistic Rollups, what builders need to know, and of course…wen token?!
------ 📣 Infura | New SDK for NFT APIs For Devs https://bankless.cc/Infura
------ 🚀 JOIN BANKLESS PREMIUM: https://www.bankless.com/dashboard
------ BANKLESS SPONSOR TOOLS:
⚖️ ARBITRUM | SCALING ETHEREUM https://bankless.cc/Arbitrum
🐙KRAKEN | MOST-TRUSTED CRYPTO EXCHANGE https://bankless.cc/kraken
🦄UNISWAP | ON-CHAIN MARKETPLACE https://bankless.cc/uniswap
👻 PHANTOM | FRIENDLY MULTICHAIN WALLET https://bankless.cc/phantom-waitlist
🦊METAMASK LEARN | HELPFUL WEB3 RESOURCE https://bankless.cc/MetaMask
🚁 EARNIFI | CLAIM YOUR UNCLAIMED AIRDROPS https://bankless.cc/earnifi
------ Timestamps
0:00 Intro 8:15 zkSync’s Era Mainnet Launch 8:53 The Importance of zkSync Era 9:53 zkSync Era 13:53 Staged Roll-Out 18:50 zkSync Era Projects 21:14 Engineering Challenges 26:25 What Does zk Unlock? 28:16 zkEVMd vs Optimistic Rollups 36:35 How Low Can Gas Fees Go? 39:22 The Power of zkEVMs 48:58 How is zkSync Era Different? 53:08 New Risks to Pay Attention to 55:35 Path to Decentralization & Security 1:03:42 What Do Builders Need to Know? 1:05:36 Resources 1:07:12 Token?! 1:08:20 Closing & Disclaimers
------ Resources:
zkSync Website https://zksync.io/
Alex Gluchowski https://twitter.com/gluk64
Anthony Rose https://twitter.com/anthonykrose
------ 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.
If we want to build a truly limitless internet of value, internet of throw ups, it has to be trustless. So all the bridges must be ZK and that means that all the chains participating in this network have to be ZK chains. This is our vision for hyperscalability. The ZK EVM is here. It's on mainnet. David, we've got the episode announcement just went out as we are pressing publish on this episode. What are we talking about today? We are talking about ZK sync era. The mainnet is live. As of right now, we got the two people from the ZK sync team. We got Alex Lukowski who's been with ZK sync since forever, co-founder and CEO of Matterlabs, the team behind ZK sync.
We also got Anthony. Anthony is the new head of engineering, which is a very ambitious role as it relates to ZK stuff that sounds challenging. We're going to walk through what this announcement is. What does it mean for a ZK EVM to go live? In the era of bank failures, we have a new era for Ethereum. At least that is what the ZK sync is saying along with. There's ZK sync era. Chain. So that is the announcement. We're going to get into all these details and more so you can be informed about what this new frontier Ethereum is. Yes, this is the frontier of the frontiers. And that's where we're headed today.
Hey, David, before we get in, got to do a shout out. This one's for the devs. We got a special announcement for the devs sponsored by our friends over at consensus on the Infura team. David, what do they want folks to know? Yeah, specifically for the NFT devs out there. This is coming down from Infura. So Infura's got an NFT SDK and toolkit for you to build your NFT projects. And so it's got 14 different endpoints that allows you to read data from eight different blockchains. You can aggregate it, analyze it, filter it, build a dashboard. And this SDK allows you to provide you tools to write to five different blockchains.
All of the use cases that you need for your basic NFT stuff, selling NFT, buying NFT, minting NFT, all of this SDK from Infura is to help you the NFT dev build your NFT product. There is a link in the show notes to get started with this if you knew SDK from Infura. That's really cool. Infura, of course, started with Ethereum nodes. Now they're providing a full NFT API SDK for the devs. Go check that out. David, before we get in, we have some disclosures to make. Of course, you can always find all of our disclosures on our disclosure page at bankless.com slash disclosures. Just want to let the bankless audience know we are advisors to ZK sink.
We are friends of the project. We believe in its mission. We believe in scaling if you're in through ZK EVMs. That is not why they're on the podcast today. They are in the podcast today because they built something. They launched something really big. David, what should folks pay attention to going to this episode? This is truly a new frontier. We all know what a roll-up is. We have experienced these roll-ups with Polygon, Arbitram and Optimism. These are a different kind of roll-up. This is a new unlock. Simply put, ZK EVMs, ZK roll-ups have more scale. But if you just think that they are optimistic roll-ups with more scale, you're going to miss the force for the trees.
That is a conversation that we have in this episode. There are specific and unique new use cases that the ZK roll-ups, ZK EVMs, unlock that are not unlocked by optimistic roll-ups. This is a new frontier. There is new trider out here. There are new things to build. There is new optionality for devs to build cool new things that optimistic roll-ups, even though we love them as much as we do, just don't offer. As you are listening to this episode, dear listener, perhaps dev listener, try to identify what those new opportunities lie. We name some specific ones, but really it's up to your imagination.
Right now, many new ZK EVMs are coming online. They are all relatively blank slates of opportunity. We've played this game before. We all remember, maybe not all of us, but I remember a time when Ethereum was just a layer one. Now there's been a bunch of layer two opportunities. Now we can experience that all over again with the ZK EVM revolution, with ZK sync leading the charge. That is my long rant about what listeners should pay attention to in this episode. Here you go, guys. We told you that later, two summer was coming. We've been telling you for two years. It's here. How do we know that?
Because we're shipping a maintenance. That's how you know. Go try this out. Of course, there'll be some risks in the episode. You can listen to that, but this is an opportunity for you to get on board to the ZK EVM platform. Guys, we're going to get right to the episode. But before we do, we want to thank the sponsors that made this possible, including our number one recommended crypto exchange Kraken. Go create an account. Go check them out. There's a link in the show notes. Kraken has been a leader in the crypto industry for the last 12 years dedicated to accelerating the global adoption of crypto.
Kraken puts an emphasis on security, transparency and client support, which is why over nine million clients have come to love Kraken's products. Whether you're a beginner or a pro, the Kraken UX is simple, intuitive and frictionless, making the Kraken app a great place for all to get involved and learn about crypto. For those with experience, the redesigned Kraken Pro app and web experience is completely customizable to your trading needs, integrating key trading features into one seamless interface. Kraken has a 24-7 365 client support team that is globally recognized. Kraken support is available wherever, whenever you need them by phone, chat or email.
And for all of you NFTers out there, the brand new Kraken NFT beta platform gives you the best NFT trading experience possible, rarity rankings, no gas fees and the ability to buy an NFT straight with cash. Does your crypto exchange prioritize its customers the way that Kraken does? And if not, sign up with Kraken at Kraken.com slash bankless. Arbitram 1 is pioneering the world of secure Ethereum scalability and is continuing to accelerate the Web 3 landscape. Hundreds of projects have already deployed on Arbitram 1 producing flourishing, DeFi and NFT ecosystems. With a recent addition of Arbitram Nova, gaming and social apps like Reddit are also now calling Arbitram Home.
Both Arbitram 1 and Nova leverage the security and decentralization of Ethereum and provide a builder experience that's intuitive, familiar and fully EVM compatible. On Arbitram, both builders and users will experience faster transaction speeds with significantly lower gas fees. With Arbitram's recent migration to Arbitram Nitro, it's also now 10 times faster than before. Visit Arbitram.io where you can join the community, dive into the developer docs, bridge your assets and start building your first app. With Arbitram, experience Web 3 development the way it was meant to be. Secure, fast, cheap and friction free.
Learning about crypto is hard. Until now, introducing Metamask Learn, an open educational platform about crypto, Web 3, self-custody, wallet management and all the other topics needed to onboard people into this crazy world of crypto. Metamask Learn is an interactive platform with each lesson offering a simulation for the task at hand giving you actual practical experience for navigating Web 3. The purpose of Metamask Learn is to teach people the basics of self-custody and wallet security in a safe environment. And while Metamask Learn always takes the time to define Web 3 specific vocabulary, it is still a jargon free experience for the crypto curious user.
Friendly, not scary. Metamask Learn is available in 10 languages with more to be added soon and it's meant to cater to a global Web 3 audience. So, are you tired of having to explain crypto concepts to your friends? Go to learn.metamask.io and add Metamask Learn to your guides to get onboarded into the world of Web 3. Bankless Nation, we are here with the Matter Labs team, Matter Labs, the creators of ZK sync. We got Alex Glukowski, the co-founder and CEO of Matter Labs. He has been on the podcast before Alex. Welcome back to the show. Hi, David. Hi, Ryan. Hello, everyone. Pleasure to be here.
And new to Bankless. We have Anthony Rose. Anthony Rose is the head of engineering at Matter Labs and has a background in software and machine learning, interestingly enough, prior to joining Matter Labs. Anthony spent a number of years in the industry building teams at SpaceX, but pretty cool that we snagged him for the crypto world. Anthony, welcome to the show. Thanks a lot. Yeah, very happy to be here. So we always love frontier metaphors here at Bankless and with this announcement that we're going to walk through today, we have discovered a new frontier to explore. Can you guys walk us through the announcement of what you guys are dropping today?
What is the big news? Well, the ZK sync era, our ZKVM solution is now open to the users. Everyone can now start using it. It's a consummation of the launch which took a very long time, but that's also the beginning of a new journey. And that's that. All right. We're wrapped. The network is live. It's here. It's fine. But what does this mean? Alex, kind of walk us through the significance of this. Can you kind of place this into perhaps even like Ethereum's history? Why is this a significant thing, both for Matter Labs and ZK sync and why is this significant for Ethereum at large? I genuinely think it's significant for Ethereum as a large because ZKVMs have been considered the holy grail of scaling Ethereum from the inception of this concept.
It took a very long time. People thought it's going to take much longer. But here we are. And this is really the pivotal point for Ethereum where the real mass adoption with full preservation of all the things that make Ethereum valuable really begins. We will talk about those things, but this is where we. There is by now, I think, a broad consensus that zero-knowledge tag ZKVM and more specifically ZKVMs is this path into the future and it has multiple reasons. And there's also a new name for this network. Can you walk us through this new brand for ZKSync? Yes, we really think it's a new era for humanity where you can fully own yourself, your assets, your identity, all of your transactions.
For us, we started ZKSync four years ago. From day one, there was a mission there. We won't accelerate the mass adoption of crypto. We will love the ideas from Bitcoin. We will love Ethereum. We love those technologies because they open humanity to more freedom, gives you the ability to actually, you know, transact with anyone in the world without barriers, without asking for permission, without banks, without any kind of intermediaries. And it was revolutionary. It's for the first time in history that we have these technologies of global scale cooperation without the trust assumptions. And for me, the question was, how can we bring it to anyone in the world?
What needs to happen to get there? And it was clear that a few things must be changed or must be invented and implemented. We had a long way to improve the UX. People had to build applications. People had to build wallets and only infrastructure on the crypto. But there was this one technical problem of scaling, which seemed impossible from the point of view of technologies that we had four years ago. When I stumbled upon the idea of ZK Proofs, a 600-year-knowledge proofs that are called them Proofs of Computational Integrity or Snarks, it was this aha moment where like, wow, this could be it.
It feels like magic, not clear what it works, but it works and you can really verify any number of transactions with a single lightweight hardware like your cell phone or full-node or Raspberry Pi. And there is no limit. You can do one verification, all the blogs, all the transactions are processed. So you're not breaking out of the blockchain or you are breaking out of the blockchain through Lama. You're not introducing new trust assumptions. You don't have to trust anyone. You still verify everything, but in a trustless way. So the new name is called a ZK sync era. That's what you are launching with and certainly we are living in an interesting era and interesting times.
Dave and I have done so many podcasts this week and I think we will next week and probably the weeks to come about a bank crisis that seems to be going on in the United States and Europe and other parts of the world. We're not sure how far this will spread or what all of the implications are. We're still trying to unpack that as is everyone else. But the root of it is kind of a meta banking crisis that we will probably never be able to resolve in the existing banking system. And that is we cannot verify transactions. We don't know if the dollars in our account are actually backed or what they're backed by.
This is the promise of something like a technology like Ethereum. The reason Ethereum has fallen short on living up to that promise so far is it has been scalable as of yet, although a lot of talented engineers have been working on that, including matter labs. And now here we have a ZK EVM launching on chain on main net and available with the next stage of that promise being fulfilled for Ethereum. And I got to say, well, the world is kind of on fire in various ways crypto is silently building this new scalable infrastructure that we hope and I know you guys hope can onboard the world into this bankless money system.
So congrats and thank you for shipping. This is hugely it's it's a monumental event that we have a ZK EVM in production on main net and you guys have been doing fantastic work in the background to make that happen. One question I have for you is we've talked to many later to you previously on bank lists. Our listeners will be familiar with this. What kind of staged rollout might we see at this point? So when you guys say it's available on main net that's here. What does that mean? What's the user experience? Are there gates? Are there still kind of places that are off limits for now or is this fully enabled, fully permissionless, fully open?
Can you talk about that for a minute? I am happy to talk about that before that I just want to say thank you for for all the good works and I also want to extend this gratitude to the entire community to all the people who work into reading work to the first of all to all the employees of metal labs and only all the people who we worked with to make this happen. And to all the people who contributed to the creation of serenology proofs to the creation of Ethereum Bitcoin like all of these technologies. We're standing on the shoulders of giant giants. It's not an isolated thing. Everything is interconnected and everything is contributing to everyone's selfless work.
So this is really a combination of the work of the entire community. It's not just our tune. So to the user experience and what to expect from the manate. The staged rollout is here. In fact, it started a long time ago. We launched, we deployed the existing manate contract with the address that everyone can see now. And if you look carefully at the address, you might know this interesting thing about it half a year ago. So it was the first moment where we touched the manate as we promised that if see back in summer, we started experimenting with it ourselves internally. We conducted a number of security audits and we bunch of stress tests and a lot of things, lots of experimentation, lots of learnings from from operating the manate.
And we opened it to developers about a month ago. So the builders who registered could deploy their applications. The bridge there, there were whatever tokens they wanted. If or year, see 20 tokens and start building and start experimenting on the test. Was there on the minute? The test is live for over a year and has processed something like 8 million transactions now. This time we are opening the gates to everyone. We actually started onboarding the users also two weeks ago at it. And we were able to see where we sponsored the food truck experience. So all the people who got the food truck tokens from it.
We used them in a very limited way, not interacting with smart contracts, but just using them to pay for food trucks, using our account abstraction feature. But now it's opening to everyone. So what you can do, you can bridge your assets onto the casing era. You can start interacting with projects that are live from day one. Every day we expect to see more and more projects going live. We know that the pipeline of projects about to deploy is much longer than it's currently live. And we encourage everyone to do it gradually. And only move smaller amounts and do things like don't risk a lot because it's a brand new technology that has never been tested before.
It has never been used in production before until now. So we don't want to rush. We want to take the maximum cautious approach to this. So what what what it means in practice for the users. The basically there are no limitations except that withdrawals will be delayed by some small timeframe. So they could withdrawals or finalization of the blocks or how to say initially is going to happen after 24 hours from the moment of the bulk commitment. We're we're soon will reduce this time to several hours and eventually want to get rid of it once we get rid of the word alpha in the name of of network.
Right now it's in alpha. So the conference are upgradable. There is yet no security console. Like treated as a is a guarded managed network that is life and production is fully available. No limits, but it's still in kind of this test. Flight mode. Okay, so the theme park is opening gates of the theme park parker opening users can go in. There are some rides there. Some of these rides might might throw you off and like you know might have a bad time in the roller coaster. So be careful. There's caution tape around some these things only only across the line if you are an explorer. If you're on the frontier as I know many bankless listeners are.
But once they're there someone else go first. Yeah, I'll let David go first. J.K. I'll be there. So but but like what can we actually do there when when we get there. So you mentioned some projects are launching have launched. So what are some of these early theme rides? I know more will be added over time. Of course, but is there you know what would be kind of the you know your first recommendation on on a project or a place to visit once folks have bridged across to ZK sync era. I don't want to pick the big favourites. You just go to ecosystem dodgy sync.io and you will see the status of the project who is live who is not five and you can just experiment from.
All right, well, well said, I'm incredibly neutral approach. Yeah, I wanted to emphasize like we really we are doing our best to remain fully neutral from all aspects. So we have not like we open the the may not to developers with the white listed. Registration, but we have not censored a single application like everyone who applied could use the network. So it was more for us to gather contacts and to be in touch with those people, but not to prevent anyone from launching. So we're following the strict fair launch approach. We're not going to pick any favourites to like push them to make them special case.
We want to create an even playing field for everyone. This is really important. That's cool. Okay, so Anthony and Alex cannot pick favourites, but of course David and I can. So we'll go test this out and we'll probably release some updates in the bankless newsletter about some of our favourite places to visit. Anthony, did you want to say something to. Just I would definitely recommend taking a look at the page that Alex mentioned regarding the ecosystem. There is a sort of huge cross section of the projects that many people will be familiar from layer one. But some of the other things are exciting are, you know, the projects that are building sort of layer to native and, you know, thinking through what you can do in an environment with.
You know, how transaction throughput much lower fees, you actually start to open up the design space for applications. Because we often get this question about, you know, what do you expect people to build at layer two. But I feel like maybe I have a very bad imagination, but if I rewind the clock, I don't think I would have predicted, you know, some of the really interesting things we've seen in the world of DeFi, I definitely wouldn't have predicted some of the, you know, really interesting use cases for NFTs. So, you know, for me, the exciting thing about layer two is also, you know, I wonder what we'll see next and some of the sort of creative ideas that you can build in an environment that like unlocks application development that isn't maybe economically prohibited in the way it might have been at later one.
Yeah, and Anthony, I got more of engineering questions, but really just to drive this point home, if to make this just super cleanly obvious. I know we have this drop down menu in Metamask, for example, when we need to switch to Arbitrum or Optimism and we expect to see just ZK sync just added to that network list as soon as you add the RPC endpoint inside of Metamask. So now, you know, Arbitrum, Polygon, Optimism, ZK sync, the first ZK EVM to be added in this drop down menu. I'm excited to see that logo there. But, Anthony, this is different because it says ZK EVM, not an Optimistic Rollup, Optimistic Rollers have the benefit of just being able to be basically clones of Ethereum, like microcosms of Ethereum, but this is different.
And so, as the head of engineering, I can't imagine a more intimidating job to be the head of engineering of a ZK EVM. I can think of one, David, maybe launching rockets, right? Well, that's a good point. Anthony, like, we have security. Security is another interesting thing. We have a whole entire security conversation to talk about, but as it comes to teams that are onboarding from regular old Ethereum layer one or other layer twos, what are the engineering challenges about that? What are the engineering challenges that I don't even know to ask about? Like, how big of a lift is this whole thing?
And how do you expect to get new projects migrated onto ZK sync? Yeah, this is a great question and obviously something we think a huge amount about. I would say that a lot of the way that we're thinking about this is broadly, you know, attempt to make decisions with, like, developer first in mind. Obviously, the engineering team, we are engineers and we think about the people that we're building for. So, first approximation, I mean, are also developers, you know, we have a system that ultimately we expect the application layer to add value to eventually millions and tens of millions of users.
But in terms of the design decisions that we make, the people that are probably affected most directly, particularly today are the developers who are going to be building on ZK sync. So, we do think a lot about, you know, a good UX and the good UX is not just the user experience, but also the developer experience. So, when it comes to building on era or migrating from say layer one or another EVM compatible layer two. The goal is to reduce that friction as much as possible, you know, we've invested heavily in building a compiler such that we are source code compatible that to a first approximation, most teams experience in terms of like, you know, migrating from layer one onto the test net or now the main has been that sort of things just worked.
You know, you can take the contracts that you originally developed for Ethereum or for, you know, whatever other layer to happen to be, recompile with the ZK sync compiler and redeploy and to a first approximation. This has been, you know, it's kind of a good and bad thing for us during the test net phase because you want lots of feedback, but in cases where things just work, you know, the experiences sometimes smooth and there's not a lot for developers to say. There are differences, though, you know, we are building a virtual machine, which is optimized with the future in mind, you know, a lot of the design decisions that we've been making are not so much based on, you know, what's the, what are the properties of the system that we want to see exists today.
But really, you know, what are the design decisions that are going to allow us to extend the future in a way that makes sense where we're talking about where we really want to be, you know, projecting forward six months, 12 months, 24 months and as we mature the system, you know, the version of the system that will be going live or is going live today is very much an alpha, you know, in the same way that I think many teams think about building, you know, the approach that we've taken is let's build the core critical pieces of the system. Let's make design decisions today that set us up not just for the system, you know, to make good architectural choices for the system we want to see immediately, but really provide a firm foundation on what we can like build and extend towards the future.
So we've extensively documented areas that I think are unique to ZK sync and where we've made design decisions that deviate from what people might expect elsewhere. And some of these are where we've made sort of opinionated decisions that are in our opinion, probably, you know, going to provide a nice feature set for interesting and, you know, powerful application development. I think native account abstraction is a good example, you know, there is if the idea was to just go as fast as we could to build the system and get something on minute. You almost certainly would have, you know, not attempted to take on a project like that, an extension like that.
So for us, you know, this is a really exciting time. We have sort of the combination of two years plus of engineering work. Finally, you know, really, really ready for the external world to engage with in a way that we're excited about. But there's so much more to come and, you know, this is sort of one step on a very, very long journey as we really extend the system into the future. And Anthony really just asking the barebone simple question, what does all of this engineering effort get us again? We are familiar with arbitragem and optimism, but when we zoom zoom out and look at the massive engineering lift that is a ZK EVM and we try and look at the forest for the trees.
Transactions on arbitragem, pretty damn cheap, you know, like the ZCOS systems are pretty live. What does the ZK part of this whole thing really unlock for us that's new? And just as it relates to the user experience and user story and perhaps the applications that can also be built. Yeah, I think the ZK part and the reason why I think I would argue this is critically important in the forms of time is really about that trustlessness and that security. Like inheriting those properties that I think broadly, you know, everyone at MATLABS and probably many of the listeners, like these are the properties of Ethereum that resonates so deeply.
And the question is, you know, how do we take on this serious problem, the scalability problem without compromising these in any serious degree. So the proof of computational integrity, like the guarantee of the correctness of the state transition of the layer to is really the thing that I think today you can point out and say this is this is a massive step forward. In the fullness of time, I think, you know, when we're talking about hyperscale, when we're talking about really, you know, sort of projecting the application layer much further into the future, talking about millions, tens of millions, hundreds of millions of users.
We believe that it is also true that the ZK, like this trustless aspect of the system is going to provide, you know, this, this future architecture that can support hyperscale where you can have multiple instances, trustlessly able to sort of communicate and move, move data or move value between them. We just have a follow up on that too, just to make this crystal clear. So what can you do with a ZK EVM that you can't with an optimistic roll up? So is it to do with fraud proofs? Is it to do with like lower transactions, lower cost transactions? What is kind of like the bottom line? And if we're not here yet, what do we hope we can we can get to from kind of a user experience perspective?
This is a great question. I would split it into two separate groups. The first group of like the first answer will cover all ZK EVMs. What are ZK EVMs fundamentally give you or optimistic roll ups or any other scaling solutions or specifically optimistic roll ups because anything else but roll ups doesn't really matter in a theory moral. And the second group, a second dancer will be about the specifics of what you can get if you use the ZK technology to its maximum. So to answer the first one, ZK roll ups basically allow you to bridge faster. Like what the users will feel like apart from security and trust us and guarantees that you get the tangible result of using ZK over optimistic roll ups is to be able to bridge faster back to the theorem.
You don't have to wait seven days period. You don't even have to wait this 24 hours, which I mentioned before because that's just a training wheel which is going to be removed can bridge immediately. Now, you probably don't really want to bridge back a lot from from the roll up to to layer one because roll ups are here to enable scale. Like where one is going to remain for very few use cases which require some specific things to happen. In the layer one context, most of the users and most of application will live in a layer two space. But there will be a very important use case of bridging between the roll ups.
And if you're bridging between optimistic roll ups or between a optimistic and ZK roll up, you always will fall back on the longest wait period. And you can't really accelerate that you can you can only accelerate that by using external capital using some other things that that work in. You can't accelerate it without taking on additional risk or additional capital. So you can't really so that means like you basically can't accelerate without having some trust assumptions introduced injected into the system. If we want to build a truly limitless internet of value, internet of roll ups, it has to be trustless.
So all the bridges must be ZK. That means that all the chains participating in this network have to be ZK chains. This is our vision for hyperscalability. This is probably this is a much bigger topic that would require several conversation. But this is long term what the what ZK attack will give you like infiniteness or limitless of scale. But then there is the second aspect. It only applies if you use ZKVM in a specific way. So you you might opt to be as close to Ethereum as possible and just emulate optimistic roll ups. And this is what we see many ZKVM projects that are currently existing and in development are doing.
They are going for this like let's get as close as possible to this old system as be backwards compatible. Let's do data availability management the way optimistic roll ups to let's publish data availability for every transaction. Let's publish the inputs of transactions. For example, as one thing. And we here is where we deviate from all of them from all these ZKVM's in existence today. We decided to look at ZK proofs and ask ourselves like what is what what what cannot give you if you like what's the the best way you can use them. And we decided for example that we want to manage data availability by publishing the state diffs.
So the updates of the of the storage slots that the transaction touches. And that gives you a few very interesting properties for one. It gives you free call data. You don't have to pay for call data for transaction inputs to you don't have to pay for data availability of this. You're only paying zero knowledge proofs. And the general proof generation is cheap and in this only going to get cheaper. So it's it's just a fraction of a set that that is not important. So you can have a very large input. You can process a lot of data, which is very important for site use cases is account abstraction.
Because in account abstraction you want to submit. Like you you you have your user key that controls the account. But then you want to submit some limits for this transaction. You want to submit the custom signature that maybe you you signed on your iPhone in a secure enclave. Maybe you want to submit some additional metadata for the trading routes and limits that you want to take on on on interact with spot contracts. All of that will come essentially for free. So that's one big game. Second big game is data compression. That is imagine a use case such as Oracle updates. On optimistic crawl ups and on ZKVM's that use this optimistic approach, optimistic roll up approach to data availability.
You would have to pay. Data availability for each individual Oracle update. And remember data availability is our scarcest resource. That's what all roll ups share like there is a single limited bandwidth of data availability on Ethereum. It doesn't matter how how scalable your ZK proofs are circuits. You still have to like share that and like all their all ups compete for this limited space. So the more transactions we have a we will see the same dynamics that the transaction prices will go up. So Oracle updates you have to pay individually for each of them with optimistic approach with what we're doing.
You're only going to pay the final price for the single storage slots at the end of the huge batch. So you can do the Oracle updates as frequently as you want. You can do them every second. They still will be trustless. They will still be feeding you can you can use a lot of oracles. But then they are going to be much cheaper. And the same thing applies to all use cases where users interact with the same contract with the same data or with transient data. For that matter within the one single batch and the batch can be very large. For example, trading on liquidity pools like union swap pools.
You do a lot of trades but at the end you only pay for one or all the users in the batch will pay for one. So that is that is to data compression. And finally you can do data extension. There was the architecture we introduced a long time ago called SDK Porter, which is a variation of of a validity system where the data. Some of the data does not need to be published on the theory for some accounts or for some specific use cases. You don't need the absolute 100% security inheritance from the theory. You only need the validity of your transactions to be guaranteed by Ethereum so that no one can do wrong things.
But the data maybe it's discardable. Maybe it's just some one time voting campaign or maybe it's a wallet that you only use for some small like your current account where you put little money and you don't want to pay huge fees. But you want to do a lot of cheap transactions. You can use SDK Porter for that. And in our architecture, Z key Porter will be seamlessly interoperable with the Z key role up, which is not possible again if you're using this transaction inputs. So those are things around just one specific aspect. So Alex, just kind of from the user perspective, bridging much faster, it can be instant that that can't happen in optimistic roll up.
You know, you have kind of seven days and this will reap many benefits. Just curious on kind of a way a user experiences what you just said that optimization that efficiency. So if like a main net transaction cost a dollar on Ethereum, right, and something like an optimistic roll up gets it down to like, you know, ten cents or maybe five cents or maybe one cent or something. Is our ZK roll ups and is a ZK sink Eric going to deliver another order of magnitude lower cost on transactions. That's one like this may be a layman's question to you. But that this is one way users see it is like are my track transactions going to be cheaper.
Another way I want to ask the same question is like, I remember the early days of Arbitram deploying. They were like, hey, we're deploying main net. This is our first deployment. We still have some guardrails on. We have just increased the capacity of Ethereum by one. So we just shipped one more Ethereum's. And that was easy for bank listeners to understand. And then they delivered some efficiency and they were like, now we have three more Ethereum's, right? Can you give us a comparison? For the record of seven now. Okay. There's seven Ethereum's there. How many Ethereum's are we going to get out of a ZK sink?
How low can our gas fees go? We will get at least as many as optimistic rollups give you. But in addition to that, for it depends on the use case for some transaction types, it will be comparable to optimistic collapse just because it's an individual transaction. You still have to pay for it full data availability. But for other transactions, you will have to pay zero fees because the contract will subsidize this transaction. And this is possible with account abstraction. This is possible because we support it natively. And from the economic perspective for this protocol, it will make sense because they are only subsidizing at once for all the users because they will be then reusing the same data availability storage.
And this gives you like hundreds Ethereum's of thousands of Ethereum's. But from the user perspective, like the magic is really you don't have to pay anything. It's like the transaction is completely gas free. And like this is why it was important to implement it natively. Unfortunately, things like EAP 4 or 3 or 3 or 7 would not allow this to the Ethereum. Even if you use this this relayer, if you agree to use this third party relayer, they still cannot do it for externally owned accounts, which are most wallets in network today, but it's possible. So the idea of like how many Ethereum's do we get is a very easy way to just imagine this.
And the answer is with ZK sync, we get a lot of Ethereum's with ZK tech. But I really want to double down. Yes, I really want to double down on like that there's this idea of the some of the parts. I always mess up this. Yeah, the whole is greater than some of the parts. Thank you. That's the kickstart I needed. So yes, we get we get more Ethereum's we get more scale things get cheaper. They're all also faster, but it's not such a just a linear is like, oh, we can do things cheaper and faster. It's more than that. Not only do you get cheaper and faster, which enables new use cases like oracles.
We can have more oracles because more oracles become viable. We have more use cases because more use cases become viable. We have native account abstraction because account abstraction becomes viable. We have cross ZK EVM composability because that is now viable. You have instantaneous withdrawals to layer one and that's with now viable. All of these use cases can relate to each other and offer surface area for builders to extract the value out of those interrelations that specifically ZK EVM's create. So understanding like, yeah, we get 10 Ethereum's is like a great way to start. But also you get the level of composability that Ethereum created and a zero to one moment from like Bitcoin to Ethereum on the app layer and smart contracts.
We have like another zero to one moment in terms of use case composability because of the instantaneous nature of ZK tech across all use cases. In addition to the raw cheapness of the transactions that in this in of itself also unlocks new economic activity. And so like this is kind of a tough idea to wrap people's head around. So like all of these security dependencies. But I really think like the whole the sum is greater than the whole of the parts. I think it's a great like mental model to be left with when we walk away from. I mean, my mental model here David any time you say that and by the way that always gives me shivers when you go on your ZK EVM's are amazing, you know play.
It's just like it's going to feel just like fintech. It's going to feel just like the best fintech platform you've ever used except now you're not dependent on the banks. And I'm not saying now I'm not saying day one. I'm not saying like when you guys release but when we get account abstraction and smart contracts and everything David already said we we develop that app layer. It's just going to feel like a web to app except it's completely backed by you know trust trustless guarantees and crypto economic security, which is with the amazing thing. Is that about right or are we like overselling it is absolutely right and I just just have one thing to add like if you throw ZK Porter into this mix.
Then you you basically get infinite number of almost the theorems in addition to multiple. The also almost the theorem work which is coming very very close to the security guarantees of the very not quite there but like it's it's good for for a lot of good things and you can get infinitely many of them. So this infinite part is really important like where I should rather say not infinite because it's a mathematical term limitless. We want to get to a point where there are no limits on how many users we can accommodate, how many transactions, how many things can run in parallel. This trustlessly is only possible with ZK attack and if we want it to be on the theorem then it's only possible to CK EVM so that all the applications can leave on all those infinite parallel chains that are like this multiverse world of.
Multi raw ups interconnected interpretable maybe just echo something you said there because I think you really captured at least you know sort of reflection of how we think about this that I think is really important to highlight. You know when you first start thinking about scale it can feel like an infrastructure problem right can feel like how do we optimize the system to be able to process lots of transactions. Drive down fees and if can start to feel very much like this is really the way to think about solving the scalability problem but actually I don't think that's enough right to count abstraction because.
If the if we don't address the user experience that I think many of us are like you know come to learn to live with that layer one. This isn't for everybody right you know it's still true today that I think the user experience at layer one can feel you know janky awkward at times even scary you know when you're you know moving substantial value this you know it's not a super friendly experience at times and I think it's that sort of combination of both. Tackling those architecture problems you know thinking about how you think about performance thinking about how you drive down fees but then also you know you do need to have an environment in which people can build applications that millions of people want to use and millions of people won't be.
Forced to confront some like awkward user experience just to engage with the system so I do think you know what we're working towards you kind of have as an infrastructure problem but as a user experience problem as well and I think a kind of structure is like a critically important part of solving that part. Yeah well said well said Anthony and I really just want to drive this point home one more time like. Right and I infinitely bullish on optimistic roll ups we love all of our layer two's but linear scaling is not going to be like the quote unquote broadband moment that made the internet into what it is today.
Like once upon a time internet 1.0 was a text based forum experience where JPEGs loaded over 10 minutes right and now we have YouTube and Facebook and Instagram and Twitter that was a broadband moment that was a zero to one paradigm shift and you know optimistic girls are great for adding you know single digit more theorems to layer two's but really like the linear scale isn't really going to take this revolution that we are all trying to make people feel into the mainstream is really going to take. What is you know more more than 10 theorems but then also the second order consequences that I also illustrated so.
This is just what I really want to impress upon listeners about why this ZK cryptography magic is so impactful Alex Anthony I want to ask you a few more questions in a couple of different categories. Polygon ZK EVM hot on your guys his heels we want to talk about how ZK sings era is different what are you what is the era chain optimized for what have you guys really emphasize here and prioritize and what is your competitive differentiator between the other ZK EVM's that are coming on to the scene. And so I want to ask about that and overall just like where does this go from here what are the next steps what are the short term goals and long term milestones that we should all be paying attention to as the scene develops but first before we get to these conversations a moment to talk about some of these fantastic sponsors that make the show possible.
Uniswap is the largest on chain marketplace for self custody digital assets. Uniswap is of course a decentralized exchange but you know this because you've been listening to bankless but did you know that the Uniswap web app has a shiny new fiat on ramp. Now you could go directly from fiat in your bank to tokens in defi inside of Uniswap not only that but polygon arbitrum and optimism layer twos are supported right out of the game but that's just defi. Uniswap is also an NFT aggregator letting you find more listings for the best prices across the NFT world. With Uniswap you can sweep floors on multiple NFTs and Uniswap's universal router will optimize your gas fees for you.
Uniswap is making it as easy as possible to go from bank account to bankless assets across the theory and we couldn't be more thankful for having them as a sponsor. So go to app.uniswap.org today to buy, sell or swap tokens and NFTs. How many total air drops have you gotten? This last bull market had a ton of them. Did you get them all? Maybe you missed one. So here's what you should do. Go to earnify and plug in your Ethereum wallet and earnify will tell you if you have any unclaimed air drops that you can get. And it also does pro apps and mintable NFTs any kind of money that your wallet can claim earnify will tell you about it.
And you should probably do it now because some air drops expire and if you sign up for earnify they'll email you anytime one of your wallets has a new air drop for it to make sure that you never lose an air drop ever again. You can also upgrade to earnify premium to unlock access to air drops that are beyond the basics and are able to set reminders for more wallets. And for just under $21 a month it probably pays for itself with just one air drop. So plug in your wallets at earnify and see what you get. That's E-A-R-N-I dot F-I and make sure you never lose another air drop. The Phantom wallet is coming to Ethereum.
The number one wallet on Solana is bringing its millions of users and beloved UX to Ethereum and Polygon. If you haven't used Phantom before you've been missing out. Phantom was one of the first wallets to pioneer Solana staking inside the wallet and will be offering similar staking features for Ethereum and Polygon. But that's just staking. Phantom is also the best home for your NFTs. Phantom has a complete set of features to optimize your NFT experience, pin your favorites, hide your ugly, burn this fam, and also manage your NFT sale listings from inside the wallet. Phantom is of course a multi chain wallet but it makes chain management easy displaying your transactions in a human readable format with automatic warnings for malicious transactions or phishing websites.
Phantom is already saved over 20,000 users from getting scammed or hacked. So get on the Phantom wait list and be one of the first to access the multi chain beta. There's a link in the show notes or you can go to phantom dot app slash wait list to get access in late February. Bank of station we are back with Alex and Anthony of Z casing of matter labs with a brand new Z casing era main net launch once again congratulations guys Alex I've heard over and over and over again that you have this incredible back story and why trustless cryptography so important to you. I've been having you for a podcast for now for a while now and we'll eventually get that one recorded but I want to ask you about how Z casing era has come to express certain priorities.
What is it really doubling down on what makes it unique. There are so many other not so many there are other ZK EVMs that are coming on to main net I believe Z casing might be first I think that's right. But why is the casing era different than the alternatives that are out there on the scene. I can highlight a few things which I think are really at the core of Z casing and I think that makes them different and they might be other products also want to embrace this this ideas and implement them who will be really happy to see this base get a richer through it. But I think what defines us is the these three core priorities number one alignment with on ethos with the theory on with the general crypto community.
We are here for a mission. We have always been there for a mission and we'll always be there for a mission. It's not a commercial project in the first place. It's a mission driven project. It's a mission. We're not a company we are really a mission. Our mission is to accelerate the message option of crypto or say it's simpler to scale freedom. We're in it for freedom because freedom is the what empowers people what could create wealth what creates fairness in the world what what lets people you know defend themselves against corrupt regimes corrupt. Infrastructure institutions and so on so like freedom is is everything that like the young goal and also the way we operate the metal apps, the company and the our team is structured in a way that everyone has very broad autonomy, very broad ownership over over topics and they they they own them and have freedom to operate the way they want.
Freedom is number one and ethos number two is we are we prioritize security. It's really important for us like we understand that this is a space where there is basically no margin for error and you can't rush and you can't cut corners because. One big mistake and throw the entire space like here's back because the trust can be undermined so we're we're taking security very seriously and we are like. We are anti hype in this regard we always emphasize this we always push we always like from from all the choices that we can make we take the one we just most say now that doesn't guarantee that like things will not happen and like this is again my my attempt to to convince everyone to take things slower not rush experiment with only with like this very high risk awareness.
Security is number two and number three is we are in for a very long run we understand that this space will only succeed if we all run marathon not a sprint so we are building things for the future that might set us back. Slightly in the beginning like you know like we we're not going for a fully the ambulance you would obviously be easier to just like go for fully the ambulance and have all applications not like not to have to change a single line of code. No one is really doing that no one can do that like the some modifications are required in any role up in no matter optimistic risic it's just the degree of the specifications that various.
And we're not going to optimize that part we are optimizing for the future not for the past this future or this is the third priority so to recap values security and building for the future. Alex we're on this new frontier there's a bunch of new use cases that we're all very excited about there's also new risks and so as users come and use the casing as builders build on the casing what are the new concerns what are the new risks that they might need to be informed about. Certainly there are let's begin with this like this is a brand new technology so we have like just basic systematic risks of like any smart contract that you deploy.
Every needs to be tested with time you know like recently we have a book in Euler finance that has been live there for eight months and it has been audited and there was still this bug and it was like let explain it so you need time you need to put significant stake at risk and then like bottle test it but then. Even that is not enough you have you want to put in more mechanisms more mitigations like layer of security like if one thing fails you always want. Better things to rely on but like things happen even even planes can can can fall you know so they even if you take it with the most conservative approach.
This complex systems have inherent risks it's really hard to predict where in the complex system risk and can materialize so that that's why you want to build systems that are as simple as possible. As isolated as possible if you have multiple subsystems they should work through clearly defined interfaces and you want some guards between those interfaces but like really from the end user perspective it's it's hard to say what can go wrong. You know so the basically the the the the the the only scene approach would be like take things carefully. Yeah my my take on this is how we end every bankless podcast by the way we're not ending right now but recall bankless nation what we say cryptos risky defies risky you could lose what you put in.
This is the frontier right and that's really where we are we're on the frontier of the frontier with some of this ZK EVM technology we wouldn't rather be anywhere else. This is where we want to be and yet at the same time your explorers and you know things can happen on the frontier for sure one I think I guess trade off or decision point for any role up team to make is kind of this trade off between security into centralization maybe that's not even the right the right vector but a lot of teams have needed to keep. Access like maybe call it root level access to be able to make changes and modifications to a roll up in case something goes wrong in case funds are locked in that sort of thing can you talk to us about the path towards full decentralization because I have to imagine this is somewhat similar to other roll up implementations in that stage one is not fully decentralized yet you have some safeguards in place you have some training wheels in place and.
We would probably expect that right I mean you want to make sure that you can unlock the keys if you lock them in the car. Anthony I'm wondering if you talk about this path to decentralization and and how ZK sync is thinking about this maybe if you allow me to begin because I was part of this journey with ZK sync version one which we can now call ZK sync live and I just just want to talk. I would say that this is a choice or dilemma between security and trustlessness not so much decentralization at this point like decentralization is a broader concept but here you're really asking yourself am I going to keep some trust assumptions with on the team or do I want to go fully trustless but then no one can intervene and fix my problems.
So we encountered that back when we launched the first roll up ZK sync live the ZK roll up specialized payments with very first version was completely immutable with a time locked upgrade ability where with the team could propose an upgrade but there was no way for us to accelerate it it was it would take several weeks and the users would have an option to to withdraw from where to to where one. Fully permissionlessly without any censorship through where one emergency hatch or like the priority queue. We then realized that it's not going to it's not pretty to do this because there was a vulnerability and we had to make an upgrade and likely everything was fine but like we realized it's it's really important to go slower and introduce some trustlessness.
So the possibility of a bug is much higher initially at least for even from the user perspective from external user perspective than the probability that the team is going to be corrupt. So for the alpha we decided that we we just going to introduce the instant upgrade ability for ZK sync era for for light what we did was we came up with the concept of security console. We were the first to introduce this idea where we said let's summon a group of highly trusted community members from Ethereum community we had 15 of them and it will require their permission and approval to accelerate an upgrade for an emergency use case.
If there is an emergency then the team can propose and upgrade the security console can approve it and then it goes faster on the fast track by passing the this upgradability time lock. And this is the next stage which we will use for error like after we feel that the protocol is stable enough mature enough we will transition to security console but we don't want to stop there because the security console is also a set of people that can can basically do anything with the protocol even though it's a broad set of people we it's not what we want crypto to be. So for for the ultimate vision we can imagine going beyond that and lowering trust assumptions even further.
So for example we could say that the security console can only initiate freezing of the protocol not immediately upgrading but only freezing for short period of time and then we could rely on the broader protocol governance to decide what's going to happen with with this problem. Is this a real problem or was the security console corrupt. If it was a real problem then the governance can approve an upgrade platform and we can go even farther from there what if the governance if you know if we have some broad community participating through I don't know some means to decentralize it maybe we have token maybe we have to like the token holders have to vote for it.
But what if the majority of the token holders is is a game corrupt then we would think we need to save the minority because that's what crypto is standing for full trustlessness not rely on others majorities so eventually we can build a system where the security console could freeze the contracts and then it would take the soft fork of the layer one itself to resolve the conflict if there is any problem there. So this is my rough thinking I see that Ryan wants to ask something. No, it's just going to say that's really cool. You know well spelled out and where I guess we're in the first stage where the team still has some of the control and then you're moving to security council later and then you limit the powers of the security council and then you have some sort of governance coordination and ultimately it's kind of fork choice rule in the same way that if you remember Bitcoin are on main net is pretty cool Anthony do you have anything to add to this.
I mean I think Alex is subject up really nicely but one thing to say maybe just to try and be unambiguous like the plan for the alpha label is essentially to be a very strong signal to the community to developers to users about our sort of internal security posture and confidence in the state of the system. We aren't expecting for example there to be sort of this journey to the Greek alphabet of like. Now we're alpha now we're in beta it's really more did once this as long as this alpha label is attached to the system this is meant to kind of imply that we're in this early phase where there are these trust assumptions.
I mean you can look at tools I think there's this maybe many people familiar with this really beautiful page put together by the L2 beauty regarding sort of risks across the L2 space phenomenally helpful in a huge amount of work has gone to try and distill a lot of this sort of complexity when when people have to think about the risk in these systems. But even you know you look at that tool and you realize the problem for users is a there's many of these systems and be the the risk space is complex and to have like a principled you know internal opinion on the risks of all of these different systems when you're not an expert is extremely difficult.
And I would say maybe even impossibly difficult for most users because the opportunity cost of even reading you know every single one of these things is extremely high so for us the alpha label is our signal to the community about like our posture here and we will attempt to be extremely unambiguous when we're talking about risk. And we're talking about you know and we'll be releasing a huge amount more security as Alex mentioned before is always top of mind for us and I think we've got a track record at this point of that being you know us having a serious commitment to that but it's that alpha label that will we will attempt to distill everything into it to a degree for users.
By the nature of this new technology this new frontier the risks are present today yet there is still a bunch of building to do in the app layer with all the builders and so all the cool fun stuff that we can imagine the future still needs to be built yet. The risk are always here on day one so that is always just a word of caution for all the users out there but Anthony with all of this future state of the you know theorems broadband moment on everything that ZK tech can really unlock for a theorem what do builders need to know there's so much left there's so much room for activities on ZK sink how do builders find out what they need to do in order to start building on ZK sink where's the top of the funnel for this rabbit hole for the builders.
Yeah it's a excellent question so I would say you know if you wanted to get started as a builder on ZK sink we have overhauled all of our documentation in the sort of build up towards this moment and over the last few months and we've also attempted to be thoughtful about how we consider the focus for this documentation so much overlaps in terms of what you can do with L1 given the EVM compatibility so you'll see that where we've deviated from L1 or where we have sort of. You know new things available L2 there'll be just a much richer set of documentation you know we focused on things like account abstraction things like bridges so in terms of the documentation there is a lot there is also a lot of focus on the specifics that become available for you when you're thinking about working on on ZK sink era beyond that we have an extremely active and passionate community the discord is very very active.
We're growing you know DevRel and DevExperience team so we have both you know highly engaged community but also lots of technical support and so for sort of real time conversations about you know I have this idea I'm thinking through how I implement this on ZK sink or I've run into this issue and I'm trying to work my way through it there's multiple channels but but definitely the discord is fun and helpful so both technical support and you know lots of interesting community memes and. It's in pieces well we will get the links to the discord in the docs into the show notes and also Anthony what's the link for the users out there the ecosystem applications link where they can go check all those out if you could just say that one more time yeah sure so if anyone wants to see the state of what they can engage with on the system today it's just ecosystem dot ZK sink dot IO this will be a page with very frequent updates in the coming weeks as as more and more builders deploy and configure applications and yeah things become available for for you.
We use this to test basically users can find all links from ZK sink dot IO it's it's a half or they will get it through beautiful Alex Anthony thank you so much for walking us through this announcement is extremely exciting there's a new frontiers and we love this frontier metaphor here on bankless not too many people know the ZK sink was actually one of the first ZK roll ups not EVM ZK roll ups where people could process payments I remember using it back in 2019 on get coin so it was a way that I got started. bootstrapping my own content production here in the Ethereum ecosystem and Ryan would run in the bankless get coin as well so we have thanks to give you guys for that as well Alex I know you've been in this space a very long time Anthony you're a little bit newer but I know that this topic is very very large and very very big is there anything that we haven't touched on yet today in the show that the way you absolutely must before we close out here.
I would just say that we're still growing our team and if you are feeling like you want to help us scale Ethereum and create the stressless future please check out the the job to the jobs that we have open on our website. I'm sure there is a lot of milestones and developments ahead of us when might one of those milestones involve a token. The next thing that we're focusing on is really decentralization so are they making the system fully permissionless removing any points of trust any points of central control that is to remain. And then also internal improvement performance improvements security implementing new mechanisms in new features so what I'm here is that is the when token conversation is similar to the when the central decentralized answer perhaps.
Yeah when when necessary when it's necessary Anthony Alex actually one of the most clear answers we've ever gotten from a layer to when it's necessary wow just that's it well said Alex Anthony thank you guys so much for joining us on bankless today appreciate it. Bankless nation got to end with this and none of this has been financial advice of course your standard risk and disclaimers apply as with anything in crypto even more so when you're on the frontier but crypto is risky so is defy so our new roll ups you could lose what you put in we're headed west this is the frontier it's not for everyone but we're glad you with us on the bankless journey thanks a lot.
you