Skip to content

Commit a9eae35

Browse files
adding notes from chat
1 parent 9b860d3 commit a9eae35

File tree

8 files changed

+28
-6
lines changed

8 files changed

+28
-6
lines changed

docs/cdk/concepts/dac.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,8 @@
1-
A data availability committee (DAC) is an offchain network of nodes that provides data to a blockchain network. The advantages are:
1+
!!! note
2+
fix this: https://medium.com/coinmonks/what-is-data-availability-and-why-do-we-need-it-7993c039fc44
3+
4+
5+
A data availability committee (DAC) is an optional offchain network of nodes that provides data to a blockchain network. The advantages are:
26

37
- **Lower transaction fees**: Reduced computational requirements lead to lower fees.
48
- **State privacy**: A secure copy of state transitions ensures data integrity and privacy.

docs/cdk/get-started/overview.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
Polygon's Chain Development Kit (CDK) is a software tool for blockchain developers which allows easy install and configuration of a variety of chain architectures.
22

3-
!!! warning
3+
!!! warning "INCORRECT"
44
- At the time of writing, the CDK only supports validium nodes. The CDK in validium mode is in active development, with ongoing feature enhancements and issue resolutions.
55

66
For the latest updates, follow our official GitHub repositories:
@@ -10,4 +10,12 @@ Polygon's Chain Development Kit (CDK) is a software tool for blockchain develope
1010
- [Contracts](https://github.com/0xPolygon/cdk-validium-contracts)
1111
- CDK zkEVM-rollup mode is in development.
1212

13-
![CDK flavors](../../img/cdk/cdk-modes.jpg)
13+
![CDK flavors](../../img/cdk/cdk-modes.jpg)
14+
15+
16+
Notes from chat with Gabriel:
17+
18+
open source, **modular set of concepts, projects build L2/blockchain specific to needs/use cases
19+
20+
CDK -> conifguration choice of rollup and validium you make before you deploy
21+
? -> zero (type 1 prover), EDGE, Miden, zkWasm,
Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
Spin up an zkEVM ...
2+
3+
Then ...

docs/cdk/get-started/quickstart.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
1+
SME: Gabriel
22

33
!!! info
44
Please view the third-party content disclaimer [<ins>here</ins>](https://github.com/0xPolygon/wiki/blob/master/CONTENT_DISCLAIMER.md).
Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,6 @@
1+
!!! note
2+
Only validium
3+
14
## Policy overview
25

36
A **policy** is a set of rules that govern what actions are allowed or denied in the transaction pool.

docs/cdk/specification/performance-benchmarks.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,8 @@
11
[comment]: <> (data comes from here: https://www.notion.so/polygontechnology/CDK-Validium-TPS-Analysis-8aafda0d6b824c3781270cca30a8f70d#c6725ef8b93748ea8879d7e49e67c2fc and results are marked as OLD.. SME > @ruchawalawalkar)
22

3+
!!! note
4+
validium only
5+
36
## Strategy
47

58
The team calculated transactions-per-second, `tps`, for three transaction types:

docs/cdk/specification/validium-vs-zkevm.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ Polygon CDK running in validium mode inherits the core functionalities of a zkEV
44

55
## Key differences
66

7-
| | zkEVM (non-CDK) | Validium |
7+
| | Rollup | Validium |
88
| ------------------------ | ----------------------------------------------------------- | ---------------------------------------------------------------------------------- |
99
| **Node type** | [zkEVM node](https://github.com/0xPolygonHermez/zkevm-node) | [Validium node](https://github.com/0xPolygon/cdk-validium-node): zkEVM node with validium extensions |
1010
| **Data availability** | On-chain | Off-chain via DACs + [DA node](https://github.com/0xPolygon/cdk-data-availability) |

mkdocs.yml

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,9 +50,10 @@ nav:
5050
- Get started:
5151
- Overview: cdk/get-started/overview.md
5252
- Quickstart validium: cdk/get-started/quickstart.md
53+
- Quickstart zkEVM: cdk/get-started/quickstart-zkevm.md
5354
- Deploy validium: cdk/get-started/deploy-validium.md
5455
- How to:
55-
- Manage policies: cdk/how-to/manage-policies.md
56+
- Manage allowlists: cdk/how-to/manage-allowlists.md
5657
#- Architecture:
5758
- Specification:
5859
- Validium vs zkEVM: cdk/specification/validium-vs-zkevm.md

0 commit comments

Comments
 (0)