Validium
Uses validity proofs like ZK-rollups but data is not stored on the main layer 1 Ethereum chain. This can lead to 10k transactions per second per validium chain and multiple chains can be run in parallel.
Prerequisites
You should have a good understanding of all the foundational topics and a high-level understanding of Ethereum scaling. Implementing scaling solutions such as Validium is an advanced topic as the technology is less battle-tested, and continues to be researched and developed.
Pros and cons
| Pros | Cons |
|---|---|
| No withdrawal delay (no latency to on-chain/cross-chain tx); consequent greater capital efficiency. | Limited support for general computation/smart contracts; specialized languages required. |
| Not vulnerable to certain economic attacks faced by fraud-proof based systems in high-value applications. | High computational power required to generate ZK proofs; not cost effective for low throughput applications. |
| Slower subjective finality time (10-30 min to generate a ZK proof) (but faster to full finality because there is no dispute time delay). |
Use Validium
Multiple projects provide implementations of Validium that you can integrate into your dapps:
Further reading
Know of a community resource that helped you? Edit this page and add it!
Aidez-nous avec cette page
Si vous êtes un expert sur le sujet et que vous souhaitez contribuer, modifiez cette page et enrichissez-la de votre sagesse.
Vous serez crédité et vous aiderez la communauté Ethereum !
Utilisez la flexibilité de ce Modèle de documentation
Des questions ? Demandez-nous dans le salon #content de notre Serveur Discord
Modifier la page