sv9tsick.metis🅱️ullEtin
sv9tsick.metis🅱️ullEtin 6 minutes reading from Ethereum

Longread: Metis, Ethereum, ZK, Monero, ERC-20 Tokens

Сontinuation of this thread

Metis ETH ZKP ZKRollups zkEVM

sv9tsick(❄️,🐻)🅱️ullEtin🫠 on Twittersv9tsick(❄️,🐻)🅱️ullEtin🫠 on Twitter

A three-layer model allows an entire sub-ecosystem to exist within a single rollup, which allows cross-domain operations within that ecosystem to happen very cheaply, without needing to go through the expensive ETH

But transactions between layer2s will also be cheap because the token does not need to be issued in the root chain

Your ERC20 token on Metis, can be wrapped on Optimism/ Arbitrum , you can move it between them without expensive fees on ETH

But what if we need to send our ERC-20 tokens to Ethereum ?

Depositing also requires waiting the fraud proof window Withdrawing from Metis back to ETH takes a week delay, but depositing is instant This is weakness of optimistic rollups but not for ZK-rollups

ZK rollups do not require a week-long waiting window for security reasons, but they do still require a shorter window (~ 12 hours with 1st-generation technology)

And that's why: 1⃣Complex general-purpose ZK-EVM rollups require more time to cover the non-parallelized computation time when proving a block 2⃣There is the economic consideration of needing to submit proofs rarely to minimize the fixed costs associated with proof transactions

Next generation ZK EVM will have to solve these problems

Vitalik tried to solve the problems by creating a ZK rollup inside a ZK rollup using Layer3 concept And the problem is solved, but there's a different approach to solving it, more interesting approach for Metis eco

This approach relies on ERC 4337 aggregate verification

The ZK rollup would accept a message from a batch verifier contract that says that it has verified a proof of a batch of statements, where each of those statements is of the form

This would be an open protocol: any ZK-rollup could join, and any batch prover could aggregate proofs from any compatible ZK-rollup, and would get compensated by the aggregator with a transaction fee

The batch handler contract would verify the proof once, and then pass off a message to each rollup with the triple for that rollup; the fact that the triple came from the batch handler contract would be evidence that the transition is valid

Instead of

🔵base layer (ETH)<- rollup <- validium We have

🔵base layer (ETH) <- batch mechanism <- rollup or validium

Also reminiscent of the architucture scheme of layer 3? Maybe but there's an important difference

In this scheme, the middle level is not a complete EVM system

It's a simplified and highly specialized object, and so it's more likely to be

✅Secure ✅Built at all without needing yet another specialized token ✅Governance-minimized and not change over time

Do you see where I've been leading you all this time?

A hint:

@ElenaCryptoChic said about adding a ZK as an option Metis team works on that "specialized object"

I hope I'm not wrong in my guessing

Plus ✅ZKP (0-knowledge proof) prioritized wallet @FoxWallet on @MetisGovernance

✅At Tokyo Web3 Hackathon where Metis will be, there will also be @zkPass

I think they'll be able to communicate😁 Also there will be @binance @avalancheavax @0xPolygon etc

It does not matter what to call it layer 3, additional function or whatever, the main thing is that the Metis team is building and going towards improving the technology

All we have to do is to keep a close eye and sometimes make guesses👀

This post is based on this twitter thread.

Comments

Please login to comment.