# Technology ### 1.ZKSpeed ZKSwap's first version of the scaling solution (ZKSpeed) combines the features of ZK-rollup, Validium, and Plasma solutions. In addition to this, three optimization improvements including aggregation proof, GPU optimization, and proof circuit optimization are applied to further improve the throughput of the entire network. For details, see the following: [ZKSwap Introduces Practical ZK-Rollups — ZKSpeed, Achieving High TPS and Low Gas Fees in Real Layer2 DeFi Use Cases](https://medium.com/zkswap/zkswap-introduces-practical-zk-rollups-zkspeed-achieving-high-tps-and-low-gas-fees-in-real-6effe4e789e0) ### 2.ZKSwap Design Specification Thanks to ZKSync who provides the ZK-Rollup framework for ERC20 token L2 transactions. ZKSwap is a Layer-2 token transaction protocol that uses ZK-Rollups on Ethereum and is based on the PLONK proof system. The ZKSwap design specification explicates the ZKSwap protocol and its difference against ZKSync. [ZKSwap Design Specification](https://medium.com/zkswap/zkswap-design-specification-ca5ccb32791e) ### 3.Validator ZKSwap validator is currently run by L2labs Foundation. Many high-frequency AMD CPU servers have been deployed to generate zero-knowledge proofs (ZK-Snarks). In fact, it doesn’t matter who generates or provides the ZK-Snarks, as long as the ZK-Snarks are submitted to the layer-1 network in time. \ ZKSwap team is committed to developing **ZKSwap** into a fully decentralized protocol. We intend to achieve it by introducing an independent consensus mechanism and Proof-of-ZKSnarks mining to encourage users to contribute their computing power to securing the network. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://en.wiki.zks.org/techonology.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.