Hi everyone,

My name is Chris Veselinov, CTO of LimeChain, and I’m writing this thread to propose the development (and funding) of a Parachain Validation Conformance Testing.

With this proposal, we’re looking to identify test cases and implement conformance tests for the execution of the parachain verification function across different node implementations and wasm engines. 

This project is inspired by the currently open RFP for **[Parachain Validation Conformance Testing](https://github.com/w3f/Grants-Program/blob/master/docs/RFPs/Open/parachain_validation_conformance_testing.md)**

The ultimate/end goal is to define the baseline for the execution of parachain validation functions within a reasonable limits across different implementations. This will ensure that updating wasm engines, introducing new node implementations etc. can be done in a sane way without hoping for the best.

**Please see the official proposal document [here](https://docs.google.com/document/d/1C44lIlpoQMDaGlni9XT-SXJUtT-Ei3Et1osFoa-1W-g). Any feedback or comments are highly appreciated.**

About us: LimeChain is a blockchain development company founded in 2017 with a focus on building core blockchain infrastructure, developer tooling and dapps. We dove into the Polkadot ecosystem about 2 years ago with [Subsembly](https://github.com/LimeChain/subsembly) - a framework used to design and implement Substrate runtimes in AssemblyScript, again funded by the W3F. 
Some of the ecosystem work we’ve done involves the creation of Runtime from scratch and evolving it into fully capable frameworks for building Substrate Runtimes. Since the end of 2022, we are also actively working on [gosemble](https://github.com/LimeChain/gosemble) which is a framework for developing Substrate compatible Runtimes.

LimeChain is also leading the initiative for Polkadot Java host implementation and [research](https://github.com/LimeChain/java-host-research). This will further extend our knowledge of the PVFs and the specifics of their execution.

[Link](https://polkadot.polkassembly.io/post/1683) to the discussion.

Thanks on behalf of the whole LimeChain team!

Approve a proposal. At a later time, the proposal will be allocated to the beneficiary
and the original deposit will be returned.

May only be called from `T::ApproveOrigin`.

# <weight>
- Complexity: O(1).
- DbReads: `Proposals`, `Approvals`
- DbWrite: `Approvals`
# </weight>



- Proposal to develop and fund Parachain Validation Conformance Testing
- Official proposal document here: https://docs.google.com/document/d/1C44lIlpoQMDaGlni9XT-SXJUtT-Ei3Et1osFoa-1W-g
- Goal is to define baseline for execution of parachain validation functions across different implementations
- Proposed by Chris Veselinov from LimeChain, a blockchain development company focused on core infrastructure, tooling and dapps
- LimeChain is also leading initiative for Polkadot Java host implementation and research

#389 Parachain Validation Conformance Testing