What is ZKParallel?

Keep locally track of the state root and give merkle path for all starting value and all end values.

In a typical blockchain network structure, nodes can be classified into two main categories: execution nodes and validator nodes, based on their functionalities. Execution nodes are responsible for ordering, executing, and packaging transactions into blocks to ensure network consistency. Validator nodes, on the other hand, verify the blocks after receiving them by re-executing all the transactions in sequential order. In other words, to achieve the same processing efficiency, validator nodes need to have the same computational capabilities as execution nodes. We believe this is unreasonable as it unnecessarily duplicates the same computational work in different places.

For public blockchains like Ethereum and Binance Smart Chain (BSC), this approach increases the overall server costs of the network. Additionally, high-performance cluster-based public blockchains like Solana and Avalanche make it difficult for regular users to run and maintain their own nodes, leading to further centralization of the network.

We have designed an asymmetric node mechanism consisting of two types of nodes. This mechanism enables the majority of nodes in the blockchain network to process transactions in parallel, leveraging the performance of the servers and achieving the goals of increasing the network's transaction per second (TPS) and reducing server costs. In our tests conducted on EVM-based networks, we were able to save users running Ethereum nodes 60-80% of their server expenses.