Polygon Adds Besu Support to CDK for AggLayer Connectivity
Key Highlights
- Polygon CDK now supports Hyperledger Besu, enabling institutions to launch private chains with native AggLayer connectivity from genesis.
- Cross-chain transfers use pessimistic zero-knowledge proofs verified on Ethereum, with accounting checks designed to prevent withdrawals exceeding a connected chain’s asset balance.
- The architecture removes reliance on external signer committees for bridge security while preserving each institution’s control over validators and permissioning.
Polygon, a Layer-2 scaling and infrastructure platform, has added Hyperledger Besu as a supported configuration of its Chain Development Kit (CDK), enabling institutions to launch private Besu networks connected to AggLayer. The update allows institutions to launch private Besu chains that connect natively to AggLayer from the first block. Transfers between connected chains settle against zero-knowledge proofs verified on Ethereum.
According to the official announcement, Besu is an open-source Ethereum client that supports permissioned networks in which a known set of validators participates. Institutions have commonly selected it because it is familiar to enterprise security teams and supports consensus mechanisms such as QBFT.
Private Besu networks have traditionally operated in isolation, requiring separate integration work or bridges that depend on committees of signers to move assets to other chains.
How the integration works
The announcement notes that, with the new Polygon CDK Besu configuration, a private Besu chain can run the standard Besu client while maintaining a connection to AggLayer. Bridge contracts are written into the chain’s genesis block. A dedicated set of services keeps the chain synchronized with the shared bridge state and packages bridge activity into certificates.
AggLayer then requests a pessimistic proof that verifies the accounting balances across connected chains. Once the proof is verified on Ethereum, the transfer can be claimed on the destination chain.
The architecture does not rely on external signers or committees for bridge security. Each connected chain maintains a running balance of assets received and sent. Before a withdrawal finalizes, the accounting must balance. If a chain attempts to withdraw more of an asset than it holds, the proof fails and the transfer does not proceed.
Features for institutional networks
A chain launched with Polygon CDK Besu keeps control of its own validators and permissioning rules. Transaction data remains within the institution’s private infrastructure and is not posted to Ethereum.
Assets can move between the private chain and other AggLayer-connected networks, including public chains with stablecoin and tokenized-asset liquidity. Polygon says AggLayer is designed to maintain a canonical representation of assets across connected chains, rather than relying on separate wrapped versions for each bridge.
Polygon stated that no revenue share is owed to the company on activity generated by networks using the configuration. The deployment documentation is available publicly on GitHub. The stack is live for production use on the Ethereum mainnet, with testnet and development network options available for evaluation.
Context within Polygon’s broader activities
The addition of Besu support forms part of Polygon’s ongoing work on its Open Money Stack. In mid-October 2026, Polygon completed the acquisition of Coinme, a licensed U.S. money transmitter. The deal provides regulated money-movement coverage across 48 U.S. states through state licenses and FinCEN registration. Polygon has also expanded the Open Money Stack to support USDT payment flows on the TRON network, covering custody, cross-chain transfers, and payouts.
Separately, Polygon recently implemented two coordinated hardforks across its proof-of-stake clients to address denial-of-service vectors. The changes were activated on the mainnet before public disclosure, following a process that included private rollout and testing on the Amoy testnet.
Options for institutions
Polygon CDK previously supported the OP Stack configuration. Both CDK Besu and CDK OP Stack connect natively to AggLayer. The choice between them depends on the client software already familiar to an institution’s technical team and the specific requirements of the intended network. In the Besu configuration, validators run QBFT consensus while additional services handle the AggLayer connection and keep validators isolated from public network exposure.
The Linux Foundation, which governs Hyperledger Besu, has noted that interoperability remains a priority for institutional blockchain deployments. Polygon’s documentation positions the CDK Besu stack as a way for institutions to retain control over a private network while gaining a built-in connection to other chains through zero-knowledge proofs rather than multi-signature bridges.
Also Read: Multicoin Capital Rejects Standalone AI Investments to Focus on Crypto
Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.


