Polkadot&rsquo;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 (<a href="https://polkadot.subsquare.io/referenda/105" target="_blank" rel="noopener">1</a>, <a href="https://polkadot.subsquare.io/referenda/442" target="_blank" rel="noopener">2</a>, <a href="https://polkadot.subsquare.io/referenda/892" target="_blank" rel="noopener">3</a>, <a href="https://polkadot.subsquare.io/referenda/1290" target="_blank" rel="noopener">4</a>), 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 &ldquo;point of entry&rdquo; for many developers who are first learning smart contracts, who study OpenZeppelin&rsquo;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:
<ul>
<li><a href="https://dune.com/openzeppelin/openzeppelin-contracts-metrics" target="_blank" rel="noopener">$20 Trillion USD</a> of total value has been transferred across OpenZeppelin contracts</li>
<li>Market Share of ~19% of all transactions on all chains</li>
<li>100% penetration for OpenZeppelin contracts across top 50 DeFi protocols</li>
</ul>
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 <a href="https://blog.openzeppelin.com/introducing-openzeppelin-contracts-library-for-uniswap-v4-enhancing-security-and-innovation-with-hooks" target="_blank" rel="noopener">Hooks library</a>, and is currently developing a <a href="https://www.prnewswire.com/news-releases/taiko-and-openzeppelin-partner-to-develop-next-generation-based-rollup-stack-302359509.html" target="_blank" rel="noopener">based rollup stack</a> 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 <a href="https://docs.google.com/document/d/1UmbQhXxlK7yLwqw1zj45PfC4Hf1OcbkSUEXMTOotRwM/edit?usp=sharing" target="_blank" rel="noopener">here</a>.

OpenZeppelin Support for Polkadot Hub and Polkadot Cloud in 2025

Treasury

Propose and approve a spend of treasury funds.

## Dispatch Origin

Must be [`Config::SpendOrigin`] with the `Success` value being at least
`amount` of `asset_kind` in the native asset. The amount of `asset_kind` is converted
for assertion using the [`Config::BalanceConverter`].

## Details

Create an approved spend for transferring a specific `amount` of `asset_kind` to a
designated beneficiary. The spend must be claimed using the `payout` dispatchable within
the [`Config::PayoutPeriod`].

### Parameters
- `asset_kind`: An indicator of the specific asset class to be spent.
- `amount`: The amount to be transferred from the treasury to the `beneficiary`.
- `beneficiary`: The beneficiary of the spend.
- `valid_from`: The block number from which the spend can be claimed. It can refer to
  the past if the resulting spend has not yet expired according to the
  [`Config::PayoutPeriod`]. If `None`, the spend can be claimed immediately after
  approval.

## Events

Emits [`Event::AssetSpendApproved`] if successful.

- Problem Statement: OpenZeppelin collaborating with Parity to support the launch of Polkadot Hub in 2025 for developer enablement.
- Significance: OpenZeppelin's experience in developer enablement is crucial for attracting Solidity developers and DeFi protocols to Polkadot Hub.
- Proposed Solution: Collaboration between OpenZeppelin and Parity to provide developer enablement and support for Polkadot Hub and Polkadot Cloud.
- Expected Outcomes: Enhanced developer support, increased adoption of Polkadot Hub, and strengthened strategic partnership between OpenZeppelin and Parity.

#1465 OpenZeppelin Support for Polkadot Hub and Polkadot Cloud in 2025

No Active Proposals