The Ethereum blockchain would develop a client with three layers. The issues of latency and data efficacy persisted.
A few years ago, Ethereum [ETH] was beset by transaction delays and network congestion, but many scaling solutions have enabled it to overcome these obstacles. The last is Polygon’s [MATIC] zero-knowledge integration with the Ethereum Virtual Machine [zkEVM].
Typically, these users constitute two-thirds of the network. However, introducing zk rollups has ensured this is no longer the case. Consequently, developers can intervene while the chain ceases to finalize blocks.
In addition, Vitalik noted that zkEVM would become the third Ethereum client due to the free space. However, he said that it would not be as immediate because the L1 must work on utilizing them for execution verification.
Vitalik stated that despite zk’s capability, there were issues that no L2 could solve. He mentioned the latency issue, which could disrupt the chain if a block is published late, in addition to data efficacy, which could reveal validator signatures.
Additional insights into the publication cited the zk Simplified Non-Interactive Argument of Knowledge. (zk-SNARKS). As zk proofs permit parties to verify a true statement without disclosing additional information, zk-SNARKS allows proof of possession without interaction between the prover and verifier.
In the meantime, the chief of Ethereum acknowledged that the entire process would require considerable time to materialize. In addition, he admitted that sluggish block execution and verification could be a problem in the beginning.
Also Read: Elon Musk Demands Dismissal Of A $258 Billion Dogecoin Lawsuit
Wallets