zkEVM is here! Alex Gluchowski, CEO & Co-Founder of Matter Labs and of zkSync is here to talk about the huge accomplishment he and his team brought to market this past week. This is the first EVM-compatible ZK Rollup on Ethereum’s testnet!
Is this the endgame of blockchain scalability? How were Alex and his team able to bring this to market way sooner than expected? Why is this important and a monumental leap forward for the space? Find out the answers to these questions and much more on this week's State of the Nation with Ryan and David!
DONATE TO UKRAINE USING CRYPTO: https://twitter.com/Ukraine/status/1497594592438497282?s=20&t=kiFqqEmK2QtdOA8KcwUq1g
------ 📣 OPOLIS | Sign Up to Get 1000 $WORK and 1000 $BANK https://bankless.cc/Opolis
------ 🚀 SUBSCRIBE TO NEWSLETTER: https://newsletter.banklesshq.com/ 🎙️ SUBSCRIBE TO PODCAST: http://podcast.banklesshq.com/
------ BANKLESS SPONSOR TOOLS:
⚖️ ARBITRUM | SCALING ETHEREUM https://bankless.cc/Arbitrum
🍵 MATCHA | SMART ORDER ROUTING https://bankless.cc/Matcha
🚀 SLINGSHOT | LAYER 2 SOCIAL TRADING https://bankless.cc/Slingshot
🏦 GEMINI | TURN FIAT INTO CRYPTO https://bankless.cc/Gemini
🦁 BRAVE | THE BROWSER NATIVE WALLET https://bankless.cc/Brave
🦄 UNISWAP | DECENTRALIZED FUNDING https://bankless.cc/UniGrants
------ Topics Covered:
0:00 Intro 6:00 Alex from Matter Labs 9:51 What is a zkEVM? 15:57 The Breakthrough 19:08 zkSync 2.0 Public Testnet 24:04 The User Experience 29:37 Developer Tooling 32:48 Why zkRollups? 37:22 Security, Centralization, Trust 41:51 Justin Drake's Question 46:33 The Roadmap 50:30 Wen Mainnet? 53:15 Wen Token? 58:51 zkDAO 1:00:52 Ukraine 1:06:57 Crypto's Impact in Ukraine 1:11:00 Closing & Disclaimers
------ Resources:
UkraineDAO https://twitter.com/Ukraine_DAO?s=20&t=k_QiuIA3ZukqUPd9gy--LA
Alex Gluchowski on Twitter https://twitter.com/gluk64
zkSync on Twitter https://twitter.com/zksync
zkDAO https://twitter.com/zkdao_official?s=20&t=9HO7KyxvPEwqBhAo6SgbEA
zkSync's Website zksync.io
zkSync 2.0: Public Testnet is Live! https://matterlabs.medium.com/zksync-2-0-public-testnet-is-live-de870ba9632a
Modular vs Monolithic Blockchains https://shows.banklesshq.com/p/modular-vs-monolithic-blockchains?s=w
----- 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://newsletter.banklesshq.com/p/bankless-disclosures
No summary for this episode yet.
Hey, Bankless Nation, welcome to another State of the Nation episode. We've got a fantastic episode here for you. Look, something we thought they said was years away apparently has just come to Ethereum. This is a key cornerstone in the efforts to scale Ethereum into the future, and that is a ZK EVM compatible roll-up. We're going to be talking about that today. David, who do we have on the show today to speak about that? Yeah, we have Alex, the co-founder, CEO of Matter Labs, who is the team behind ZK Sync and ZK EVMs, what we're talking about today, or ZK Rollups. Especially in the last year of 2021 of Ethereum, that video of Vitalik talking about how the Internet of Money needs to cost five cents has been a source of comedy for everyone who's pointing at how high Ethereum's gas fees are.
Well, when Vitalik made that comment about how the Internet of Money needs to be five cents, he's talking about ZK roll-ups. He's talking about the ZK EVM. And as of very recently, the ZK Sync team, the Matterlabs team, has been able to put a ZK EVM on a test net, which means we have a ZK EVM ready to go. We just got tested out first. And so we're going to ask Alex about all of these questions that we have as what's left in this roadmap. What can people do now? When is this going to be ready for users? And of course, the obvious and most fun question, when token? And just a few more conversations of that nature.
Yeah, it's an incredibly important subject, particularly this year. This is the year, it's a proof year for Ethereum scalability approach. We're also going to be talking about, probably toward the end of the episode, maybe at the front too, about Ukraine. Understand many of the Matterlabs team is actually located in Ukraine. Alex himself was born in Ukraine. I think crypto has a story to tell and a role to play there. So we'll be talking about that. David, before we get into the episode, though, we've got a special PSA from our friends at Opolis. All right. Opolis is awesome. Like straight up awesome.
If you want to become a self-sovereign Web3 worker, you got to check out Opolis. What does it do, David? Opolis is a DAO that helps people work for other DAOs. It's a DAO that supports the DAOs. And so a lot of people would love to work in Web3, would love to be a self-sovereign worker, but we still haven't figured out things like health care and benefits and payroll and taxes and all that stuff. And Opolis is bridging the world of traditional employee benefits to people that work for a DAO. So it's like a health, it's like a employee infrastructure collective. and so we all get to share our resources that we need in order to live a self-sovereign life when it comes to our employment but also still get all the benefits that we need to make sure that our risk our personal risk our health care risk family risk all that stuff is taken care of so you can actually sign if you sign up for opelis before i believe march 1st which is you know you got some time but not too much time you actually get a bonus of a thousand work tokens which is the opelis dow token and a thousand bank tokens out of the bankless dow uh oh may 1st excuse me May 1st, even more time.
So if you are trying to get into the world of Web3, if you're listening to Ryan and I yell at you every single weekly roll up about getting a job, Opolis might make this life easier, this transition easier for you. Yeah, totally. I mean, I resisted becoming a self-employed individual for a number of years just because I got health care insurance, health insurance through my corporate employer. And I couldn't let that go. But Opolis provides an awesome off-ramp to that. They give you health insurance, take care of your benefits, all the messy stuff. So go check that out, guys. All right, David, got to start with the question I always ask you in these State of the Nation episodes, which is this, what is the state of the nation today?
Right, the state of the nation is we are getting synced. We're talking with the ZK sync and we're getting synced with ZK sync. I really wanted to do like a zip. That's synced, not sunk, right? Synced, yes, not sunk. I really wanted to do like a zip metaphor because for some reason, ZK Sync and ZKs always feels like very zippy to me, but I couldn't figure out. Yeah, fast. Yeah. But I couldn't figure out how to roll that into a metaphor, but I'll just talk about how we're getting synced with Alex from ZK Sync today. Awesome. We definitely want to get in sync on ZK Sync and that is coming up for you.
We're going to get to Alex in just a moment, but before we do, we want to talk about the sponsors that made this episode possible. Slingshot is a decentralized trading platform that combines the performance and ease of a centralized exchange with the openness and transparency of DeFi. Slingshot aggregates liquidity from all of DeFi in order to find the best price on thousands of crypto assets. Every token on Slingshot comes with a price chart and trade logs to give you insights into the market's activity in real time. Slingshot is available on Polygon, Arbitrum, and Optimism, saving you from the high gas fees and low transaction speeds of the Ethereum L1.
There are no fees to trade on Slingshot, and any positive slippage is given to the users. Trading on Slingshot is a social experience. You can even set your chat avatar to your favorite NFT or soon a Slingshot 2099 NFT avatar. Once you bridge your assets to Polygon, Arbitrum, or Optimism, go to app.slingshot.finance to trade and use the chat box to share your trades with others and find other tokens to ape into. The Brave Browser is the user-first browser for the Web3 internet with built-in privacy and ad blocking to keep you in charge of your digital footprint. Inside the Brave Browser, you'll find the Brave Wallet, the first secure crypto wallet built natively inside of a Web3 crypto browser.
Web3 is freedom from big tech and Wall Street. More control and better privacy. But there's a weak point in Web3, your crypto wallet. The Brave Wallet is different. Brave Wallet is built natively inside the Brave browser. No extension required, which gives the Brave Wallet an extra level of security versus other wallets. With the Brave Wallet, you can buy, store, send, and swap your crypto assets. And you can even manage your NFTs and connect to other wallets and DeFi apps, all from the security of the best privacy browser on the market. Whether you're new to crypto or a seasoned pro, it's time to switch to the Brave wallet.
Download Brave at brave.com slash bankless and click the wallet icon to get started. Arbitrum is an Ethereum scaling solution that's going to completely change how we use DeFi and NFTs. Over 250 projects have already deployed on Arbitrum and Arbitrum's DeFi and NFT ecosystems are growing rapidly. Arbitrum increases Ethereum speed by orders of magnitude for a fraction of the cost of the average gas fee. When interacting with Arbitrum, you can get the performance of a centralized exchange while tapping into Ethereum's level of decentralization and security. If you're a developer who wants low gas fees and instant transactions for your users, visit developer.
offchainlabs.com to get started building your application on Arbitrum. If you're a user, keep an eye out for your favorite DeFi apps or NFT projects building on Arbitrum. Many of your favorite apps are already live, with many more coming over soon. You can find these apps at portal.arbitrum.one, and you can bridge your assets over to Arbitrum using bridge.arbitrum.io in order to experience DeFi and NFTs the way it was always meant to be, fast, cheap, and friction-free. Hey, guys. We are back with Alex Glukhovsky. He's the co-founder of Matter Labs. Matter Labs is the team behind ZK Sync. That's what we're going to talk about today, the ZK roll-up that is pioneering a ZK EVM.
Just went to Testnet. Want to hear all about that. Matter Labs is really special, I think, for bankless and for those who are decentralization maximalists because they've been uncompromising on many things, including open source values. This is also why we're excited to bring Alex on Bankless. Alex, it's great to have you on Bankless. Thank you, Ryan. Thank you, David. It's an honor. You know, Alex, we want to start because we understand that a large part of the team or part of the team of Matterlabs is actually located, has been located in Ukraine. How's everyone doing? Give us an update. everyone safe what's what's happening yeah so obviously everyone is uh uh in a lot of stress uh because we have a really large part of the team in both russia and ukraine and we were lucky we managed to evacuate most of our ukrainian team in safe places mostly abroad uh before that happened because we are uh security uh first company like security is is the the paramount concern that mineral absence kissing and uh we live by the motto uh only the paranoid survive and the rumors appear that the situation might escalate we just thought we can take risks the history is full of black swans and uh if um things happen you know that it's going to be really really difficult to do anything but it's really cheap to get a team on a few weeks vacation abroad so we decided we should go for this even if the probability is very low Unfortunately, though, a lot of team members have family members back in Ukraine, and some of them are trying to evacuate them.
So yeah, there is a lot of stress going on. It sounds like a very stressful time. We are glad that you guys were able to make some provisions and keep everyone safe during this time as well. Alex, if you're okay with it, we want to talk a bit more about Ukraine. Understand you're born in Ukraine. You have some personal experience there. Also in the world of crypto, of course, you are here for reasons of values alignment with what we're doing in the space and decentralization. So I think we want to talk more about that maybe toward the end of the episode. Would you be okay with that? Absolutely.
We'll be happy. Okay, awesome. Well, let's see that. First, we want to get into some of the recent events and news from a technology perspective, which is this. And this is very big. This happened last week, I believe. The ZK EVM on Testnet. Okay, this is something I think the crypto community thought was years away. In fact, as recently as a year ago, when we had Vitalik on the podcast, we talked about the future of roll-ups and scalability. And he was very optimistic about ZK roll-ups, in particular ZK EVM roll-ups. EVM stands for the Ethereum Virtual Machine, of course, which allows all the programmatic DeFi magic that people experience on Ethereum.
But he thought at the time that would be years away, like years plural, maybe three to five. And here we are one year later, and you guys have just released an EVM-ZK roll-up on Testnet. Was this a surprise development? Tell us about what was actually released and how you were able to deliver it maybe ahead of what a lot of people thought was going to be the schedule for this thing. Absolutely. It was not just Vitalik's prediction, but actually an opinion of a lot of top cryptographers in the world that this will take a lot longer to deliver because of inefficiencies of zero-knowledge proofs for general computation.
Zero-knowledge proofs are, you know, you have to convert your program into specialized arithmetization form, like essentially it's a mathematical representation of this program, and it only works well if your program is fixed and well-defined. But with generic computation, we have loops, we have recursion, we have all-with-tree-in-compete flexibility. We can build any programs. And it just doesn't convert well like you have a lot of overhead when you're trying to represent this flexibility in terms of pure mathematical function. You can imagine like huge polynomial mathematical function. So and everyone thought, Well, this has to stay.
So we just have to find better ways to be more efficient with proving, with overcoming this massive overhead through maybe more efficient hardware, maybe more efficient proof systems and so on. But what we did was we just realized there can be, there are shortcuts to make, and they will compensate for this huge inefficiency in interesting ways. What we realized is that during complete part of the program is only going to take maybe 1% of the entire computational power that we need. While most computations will be spent on like heavy specialized operations, which include hashes, storage access, and so on and so on.
So what we did, we built a hybrid product which combines this flexible part with the rigid part. And the rigid part is well optimized and we knew how to do this. And there was a number of breakthroughs also in the cryptography around knowledge proofs. So this combination gave us this breakthrough which allowed to deliver technology much quicker. So Alex, let me regurgitate that to make sure that I'm following. as much as I like to think that I understand zero-knowledge cryptography, it's not really my strong suit. And I would imagine that's probably true for the listeners. So you talked about two components of a ZK EVM that are really needed to have a fully-fledged, fully-expressive roll-up that has all the composability that we all enjoy in DeFi.
Really, the thing that really makes DeFi powerful is its composability. and making sure that we retain composability in a zk evm on a zk rollup is a tough challenge and you talked about how there's the expressive flexible side and then there's this side the other side of things that are i think just always the same something like signatures or things about a rollup that just like don't change but are necessary and rigid and always there for all the roll-ups. And so you've been able to compartmentalize these things. And the things that don't change, you've been able to extremely, extremely optimize.
And then that's been able for you to separate or compartmentalize away from the flexible things and allowing you to maybe tackle these two problems separately, simultaneously. Is that a fair way to put this? Yeah, you can think it as imagine a computer which can which has a cpu which can execute any program and then you have some specialized micro schemes for digital process like a let's say a gpu for specifically for graphic processing it can do one thing but it can do it really really well and much more efficient than the cpu and cpu is very generic can execute any program arbitrarily but it's it's slower so this is the kind of analogy we have here um and for for uh as far as composability is concerned if we can express an arbitrary program an arbitrary turing complete program then we can do anything evm can do so we including composability composability it's not some unique special case so what what what's really important also in this regard is that we should be able to execute programs of arbitrary length and it's it's a little bit hard with snarks because they have a limited proving capacity but we use recursion which was one of the breakthroughs i mentioned where we can combine we can have a lot of um circuits of limited size but we pile them together in the line and then we recursively prove them uh with multiple layers until we get one single snark which attests to the validity of the entire execution of the block.
So with this particular design of a ZK-EVM, would you say that this is the end state of, or the end goal of a ZK-EVM, or do you think that further designs and further iterations will actually change the basic fundamental primitive, or do you think that this is the design structure that we're going to go with for the foreseeable future? I think the design structure, the architecture, the big picture is going to remain roughly the same. There are a few things which I expect to change. So first of all, I have to clarify that when we say ZKVM, it doesn't really mean that we execute EVM bytecode. What we execute is the virtual machine bytecode, which is optimized for zero-knowledge proofs.
And we have a compiler from Solidity and from Viper, which and from intermediate code, like any other languages, going through LLVM, which is a very optimized, very well-known compiler platform, compiling into this ZKVM bytecode. And then we execute this efficient bytecode. So LLVM actually allows us in the future to integrate other, like most modern languages from Rust to C++ to GoLand to Python, whatever, all of them have frontends for LLVM. And then we can reuse those frontends and then use our backend to produce the resulting bytecode. So if people will find other languages to be more useful for specific tasks in the future, then they will be using those.
And generally, I also think that in the further future, we will switch from pure Snarks based on Plonk to something fully transparent that doesn't require a trusted setup. But generally, the architecture I expect it to remain roughly the same. Well, opening up the design space for developers to make life easier for developers is, of course, crucial for building out ecosystems. We're going to definitely talk about that later in the show. One last question before we get back to some of the basic stuff about the testnet. Is this ZK Sync's breakthrough? If breakthrough is the right word, is this ZK Sync's breakthrough, or is this just kind of shared knowledge?
Is this your guys' victory here with the design pattern that you've discovered, or how is this design structure being shared around just the greater ZK roll-up ecosystem? I think it's a general approach. It lies on the surface. So we independently came to it from guys from Stackware, for example. But we are building on the shoulders of giants. We are using the pattern of TinyRAM, which was introduced actually by founders of Stackware also a few years ago uh but then uh we we're using this like we invented this approach of combining the uh the heavy and and flexible parts together i think independently from from other teams but i i can confirm because i don't know what their decision process was okay alex so uh tell us uh what is here today in the here and now with the zk sync 2.
0 public testnet release which is a zk evm on testnet so what is this uh the the subtitle is the zk evm has arrived the first evm compatible zk roll up on ethereum's testnet so what does this look like in practice how mature is it and then you know after this the question we're about to ask is uh when mainnet but first tell us what's here now uh well what you have now is a separate testnet where you can deploy smart contracts written in solidity and you can interact with them using web3 api which you normally use with other ethereum dabs so it looks very similar to other l2s and side chains that people are currently using for scaling uh just that it's based on zkvm technology so how mature is it is it uh we the this announcement is about the opening the test to the public it's been running in private for quite some time.
We had teams building on it and we were collecting feedback and fixing problems. So we wanted to release something to the public that is more or less mature and people are not having children's diseases. So Alex, what are the goals of this testnet? Are you trying to get developers to like try and break it or are you just allowing them to get a feel for what it's like to build on a CK EVM? What are you looking to get out of this testnet? It's well, we're just offering people to start building because the interface won't change. The interface will only be extended by certain things which which are clearly documented in our docs.
But the basics will just work. So we wanted to show that you can take your existing code and deploy it without modifications or with only minor modifications. And it's really important that you can reuse your code bases across L1 and different L2s, and you don't have to worry. You don't have to rewrite everything completely from scratch. You can rely on existing security patterns, which you understand well. You can use code bases that have been heavily audited. It will all just work. And yeah, we intend to release the mainnet as soon as the test initials mature and everything around the full specification is fully implemented.
So Alex, can we talk about that for a minute? So say I'm a DeFi app developer and I have something I've wired up in Solidity. It's working on the EVM right now. Maybe that same Solidity app, I've now ported that to like Polygon, for example, their proof of stake network. Maybe I'm trying to port that to you, Arbitrum and Optimism as well. If I take that code and I try to deploy it on the zk-sync testnet, how much modification is really required there? Because our understanding is that there's like degrees of the modification that is required. And could you contrast that with maybe what something like Starkware requires a developer to do to port their application?
Absolutely. So the degree to which you have to make modifications depends on what your program is using uh if you are uh if you have just generic code most likely you will not need to change anything we support most things most uh primitives including creating contracts create create two uh you know like hashes all the ethereum hashes which by the way translate to the same you know we actually like if you if you use ketchup it's going to produce ketchup hash if you use SHA-256, it's gonna use SHA-256. We're not replacing them under the hood as previously was thought of that we'll need to. So there are a few things that are just not supported yet.
So if you rely on them, you will either have to wait or you will have to circumvent those by the code, replace them with something different. Those are some certain cryptographic primitives. So we don't support pairings yet. We don't support mod operations, although the compiler will soon also bridge that functionality. And we don't support native ETH sending and receiving. So you have to wrap ETH as a ERC20 token for now. So apart from that, everything should work. And whatever is not working is clearly documented. Could you contrast that with Starkware? So far, a lot of that sounds similar to some of the optimistic roll-up style EVM change that we've seen.
But how does that compare with Starkware? I mean, I understand they have a different programming language. They have a completely different programming language, which you have to use from, like you have to actually rewrite your code from scratch in that language. They have a transpiler, but I'm not sure to what degree it's functional. And my understanding is that it will produce Cairo code, which you will have to then manually review and adjust. You can adjust, like keep your code in solidity, but maybe I'm wrong here. But in any case, the input for StackR compiler is called Cairo. Whereas for us, it's EVM code.
And what's really important, we support the same Web3 API as all the other devs. You most likely will not have to change your interface. You will be able to rely on the interface and you will be able to integrate services or have integration of services that already implement this Web3 API, like Etherscan and the graph and a bunch of tools that work with EVM today on mainnet and on different L2s. And they will just work out of box, which is not the case for Kyren as far as I know. I want to just reorient to the user's perspective here. So are you saying that it could come to pass that your favorite DeFi application, say an Aave, a Compound, a Maker, a Uniswap, same interface you're using on the existing Ethereum mainnet with high gas fees, of course.
And then one day you have the option with the exact same interface to use ZK Sync instead. And it's all, you know, EVM, ZK under the hood. And suddenly your gas fees drop from like dollars to cents. And from a user perspective, you know, it's the same kind of UX experience that I've always received, except now there's far lower gas fees. Is that the sort of thing that we can expect I mean, same block explorer, same wallet, same user interface, just lower gas fees? Or is it going to be a bit more incremental and clunky than that? No, it's actually the exact same user experience. So a big part of that is that we allow people to reuse wallets.
So any Ethereum wallets works natively. And the keys are actually kept in the wallet. So you can sign a transaction, you just sign it from the wallet. So that's really important. and say, yes, this allows for the migration of the entire ecosystem on us. So you bootstrap the ecosystem by default. You don't have to write all of that transfer. I think Argent is maybe one example of this. People, are they using, they're using ZK Sync. I'm not sure if they're using the ZK EVM under the hood. But Argent is kind of a wallet wrapper that's generally been on Ethereum for most of its life. And now it's starting to spin up wallets on ZK Sync.
Is that an example of this? Are they using the same infrastructure technology here? Well, Argent is a really interesting example of... So Argent is on the mission to allow mainstream adoption for Ethereum in general, because they solve the problem of security and usability. You don't have to mess with their seed phrase, which is hard for most people. They don't understand security of it. they have never been hacked in their history of Argent. So right now we integrated Argent with ZkSIM version one where people can make transfers, can make trades and can interact with existing DeFi contracts on main Ethereum through badges with liquidity providers.
But it's also going to be used on version two and for the users the experience will remain the same you you will just have more functionality because you will be able to interact with contracts on it to also directly uh so what when i say the experience is going to be the same it's actually not true because the experience is going to get better so uh there are a lot of things which will be possible on uh where to which are currently limited in ethereum for example account obstruction So it thinks Argent, for example, will work much better on ZK-SYNC than it works on Ethereum. It's going to be a lot cheaper and easier to maintain the code.
You will not need relayers. People will be able to interact directly with the peer-to-peer network to propagate transactions. People will actually be able to pay native gas, not just in ETH, but in any token they transact in. So it's going to open a lot of possibilities. And also for other use cases, other dApps that will do interesting things with the counter-obstruction, with meta-transactions, et cetera. This is why a lot of people in the Ethereum ecosystem think that the ZK EVM, ZK roll-ups are going to unlock the golden age of UX for DeFi, which is something that we've just been missing basically since the entirety of DeFi's existence.
And Alex, one of the properties about optimistic roll-ups is that both arbitrage and optimism just boast about how you can just take your code and immediately deploy it on an optimistic roll-up. And that's one of the benefits of optimistic roll-ups is that it's just a very low-touch transition. And that's what I'm hearing coming out of you and ZK Sync is that it doesn't actually take all that much work to deploy your code on ZK Sync, which is just phenomenal because we already have so much of DeFi built out on the Ethereum L1. As soon as just being able to copy and paste it and put it on a ZK roll up is it kind of almost sounds too good to be true.
But what I do know that I want to check with you is that while we do have this benefit of just being able to copy and paste and put it on ZK Sync, the developer tooling, I think, still is going to be something that the ZK EVM ecosystem needs to build out. Because the developer tooling for building DeFi on the Ethereum L1 has been extremely robust because that's what we've been having. That's what we've had for the last six years. Is this an important conversation when it comes to building out the ZK EVM ecosystem? How much rewriting and just like rebuilding of the developer tooling needs to be done to truly enable developers to unlock their full potential for building out DeFi on a ZK EVM?
Yeah, this is a great question. So we have to split developer tooling into two categories. One is the tooling around the code itself. And the other one is general tooling around smart contracts, deployment, and so on. So the second category is completely covered by our support of Web3 API. So things like Etherscan or the graph and so on will just work out the box. Chainlink oracles, stuff like this? Chainlink oracles and so on. Yeah, so this will be all provided by default. Now there is a smaller part of the developer tooling is like when you have to debug your code where you have to see what's happening and by the way also events are fully compatible with ethereum so like uh so like everything around the where like code doesn't matter will work everything what concerns the code will have to be adjusted but that's a small part and we're working with teams to uh to make those changes and to provide whatever you need to make it work.
So for example, we built an extension of the hard hat plugin for ZK-Sync to just deploy contracts. Like you can use your hard hat to test, deploy, compile, build contracts. And yeah, so like if you tools will have to be adjusted. How much of a lift is this going to be? Can you kind of measure how much work needs to go in in order to provide developers a comparable developer ecosystem to building on zkSync? As I said, the tools that are missing or need adjustment are a minority. So it won't be much. We expect everything to be fully functional within a few weeks, months from now. Alex, you said earlier that we're talking about not just the same UX as the Ethereum mainnet people have come to expect, but better user experience potentially in this ZK rollup enabled world.
Can we also, because this is not something we've talked about yet in the show, but we've talked about on many Bankless episodes, including our episode on monolithic versus modular blockchains that people can go back and listen to. But can we talk about the decentralization that we're trying to preserve here? It's like, take us a few notches above. Let's go to the higher level and talk about why are we going to all this effort in the first place? Why ZK roll-ups in the first place? And what sort of trust assumptions exist in something like the ZK EVM? What are we trusting versus other techniques and other chains and monolithic layer ones?
Talk to us about that. So this is a really interesting question, which goes to the roots of why we were building ZK-Sync in the first place. So we started with a very clear mission. and it's still rooted as the, like, we are very, very mission-focused project where we want all the world to go bankless. We want people to have full control over their financial assets and be fully self-sovereign. And that means we need to go absolute mainstream. Like, we need to be able to serve millions of people, billions of people without limits. We can only do this if we keep resilience of the network. We cannot have centralized entities performing like, you know, it would not even work physically, that we have one entity that controls all of the internet of value, where all of the transactions have to go through the bottleneck of a single server or a few a few old circles, right?
They just won't work. So we need to decentralize these things and we need to make sure that they cannot be killed by really powerful actors because what we see right now in the world that politics is going way beyond what people would entrust them with and taking too many authorities on them so we want to keep these limits in place. So ZK rollups are the only technology we have today that can allow truly limitless extension of this internet of value. The reason for this is since we cannot have a single cluster where everything will be happening because we will be limited by a throughput of a single consensus of decentralized nodes or a single drift to peer network or single data availability sharding system and so on we'll have to have many of those clusters and they will need to be able to trust each other and trust each other in in an objective manner when i say objective i mean like machine machine, not people to people, because you will have like an internet, you have a whole big network of those subnets that interact with each other.
So whenever you pass a message in internet, the systems on the other side of the world can verify the digital signatures, they can verify encryption and see that it's coming from the person or the entity that actually produce the message uh with digital with the word of value it's a lot harder because we we're not just passing messages we're passing value so we have to trust that consensus mechanisms were enforced in the other subsystems and we preserve the scarcity so like if you send something from one side then it actually disappeared on that side and if you're on the other side and this requires this fully objective way to do to check that like you can trust the the seller systems uh and this is only possible with your knowledge proofs uh for the reasons that uh vitalik uh explained in in recent posts about um bridges uh we we can try to go into them and explain it more technically.
Alex, I'm curious if you agree with the bottom line here, which I've heard described with ZK, the ZK EVM, is basically you're trusting two things. You're trusting one, the security of the Ethereum mainnet, and two, you're trusting ZK math, that kind of cryptography. Are those the two trust assumptions, or are there others here? Those are the two trust assumptions. With the cryptography, if you rely on trusted setup, you would also trust the correctness of the setup, but that's kind of minor and transitory. We expect in the long run to not be required. But yes, you trust Ethereum as the settlement layer and the main data availability layer and the source of consensus.
And you trust the math and the code that implemented this. And is there like with ZK-SYNC EVM right now on testnet and, you know, I still haven't asked about the date of when mainnet, which we'll get to, I promise. But are there any kind of centralized operators in the mix here? Are there any sort of escape hatches? I know many roll-up solutions have sort of left in some centralization vectors on purpose because they are still testing the systems. How about in zkSync? Are there still some centralization vectors that you have in place in these early stages that you plan to take away later on? We do have centralization of the sequencer right now because it's a lot easier and faster to develop.
So all the transactions will have to go to the central server, and the server then produces the box. And this is only for a short time until we have L2 consensus running, which will be fully decentralized. But where we're not willing to take any compromises is the security of the assets. And the security prerequisite for that is that you have this escape hatches. What this means is you should be able to enforce any transaction so like if you have any money in l2 on the casing any assets you should be able to take those assets out if you don't trust the network anymore if the network becomes malicious either because the server is compromised or is just down and is not responding or if you don't have a server maybe you have a consensus mechanism uh governed by by some community by send out but maybe the majority of the stakeholders is compromised or was subject to malicious takeover so you just don't trust them anymore you should be able to go to ethereum as a court of higher appeal and demand your assets be up uh and like this is what we will have from day one on uh zk sync uh and this is actually a big difference from uh from starknet starknet uh for example they they they took a decision to implement um zero knowledge proofs in a slightly different way and they cannot currently build this enforcement mechanism because they cannot prove that a failed transaction failed they can only prove successful transaction um so we we decided to take additional overhead in the way virtual machine works in order to be able to prove that any transaction you made a call to this address to these arguments this call was coming from ethereum mainnet uh as like through a priority queue which enforces transactions and then we can prove that here is the outcome of this call here here is what happened.
And like what could have happened is the transaction failed and nothing executed. But we will still include this transaction and we will still need the proof that it's not executed. And for the listeners that are familiar with arbitrage and optimism, and they also have centralized sequencers at the same time. So zkSync is about comparable with the current centralization levels of the other rollups that users might have already interacted with. And basically what a centralized sequencer means is just that ZK-Sync, Optimism, Arbitrum are the people that are ordering the transactions in the roll-up.
And so this is kind of par for the course for where we are in the current state of roll-up technology. Alex, I have a question here coming out of Justin Drake, and I'm going to actually have to ask you to help me ask the question and understand the importance of it. But he asks, can we ask about the prover cost denominated in either US dollars or gas and also the prover setup, as in what type of AWS instances they use and how many? Alex, why is this question significant? And also, what's the answer? It's significant because it puts some limits on what the minimum transaction costs will look like.
and I can share that it of course it depends on the type of transactions and on what operations it employs like a single transaction can be having a lot of storage accesses and a lot of execution or it can be like something very simple like a token transfer but in general the costs estimates do not differ much from the cost costs on version one so you can like zk-sync version one you can think of the transfers there as uh uh you know like using roughly the same computational power as what we will have for like simple erc token transfers or uh ethereum transfers in v2 and right now the uh the basic cost is something like 0.
1 cent uh and and this remains like the basis so a simple transfer cost list. Now if your contract call requires multiple transfers and some other logic and some hashing then it will be added on top of that. But that's the proof of costs. But of course in the roll-ups, costs are always dominated by the data availability costs. So this is going to be the case for all roll-ups. We are all using the same Ethereum bandwidth space. we are competing for it so uh the like the more usage we'll have enough to share by rollups the higher this cost is going to be we already see it in um you know like optimistic rollups are not cheap uh easy care all ups are not like not as cheap as uh some side chains because we still have to pay those costs to ethereum uh but the beautiful thing about zk sing is that we actually plan a volition called zkporter so the users will be able to choose uh how they want to they to secure their data available do we want their account to live in in the roll up where they have the full security of ethereum this theoretically like spare box or they are they are willing to accept certain risks uh and have their data they will be secured by a group of of special actors called guardians, which is still pretty secure and like incentive aligned with the interests of the user, but they will pay a lot less.
So if a roll-up transaction will cost, let's say $1, then the portal users will pay maybe one cent. That's really great. And I think that's helpful. So, you know, for bankless listeners, once again, I would refer you to that podcast, the, you know, monolithic versus modular design podcast to make even more sense of what Alex just said. But, you know, a base understanding is the Ethereum scalability strategy and the modular design is we have three layers. We have the consensus layer, the data availability layer, and the execution layer, right? The execution layer is what's happening. The data availability layers is what's happened.
the consensus layer is what's true, okay? And then Ethereum in this design, the main net, remains the consensus layer. What you were just talking about, Alex, is ZK Sync being an execution layer and then using ZK Porter for some data availability, right? And this could further reduce the costs of transactions. And it's user-dependent, whether they want to use Ethereum for data availability or whether they want to use ZK Porter for data availability. So that's a whole topic in and of itself, and it's super cool. But the net result is two things. One, transactions are about to get a hell of a lot cheaper.
Good news for DeFi. And number two, what Alex just said is super cool, is all of the roll-ups, all of the execution layers are competing for us right now. You guys are all competing for us. You're competing for DeFi users. That is a great thing, I think, for the ecosystem because it brings a lot of innovation. Alex, want to ask one more clarifying question on all of this, which is getting released. And this is kind of a roadmap type question. So ZK Sync 2.0, the EVM public testnet is live. That just went live last week, I believe. You've already had ZK Sync out in the wild. Here it is on a Layer 2 beat.
It has 74 million in total locked value. It's a ZK rollup. Can you talk about the difference between the ZK-SYNC that's out in the world today? And people have used this, I've used this before, for payments, for example, and the ZK-SYNC that you just released to public testnet, and the trajectory of what's next and how that relates. Should we think of the ZK-SYNC that's on mainnet right now as kind of a 1.0, and this new EVM compatible ZK-SYNC is sort of the 2.0? Is that the way to think about this? That's absolutely correct. The ZK-SYNC 1.0 was an application-specific ZK roll-up, which you can only use for payments and swaps.
And since last summer, also for NFTs, but nothing else. You cannot have arbitrary contracts. Whereas ZK-SYNC 2.0 is the full extension of Ethereum, where you can deploy anything. and you can build the entire ecosystem there. So this is like going from a Nokia 3100 to an iPhone. Well, I think that's the part of the story that everyone is really excited for. Alex, we have some questions that we still want to ask, such as how we go from testnet to mainnet, when we go from testnet to mainnet, and then, of course, when token. So we got these questions lined up coming for you next, right after we talk about some of these fantastic sponsors that make the show possible.
When you shop for plane tickets, you probably use Kayak, Expedia, or Google to compare ticket prices. So why would you limit yourself to just one exchange when you trade crypto? When you make your trades, you want to make sure you're getting the best possible price on your trade. And that's why you should be using Matcha. Matcha has smart order routing that splits your trade across all the various liquidity sources in Ethereum and is also operational on Polygon, Avalanche, Binance Smart Chain, and other chains. Trading on Matcha is super easy because it pools the liquidity for me in a single easy to use platform and allows me to make limit on-chain orders so you can set and forget your DeFi trades and they will go through automatically while you're away.
So when you're making a trade, head over to matcha.xyz slash bankless and connect your wallet to start getting the best prices and most liquidity when you trade your crypto assets. The Gemini exchange has been my exchange of choice ever since I got into crypto. I use Gemini to both buy the dips and also manage my regular automatic monthly purchases of my preferred crypto asset. On Gemini, you'll find over 50 different cryptos, including many of the top DeFi and Metaverse tokens like YFI and Axie Infinity. Using Gemini Earn, you can earn yield on your various cryptos, including 8% on the GUSD stable coin.
Gemini is available in all 50 states and more than 50 countries worldwide. So if you're looking to upgrade your crypto exchange, sign up at Gemini with Gemini.com slash GoBankless and get $15 of Bitcoin after you trade $100 or more within the first 30 days. That's Gemini.com slash GoBankless. Bankless is proud to be sponsored by Uniswap. Uniswap is a new paradigm in asset exchange infrastructure. Instead of a cumbersome order book system where trades are matched with other humans, Uniswap is an autonomous piece of software on Ethereum that lets you trade any token at the current market price.
No human counterparties or centralized intermediaries, just autonomous code on Ethereum. Input the token you want to sell and receive the token you want to buy. The Uniswap grants program is accepting applications for grants. Do you have something of value that you think you want to contribute to the Uniswap ecosystem? No matter how big or small your idea is, you can apply for a uni grant at uniswapgrant.org and help steer Uniswap in the direction that you think it should go. Thank you, Uniswap, for sponsoring Bankless. All right, guys, we are back with Alex from ZK Sync. We're talking all about the current EVM, ZK EVM testnet.
But I want to hear, Alex, about when it becomes the ZK EVM mainnet. So how does that transition look? Are we just going to wipe the slate clean with a testnet and start from scratch? Or are we going to roll the testnet into a mainnet? How is the transition from test to main going to happen? And then also, when is that going to happen? So the testnet, from the developer perspective, is going to remain essentially the same interface. As I said, a couple of features are coming. But the contracts that are compilable and deployable now will just work. You will not need to do anything. We expect one major upgrade of the virtual machine to happen before the mainnet happens.
It's already on the way, so it's a different version of compiler and a virtual machine, which has been developed in like entire server. And then just making sure that the testnet is mature and we can cover all the functionality and everything just works. And yeah, we're not going to delay it for unnecessary reasons. We have cut, in our roadmap, we have cut all the unnecessary things and we want to get to the mainnet as soon as possible, in the shortest possible way. And so is the state of the testnet going to be preserved as if a developer deploys like SushiSwap or Uniswap on ZK Sync? And then it goes into mainnet.
Is all of the state of the smart contracts and the assets on the test net preserved into mainnet? Oh, no, no, no. The test net is test net. Think of it as a Rinkaby or Gurley or Kauffman test net for Ethereum. It's a completely separate deployment. So it's actually tied to a particular Ethereum test net. I think it's now we're on Gurley. So we actually have a deployment of ZK-SIM contract on the Ethereum test net, which the L2 state is attached to and will do. So Alex, how long are we talking here? I mean, there's this phrase in the Ethereum world that's become popular, weeks, not months, right?
Are we talking weeks? Are we talking months here? Are we talking years? We're realistically probably talking months, but not years, for sure. Okay. It will happen this year. Before the merge. When's the merge going to be, David? June 14th. I did not say that. Okay, so Alex, I think the other question that everyone really wants to hear is, when token? Well, that's also an interesting question. So we're going to deploy ZK Sync in stages. In the first stage, we're only going to deploy ZK Rollup, which does not yet really require a token. But the token is really needed for ZK Porter because we need to secure the data with something that has inherent connection to this data.
That like, you know, like we will have consequences if the data becomes unavailable and it's hard to manipulate. So we, yeah, we will definitely need token for that and we will need the token to introduce layer 2 consensus. uh and we also don't want to delay those things so they are next on the roadmap right after launching the payment so the the token is needed to uh slash people that do not secure the zk porter appropriately and then it's also needed to decentralize the sequencer are those the two use cases that you just stated uh that's right although we don't we're not gonna slash individual people securing the data, this is pretty interesting.
In DKE Porter, you are never slashed. You just like, you're taking risks if you don't provide data. Like you are only slashed if you are not providing data that you previously agreed to provide. This is very different. So under normal circumstances, you never need to provide this data. It's only required in the case when the operator becomes malicious the validator consensus becomes malicious and like stop serving users which hopefully never happens uh but um you as a user you actually don't have any consequences you you you should not be afraid of running a guardian node that secures the k-sync on your ordinary laptop or or even you know like when i own this machine in the cloud that you control there is nothing like nothing can go wrong immediately if you are compromised unlike staking in in normal consensus mechanisms so is the theorized one of the theorized uses of the token is to to validate the zk roll up the zk sync and then receive compensation or fees from the from the sequencer and so if you are if you are validating on on zk sync you get to order the transactions and then the incentive would be that you get to extract some amount of MEV from the ZK rollup.
Is that right? Or perhaps is that right? So, yes, if you are a validator in the ZK sync, then you are the sequencer. The validators will serve as a collective decentralized sequencer. And yes, of course, you get some fees from the users to you for this work that you provide. Do you have any details or notes? Because we want these things to be decentralized. But then when we mint this token, it starts off centralized. Do you have any notes for us on how you plan on what the theorized plan is from going from a centralized token supply to a decentralized token supply? So you mean... How are you going to defuse the token?
How are we going to defuse the token? This is a big question which I'm not ready to answer now, but it must be done in a way that maximizes decentralization. Because with data availability, you don't want them. The malicious majority can do as much harm as comparable to the side chain. So it's not just about the controlling the sequence of transactions or extracting MVV or something like that. It's really a matter of security. And it's really, really important for us to get it in the hands of individual people. And this is why it's important that you can run a Guardian Note on a normal laptop.
Because we expect the, and also there no latency requirements. You don't have to be online all the time. You don't have to be online with a super fast internet. You can just run it on the laptops. We expect a lot of people to contribute to actually become validators. Just like they run Ethereum full nodes right now, requirements will be roughly the same, but you get paid for it, unlike Ethereum. So we think the decentralization of the portal will be very, very high. And it must be reflected in the initial distribution of the token, which we'll have to design accordingly. That is fascinating. I hope Bankless listeners are reading between the lines here a little bit.
I mean, we have confirmed the existence of a token. It's necessary for the operation of ZK Porter and for the ZK Sync consensus layer. Don't have an answer on when token, of course, which is very difficult to answer, but it feels like it's a prerequisite for both of those two technologies. And it also feels like there's great opportunity to get plugged into this ecosystem and start giving the network what it wants. What does the network want? It wants developers. It wants users. It wants liquidity. It wants decentralization. Give it those things. Start trying to run some of this infrastructure.
Run guardian nodes. that's my footnote I think on everything you just said Alex there's also this other entity here called ZKDAO that has recently spun up can you tell us a bit more about ZKDAO what is this and how is it related to the primary ZK-SYNC project that we've been talking about so far well ZKDAO is a separate thing it's a cooperation with uh bit dow uh that pledge to to support the uh l2 ecosystem and invest in projects and support projects that are building on layer 2 um uh and yeah so it's it's open for as a source of funds for uh developers which we encourage to um to start using and that was uh 200 million dollars I think BitDAO committed to funding the ZKDAO with $200 billion around coordinated milestones.
So it's another way for bankless listeners to get plugged in. Go check out what ZKDAO is doing. I think they're just getting spun up right now. Alex, before we shift the conversation to Ukraine a little bit and talk a bit more about that, is there anything else you want to tell us that we haven't touched so far that you think is super interesting for the community to know about ZK, Sync, and your plans moving forward at Matterlabs? I think that the... I touched on this already, but it's really important to understand that zero-notch proofs will be the technology that will enable us to go to this completely limitless internet of value.
And this is going to change... Yeah, this is going to change the world, I think, in the way how freedom is promoted and how self-sovereignty is promoted because literally everyone will be able to get a grasp of those things. And we'll see the transformation of social media, of everything powered by this technology. So, yeah. As we shift the conversation, Alex, and thank you so much for your massive contributions to the space. On behalf of us at Bankless and crypto, we believe very much in the principles of decentralization. And you guys are painstakingly building out those value systems into the code that you're pushing out there.
And it's just fantastic to see. So as we transition the conversation of Ukraine, I'm just kind of curious to hear a bit more about your personal story, because it feels like you've got a story in Ukraine, having been born there, interested to hear about that. And then why crypto became important to you as well. So I guess, first of all, high level, what's your lens on everything that's going on in Ukraine right now? And how do you think the crypto story dovetails with that? Does the crypto industry, the technology that we're building, does it offer any solutions, any help to some of the conflict that's going on?
What's your take here? Yeah. Well, I was born in Soviet Ukraine. I grew up in Ukraine when I was very small, when Ukraine became independent. And the conflict we see now is really a continuation of the tragedy that the country experienced with the Soviet rule. And this is direct cause of, for me, what brought me, this is systematic, the root motive that brought me to crypto. Because as a kid, I saw the consequences of the centralized economy, centralized political system playing out on the society, where everything collapsed. Not that it collapsed, it just never really worked in the first place.
The Soviet Union was a total mess. It was a completely inadequate system of governance, an economical system where everything was in shortage, shops were empty, everything was disbalanced, people were dis-motivated. few branches that enjoyed a lot of attention by the government like military got some degree of you know world uh achievements but the rest of the country was completely in shape so uh what we see now is like the empire strikes back and wants to take it back because the uh processes in russia took it back earlier than than what we've seen now um and the Antidote to this is to give more power to people.
Economical power, which will enforce their political powers. The sooner we can get there, the less likely such scenarios on a huge scale will actually play. You have a single person which is capable of taking decisions that will destroy the world or destroy entire countries. because everything is subordinated and highly centralized. So I was, I think, seven when there was a high inflation going on in my country where prices would rise by 30% every single day for a period of a year. I saw how that works. so I was surrounded by people that were highly mistrustful of governments and banks for sorts and since then I once made a collage of bank financial or other types of crisis involving money that happened in the world ever since then like almost every year in some part of the world and sometimes globally where people could not get money from the banks, where you could see the queues before ATMs, where the economy would stop working, like you would get capital controls, you would get mandatory orders to sell foreign fiat reserves and stuff like that.
And you would see people losing all of their fortunes overnight that they were working really hard to get and were hoping to pass on to to their kids. A lot of tragedy, a lot of suffering that all roots down in the way the society is organized. Freedom is lacking because certain groups of interest want to preserve their interest and they're abusing the power. Most of the people in the world live under corrupt regimes, they're not living in democracies. Even if you live in a democracy, you can have a situation like you know we recently have in canada uh where money is being confiscated without court orders without any like any even like pretext of some legal uh decency uh so it should be a really really strong message to everyone like it will only stop if you don't let these things to happen And the way to not let this happen is to have full control, to empower the individual and not some authority that claims to work on people's behalf.
And to me, this is what crypto is all about, starting with Bitcoin and then extending with Ethereum, which gave it a lot more powerful capabilities to build really, really interesting things and expand it like to actually absorb all of the world's finance all of the world's uh values into this huge internet of internet 2.0 3.0 alex there's been a number of just examples of how crypto has been a part of this story there's a ukraine dow that has helped raise four million dollars there's the the bitcoin volumes jumping to all-time highs in the russian ruble to the due to the devaluation of the of the ruble uh there are stories of people being able to maintain their wealth as they flee from kiev and other ukraine stories because of the power of private keys are there any stories that you've heard that have stood out to you as uh examples of like crypto really helped here is there any any stories that you've heard that you can share with us uh well they just the donations uh is is is a really big powerful thing uh because it's it's really, you know, banking system is not reliable, it was already hard to send money in Ukraine for certain things, like sometimes money comes back, it's just like a lot easier for for you to donate.
And I actually I spoke personally to the founders of Ukraine now, the Unchain fund, the people who manage the like people from the Ministry of Digital Transformation donations the Twitter at Ukraine. All of them are legit. Please donate because as we speak right now, there is war going on and people are dying, people being bombarded, civil citizens being bombarded. Please do something. There are close to half a million refugees now on the borders with 20-hour long queues to just leave the country. Not everyone can leave a huge tragedy, huge humanitarian crisis going on. So please donate. Well, we can definitely get those links into the show notes.
I'll do that as I ask this next question. Do you have any idea how, when we send Ether or Bitcoin to the addresses that have been generated and verified by the Ukraine DAO and the actual Ukraine digital organization, how does the Ether that we send or the USDC that we send, How does it actually translate into actual help on the ground? Do you know how those two things are bridged? Yeah, so they either sell it in Ukraine for Hryvnia and send it to bank accounts or just get cash and pay people in cash for the goods that are needed on spot. Or they sell it abroad on foreign accounts and purchase stuff that helps people and transport it back into Ukraine.
Alex, I'm curious as well. What does the crypto community look like in that part of the world, Ukraine, even parts of Russia? Is it strong? Is it robust? Just in general, what does it look like? Well, there are a lot of technological projects coming from Russia and Ukraine, with a lot of Russian and Ukrainian developers, because the mathematical and scientific school in Soviet Union was pretty strong. because it was necessary for the defense and military. But the good outcome is that we have a lot of smart people who are really well trained in mathematics, programming, and they're building stuff.
There is less crypto business crypto projects, like most people who are founders of some projects like uh guys uh from meteor protocol uh solana is part of the family by ukrainians uh a lot of others they're mostly in the west because like crypto is a truly global movement and it doesn't know boundaries and like people just move around and most people are just nomads to the information purposes as i've put the donation addresses of bitcoin and ethereum which have been verified into the YouTube show notes. So if you're watching live, you can go ahead and refresh the page and the addresses will be there available to you.
And they'll also be in the podcast show notes as well. Alex, thank you for your perspective and also just sharing everything else with us on today's State of the Nation with ZK Sync. So thank you for your time, sir. Thank you guys. And thank you all of our listeners. It's an incredible privilege to talk to you, to talk to folks like Alex. I'm saying this to you, to Bankless listeners. You know, I know we've had many generations of freedom fighters. And Alex, to me and his team is an example of the freedom builder, which is fantastic. This is truly a technology for the people and by the people, whether you're Russian, Ukrainian, somewhere from the West.
You know, this is why we're on the bankless journey is for decentralization, for power back to the people, self-sovereignty. So it's a fantastic story to see. anyway guys risks and disclaimers of course none of this has been financial advice it never is eth is risky crypto is risky so are roll-ups at this stage in the journey so is defy you could lose what you put in but hey the world's kind of risky too so what do you have to lose i don't know we're headed west though this is the frontier it's not for everyone but we're glad you're with us on the Bankless journey. Thanks a lot. 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.