OpenZeppelin Support for Polkadot Hub and Polkadot Cloud in 2025

Ecosystem
1

Polkadot’s strategy in 2025 is driven by the release of a new EVM-compatible smart contract platform in Polkadot Hub as well as the continued evolution of Polkadot Cloud. As a follow on to the four OpenGov proposals OpenZeppelin completed in 2024 (see links below), OpenZeppelin has been collaborating Parity to support the launch of Polkadot Hub in 2025 with developer enablement (Solidity contract libraries and tooling) and to continue to support Polkadot Cloud with iterative updates.

OpenZeppelin brings a wealth of experience in developer enablement to the ecosystem, especially as Polkadot moves to target native Solidity developers and widely-used DeFi protocols for Polkadot Hub launch. Not only has OpenZeppelin has been the “point of entry” for many developers who are first learning smart contracts, who study OpenZeppelin’s contract libraries, such as the ERC20, ERC721, upgradeable, and so on, but OpenZeppelin contracts are the standard contracts that almost all protocols build upon:

  • $20 Trillion USD of total value has been transferred across OpenZeppelin contracts
  • Market Share of ~19% of all transactions on all chains
  • 100% penetration for OpenZeppelin contracts across top 50 DeFi protocols

OpenZeppelin is on the leading edge of a number of cross-ecosystem initiatives, including interop, privacy/ZK, and standards creation. Most recently, OpenZeppelin wrote and audited the flagship feature of Uniswap v4, the Hooks library, and is currently developing a based rollup stack with Taiko.

With this experience, OpenZeppelin can be a strong strategic partner to Parity and the broader Polkadot Ecosystem in their mission to launch a new platform and attract a new generation of developers with Polkadot Hub.

The collaboration has already started, and OpenZeppelin is currently working with Parity following the completion of the last treasury proposal. This proposal provides a context for the official working relationship over the next year.

Please see the full proposal here and the discussion on Polkassembly here

Note - links had to be removed due to the forum policy. See the Polkassembly link above for all links.

3 Likes
2

Tools support: OpenZeppelin will provide a customized Polkadot Contracts Wizard

What are the expenses for this on the OpenZeppelin side? revive, today, compiles all contracts featured in the wizard with all features enabled (including upgradable contracts) fine against v5.0.0. Having maintenance costs for Solidity libraries is exactly something we want to avoid by having Solidity as a first class citizen on AssetHub.

3 Likes
3

Thanks for taking a look, Cyrill.

The proposal here is not meant to point out shortcomings in PVM - actually you’ve been doing great work in designing this for compatibility. The goal for this proposal is to build trust with the broader non-Polkadot developer community by ensuring our libraries and tools work with Polkadot. Having first party support for those tools and tooling brings credibility, awareness and distribution that complements the work that Parity team is doing getting the technology into place.

The breakdown in cost among the different areas can be seen in the full proposal, which is linked above.

1 Like
4

Gotcha - ensuring continued support for the OpenZeppelin libraries is definitively what we want. I had to jump on this because I would consider our Solidity compatibility efforts a failure if we can’t get (most parts of) the most popular Solidity library to work well. Also, just because they compile doesn’t mean we are finished yet. There might be bugs, corner cases and I’m sure there could be changes made to the source code to optimize it for our target runtime. I’m looking forward to this collaboration!

1 Like