-
Notifications
You must be signed in to change notification settings - Fork 332
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
updates to overview and release notes
- Loading branch information
1 parent
8d5197f
commit d8834b1
Showing
3 changed files
with
65 additions
and
93 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,42 +1,52 @@ | ||
| The **Polygon Chain Development Kit (CDK)** is a modular, open-source framework for building scalable and secure Layer 2s (L2s). Designed for flexibility, the Polygon CDK stack has 3 main configurations (with options to customize further): zk rollup config, validium config, and the Agglayer native config. | ||
| # What is Polygon CDK? | ||
|
|
||
| Polygon CDK is a modular, open-source framework for building Ethereum-compatible Layer 2 blockchains. It allows developers to create scalable, customizable chains, including: | ||
| - **zk-Rollups**: Chains using zero-knowledge proofs for high throughput and trustless finality. | ||
| - **Validiums**: Chains with off-chain data availability for cost-efficient scalability. | ||
| - **Sovereign Chains**: Chains natively connected to the Agglayer, secured via pessimistic proofs, enabling interoperability and shared liquidity. | ||
|
|
||
| With Polygon CDK, developers can build chains tailored to their needs while leveraging Ethereum’s security and existing ecosystem. | ||
|
|
||
| --- | ||
|
|
||
| ## Why Use Polygon CDK? | ||
| ## How Does It Work? | ||
|
|
||
| Polygon CDK simplifies the process of building Layer 2 blockchains by providing pre-built components for every essential layer of a chain. Here’s how it works at a high level: | ||
|
|
||
| ### Execution Layer | ||
| - **Sequencer Nodes**: Handle transaction ordering and provide RPC (Remote Procedure Call) endpoints for interacting with the chain. These nodes are essential for processing and validating transactions. | ||
| - **zkEVM Prover (Hermes)**: For zk-Rollups, this component generates zero-knowledge proofs to ensure transactions are secure and trustless. This is optional for other configurations. | ||
| - **Pool Manager**: Optimizes resource allocation for zkEVM-based chains, used in zk-Rollup configurations to process transactions efficiently. | ||
|
|
||
| ### **1. Build ZK-Powered Chains** | ||
| Polygon CDK enables developers to launch chains using cutting-edge zero-knowledge (ZK) technology for: | ||
| - **Trustless Finality**: Transactions are validated without relying on centralized authorities. | ||
| - **Maximum Security**: Leverage zk-proofs to safeguard user data and ensure cryptographic integrity. | ||
| ### Data Availability | ||
| - **Ethereum DA**: Stores transaction data directly on Ethereum for zk-Rollup configurations, ensuring maximum security and decentralization. | ||
| - **Custom DAC (Data Availability Committee)**: For Validium configurations, this off-chain solution provides scalability and cost-efficiency while maintaining data integrity. | ||
| - **Agglayer Pessimistic Proofs**: Used in Sovereign Chains, Agglayer ensures security and enables cross-chain functionality without requiring zk-SNARKs or on-chain data storage. | ||
|
|
||
| ### **2. Modular Architecture** | ||
| - **Customizable Components**: Select and configure modules like consensus, data availability, and proving systems to fit your use case. | ||
| - **Future-Ready Design**: Adapt your chain as requirements evolve or new technologies emerge. | ||
| ### Settlement Layer | ||
| - **Ethereum Bridge Contracts**: Used by zk-Rollups to finalize transactions on Ethereum, ensuring trustless settlement. | ||
| - **Agglayer Integration**: Sovereign Chains settle transactions and enable interoperability through Agglayer, which uses cryptographic pessimistic proofs to secure cross-chain interactions. | ||
|
|
||
| ### **3. Interoperability** | ||
| - **Agglayer Integration**: Seamlessly connect to Agglayer for cross-chain functionality and ecosystem bootstrapping. | ||
| - **Ethereum-Compatible**: Build on a foundation that supports Ethereum tooling, enabling easy adoption and user migration. | ||
| ### Sequencer | ||
| - **Sequence Sender**: Ensures that transactions are ordered properly and maintains the chain’s data integrity. | ||
|
|
||
| ### **4. High Performance** | ||
| - **Erigon Client**: Benefit from faster syncing and high transaction throughput powered by the optimized Erigon architecture. | ||
| - **Cost Efficiency**: Reduce transaction fees by orders of magnitude compared to Ethereum Layer 1. | ||
| ### Interoperability | ||
| - **Bridge APIs**: Enable cross-chain transfers of assets and data, connecting Polygon CDK chains with Ethereum and other Layer 2s. | ||
| - **Aggregator**: Combines multiple proofs into a single proof for zk-Rollups, optimizing validation processes. | ||
|
|
||
| ### **5. Sovereignty** | ||
| Maintain full control over your chain’s: | ||
| - Governance and revenue. | ||
| - Security policies and economic frameworks. | ||
| - Finality and operational structure. | ||
| ### A Note on Sovereign Chains | ||
| Sovereign Chains built with Polygon CDK don’t use a prover like zk-SNARKs. Instead, they rely on the Agglayer for security via cryptographic pessimistic proofs. This approach ensures interoperability and scalability while allowing Sovereign Chains to maintain full independence. | ||
|
|
||
| By combining these components, Polygon CDK provides the flexibility to build zk-Rollups, Validiums, or Sovereign Chains based on your project's requirements. The framework is designed to deliver high performance, low costs, and seamless interoperability. | ||
|
|
||
| --- | ||
|
|
||
| ## Key Features at a Glance | ||
| ## Why Should Developers Care? | ||
|
|
||
| - **Low Costs and High Performance**: Polygon CDK chains offer significantly lower transaction fees and faster finality compared to Ethereum Layer 1 and many other Layer 2 solutions, making them ideal for high-throughput applications. | ||
|
|
||
| - **Seamless Cross-Chain Interoperability**: With Agglayer integration (currently in testnet), Polygon CDK chains can securely interact with other chains and external networks. This enables shared liquidity, cross-chain functionality, and ecosystem bootstrapping. | ||
|
|
||
| | **Feature** | **Description** | | ||
| |-------------------------|---------------------------------------------------------| | ||
| | **Trustless Finality** | ZK-powered chains with decentralized validation. | | ||
| | **Scalable Design** | Optimized for high transaction throughput and low fees. | | ||
| | **Customizability** | Modular components tailored to specific use cases. | | ||
| | **Cross-Chain Ready** | Connect seamlessly to other chains via Agglayer. | | ||
| | **High-Speed Syncing** | Built on the ultra-efficient Erigon client. | | ||
| - **Modular and Future-Ready**: Developers can customize their chain’s architecture to fit specific needs, whether creating zk-Rollups, Validiums, or Sovereign Chains. The modular design ensures compatibility with emerging technologies. | ||
|
|
||
| --- | ||
| - **Ethereum-Compatible**: Polygon CDK supports EVM tooling, ensuring a smooth developer experience and easy migration for existing applications while tapping into Ethereum's established ecosystem. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,60 +1,22 @@ | ||
| The **Fork ID 12 release** introduces the most robust Polygon CDK stack to date. With a focus on stability, performance and interopability, this release was driven by feedback from the ecosystem, developers, and IPs. | ||
| Fork ID 12 introduces significant updates to the Polygon CDK stack, enhancing performance, scalability, and the developer experience. This release focuses on improvements across the client layer, proving systems, and developer tooling, making it easier to build and operate high-performance Layer 2 chains. | ||
|
|
||
| --- | ||
|
|
||
| ## What’s New in Fork ID 12? | ||
| ## Key Updates | ||
|
|
||
| ### **1. Full Execution Proofs** | ||
| - **Trustless Finality:** Advanced zk-based finality ensures transactions are secure, decentralized, and verified without reliance on centralized entities. | ||
| - **Customizable Proving Systems:** Developers have full control to define and optimize proof configurations for zk rollups, validium setups, or Agglayer-native configurations. | ||
| 1. **Erigon Integration** | ||
| - Faster syncing for quicker chain setup and operation. | ||
| - Improved transaction throughput and resource efficiency. | ||
| - Full compatibility with Ethereum tools and infrastructure. | ||
|
|
||
| ### **2. Erigon Integration** | ||
| - **High-Speed Data Syncing:** Integrates the Erigon client to deliver faster syncing and improved resource efficiency, enabling high transaction throughput. | ||
| - **Seamless Ethereum Compatibility:** Leverages Erigon’s Ethereum foundation, ensuring smooth integration with Ethereum tooling and infrastructure. | ||
| 2. **Proving System Enhancements** | ||
| - Increased capacity for handling complex transactions and higher volumes. | ||
| - Faster proof generation for quicker deployment and smoother operations. | ||
|
|
||
| ### **3. Prover System Upgrades** | ||
| - **Increased Proving Capacity:** Expanded zkCounter limits now support complex computation and higher throughput. | ||
| - **Faster Proof Generation:** Optimized proof pipelines reduce time-to-deployment and enhance performance in production environments. | ||
| 3. **Developer Tooling Improvements** | ||
| - Simplified CLI for easier chain deployment and configuration. | ||
| - Updated documentation with step-by-step guides for developers. | ||
|
|
||
| ### **4. Developer Tooling Improvements** | ||
| - **Refined CLI:** A more intuitive and streamlined command-line interface simplifies chain deployment, configuration, and testing. | ||
| - **Documentation Updates:** New and improved guides provide step-by-step instructions for deploying, customizing, and migrating L2 chains. | ||
|
|
||
| --- | ||
|
|
||
| ## Why This Matters for Developers | ||
|
|
||
| ### **1. Enhanced Modularity** | ||
| Fork ID 12 enables developers to design chains specific to their use case, with modular components for: | ||
| - Consensus and governance mechanisms. | ||
| - Proving systems and data availability configurations. | ||
|
|
||
| ### **2. Industry-Leading Performance** | ||
| The integration of Erigon and enhanced proving capabilities allow: | ||
| - Greater scalability for high-transaction environments. | ||
| - Stability and performance improvements to keep the chain operational at high capacity. | ||
|
|
||
| ### **3. Simplified Interoperability** | ||
| Chains built with Fork ID 12 can integrate with the **Agglayer** in the future unlocking: | ||
| - Cross-chain transactions. | ||
| - Ecosystem bootstrapping for liquidity and growth. | ||
|
|
||
| ### **4. Increased Security and Sovereignty** | ||
| Leverage zk-proofs for robust, trustless security while maintaining control over your chain’s: | ||
| - Governance. | ||
| - Economic policies. | ||
| - Finality mechanisms. | ||
|
|
||
| --- | ||
|
|
||
| ## Key Benefits at a Glance | ||
|
|
||
| | **Feature** | **What’s Improved in Fork ID 12?** | | ||
| |-------------------------|----------------------------------------------------------| | ||
| | **Proving Systems** | Higher throughput and faster proof generation. | | ||
| | **Erigon Integration** | Faster syncing and Ethereum compatibility. | | ||
| | **Developer Tooling** | Simplified CLI and detailed documentation. | | ||
| | **Customizability** | More options to tailor chains to unique requirements. | | ||
| | **Cross-Chain Ready** | Native Agglayer support for seamless interoperability. | | ||
|
|
||
| --- | ||
| 4. **Full Execution Proofs** | ||
| - Comprehensive Validation: verifies that all state transitions executed by the underlying VM (such as Polygon zkEVM) adhere to the protocol’s specifications. | ||
| - Flexibility Across Modes: FEP supports both rollup and validium modes, providing scalability and security tailored to different use cases. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters