OpenZeppelin x Polkadot Ecosystem Growth Phase M2
2 years ago
treasury
infrastructure
opensource
parachain
runtime
Executed
This proposal, the second of four quarterly submissions by OpenZeppelin, aims to continue the momentum in developing open-source Polkadot parachain runtimes and FRAME pallets. Our focus is on accelerating the development and deployment of new, secure parachains in the Polkadot ecosystem.
Key initiatives since the proposal's approval in August 2023 include:
- Start of the Generic Runtime and FRAME pallets development, adhering to milestones set for December 2023 (delivered) and February 2024 for the first deliverable of the Generic Runtime.
- Formation of a fully operational team of three skilled engineers, complemented by a project manager and CTO, to drive our open-source development efforts. This team is actively engaging with the Polkadot community to align priorities around the parachain runtimes templates.
In this phase (2 of 4), we seek funding for the period from November 2023 to February 2024, focusing on:
- Continuing the development of the first parachain runtime template, in line with our established milestones and publicly available roadmap on GitHub.
We are committed to transparent progress and welcome community feedback as we advance in strengthening the Polkadot network's foundation.
Comments (5)
Requested
34.32K DOT
Proposal Passed
Summary
0%
Aye
0%
Nay
Aye (100)0.0 DOT
Support0.0 DOT
Nay (53)0.0 DOT
Requester address: 14PiQ7uar36zPMgEckA7qWUahYheavRL6NHCbUCkXXRNrFSc Verified identity: Yes EMAIL finance@openzeppelin.com WEBSITE https://www.openzeppelin.com/ TWITTER openzeppelin When registered/verified: 18 Nov 2022 / 27 Jul 2023 Previous OpenGov TPs from this account: 24 - passed - https://polkadot.polkassembly.io/referenda/24 105 - passed - https://polkadot.polkassembly.io/referenda/105 W3F Grants: None
Good day OpenZeppelin, and thank you for your proposal.
Since we voted Aye on the previous demand (REF_105), we lean toward support again, being « invested » already. We would appreciate, however, a broad explanation in layman terms of what it brings to the table and why it is, in your view, necessary and pertinent in the current context (Polkadot 2.0).
We are not software engineers, and it is difficult for us to understand what is meant by "Generic Runtime and Frame pallets development", or why it is of any import. We, quite frankly, are not equipped to understand that level of lingo.
It is not our intention here to critique OpenZeppelin in any way. Yet, we are of the opinion that, in the search for good governance, more efforts should be put forth by proposers to explain their approach in an « accessible to all » manner.
All in all we will support or abstain.
Thank you for your time and understanding.
@cosmotron thank you for your support in the last referendum. Below is a breakdown of the terms, highlighting why they are needed and how they align with Polkadot 2.0.
What is a Runtime in Polkadot?
Think of the Polkadot Runtime as the "engine" of a parachain (a blockchain in the Polkadot network). It defines the rules and operations of the blockchain, such as how transactions are processed and validated.
What are FRAME Pallets?
FRAME Pallets are like "modules" or "plugins" for this engine. Each pallet adds a specific feature or functionality to the blockchain. For example, one pallet might handle the blockchain's token system, while another could manage user identities.
What is a Generic Runtime?
A Generic Runtime is a basic, versatile version of this engine. It's designed to be easily adaptable for a variety of projects. Think of it as a standard, basic model car that can be customized as needed.
Why is Generic Runtime Development Important?
Developing a secure Generic Runtime is important as it provides a strong, flexible foundation for new blockchains in the Polkadot ecosystem. With our runtime templates, developers can quickly launch their projects, customizing the basic model to fit their specific needs. It is like if instead of everyone going through the process of building their car from scratch, they can use our foundation and build from there - saving time and, in the future, expanding the pool of interesting adaptations of the car, allowing future refinements.
How Does This Benefit Polkadot 2.0?
This current proposal aligns with Polkadot 2.0, specifically enhancing flexibility and scalability. Polkadot 2.0 introduces a more adaptable system, with features like elastic cores and a new blockspace purchasing model. The runtime templates we are developing are designed to leverage these advancements, providing developers with a great platform that is easily customizable and efficient to deploy their parachain.
Happy to address any further questions 🙏