Source: Polygon Forum; Author: Baishui, Golden Finance
Preface
We invite the community to discuss a proposal to securely connect Polygon PoS to the AggLayer using zero-knowledge (ZK) validators to verify the network’s consensus mechanism, thereby establishing the finality of network settlement to the AggLayer. This consensus proof is complementary to the pessimistic proof and ensures the security of all chains connected to the AggLayer. For more information on pessimistic proofs, see here: Introducing Pessimistic Proofs 2
Consensus proofs will be secured by the Plonky3 proof system via Succinct Labs’ SP1, a general-purpose zkVM that allows for the execution of the AggLayer proof standard Rust. More information on the collaboration between Polygon Labs and Succinct Labs can be found here: SP1, built on Plonky3, will help secure unified liquidity 1
This upgrade will bring two immediate benefits:
Aggregate liquidity, users, and status through AggLayer to bring greater network effects to users and developers;
An upgraded bridge experience, including permissionless token transfers.
background
A year ago, the community began discussing a proposal that would make Polygon PoS a zkEVM Validium, upgrading the network to a ZK-powered L2. This remains the long-term goal for the final state of Polygon PoS. The challenges of achieving this goal largely depend on a commitment to maintaining the low-fee, Ethereum-for-all ethos of Polygon PoS.
The Type 1 zkEVM prover used to upgrade Polygon PoS to ZK L2 is already able to attest to existing Ethereum blocks at low cost. For the application of Polygon PoS, the question now is how to do this at scale.
For now, if this discussion is favorable and the subsequent PIP is accepted by the community, the upgrade will serve as an intermediate step to becoming a full ZK L2. Connecting Polygon PoS to the AggLayer will provide the benefits of a unified bridge while still being able to rely on the enhanced security guarantees provided by the validator set.
technical details
If community discussion develops around this proposal, a future PIP or PIPs will provide appropriate technical specifications. However, at a high level, this upgrade would require at least the following:
Proof of Consensus: A new consensus validation contract will be deployed on Ethereum. This contract will be able to verify that Polygon PoS has reached consensus and that any withdrawals meet the criteria set by the pessimistic proof logic. A proposal will be created to add it to the list of available validation contracts for the Unified Bridge. (See the practical question below for additional considerations on this point.)
Bridge Implementation: The Unified Bridge contract will be deployed on Polygon PoS.
PoS Portal: Existing tokens in the PoS Portal Bridge will be upgraded to use the Unified Bridge and ownership will be destroyed, eliminating multi-sig control over these tokens.
Network Roles: Using a consensus proof design Settlement to the AggLayer will require some entities to submit the required information. (See Practical Issues below for additional considerations on this point.)
Client Changes
No significant client changes to Bor or Heimdall are required to complete this upgrade. While upgrading to Heimdall v2 may allow for future optimizations, this is not necessary for initial deployments.
Bridge Changes
No changes are required to the StateSync mechanism that supports FxPortal or Plasma Bridge to accomplish this upgrade. In addition:
The Unified Bridge will be deployed as a new, standalone bridge.
Tokens mapped using the PoS Portal will be upgraded to use the Unified Bridge instead of the FxPortal, and the PoS Portal will be deprecated.
timeline
If the outcome of this discussion is satisfactory, a formal PIP will be released. The main dependency is the completion of a production-ready implementation of pessimistic proofs, expected to be completed by mid-summer. Once completed, a formal PIP will be released, most likely in the fall. Following this timeline, connecting Polygon PoS to AggLayer could be completed by the end of 2024, assuming community acceptance.
Meanwhile, Polygon PoS core engineers expect the upcoming Ahmadabad hard fork to be deployed in July, with Heimdall v2 expected to be launched sometime after that. Currently, neither upgrade is a dependency for connecting Polygon PoS to the AggLayer. However, there is another way to implement consensus proof that requires deeper changes to Heimdall.
Practical problems
Signature-based consensus proof
The proposal outlines the use of Polygon Plonky3 to represent the consensus of Polygon PoS, with the SP1 zkVM providing the maintainability and developer velocity benefits of Rust. Broadly speaking, the goal of consensus proof is to represent the local chain state. This can also be achieved by modifying Heimdall to use a different signing method.
For example, if BLS or ICE-FROST threshold signatures were used during consensus, that single signature could represent the consensus of the AggLayer. One benefit of this approach is simplicity: communication between Polygon PoS and AggLayer can be added to Heimdall as a task, in the same process that currently submits checkpoints to L1.
One potential drawback is that this approach would require deeper changes to the network’s consensus mechanism, which could extend development time. This design would eliminate the need for new network actors.
Network roles that communicate with the AggLayer
In order for Polygon PoS to connect to the AggLayer using consensus proof, a new role is required. This role will be responsible for submitting the following information to the AggLayer:
The local bridge status of the network;
Proof of consensus.
How and by whom this function is performed is an area of active investigation. At a high level, protocol researchers are considering one of the following:
Allowlist addresses perform this role first, with the goal of making it permissionless after the AggLayer stack has had a chance to harden;
This role is immediately permissionless, in which case the network participant will perform this function in exchange for some as-yet-unquantified reward. If this is the preferred option and there are no other security concerns, then it will need to be determined by what mechanism this network participant is selected; one potential option is to use the existing leadership selection in Heimdall.
Summarize
With over 400 million unique addresses, over $2 billion in assets bridged from Ethereum, and tens of thousands of applications, Polygon PoS remains one of the most widely used blockchains in the world. Users and developers love it because of its strong community, network effects, and low fees for everyone, which are often orders of magnitude lower than the famous Ethereum L2.
The core developers of Polygon Labs have been focusing on the research and development of Ethereum scaling technology for many years; it started with Polygon PoS. Over the years, they have come to two conclusions: ZK technology is the only practical way to achieve verifiable off-chain computation, and aggregation is the only way to achieve multi-chain interoperability without sacrificing chain sovereignty.
The joint efforts of Succinct Labs and Polygon Labs are based on a shared belief that collaboration with open source technology can build the best public interest. The outcome of discussions about the future of Polygon PoS is ultimately in the hands of the community. We once again invite you to analyze, discuss, and hopefully reach a consensus to implement this proposal.
