Skip to content

Commit a8a185e

Browse files
committed
update CDK intros done
1 parent f5befe1 commit a8a185e

File tree

6 files changed

+16
-5
lines changed

6 files changed

+16
-5
lines changed

docs/cdk/concepts/dac.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ The CDK validium DAC is a secure consortium of nodes that ensures off-chain data
2424

2525
## DAC data flow
2626

27-
![CDK validium DAC dataflow](../../img/cdk/zksupernets-dac.png)
27+
![CDK validium DAC dataflow](../../img/cdk/cdk-val-dac-02.png)
2828

2929
The DAC works together with the sequencer to control the flow of data. The process can be broken down as follows:
3030

docs/cdk/concepts/index.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1,3 @@
1-
Welcome to the Concepts section.
1+
This section covers some of the basic concepts needed to understand the CDK setting, which is a platform designed to allow developers to choose between validium and zk-rollup architectures.
2+
3+
Concepts such as a rollup, a validium and data availability committee (DAC) are defined. Implications of off-chain data availability are briefly discussed.

docs/cdk/concepts/validium.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
Validiums are blockchain scaling solutions that do not store transaction data.
1+
Validiums are blockchain scaling solutions that do not store transaction data on-chain.
22

33
!!! info "Recommended resource"
44
See Ethereum.org's detailed [description of validiums](https://ethereum.org/en/developers/docs/scaling/validium/).

docs/cdk/how-to/index.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1,4 @@
1-
This introduction to the how to section is being written.
1+
This section describes how to manage policies pertaining to data access in the case of a Validium.
2+
3+
Validia store data off-chain, and with this option comes the need to manage both the data and access to the data. This is facilitated through policies that stipulate which addresses can have access to data. Lists of addresses, such as the Allowlist and Denylist, are therefore kept to exclude or include certain addresses to having access.
4+

docs/cdk/spec/index.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1,7 @@
1-
This introduction to the specification section is being written.
1+
This section gives a comparison between a validium and a zk-rollup.
2+
3+
The main difference is the fact that a validium has a data availability layer whereas a zk-rollup does not. This difference alone is the reason for the substantially reduced gas fees for a validium compared to the zk-rollup.
4+
5+
However, with this off-chain data availability, there is a trade-off between gas fees and security. Unlike in the zk-rollup, where forced batches are activated, the validium suffers from the possibility for the sequencer to go offline or the DAC to collude among themselves to withold state data.
6+
7+
What remains common between the two architectures is the generation of proofs.

docs/img/cdk/cdk-val-dac-02.png

434 KB
Loading

0 commit comments

Comments
 (0)