This proposal is the fourth of our quarterly submissions by OpenZeppelin to accelerate the development and deployment of secure parachains in the Polkadot ecosystem. Since our last approval in July 2024, we have achieved:
- The launch of an EVM Runtime Template configured with Frontier pallets to support Solidity smart contracts seamlessly on Substrate chains.
- A detailed developer guide to assist in migrating Solidity contracts from Ethereum to our EVM runtime template.
- Collaboration with R0gue to integrate Pop CLI with our templates to give developers an even easier experience.
- Account abstraction support and pre-deployed contracts.
In this fourth phase (M4) we request the funding to:
- Meta Pallets: Streamline developer experience by creating higher-level, opinionated "meta pallets" that encapsulate common pallet functionalities. This reduces the number of pallets required for a project, simplifying development and accelerating time-to-market.
- Tanssi Integration: Enhance developer experience and increase parachain launch time by making our templates compatible with Tanssi.
- Zombienet-sdk improvements: One issue we’ve faced when writing integration tests is being able to easily spin up a local chain and tear it up. After speaking with some teams we realized this is a common problem across the ecosystem, that’s why we are collaborating with Parity to improve DX for zombienet by contributing upstream. An initial iteration for this design can be found here.
- Snowbridge Integration: Snowbridge is a general purpose, trustless and decentralized bridge between Polkadot and Ethereum. Our goal is to include out of the box support for parachains that use our templates.
- Developer guides detailing the use of Meta Pallets and all new features.
We aim to maintain transparent progress and welcome community feedback to strengthen the Polkadot network.
Full proposal available here.
Using Zombienet for doing runtime integration tests is not such a great idea. You don't need a relay chain running and parachain nodes for testing a runtime. This can just be done by using chopsticks that will then run the runtime directly. Runtimes are single threaded and by its nature are required to be reproducible. Chopsticks should also greatly simplify the entire process for setting up the the environment.