Skip to content

Commit e58824d

Browse files
commit merge resolutio
2 parents 309e1c9 + 5417849 commit e58824d

File tree

14 files changed

+301
-138
lines changed

14 files changed

+301
-138
lines changed

docs/cdk/index.md

Lines changed: 1 addition & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -1,34 +1,10 @@
11
<div class="flex-figure" markdown="1">
22
<div class="flex-figure-left" markdown="1">
33
# Polygon CDK
4-
Polygon Chain Development Kit (CDK) is a modular, open source software toolkit for blockchain developers which supports the installation and configuration of a variety of chain architectures. Polygon CDK empowers developers to launch new L2 chains on [Ethereum](https://ethereum.org/en/) or, in the future, transition existing Layer 1 (L1) chains into L2s.
4+
Polygon Chain Development Kit (CDK) is a modular, open source software toolkit for blockchain developers to launch new L2 chains on Ethereum.
55
</div>
66
<div class="flex-figure-right">
77
<img src="../img/cdk/cdk.svg" class="figure figure-right" alt="" />
88
</div>
99
</div>
1010

11-
Developers can select a chain architecture specific to their needs from a set of supported, open source components. Alternatively, developers can select custom components for specific requirements. The diagram below shows the two supported configuration options, rollup or validium. Rollups post transaction data from Polygon CDK directly onto Ethereum whereas validiums only post the transaction hash.
12-
13-
![](../img/cdk/overview-1.png)
14-
15-
A chain tailored for a specific application might leverage the zkEVM execution environment, adopt the Validium mode, and implement a centralized sequencer.
16-
17-
Regardless of these individualized choices, after the completion of the in-development interop layer, every chain will have the option to be interoperable with other Polygon network chains.
18-
19-
## Why build with Polygon CDK?
20-
21-
Polygon CDK gives developers a toolkit for sovereign and modular chain design, without sacrificing future interoperability with other L2 chains. Chains built with Polygon CDK can access an ecosystem of (forthcoming) unified liquidity, optimized performance, and seamless asset transfers, all while prioritizing user experience and data security.
22-
23-
Here is what developers can expect when they build with Polygon CDK.
24-
25-
1. **Modularity and sovereignty**: Polygon CDK offers a modular environment for ZK-powered L2 chain design. Developers can customize chains according to their needs.
26-
2. **Scalability**: Polygon CDK-developed L2 chains enhance transaction speed and can be multiplied to achieve an elastically scalable ecosystem.
27-
3. **Independent data availability**: With a dedicated data availability layer and a data availability committee, Polygon CDK-developed chains provide robust off-chain data access and reliability. This structure, independent of Ethereum, ensures substantial data resilience and integrity.
28-
4. **Interoperability (forthcoming)**: Through an in-development interop layer, CDK-developed chains can be seamlessly interoperable, meaning atomic L2 <> L2 transactions. Chains deployed with Polygon CDK will have the opportunity to opt-in to the interop layer and tap unified liquidity.
29-
5. **Near-instant finality**: Chains deployed using Polygon CDK rely on cryptographic security, ensuring transaction integrity without the need of full nodes. This approach guarantees near-instant finality and robust security.
30-
6. **Extensive Web3 support**: Polygon CDK chains leverage a comprehensive ecosystem with premium service providers offering essential tools for application integration, development, and deployment.
31-
32-
The following diagram illustrates how Polygon CDK-developed chains may opt into a web of interoperable L2 chains:
33-
34-
![](../img/cdk/overview-2.png)

docs/cdk/overview.md

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
Polygon Chain Development Kit (CDK) is a modular, open source software toolkit for blockchain developers which supports the installation and configuration of a variety of chain architectures. Polygon CDK empowers developers to launch new L2 chains on Ethereum or, in the future, transition existing Layer 1 (L1) chains into L2s.
2+
3+
With Polygon CDK, developers can select a chain architecture specific to their needs from a set of supported, open source components. Alternatively, developers can select custom components for specific requirements. The diagram below shows the two supported configuration options, rollup or validium. Rollups post transaction data from Polygon CDK directly onto Ethereum whereas validiums only post the transaction hash.
4+
5+
![](../img/cdk/overview-1.png)
6+
7+
A chain tailored for a specific application might leverage the zkEVM execution environment, adopt the Validium mode, and implement a centralized sequencer.
8+
9+
Regardless of these individualized choices, after the completion of the in-development interop layer, every chain will have the option to be interoperable with other Polygon network chains.
10+
11+
Polygon CDK gives developers a toolkit for sovereign and modular chain design, without sacrificing future interoperability with other L2 chains. Chains built with Polygon CDK can access an ecosystem of (forthcoming) unified liquidity, optimized performance, and seamless asset transfers, all while prioritizing user experience and data security.
12+
13+
Here is what developers can expect when they build with Polygon CDK.
14+
15+
1. **Modularity and sovereignty**: Polygon CDK offers a modular environment for ZK-powered L2 chain design. Developers can customize chains according to their needs.
16+
2. **Scalability**: Polygon CDK-developed L2 chains enhance transaction speed and can be multiplied to achieve an elastically scalable ecosystem.
17+
3. **Independent data availability**: With a dedicated data availability layer and a data availability committee, Polygon CDK-developed chains provide robust off-chain data access and reliability. This structure, independent of Ethereum, ensures substantial data resilience and integrity.
18+
4. **Interoperability (forthcoming)**: Through an in-development interop layer, CDK-developed chains can be seamlessly interoperable, meaning atomic L2 <> L2 transactions. Chains deployed with Polygon CDK will have the opportunity to opt-in to the interop layer and tap unified liquidity.
19+
5. **Near-instant finality**: Chains deployed using Polygon CDK rely on cryptographic security, ensuring transaction integrity without the need of full nodes. This approach guarantees near-instant finality and robust security.
20+
6. **Extensive Web3 support**: Polygon CDK chains leverage a comprehensive ecosystem with premium service providers offering essential tools for application integration, development, and deployment.
21+
22+
The following diagram illustrates how Polygon CDK-developed chains may opt into a web of interoperable L2 chains:
23+
24+
![](../img/cdk/overview-2.png)

docs/index.md

Lines changed: 17 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ hide:
1111
<div class="hero-content-flex">
1212
<div class="hero-left">
1313
<h1 class="hero-heading">The Polygon Knowledge Layer</h1>
14-
<p class="hero-subext">Welcome to the resource center for Polygon protocols and technology. Learn to build dApps, how to configure and launch blockchains as Layer 2s on Ethereum, and read the latest Polygon’s research on the zero-knowledge scaling technologies being built at Polygon Labs.</p>
14+
<p class="hero-subext">Welcome to the technical documentation and knowledge resources for Polygon protocols and scaling technologies. Here you can learn how to build and deploy dApps, launch ZK rollups and validiums as Layer 2s on Ethereum, spin up nodes, and learn all about the latest in ZK research.</p>
1515
</div>
1616
<div class="hero-right"><img src="img/home/main-img.svg" loading="lazy" alt="" class="hero-image"></div>
1717
</div>
@@ -165,17 +165,9 @@ hide:
165165
<p class="home-section-subtext">Are you ready to start building?</p>
166166
</div>
167167
<div class="flexbox">
168-
<a href="pos/get-started/building-on-polygon/" class="home-feature-card w-inline-block"><img src="img/home/polygon-icon.svg" loading="lazy" alt="" class="feature-icon">
169-
<div class="feature-content-wrapper">
170-
<div class="feature-content-name">Polygon PoS: Build a new dApp</div>
171-
<div class="arrow-embed w-embed"><svg xmlns="http://www.w3.org/2000/svg" display="block" width="100%" height="auto" viewbox="0 0 16 17" fill="none">
172-
<path d="M9.98805 5.70133L3.41071 12.2787L4.58922 13.4572L11.1666 6.87976V12.2013H12.8333V4.03467H4.66665V5.70133H9.98805Z" fill="currentColor"></path>
173-
</svg></div>
174-
</div>
175-
</a>
176-
<a href="pos/how-to/smart-contracts/" class="home-feature-card w-inline-block"><img src="img/home/polygon-icon.svg" loading="lazy" alt="" class="feature-icon">
168+
<a href="zkEVM/get-started/deploy-zkevm/" class="home-feature-card w-inline-block"><img src="img/home/polygon-icon.svg" loading="lazy" alt="" class="feature-icon">
177169
<div class="feature-content-wrapper">
178-
<div class="feature-content-name">Polygon PoS: Deploy an existing smart contract</div>
170+
<div class="feature-content-name">Polygon CDK: Deploy a local test rollup</div>
179171
<div class="arrow-embed w-embed"><svg xmlns="http://www.w3.org/2000/svg" display="block" width="100%" height="auto" viewbox="0 0 16 17" fill="none">
180172
<path d="M9.98805 5.70133L3.41071 12.2787L4.58922 13.4572L11.1666 6.87976V12.2013H12.8333V4.03467H4.66665V5.70133H9.98805Z" fill="currentColor"></path>
181173
</svg></div>
@@ -191,27 +183,35 @@ hide:
191183
</div>
192184
</div>
193185
</a>
186+
<a href="pos/get-started/building-on-polygon/" class="home-feature-card w-inline-block"><img src="img/home/polygon-icon.svg" loading="lazy" alt="" class="feature-icon">
187+
<div class="feature-content-wrapper">
188+
<div class="feature-content-name">Polygon PoS: Build a new dApp</div>
189+
<div class="arrow-embed w-embed"><svg xmlns="http://www.w3.org/2000/svg" display="block" width="100%" height="auto" viewbox="0 0 16 17" fill="none">
190+
<path d="M9.98805 5.70133L3.41071 12.2787L4.58922 13.4572L11.1666 6.87976V12.2013H12.8333V4.03467H4.66665V5.70133H9.98805Z" fill="currentColor"></path>
191+
</svg></div>
192+
</div>
193+
</a>
194194
</div>
195195
<div class="flexbox items-4">
196-
<a href="zkEVM/get-started/setup-nodes/production-node/" class="home-feature-card w-inline-block"><img src="img/home/polygon-icon.svg" loading="lazy" alt="" class="feature-icon">
196+
<a href="pos/how-to/smart-contracts/" class="home-feature-card w-inline-block"><img src="img/home/polygon-icon.svg" loading="lazy" alt="" class="feature-icon">
197197
<div class="feature-content-wrapper">
198-
<div class="feature-content-name">Polygon zkEVM: Set up a zkNode</div>
198+
<div class="feature-content-name">Polygon PoS: Deploy an existing smart contract</div>
199199
<div class="arrow-embed w-embed"><svg xmlns="http://www.w3.org/2000/svg" display="block" width="100%" height="auto" viewbox="0 0 16 17" fill="none">
200200
<path d="M9.98805 5.70133L3.41071 12.2787L4.58922 13.4572L11.1666 6.87976V12.2013H12.8333V4.03467H4.66665V5.70133H9.98805Z" fill="currentColor"></path>
201201
</svg></div>
202202
</div>
203203
</a>
204-
<a href="cdk/get-started/quickstart-validium/" class="home-feature-card w-inline-block"><img src="img/home/polygon-icon.svg" loading="lazy" alt="" class="feature-icon">
204+
<a href="zkEVM/get-started/setup-nodes/production-node/" class="home-feature-card w-inline-block"><img src="img/home/polygon-icon.svg" loading="lazy" alt="" class="feature-icon">
205205
<div class="feature-content-wrapper">
206-
<div class="feature-content-name">Polygon CDK: Create your own validium</div>
206+
<div class="feature-content-name">Polygon zkEVM: Set up a zkNode</div>
207207
<div class="arrow-embed w-embed"><svg xmlns="http://www.w3.org/2000/svg" display="block" width="100%" height="auto" viewbox="0 0 16 17" fill="none">
208208
<path d="M9.98805 5.70133L3.41071 12.2787L4.58922 13.4572L11.1666 6.87976V12.2013H12.8333V4.03467H4.66665V5.70133H9.98805Z" fill="currentColor"></path>
209209
</svg></div>
210210
</div>
211211
</a>
212-
<a href="zkEVM/get-started/deploy-zkevm/" class="home-feature-card w-inline-block"><img src="img/home/polygon-icon.svg" loading="lazy" alt="" class="feature-icon">
212+
<a href="cdk/get-started/quickstart-validium/" class="home-feature-card w-inline-block"><img src="img/home/polygon-icon.svg" loading="lazy" alt="" class="feature-icon">
213213
<div class="feature-content-wrapper">
214-
<div class="feature-content-name">Polygon CDK: Deploy a local test rollup</div>
214+
<div class="feature-content-name">Polygon CDK: Create your own validium</div>
215215
<div class="arrow-embed w-embed"><svg xmlns="http://www.w3.org/2000/svg" display="block" width="100%" height="auto" viewbox="0 0 16 17" fill="none">
216216
<path d="M9.98805 5.70133L3.41071 12.2787L4.58922 13.4572L11.1666 6.87976V12.2013H12.8333V4.03467H4.66665V5.70133H9.98805Z" fill="currentColor"></path>
217217
</svg></div>

docs/miden/get-started/index.md

Lines changed: 0 additions & 5 deletions
This file was deleted.

docs/miden/index.md

Lines changed: 2 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,9 @@
11
<div class="flex-figure" markdown="1">
22
<div class="flex-figure-left" markdown="1">
33
# Polygon Miden
4-
Polygon Miden is a zero-knowledge (ZK) rollup running the Miden VM, a virtual machine that prioritizes ZK-friendliness over EVM compatibility. Polygon Miden uses a novel, actor-based state model to allow users to prove their own state locally, achieving high throughput and privacy at the same time. Polygon Miden is a general purpose rollup where developers can write and deploy arbitrary smart contracts.
4+
Polygon Miden is an in-development zero-knowledge (ZK) rollup running the Miden VM, a virtual machine that prioritizes ZK-friendliness over EVM compatibility.
55
</div>
66
<div class="flex-figure-right">
77
<img src="../img/miden/miden.svg" class="figure figure-right" alt="" />
88
</div>
9-
</div>
10-
11-
Miden is currently in-development. A public testnet for Polygon Miden is expected in Q1 2024.
12-
13-
## Why build with Polygon Miden?
14-
Polygon Miden offers features and benefits that are not available on Ethereum. Developers are empowered to build high-throughput, private dApps.
15-
16-
- **Beyond EVM**: Build novel applications, i.e., on-chain order book exchanges, complex incomplete information games, compliant and private asset management apps
17-
- **Privacy**: Control your data with local data storage. In Polygon Miden, privacy is the cheaper option and—if you want—the network only tracks a commitment to your data
18-
- **High throughput**: Build applications that can be used by many users at the same time. Client-side proving reduces the burden on the network and allows for parallel transaction execution
19-
- **Safety**: Account asset storage, account abstraction, privacy, and smart contracts in Rust are less prone to bugs and less exposed to hackers
9+
</div>

docs/miden/overview.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
Polygon Miden uses a novel, actor-based state model to allow users to prove their own state locally, achieving high throughput and privacy at the same time. Polygon Miden is a general purpose rollup where developers can write and deploy arbitrary smart contracts.
2+
3+
Miden is currently in-development. A public testnet for Polygon Miden is expected in Q1 2024.
4+
5+
Polygon Miden offers features and benefits that are not available on Ethereum. Developers are empowered to build high-throughput, private dApps.
6+
7+
- **Beyond EVM**: Build novel applications, i.e., on-chain order book exchanges, complex incomplete information games, compliant and private asset management apps
8+
- **Privacy**: Control your data with local data storage. In Polygon Miden, privacy is the cheaper option and—if you want—the network only tracks a commitment to your data
9+
- **High throughput**: Build applications that can be used by many users at the same time. Client-side proving reduces the burden on the network and allows for parallel transaction execution
10+
- **Safety**: Account asset storage, account abstraction, privacy, and smart contracts in Rust are less prone to bugs and less exposed to hackers

0 commit comments

Comments
 (0)