🇫🇷 Welcome to the Bankless EthCC 2022 Experience 🇫🇷
With fantastic guests from all corners of the ecosystem, this 8-part series is an exploration of crypto culture and the current state of Ethereum.
In episode 4, Mihailo Bjelic joins us to discuss the announcement of Polygon’s zkEVM. This explosive headline comes alongside three other zkEVM announcements.
Why now? What does this all mean?!
------ 📣Rhino.Fi | Massive Mystery Airdrop https://bit.ly/3o9trRE
------ 🚀 SUBSCRIBE TO NEWSLETTER: https://newsletter.banklesshq.com/ 🎙️ SUBSCRIBE TO PODCAST: http://podcast.banklesshq.com/
------ BANKLESS SPONSOR TOOLS:
🌱 LENS | ACCESS CODE: WAGMI https://bankless.cc/Lens
🚀 ROCKET POOL | ETH STAKING https://bankless.cc/RocketPool
⚖️ ARBITRUM | SCALING ETHEREUM https://bankless.cc/Arbitrum
🦁 BRAVE | THE BROWSER NATIVE WALLET https://bankless.cc/Brave
🌉 JUNO | BRIDGE FIAT TO LAYER 2 https://bankless.cc/Juno
⚡️ ZKSYNC | THE LAYER 2 SCALING ENDGAME https://bankless.cc/zkSync
------ Topics Covered:
0:00 Intro 3:00 Polygon zkEVM Announcements 6:50 How it Works 10:00 Road to Maine 15:30 EVM Equivalence 19:30 EthCC 2021
------ Resources:
Mihailo on Twitter: https://twitter.com/MihailoBjelic
Polygon: https://twitter.com/0xPolygon
----- 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.
No summary for this episode yet.
Welcome back to the ETHCC experience. We are almost halfway through. This one is with Michalo from Polygon. Polygon was super hyping up their announcement, which they announced at the ETHCC number six conference, which was their ZK EVM. As it turns out, fate would have it decide that they were actually just one of three teams that decided to release their ZK EVM during ETHCC week. ETHCC is big like that in the sense that people wait to release their announcements for ETHCC or they rush to get their thing announced at ETHCC. ETHCC is actually quite a big deal as far as conferences go. Polygon waited for ETHCC to release their ZK EVM, but the ZK EVM wars are on.
We talked to Michalo about everything they're doing with the ZK EVM at Polygon and of course all the other peripheral topics around Polygon. There's a fun little backstory because I was talking to hang out with Michalo at the last ETHCC and which is really where the ZK EVM announcement really got accepted behind the scenes way back when with a phone call, which I was just like sitting with my good friend Mariano Conti and having a beer with Austrian and Mahalo when he received a phone call. Fast forward one year later they released a ZK EVM test net as a fallout of that phone call. It's a fun little story.
So we tell this story and more in this fantastic episode of the ETHCC experience, but usually we do our full prerecorded ads, but instead I'm going to do them all right here right now super fast. So here we go. One of the big themes of ETHCC week was the launch of the ZK EVM. Three different teams all launched their test net and while everyone is trying to claim who was first we can confidently say that ZK Sync has been focused on the ZK EVM for the longest. The golden endgame of the ZK EVM has been the vision of ZK Sync since the beginning and during ETHCC week they launched their 100 days to main net plan, which is now already down to 93 days.
So if you get to join the ZK EVM Wars, make sure you post about it on lens. The first decentralized social networking graph. In crypto we say not your keys, not your crypto, but on lens we say not your keys, not your content. Own your own social media handle, choose your own algorithm, and emit your profile using the secret code word in the show notes. And something that's likely going to be talked about on lens is of course the Ethereum merge. And the merge is why you should be staking your ETH with Rocketpool. It's a decentralized Ethereum Validator network where you deposit ETH and get your R ETH in return and then you can take that R ETH into D5.
And if you run a node you can let other people deposit their ETH into your node and you earn 15% of their staking commission as payment for your node operating services. And then maybe you want to take your R ETH over to Arbitrum. For all of your D5 things, Arbitrum is where you have to be. With over 35,000 contracts deployed and 1 million unique addresses, Arbitrum is leading the way into the age of rollups. You know how I know those numbers? Because I watched Arbitrum's talk at ECC, which you should definitely also watch, but not before you're done watching this video first. But in order to get your money over to Arbitrum, so you can buy your ETH natively, then you should use Juno.
Because Juno is the fastest bridge from your checking account to an Ethereum layer too. A checking account to an Ethereum layer too is absolutely crazy and it just takes minutes. Juno is your crypto checking account for the crypto era. But when you're doing all of these things, make sure that it's on a privacy first browser, which is why you should be using Brave. It blocks all the browser ads. It's got a native Web3 wallet and it puts the user first the Web3 way. And now I bring you my conversation in person with Rahalo from Polygon. What's up, Rahalo? How's it going? Hello, David. Just all over the place with all the great announcements coming from the Polygon side.
And yeah, thanks for taking your time to check. Oh, of course. Of course. Every time I see you at a conference, you're always moving a mile a minute. And it's always because you have something to announce. Yes, fortunately, it's like that. Yeah. It's a good place to be. So what is it this time, Rahalo? What did you guys announce this time? We are very, very excited. Today is a very big day for Polygon. I would say it's probably the single most important event ever since we announced Polygon. Today, as you probably know, and some people already saw the news, we announced ZKVM. So Polygon is the first project that actually shipped ZKVM, which is basically considered the holy grail of scaling.
So ZKVM, for those who don't know, is basically a ZK friendly EVM implementation. And EVM is, as most of us know, I guess, Ethereum Virtual Machine, the core execution component of the Ethereum itself. And for quite some time, we have been kind of, as a community, pursuing this holy grail of scaling that is going to have this free major, very important features in one. One is, of course, Ethereum compatibility, or Idle EVM equivalence, which is even step further. We ideally won't, we all know Ethereum is absolutely dominant in terms of developer, mind share in terms of tooling, the maturity of the ecosystem and everything.
And we, of course, want to leverage that. We want to stand on the shoulders of the giants, of the giant, and we don't want to waste all that great amount of work that the community has put so far in Ethereum and building all these tools and bullets and everything that we currently use. So with EVM equivalence, we get to leverage all that and keep the same exact same developer experience that developer are used to, same programming languages, same developer environments, et cetera. So that's what Idle EV1, that's the first major feature. The second major feature is, of course, security. So we know Ethereum is the most secure programming of blockchain in the world.
And ideally, of course, we want to leverage that security because in layer 2s, we still have millions or hundreds of millions of dollars and we really want, we really need highest level of security and that is what Ethereum gives us. So ideally, we want to leverage that. And the third major feature is scaling, of course. We need to scale significantly. We need to scale orders of magnitude if we really want mass adoption and if you want to onboard billion plus people to Ethereum. So this was that holy grail that ZK EVM has been representing until today, basically. And we are very fortunate and incredibly humbled that we were able to actually ship it.
It's full featured. It's fully open source, which is very, very important. Anyone can take a look at the code, examine, make sure, first of all, that it's really a full-blown EVM implementation with all the important top codes and everything. And then, of course, we want this to be a community effort. And like everything that Polygon has done so far, everything is, as I said, fully open source. We invite community to take a look at what we have built in the background, throughout this past year, to give us feedbacks. We expect contributions from other community members. So, yes, only an exciting moment.
Yeah. Okay. So, as ZK EVM, like you said, is considered like there are no further scaling like degrees beyond a ZK EVM. And since it's a developer conversation, it's going to take me a few questions to really fully unpack this. So, you know, there's general consensus that a ZK rollup is like the end state, kind of, as we said. It's that EVM part, that's the difficult part. We have, like, application specific ZK rollup. So far, the DYDX train used to be this. We had, like, diversify used to be a, like, a stark X-like app-specific chain. A few others, like, a mutable X used to be apps, a stark X app-specific EVM chain.
It's that generalizability, that, which is the ZK EVM, so the Ethereum virtual machine inside of a zero-knowledge rollup. And so, like, that's what we're talking about. So, that's been like the end goal. So, what was actually shipped today? Like, a mainnet? Or what was actually shipped? There is a road to mainnet that we have today announced. Of course, it's a very, any sort of mainnet is very high responsibility, especially given that we're really seeing huge level of interest for ZK EVM. Yeah. Everyone would like to try it, everyone would like to deploy, people would transfer capital. So, we want, today we announced this road to mainnet.
Today, we announced the code. Okay. We shared it with the world. Okay. The internet, internal testnet is basically days away, probably a week or something like that. Fully permissionless public testnet is weeks away, probably one month, roughly one month, one month and a half. It depends on several factors. But it's really, it will be live in a matter of weeks. And after that, the mainnet. Between public testnet and the mainnet, we really want public scrutiny. We really want multiple audits. We really want battle tested, you know, a test net that has been proven quite a while. So, it will definitely take several months, two to three months, I think.
So, we're basically targeting end of the year for the final mainnet release. But what has been released today is the code itself and everyone can actually see that we have basically re-implemented the whole EVM, which was, as you said, exactly the hard nut, the tough nut to crack, basically. Proving some of these expensive op codes of Ethereum, like Kekak, ECDSA and some others was really, really hard to the point that some people were questioning is it even practically possible? We were very fortunate that these great teams that we have under the Polygon umbrella, Polygon Hermes, Polygon Zero and Polygon Miden, there has been several cryptographic and engineering breakthroughs, very major ones.
For example, on the zero side, Polygon Zero side introduced this plunky tool, which was the fastest recursive prover in the industry, basically Goldilocks fields, which is this very specific arithmetic field that has some very interesting properties and allows us to get some very significant efficiency improvements. So, combining these breakthroughs and really great collaboration between these teams for the past 12 months, we have been able to crack these hard to implement top codes, and yes, we are incredibly fortunate. I mean, I'm excited that this happened. Okay, so what happened today was the starting pistol for the road to mainnet.
Yes. So, you guys published your code for public peer review, people get a look under the hood, it's finished code, finished. And so, and then soon, there will be like, including the prover, which is the hardest part, the Hollywood implementation, and the prover, everything is open source, everything, and it's full features. Right. Okay, so you've also published this, and like other people can take this code and run with it if they so choose. In a sense that anyone can obviously use the code, examine the code, on the license itself, we are still deciding. It's definitely going to be an open source license, as I said, the open source, the code today, we really, and we definitely make it available for everyone to reuse, moving forward, we're just deciding when the exact open source license format that we will have.
But it's definitely going to be the contribution to the community that people will eventually have will be able to use. Okay, so code is out there, people get a look under the hood, people get to judge it, make sure it's all there, there's going to be a dev net, sometimes soon, sounds like a permissioned test net, so like let some early people in there start to try and break things, then an actual test net comes later after that, and so public test net, permissionless test net, everyone gets to come and try and break this thing, or start to build their app, or just do something, and then after that, kind of like the Ethereum test nets, after that gets like, tried out in the wild for a little bit, we get more data, we get more feedback, we start to like polish off some edges, then we'll go to main net, and now we have a fully public permissionless DK EVM on main net.
Exactly, exactly, and just, I guess, relatively important thing to know there is that what is ahead of us now is, I would say a standard software, very free software release process, there are no engineering challenges, no cryptographic challenges, this was the challenging part, proving these complicated op codes, cracking that holding up the whole EVM, basically the whole implementation, that was the tough part. Now is basically just a more or less routine process of reaching the main net itself. That's certainly exciting. We've been talking about bankless, I've already brought this up in a number of interviews, but we're in this like bear market, but we're not going to get out of it until we build our way out of the bear market, so we must build in a DK EVM, can start to like produce some of the UX channels, the solves some of the UX issues at the top level, for like instant transaction speeds, basically zero transaction fees, that is fair, what is going to be?
When you start discussing transaction fees, you always have, you can technically allow zero fee transactions, but then you have this spam problem, which was by the fees were introduced in Ethereum in the first place, but we're definitely discussing negligible transaction fees. You can easily, I guess, compensate the transaction fees for users, but then again, you have this spam issue that maybe can be also addressed, it's a thing to discuss and consider, but certainly. So if there isn't compensated fees, like I'm the user and I'm going to pay the transaction fee, and I need to send you some ether, can we guess how much that can cost?
Currently for us to actually produce, when you take everything into account, the computing power that you need to actually generate the proofs, when you take all the running, I guess, operating operational costs of this solution that we have, it's currently, I can give you the exact figure, but it's 0.0087 dollars. 0.0091. So 0.0091, less than one cent, basically, is less than a penny is the actual operational cost that we have to, to, you know, process the transaction to generate proofs and everything. And again, like this was, it's also worth noting that this is the first iteration of the KVM.
We have clear idea and clear part how we're going to improve the efficiency of the KVM. It was really just, it was about proving that this is possible, basically, because no one was certain, even us, you know, in certain, at certain times, we were questioning, you know, this, this really too hard of a, not to crack, but it was really important to prove that it is actually possible. Now, when we have proven it, there are at least four major ways how we can improve, and how we are improving the KVM, improve the cryptography itself. We have very, very strong cryptographic team now, improve the code itself, optimize it, use optimal programming languages, et cetera.
Pipeline the Provers. When you have a Prover that is, that takes one minute to generate proof, you can pipeline 20 of them, and then instead of one minute to have three seconds. And the, the four thing is actually hardware acceleration. We're also working on that very actively. That's not publicly known, I guess, but we have both GPU focused and FPGA focused efforts to accelerate on the hardware level itself. So there's four major ways how we can further improve the KVM, but the current cost to actually process one transaction, improve it, is, as I said, a little bit less than one cent. Well, yeah, so the base resource cost is less than the penny, so like, maybe there's like a, because the fee market gets to like a penny or so.
Yes, that's neat. It's up to market then. Like, with my dritch, two pennies, free beads, two or three pennies. Oh, no. It's what's competing in the market. I mean, yeah, the other really exciting thing you said is the EVM equivalence aspect of this, which is something that I went down that rabbit hole and came out very, very appreciative of what EVM equivalence is. And just to speed run the listener through that, you have EVM equivalence versus EVM compatibility. And EVM equivalence is like the true copy and pacing of code without having to change anything. Like the EVM stack is one-to-one comparable where EVM compatibility is like, well, the bytecode works.
I might be fludging this, but like the bytecode works, but like producing that bytecode is like a little different and like need a different developer tooling. So with this EVM equivalent status of this EVM chain, you get to just port over the developer ecosystem, like, like, whatever, whatever that means, like, compiling tools and like, yeah, solidity tools. I'm a little bit like out of my water, out of my element here talking about this, but like, I kind of get the gist. No, no. And so like, this is coming out, like, when you launch this ZK EVM mainnet, this is like, you have everything else that all the other developers are familiar with on other EVM chains as well, like out of the box.
Yes, you're leveraging the whole ecosystem, which is very, very important, as we all know. So what you're doing, very discussing EVM equivalence, you're basically re-implementing the EVM, the way it should be implemented. It's like, almost like you're implementing a new Ethereum node, like, like, get, like, you literally take the official EVM specification and you go opcode by opcode. You're actually re-implementing the EVM, but this EVM is ZK friendly. So to say, in the background, it is able to generate ZK approves for batches of transactions. Otherwise, it's a normal EVM. It's implemented, like, get EVM, like, Erie-Gone EVM.
It literally follows the same specification. That's one thing. You just implement all the Ethereum RPC methods. Currently, you're actually running officially Ethereum tests. There are thousands of tests that every client, for example, that wants to join the network should actually pass. Currently, ZK EVM is passing, the client's passing around 30% of the tests, but we just started. We're very confident that the percentage is going to go up very, very quickly. So basically, if you implement RPC methods, you follow the official EVM specification. You pass all the Ethereum tests. You're very much Ethereum equivalent.
That's what you want to ideally have. Right. And just to really illustrate why this is so powerful, is that if something is EVM equivalent on one layer two or on the Ethereum layer one, you can instantly just take that whole thing that you've built and put it on any other EVM chain instantly. So like, all the apps that are built on any other EVM equivalent chain work on all the other EVM equivalent chains. There's tailwinds in the development labor when you work on an EVM equivalent chain. Exactly. What's the name of this thing? There's always a name for every single polygon chain. What's the name of this one?
It's still being discussed. That gives me a good segue. Polygon Hermes officially shipped the EVM. But that was very important to understand. And this was really a collaborative process of almost one year of very exciting collaboration between Polygon Hermes, Polygon Zero and Polygon Miden. There was literally zero competition between these teams and 100% collaboration. And it was really amazing. We still have regular weekly calls between the teams, daily as synchronous communication. Every month or two we have in-person workshops basically somewhere around the world. So for me personally, it was really an amazing experience watching these smart people collaborate.
And the reason I'm saying this is that's also Polygon Hermes. People feel very grateful to these other two teams for all the help and contribution. So that's why we're discussing currently the name that would maybe unify or symbolize that really this was a team effort. Yeah. I remember ECC last year, Mahalo. It was you and me and Mariano and we were getting drinks after the conference was over. And then you went in like disappeared for like five or ten minutes to take a phone call. And then you came back and sat down the table to super excited. And you couldn't tell me and Mariano what it was, but then like a couple days later.
It's all you. It was something about we acquired a ZK team, but you couldn't give us all the details. And then like three days later it announced that Polygon had acquired Hermes. I was like, oh, that's what that call was. Yes, I mean, yeah, in retrospect, it's very crazy. How much has happened in a year? Yes, very, very crazy timeline. So with all layer twos, there's always like a staking, a token staking component, maybe not always, but like that's kind of where we assume this is going. And I'm assuming Malik is the token that gets staked to validate this chain. Yes. And currently also another like there's so many things happening in Polygon at every single moment.
We are currently redesigning the token. That is something that is also actively happening as we speak. Basically, the magic ticker is probably the last legacy of the previous project. Right. Because Malik doesn't make any sense anymore. Yes. And we intentionally kept that way because when we announced Polygon, it wasn't just merely branding. It was really a symbol for us of this pivot in the vision and this new vision, grand vision that we had. And we wanted to do the same with the token. We intentionally kept the same ticker and the same design until we were actually confident that Polygon as a project and the vision has product market fit.
And now we are ready to actually migrate and upgrade the token actually to do something that will reflect where Polygon is. And then we have made certain adjustments that will make it, I guess, a powerful utility and very important component of the Polygon, Polygon's wider vision. Amazing. Well, Mahalo, why are you going to announce next year at next HTC? Every single year, there seems to be something. That's two, two, two, four, three, four, two weeks. It's genuinely hard for me to perceive. What's it doing next month? Awesome. Well, Mahalo, thank you for coming on and sharing the story. Thank you so much, David, for following our colleagues.
Of course, thanks so much.