diff --git a/docs/cdk/releases/pp-intro-components.md b/docs/cdk/concepts/pp-intro-components.md similarity index 100% rename from docs/cdk/releases/pp-intro-components.md rename to docs/cdk/concepts/pp-intro-components.md diff --git a/docs/cdk/concepts/rollup-vs-validium.md b/docs/cdk/concepts/rollup-vs-validium.md index 31b5ee48..5b767d62 100644 --- a/docs/cdk/concepts/rollup-vs-validium.md +++ b/docs/cdk/concepts/rollup-vs-validium.md @@ -59,6 +59,26 @@ Below is a breakdown of the technical differences between a zkEVM rollup and val | **Final settlement** | Transaction batches and their corresponding proofs are added to the Ethereum state. | The hash of transaction data and its proof are added to the Ethereum state, referred to as the consolidated state. | \*JSON RPC, Tx pool manager, Sequencer, Etherman, Synchronizer, State DB, Aggregator, Prover + +Polygon CDK running in validium mode inherits the core functionalities of a zkEVM rollup node and adds a [data availability layer](../glossary/index.md#data-availability-committee-dac). + +## Key differences + +| | Rollup | Validium | +| ------------------------ | ----------------------------------------------------------- | ---------------------------------------------------------------------------------- | +| **Node type** | [cdk-erigon:v1.2.24](https://github.com/0xPolygonHermez/cdk-erigon/releases/tag/v1.2.24) | [cdk-erigon:v2.1.x](https://github.com/0xPolygonHermez/cdk-erigon/releases) | +| **Data availability** | On-chain via L1 | Off-chain via a local option, or a [DAC](../glossary/index.md#data-availability-committee-dac) + [DA node](https://github.com/0xPolygon/cdk-data-availability) | +| **Components** | zkEVM components\* | zkEVM components\* + PostgreSQL database + on-chain committees | +| **Contracts** | [zkEVM smart contracts](https://github.com/0xPolygonHermez/zkevm-contracts) | [Validium-specific DAC contract](https://github.com/0xPolygon/cdk-validium-contracts) | +| **Infrastructure** | Standard infrastructure | Dedicated infrastructure for data availability layer and DACs | +| **Tx flow** | All transaction data is published on L1 | Validium only publishes the hash of the transaction data to L1. The sequencer sends both the hash and the transaction data to the DAC for verification. Once approved, the hash+signatures are sent to the Consensus L1 contract of the validium protocol. +| **Security** | High security due to on-chain data availability and zero-knowledge proofs. |Off-chain data availability can affect security if the sequencer goes offline or if DAC members collude to withhold state data. | +| **Gas fees** | High, because all transaction data is stored on Ethereum. | Low, because only the hash of the transaction data is stored on Ethereum. | +| **Proof generation** | Uses Prover to generate proofs of batched transactions for validation. | Uses Prover to generate proofs of batched transactions for validation. | +| **Final settlement** | Transaction batches and their corresponding proofs are added to the Ethereum state. | The hash of transaction data and its proof are added to the Ethereum state, referred to as the consolidated state. | + +*JSON RPC, Pool DB, Sequencer, Etherman, Synchronizer, State DB, Aggregator, Prover + ## Further reading - [Ethereum documentation: rollups](https://ethereum.org/en/developers/docs/scaling/#rollups) diff --git a/docs/cdk/releases/stack-components.md b/docs/cdk/concepts/stack-components.md similarity index 100% rename from docs/cdk/releases/stack-components.md rename to docs/cdk/concepts/stack-components.md diff --git a/docs/cdk/spec/validium-vs-rollup.md b/docs/cdk/spec/validium-vs-rollup.md deleted file mode 100644 index 19ef30b5..00000000 --- a/docs/cdk/spec/validium-vs-rollup.md +++ /dev/null @@ -1,24 +0,0 @@ - - -Polygon CDK running in validium mode inherits the core functionalities of a zkEVM rollup node and adds a [data availability layer](../glossary/index.md#data-availability-committee-dac). - -## Key differences - -| | Rollup | Validium | -| ------------------------ | ----------------------------------------------------------- | ---------------------------------------------------------------------------------- | -| **Node type** | [cdk-erigon:v1.2.24](https://github.com/0xPolygonHermez/cdk-erigon/releases/tag/v1.2.24) | [cdk-erigon:v2.1.x](https://github.com/0xPolygonHermez/cdk-erigon/releases) | -| **Data availability** | On-chain via L1 | Off-chain via a local option, or a [DAC](../glossary/index.md#data-availability-committee-dac) + [DA node](https://github.com/0xPolygon/cdk-data-availability) | -| **Components** | zkEVM components\* | zkEVM components\* + PostgreSQL database + on-chain committees | -| **Contracts** | [zkEVM smart contracts](https://github.com/0xPolygonHermez/zkevm-contracts) | [Validium-specific DAC contract](https://github.com/0xPolygon/cdk-validium-contracts) | -| **Infrastructure** | Standard infrastructure | Dedicated infrastructure for data availability layer and DACs | -| **Tx flow** | All transaction data is published on L1 | Validium only publishes the hash of the transaction data to L1. The sequencer sends both the hash and the transaction data to the DAC for verification. Once approved, the hash+signatures are sent to the Consensus L1 contract of the validium protocol. -| **Security** | High security due to on-chain data availability and zero-knowledge proofs. |Off-chain data availability can affect security if the sequencer goes offline or if DAC members collude to withhold state data. | -| **Gas fees** | High, because all transaction data is stored on Ethereum. | Low, because only the hash of the transaction data is stored on Ethereum. | -| **Proof generation** | Uses Prover to generate proofs of batched transactions for validation. | Uses Prover to generate proofs of batched transactions for validation. | -| **Final settlement** | Transaction batches and their corresponding proofs are added to the Ethereum state. | The hash of transaction data and its proof are added to the Ethereum state, referred to as the consolidated state. | - -*JSON RPC, Pool DB, Sequencer, Etherman, Synchronizer, State DB, Aggregator, Prover diff --git a/mkdocs.yml b/mkdocs.yml index 23f60a7d..7c7cfe42 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -61,10 +61,9 @@ nav: - Overview: cdk/overview.md - Releases: - Current Release: - - Polygon CDK Fork ID 12: docs/cdk/releases/fork-id-12.md + - Polygon CDK Fork ID 12: cdk/releases/fork-id-12.md - Previous Releases: - Polygon CDK Erigon: cdk/getting-started/cdk-erigon/releases.md - - Polygon CDK Fork ID 7 to 9: cdk/how-to/migrate/forkid-7-to-9.md - Get Started: - Local Deployment Guide: cdk/getting-started/local-deployment.md - CLI Tool: cdk/getting-started/cli-tool.md @@ -77,8 +76,9 @@ nav: - Resources: cdk/getting-started/cdk-erigon/resources.md - How To: - Migrate: + - General Guide for Projects: cdk/how-to/migrate/fork.md - Fork ID 9 to 12: cdk/how-to/migrate/forkid-9-12.md - - General Guide for Partners: cdk/how-to/migrate/fork.md + - Fork ID 7 to 9: cdk/how-to/migrate/forkid-7-to-9.md - Create Custom Native Token: cdk/how-to/use-native-token.md - Integrate DA Layer: cdk/how-to/integrate-da.md - Manage Allowlists with Policies: cdk/how-to/manage-policies.md @@ -103,8 +103,6 @@ nav: - CDK Rollup: cdk/architecture/cdk-zkevm.md - CDK Validium: cdk/architecture/cdk-validium.md - Staking the Bridge (STB): cdk/architecture/staking-the-bridge.md - - Specification: - - Validium vs Rollup: cdk/spec/validium-vs-rollup.md - Glossary: - Glossary: cdk/glossary/index.md - Additional Resources: