zkSync language-level vs Polygon bytecode-level zkEVM trade-off
Quote58 words17 likes
Short comment framing the zkEVM design choice as a performance versus equivalence trade-off, with zkSync taking the source-code compatibility route and Polygon bytecode-level compatibility.
Key claims
Neither approach is strictly better, the trade-off is performance vs equivalence
recently I talked about @0xPolygonZK's bytecode-level approach to #zkEVM
@zksync takes a language-level (or source code) approach
is one better than the other?
not necessarily. There's always a tradeoff and in this case it's performance vs equivalence
x.com/zksync/status/1612841650358988800
learn more about the different #zkEVM approaches here 馃憞
x.com/expctchaos/status/1569717615282782209
for more on @0xPolygonZK's byte-level approach, check here 馃憞
x.com/expctchaos/status/1612991994732609539
QUOTING @zksync
We designed zkSync 2.0 for high performance but specifically chose to maintain source code compatibility (Solidity and Vyper), which comes with added security benefits. 3/7
We designed zkSync 2.0 for high performance but specifically chose to maintain source code compatibility (Solidity and Vyper), which comes with added security benefits. 3/7