pushing updates to remote

Author: kmurphypolygon

docs/cdk/concepts/dac.md

@@ -1,8 +1,15 @@
-!!! note
-    fix this: https://medium.com/coinmonks/what-is-data-availability-and-why-do-we-need-it-7993c039fc44
+Validiums are blockchain solutions that don't store transaction data.
 
+!!! quote
+    See the [definition of validium](https://ethereum.org/en/developers/docs/scaling/validium/) on Ethereum.org's glossary.
 
-A data availability committee (DAC) is an optional offchain network of nodes that provides data to a blockchain network. The advantages are:
+Data availability in blockchain technology refers to whether or not transaction data is available onchain or off-chain. If data is available onchain, then each node has to store every piece of data related to every transaction. This can be costly for node operators as hardware and storage requirements are high. Moving data off-chain streamlines node architecture and operations.
+
+A data availability committee (DAC) implements a data storage layer in a modular chain architecture like CDK.
+
+## What is a DAC?
+
+A data availability committee (DAC) is an off-chain network of nodes that provides data to a blockchain network. The advantages are:
 
 - **Lower transaction fees**: Reduced computational requirements lead to lower fees.
 - **State privacy**: A secure copy of state transitions ensures data integrity and privacy.
@@ -33,3 +40,35 @@ The DAC works together with the sequencer to control the flow of data. The proce
 
 7. **Final settlement with zero-knowledge proof**: The aggregator prepares a proof for the batch via the prover and submits it to Ethereum. This proof confirms the validity of the batch's transactions without revealing their details. The chain state updates on Ethereum.
 
+
+INCORPORATING:
+
+
+
+## What do you Mean by Data Availability Layer?
+
+In the realm of blockchain, data availability ensures that all nodes can access and verify the complete transaction history, which is crucial for maintaining the network's transparency, security, and integrity.
+
+However, storing all transaction data on the main chain (L1) can lead to high costs and compromise privacy. Data availability layers tackle these issues by separating transaction execution from data storage. This allows for transaction data to be stored off-chain, reducing costs and enhancing privacy, while still being accessible for validation.
+
+This separation introduces new challenges, such as ensuring the secure and reliable management of off-chain data. Features like the [<ins>DAC</ins>](#what-are-dacs) within the Polygon CDK framework address these concerns, offering trusted oversight of off-chain data.
+
+The diagram below provides a high-level overview of the Polygon CDK Validium's approach to blockchain infrastructure.
+
+<div align="center">
+  <img src="" alt="bridge" width="90%" height="30%" />
+</div>
+
+## What are DACs?
+
+Data Availability Committees (DACs) are a crucial element in many blockchain protocols, tasked with ensuring the reliability and accessibility of off-chain data. In essence, they verify the availability of data associated with specific blockchain blocks.
+
+In the context of L2 solutions, DACs play a pivotal role in enhancing scalability. They aid in transferring significant computational work and data storage off-chain, thereby alleviating the burden on the main L1 blockchain.
+
+The DAC is an integral element in the validium framework of the CDK, functioning as a secure consortium of nodes to maintain the accessibility and security of off-chain data. For an overview of how the DAC functions within the CDK, please explore the DAC guide, available [<ins>here</ins>](/docs/cdk/validium/dac.md).
+
+> For a more detailed understanding of data availability, the Ethereum Foundation's guide on Data Availability is a great resource, accessible [<ins>here</ins>](https://ethereum.org/en/developers/docs/data-availability/).
+## How do L2s Built with Polygon CDK Validium Function as App-chains?
+
+Leveraging the power of Polygon's advanced [zkEVM technology](/docs/zkevm/), chains developed using the Polygon CDK offer a high-performance L2 scaling solution. Developers have the flexibility to choose the validium framework, which integrates a secure data availability layer managed by a [Data Availability Committee (DAC)](/docs/cdk/validium/dac.md). Chains built with the CDK can function like L1 blockchains tailored to specific business logic. However, as L2 solutions, they provide the advantage of near-infinite scalability. Designed with a user-centric approach, these chains prioritize core business functions and user engagement strategies without compromising on performance and scalability. The following diagram illustrates the high-level architecture of a chain developed using the Polygon CDK.
+

docs/cdk/get-started/deploy-rollup.md

@@ -0,0 +1,7 @@
+## Deploy a CDK rollup locally
+
+The [zkEVM deployment quickstart documentation](../..//zkEVM/step1-fullzkevm.md) shows you how to deploy a zkEVM rollup on your local machine.
+
+!!! question
+    What makes this CDK?
+

docs/cdk/get-started/deploy-validium.md

@@ -1,5 +1,5 @@
 !!! important "Recommendation"
-    Follow the [Quickstart](quickstart-validium.md) for a hands-on introduction to CDK in validium mode.
+    Follow the [quickstart](quickstart-validium.md) for a hands-on introduction to CDK in validium mode.
 
 Follow the steps below to deploy a CDK validium instance.
 
@@ -21,4 +21,7 @@ Follow the instructions in the [CDK validium node repository's README](https://g
 
     Finally, once the CDK validium node is operational, set up and run the data availability node. 
 
-    Instructions for this can be found in the [<ins>CDK DA Node GitHub repository's README</ins>](https://github.com/0xPolygon/cdk-data-availability).
+    Instructions for this can be found in the [<ins>CDK DA Node GitHub repository's README</ins>](https://github.com/0xPolygon/cdk-data-availability).
+
+!!! question
+    What makes this CDK?

docs/cdk/get-started/overview.md

@@ -12,8 +12,8 @@ CDK users choose a chain architecture specific to their needs and use cases.
 !!! info
     For the latest updates, follow our official GitHub repositories.
 
-    - [Rollup node](https://github.com/0xPolygonHermez/zkevm-node)
-    - [Validium node](https://github.com/0xPolygon/cdk-validium-node)
-    - [Data availability committee](https://github.com/0xPolygon/cdk-data-availability)
-    - [zkEVM smart contracts](https://github.com/0xPolygonHermez/zkevm-contracts)
-    - [Validium smart contracts](https://github.com/0xPolygon/cdk-validium-contracts)
+    - [Rollup node](https://github.com/0xPolygonHermez/zkevm-node).
+    - [Validium node](https://github.com/0xPolygon/cdk-validium-node).
+    - [Data availability committee](https://github.com/0xPolygon/cdk-data-availability).
+    - [zkEVM smart contracts](https://github.com/0xPolygonHermez/zkevm-contracts).
+    - [Validium smart contracts](https://github.com/0xPolygon/cdk-validium-contracts).

docs/cdk/get-started/quickstart-rollup.md

@@ -1,3 +1,8 @@
-Spin up an zkEVM ...
+## Run a CDK rollup locally
 
-Then ...
+The following documentation is a quickstart guide for deploying a CDK rollup on your local machine.
+
+[https://github.com/0xPolygonHermez/zkevm-node/blob/develop/docs/running_local.md](https://github.com/0xPolygonHermez/zkevm-node/blob/develop/docs/running_local.md)
+
+!!! question
+    What makes this CDK?

docs/cdk/get-started/quickstart-validium.md

@@ -1,8 +1,5 @@
 This quickstart guides you through the process of setting up a CDK validium on your local machine.
 
-!!! danger "Is it true?"
-    Please note that the current Data Availability (DA) configuration in Polygon CDK is using a Data Availability Committee (DAC) node with a local Geth client as the L1. However, the integration with Layer 1 testnets, including Sepoilla, is actively being pursued.
-
 ## Prerequisites
 
 ### System requirements
@@ -12,7 +9,7 @@ This quickstart guides you through the process of setting up a CDK validium on y
 - An AMD64 architecture system.
 
 !!! warning
-    CDK does not support ARM-based Macs
+    CDK does not support ARM-based Macs.
 
 ### Software requirements
 
@@ -121,6 +118,9 @@ To restart all services:
 sudo make restart
 ```
 
+!!! note
+    This deployment runs on an L1 Geth instance.
+
 ## 3. Test validium
 
 3.1 Verify the block explorer is running by navigating to [localhost:4001](http://localhost:4001/). 
@@ -181,55 +181,55 @@ You should see a page similar to this:
 
 CDK has a native bridge with UI that allows you to transfer funds between the L1 and the L2 validium.
 
-### L1 to L2
+### 5.1 L1 to L2
 
-5.1 Add the L1 RPC to MetaMask:
+5.1.1 Add the L1 RPC to MetaMask:
 
 <div align="center">
   <img src="/img/cdk/cdk-metamask-add-l1.png" alt="bridge" width="90%" height="30%" />
 </div>
 
-5.2 Switch to the L1 network and you will see the previously imported account with ~999 POL on the L1 chain.
+5.1.2 Switch to the L1 network and you will see the previously imported account with ~999 POL on the L1 chain.
 
-5.3 Verify the bridge UI by navigating to [localhost:8088](http://localhost:8088/). 
+5.1.3 Verify the bridge UI by navigating to [localhost:8088](http://localhost:8088/). 
 
-5.4 Click on **Connect a wallet > MetaMask**.
+5.1.4 Click on **Connect a wallet > MetaMask**.
 
 <div align="center">
   <img src="/img/cdk/cdk-bridge.png" alt="bridge" width="90%" height="30%" />
 </div>
 
-5.5 Select the previously imported account (0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266). Once you are connected, you should see a page like this:
+5.1.5 Select the previously imported account (0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266). Once you are connected, you should see a page like this:
 
 <div align="center">
   <img src="/img/cdk/cdk-bridge-connected.png" alt="bridge" width="90%" height="30%" />
 </div>
 
-5.6 Enter the amount (e.g. 5) to bridge and click **Continue**, you will see the **Confirm Bridge** page. 
+5.1.6 Enter the amount (e.g. 5) to bridge and click **Continue**, you will see the **Confirm Bridge** page. 
 
-5.7 Click **Bridge** and approve the transaction on the MetaMask pop-up:
+5.1.7 Click **Bridge** and approve the transaction on the MetaMask pop-up:
 
 <div align="center">
   <img src="/img/cdk/cdk-bridge-confirm.png" alt="bridge" width="90%" height="30%" />
 </div>
 
-5.8 Once bridging is complete, you should see the **Activity** page:
+5.1.8 Once bridging is complete, you should see the **Activity** page:
 
 <div align="center">
   <img src="/img/cdk/cdk-bridge-completed-l1-to-l2.png" alt="bridge" width="90%" height="30%" />
 </div>
 
-### L2 to L1
+### 5.2 L2 to L1
 
-5.9 Switch network on MetaMask to your validium chain and navigate back to [localhost:8088](http://localhost:8088/). 
+5.2.1 Switch network on MetaMask to your validium chain and navigate back to [localhost:8088](http://localhost:8088/). 
 
-5.10 You should see both the updated L1 and L2 balances:
+5.2.2 You should see both the updated L1 and L2 balances:
 
 <div align="center">
   <img src="/img/cdk/cdk-bridge-l2-to-l1.png" alt="bridge" width="90%" height="30%" />
 </div>
 
-5.11 Enter an amount and follow the same process to bridge the fund back to the L1.
+5.2.3 Enter an amount and follow the same process to bridge the fund back to the L1.
 
 !!! note
     You cannot bridge back fund more than what you have previously bridged from L1 to the L2.
@@ -240,12 +240,15 @@ The L2->L1 bridging is slightly different than L1->L2 and you will see the **Act
   <img src="/img/cdk/cdk-bridge-l2-to-l1-on-hold.png" alt="bridge" width="90%" height="30%" />
 </div>
 
-5.12 Click **Finalise** and approve the transaction (Note: MetaMask will pop up a window to ask you to switch to the L1 network first). Then you will see this once the bridging is completed:
+5.2.4 Click **Finalise** and approve the transaction (Note: MetaMask will pop up a window to ask you to switch to the L1 network first). Then you will see this once the bridging is completed:
 
 <div align="center">
   <img src="/img/cdk/cdk-bridge-l2-to-l1-completed.png" alt="bridge" width="90%" height="30%" />
 </div>
 
 !!! urgent
     - First time, I had an error on step 5.12 -> cannot estimate gas.
-    - Second time, I had an error much earlier on, but that's probably because I didn't clear the images up, even though I restarted. 
+    - Second time, I had an error much earlier on, but that's probably because I didn't clear the images up, even though I restarted. 
+
+!!! question
+    What makes this CDK?

…s/cdk/specification/validium-vs-zkevm.md …/cdk/specification/validium-vs-rollup.mddocs/cdk/specification/validium-vs-zkevm.md renamed to docs/cdk/specification/validium-vs-rollup.md docs/cdk/specification/validium-vs-zkevm.md renamed to docs/cdk/specification/validium-vs-rollup.md

@@ -52,12 +52,14 @@ nav:
         - Quickstart:
           - Validium: cdk/get-started/quickstart-validium.md
           - Rollup: cdk/get-started/quickstart-rollup.md
-        - Deploy validium: cdk/get-started/deploy-validium.md
+        - Deploy:
+          - Validium: cdk/get-started/deploy-validium.md
+          - Rollup: cdk/get-started/deploy-rollup.md
       - How to: 
         - Manage allowlists: cdk/how-to/manage-allowlists.md
       #- Architecture:
       - Specification:
-        - Validium vs zkEVM: cdk/specification/validium-vs-zkevm.md
+        - Validium vs rollup: cdk/specification/validium-vs-rollup.md
         - Performance benchmarks: cdk/specification/performance-benchmarks.md
       - Concepts:
         - Data availability: cdk/concepts/dac.md

mkdocs.yml

@@ -1,7 +1,7 @@
 #!/usr/bin/env bash
 set -euo pipefail
 
-/Users/ammatlala/Library/Python/3.11/bin/virtualenv venv
+virtualenv venv
 source venv/bin/activate
 pip3 install -r requirements.txt
 mkdocs serve --strict