The "ZK" comes from zero-knowledge cryptography, but the property being used is usually succinctness rather than privacy: a short proof that a huge batch of computation was carried out correctly, cheap for anyone to check. Most ZK-rollups are not private — activity is visible much as it is anywhere else. Some engineers prefer the plainer name validity rollup, which describes the job better.
The contrast is with optimistic rollups, which publish results and assume they are honest unless someone submits a fraud proof during a challenge window. That window means withdrawals back to <a href="/glossary/layer-1/">layer 1</a> have to wait. A validity proof removes the guesswork, so exits can settle as soon as a proof is verified. The cost lands on the other side: generating proofs is computationally heavy, and supporting general smart contracts inside a proof system is genuinely difficult engineering.
Two caveats deserve stating plainly. A rollup only inherits base-chain security if its transaction data is actually published there and its contracts are not quietly upgradeable; many run a single operator sequencing transactions, which can censor or reorder even where it cannot steal. And funds cross over through a <a href="/glossary/bridge/">bridge</a>: a rollup is its own <a href="/glossary/layer-2/">layer-2</a> network, so sending to the wrong one, or to a service that does not support it, is an easy and expensive mistake.
Key takeaways
- Zero-knowledge here buys verifiable compression, not anonymity; assume your rollup activity is public.
- Validity proofs remove the challenge-window wait that optimistic rollups impose on withdrawals.
- Check who runs the sequencer and whether the contracts can be upgraded before treating any rollup as trustless.
ZK-Rollup — frequently asked questions
Is a ZK-rollup private?
Usually not. The zero-knowledge machinery is proving that a batch of transactions was executed correctly; it is not being used to hide who sent what. Balances and transfers on most ZK-rollups can be inspected in a block explorer exactly as on the base chain. Privacy-focused designs do exist, but treat privacy as a separate feature a network has to advertise explicitly.
Do I need to do anything differently to use one?
Mainly, mind the network. You bridge assets over, pay fees in whatever token that rollup uses for gas, and interact with contracts deployed there rather than on the base chain. Withdrawing back takes an extra step and sometimes extra time. Always confirm the destination network before sending, because a service that does not support that specific network can put your funds out of reach.
New to crypto, or filling in the gaps? Work through the essentials in Learn, browse every term A–Z, or see live prices for the coins these concepts power.