CDK updates

Author: kmurphypolygon

docs/cdk/concepts/dac.md

@@ -1,22 +1,31 @@
-Validiums are blockchain solutions that don't store transaction data.
+Data availability in blockchain technology refers to whether or not transaction data is available on-chain or off-chain. 
 
-!!! quote
-    See the [definition of validium](https://ethereum.org/en/developers/docs/scaling/validium/) on Ethereum.org's glossary.
+If data is available on-chain, 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.
 
-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.
+!!! quote "Recommended resource"
+    See Ethereum.org's discussion on [data availability](https://ethereum.org/en/developers/docs/data-availability/).
 
-A data availability committee (DAC) implements a data storage layer in a modular chain architecture like CDK.
+## What is a validium?
+
+Validiums are blockchain solutions that do not store transaction data. 
+
+!!! quote "Recommended resource"
+    See Ethereum.org's glossary [definition of validiums](https://ethereum.org/en/developers/docs/scaling/validium/).
 
 ## 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:
+Polygon's CDK validium has an optional data availability committee (DAC).
+
+A DAC is an off-chain network of nodes that implements a data storage layer in a modular chain architecture like CDK. Some 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.
+- **Lower transaction fees**: Reduced computational requirements lead to lower fees and faster finality on the main network.
+- **Privacy and security**: The DAC stores secure and private transaction data.
+- **Trustless**: Data owners do not have to trust the blockchain operator.
+- **Scalable**: Decoupling data storage from the main chain supports more scalable networks. 
 
-DACs store the data required to reconstruct the state of the blockchain and make that data accessible so that, if the blockchain goes down, users can still access their assets and data.
+DACs store the data required to reconstruct the state of the blockchain and make that data accessible so that, if the main blockchain network goes down, users can still access their assets and data.
 
-Delegating blockchain data to a DAC in this way can be costly. However, a DAC improves finality and thus supports Enterprise use cases which require cheap and fast transactions with a private and secure data layer.
+DAC set up can be costly and therefore DACs mostly support Enterprise use cases which require cheap and fast transactions with a private and secure data layer.
 
 The CDK validium DAC is a secure consortium of nodes that ensures off-chain data access. 
 
@@ -38,37 +47,4 @@ The DAC works together with the sequencer to control the flow of data. The proce
 
 6. **Verification on Ethereum**: A designated smart contract on Ethereum verifies the submitted signatures against a list of valid DAC members and confirms that sufficient approval has been provided for the batch hash.
 
-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.
-
+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.

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

@@ -1,3 +1,6 @@
+!!! important "Recommendation"
+    Follow the [quickstart](quickstart-rollup.md) for a hands-on introduction to CDK in rollup mode.
+
 ## 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.

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

@@ -38,7 +38,7 @@ cp .env.example .env
 sudo docker-compose pull
 ```
 
-2.2 After pulling the images, start your local CDK Validium:
+2.2 After pulling the images, start your local CDK validium:
 
 ```bash
 sudo make run
@@ -95,7 +95,7 @@ zkevm-bridge-ui                  /bin/sh /app/scripts/deploy.sh   Up
 ```
 </details>
 
-2.3.1 If a service isn't running (i.e. it is in Exit 1 state), investigate further using the logs:
+2.3.1 If a service isn't running (i.e. it is in `Exit 1` state), investigate further using the logs:
 
 ```bash
 sudo docker-compose logs <container_name>
@@ -119,7 +119,7 @@ sudo make restart
 ```
 
 !!! note
-    This deployment runs on an L1 Geth instance.
+    This local deployment runs on an L1 Geth instance.
 
 ## 3. Test validium
 
@@ -159,6 +159,9 @@ You should see a page similar to this:
   <img src="/img/cdk/cdk-metamask-import-account.png" alt="bridge" width="90%" height="30%" />
 </div>
 
+!!! danger
+    Today, 21/11, I got stuck here with pending transfers that weren't picked up by blockexplorer.
+
 4.4 Transfer some tokens to another account:
 
 <div align="center">

mkdocs.yml

@@ -193,4 +193,5 @@ markdown_extensions:
 
 plugins:
   - search
- # - git-revision-date-localized
+  - open-in-new-tab
+  #- git-revision-date-localized

requirements.txt

@@ -1,3 +1,4 @@
 mkdocs-material==9.4.8
 markdown-include==0.8.1
 mkdocs-git-revision-date-localized-plugin==1.2.1
+mkdocs-open-in-new-tab==1.0.3