Hi everyone,

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

With this proposal, we’re looking to diversify and simplify the blockchain (parachain) development process, making the ecosystem more approachable/beginner-friendly and potentially more stable.

**The ultimate/end goal is creating a framework in Go, which is an alternative to Substrate.** However, it will be technically challenging to go for the direct implementation without abstracting components into different modules. Given that a modular approach has been taken, the practical goal would be to formalize those modules into a framework that can be reused by other developers.

**This is why we propose to develop a framework for building Go Runtimes.**

We recently got a [W3F grant to research the technical feasibility of the project](https://github.com/LimeChain/Open-Grants-Program/blob/application/research-feasibility-go-runtime/applications/research-feasibility-go-runtime.md), as we encountered some Go-related challenges along the R&D process. We were able to get those out of the way and you [can look at our efforts here](https://github.com/LimeChain/gosemble).

**Please see the [official proposal document here](https://docs.google.com/document/d/1i8DnmVdgJz8jxHOUxO3LM6MlX4QhGP2fE33vmQI2Vgk/edit?usp=sharing). Any feedback or comments are highly appreciated.**

About us: [LimeChain](https://limechain.tech/) 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. Due to AssemblyScript limitations, we were able to partially deliver on the framework specifications.

Thanks on behalf of the whole LimeChain team!

Framework for building Substrate-compatible Runtimes in Go (Parachains & Solochains)

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.

Thanks on behalf of the whole LimeChain team!

Parachain Validation Conformance Testing

Hi everyone,

My name is Chris Veselinov, CTO of LimeChain, and I’m writing this thread to propose the phase 2 development and funding of [Gosemble](https://limechain.github.io/gosemble/) - a Framework for building Substrate-compatible Runtimes in Go.

The development of phase 1 was funded with [Motion 292](https://polkadot.polkassembly.io/motion/292) and successfully delivered with more details in [the treasury report](https://docs.google.com/document/d/1ExVDjj4xQm4OYLkvVoiHjx_NzEFaL3gj/edit) and [this article](https://limechain.tech/blog/gosemble-empowering-polkadot-parachains-development/).

As mentioned in the previous proposal, the only current option for developing runtimes is Substrate. We believe this lack of diversity inhibits the decentralization ethos that is inherent to blockchain technology. Additionally, Rust, the language in which Substrate is written, is known for its steep learning curve.

We are excited about Phase 2, as modularising the codebase and developing additional modules will enhance progress and allow for an alternative framework to Substrate in Go. This will increase developers adoption by making it more accessible to the broader Go development community and contribute to the decentralization and security of the protocol.

For more details, including technical milestones, check out the [proposal document.](https://docs.google.com/document/d/14kJvpqNxh1pe_wbGKbJA1XcsesOF_agd/edit?usp=sharing&ouid=113946912904115479410&rtpof=true&sd=true)

Gosemble Phase 2 - a Famework for building Substrate-compatible Runtimes in Go (Parachains & Solochains)

We are excited to introduce our proposal for the Substrate Subsquid Migration to ArrowSquid & Indexing Upgrades. This project targets enhancing the performance and functionality of Subsquid, a vital component providing access to on-chain data within the Substrate ecosystem. Through this proposal, we aim to improve the speed, efficiency, and indexing capabilities of Subsquid, ultimately benefiting developers and users across various chains such as Polkadot, Kusama, Moonbeam, and Acala.

Subsquid currently provides the community with access to on-chain data via GraphQL gateways, serving as data sources for APIs and on-chain data exploration tools. The main objective of this project is to migrate the existing Substrate Subsquid ecosystem to the ArrowSquid processor as well as enhance its indexing capabilities. This migration will enhance the speed and efficiency of all 50+ public squid endpoints.

Currently, all Giant Squid Main squids utilize the previous Substrate processor, Firesquid. The recent upgrade to the ArrowSquid processor introduces significant improvements, such as the ability to ingest unfinalized blocks directly from a network node, resulting in near real-time APIs with subsecond latency. However, this upgrade to the processor resulted in breaking changes and all squids that want to use it have to be adjusted to conform to the breaking changes.

Additionally, Substrate squids currently lack support for indexing Staking and Crowdloans pallets, which contain critical information for various chains in the Substrate ecosystem, including Polkadot, Kusama, Moonbeam, and Acala. The migration will also improve the performance of Polkascan as it depends directly on the data and performance from GiantSquid

The project aims to address these challenges by:

- Migrating the existing giant-squid-main codebase to utilize the ArrowSquid processor, improving speed and efficiency across all supported chains.
- Enhancing indexing capabilities by implementing indexing of calls and events from the Staking and Crowdloans pallets, enabling access to vital on-chain information.

The project will be executed in two milestones. The first one is focused on migrating giant-squid-main to ArrowSquid, which includes upgrading the dependencies, configuration, and endpoints adaptations, as well as testing and deployment. The second milestone will be focused on indexing Staking and Crowdloan pallets calls and events.

For a detailed description of our proposal, please visit: [Polkadot Treasury - Subsquid Upgrades Proposal](https://docs.google.com/document/d/148ZnlnG7nrDRVhS-VQQ-Ld21u78qaXWqcVsV366EPn4/edit)

**Companies Background:**

Subsquid is providing the community with access to on-chain data in the form of GraphQL gateways and it is doing it completely for free for the time being. Such endpoints are being used both as data sources for complex APIs and as an on-chain data exploration tool. The purpose of the proposal is to ask for funds to cover the cost of running the infrastructure, given the utility they provide to the community.

LimeChain is a software development company founded in 2017. Positioned to handle end-to-end product development with the capability to manage projects from conceptualization and design to the complete implementation of a certain product. LimeChain specializes in blockchain technology, with an emphasis on developing blockchain-related and infrastructure solutions. In the context of the Polkadot ecosystem, the expertise is focused on developing infrastructure implementations, including [Gosemble, a framework for building Substrate compatible Runtimes in Go](https://github.com/LimeChain/gosemble), [Fruzhin, a Host implementation in Java](https://github.com/limechain/fruzhin), a framework for runtimes in AssemblyScript, a framework for runtimes in AssemblyScript. On top of that, Limechain has also implemented a [Parachain Validation Conformance Testing suite](https://github.com/LimeChain/polkadot-conformance).

Subsquid Migration to ArrowSquid & Indexing Upgrades

**Introduction:**

At LimeChain, we propose the introduction of an a number of new features for the UI of Polkadot.js API. We understand the pivotal role that developer tools play at the adoption of blockchain protocols, simplifying developers' workflows and leaving a positive impression on their experience with building on top of the protocol. As frequent users of the current application, we recognize its usefulness, but also see opportunities for improvement in UX and functionality.

We envision creating an application that serves as a daily tool for a wide range of users, including Hosts, Runtimes, Dapp, and Parachain developers. Our plan is to enhance the positive aspects of the existing application while addressing its shortcomings. For example, we aim to elevate the existing JS Console into a custom-tailored IDE for Polkadot.js API prototyping. By combining intuitive UI with cutting-edge yet reliable technologies, we aim to create a next-gen developer tools application for Polkadot.js API.

**Key Features include:**

Enabling seamless exploration of the Polkadot Ecosystem: The application will serve as the primary platform for developers to explore on-chain information across the entire Polkadot ecosystem, including blocks, chain state, referenda, xcm, and more.

Introduction of an integrated IDE for Rapid Prototyping: Users will be able to create quick proof of concepts within the browser tab, with pre-loaded dependencies tailored to their requirements, facilitating a complete Polkadot experience.

The application will be designed with adaptability in mind, ensuring longevity and adaptability as the Polkadot ecosystem evolves over time. The codebase will be open source under the Apache 2.0 license and contributed as repositories to the Polkadot-js GitHub organization.

**We outline the following milestones for our project:**

- **Polkadot.js API Sandbox IDE:** Create an integrated development environment for Polkadot.js API prototyping.
- **Real-time Block Explorer:** Develop a tool for real-time exploration of blockchain data.
- **Chain State, RPC, and Runtime Calls:** Handle various types of calls related to chain state, RPC, and runtime operations.
- **Polkadot.js API Support:** Dedicate time to address high-priority issues in the Polkadot.js API ecosystem.

**For a detailed description of our proposal, please visit:** [Proposal Document](https://docs.google.com/document/d/1XwJkcjLA03hAu-EAeC29oD14oH8lAa81fW-_BFMhXBw/edit)

**Company Background:**

LimeChain is a software development company founded in 2017. We are positioned to handle end-to-end product development, and we have the capability to manage projects from conceptualisation and design to the complete implementation of a certain product. We specialize in blockchain technology, with emphasis in developing blockchain-related and infrastructure solutions.

In the context of the Polkadot ecosystem, we possess considerable expertise in developing various tools, including

[Gosemble, a framework for building Substrate compatible Runtimes in Go](https://github.com/LimeChain/gosemble),

[Fruzhin, a Host implementation in Java](https://github.com/limechain/fruzhin), a framework for runtimes in AssemblyScript, a framework for runtimes in AssemblyScript. On top of that, we have implemented a

[Parachain Validation Conformance Testing suite](https://polkadot.polkassembly.io/motion/389)

Polkadot.JS API UI enhancements

**Introduction:**

We're excited to introduce our latest proposal focusing on the implementation of new developer tools using the Polkadot-API (PAPI). At LimeChain, we recognize the pivotal role developer tools play in simplifying workflows and enhancing the experience of developers within the blockchain ecosystem. With the emergence of PAPI, a light-client first JS API for interacting with Polkadot and other Substrate chains, we see an opportunity to revolutionize developer tools and accelerate the adoption of PAPI.

**We Propose the Following**: Creating a Next-Gen Developer Tools Application

Our proposal aims to create a developer tools application that serves as the primary platform for developers to explore on-chain information seamlessly across the entire Polkadot ecosystem. This application will feature a dedicated integrated development environment (IDE) for rapid prototyping using PAPI, providing users with a comprehensive and intuitive experience. By leveraging the power of PAPI, we aim to showcase its capabilities and facilitate its wider adoption among developers.

The implementation of this developer tools application will not only accelerate the adoption of PAPI but also enhance the performance and user experience (UX/DX) of developers interacting with the Polkadot ecosystem. By recreating familiar functionalities from existing tools like Polkadot.js UI and improving upon them, we aim to create a next-gen application that becomes a daily essential for developers and regular users alike.

**Key Features**:

Key features of the application include seamless exploration of the Polkadot ecosystem, an integrated IDE for rapid prototyping, and future-ready extensibility. With a focus on real-time exploration tools and an intuitive user interface, this application will set a new standard for developer tools within the Polkadot ecosystem.

The application will be built using Next.js for the front-end, providing a robust framework for full-stack web development. We'll leverage the capabilities of Polkadot-API for seamless interaction with the Polkadot network, and NestJS for building efficient and scalable server-side applications. Additionally, we'll utilize Kubernetes, Docker, and Grafana for infrastructure management and monitoring.

**Milestones**:

The project will be divided into milestones, each focusing on specific aspects such as application setup, IDE development, real-time block explorer, chain state, RPC and runtime calls, and SCALE messages encoder and decoder. Additionally, we'll utilize Kubernetes, Docker, and Grafana for infrastructure management and monitoring.

You can view the full proposal here: https://docs.google.com/document/d/15FOAuTf9x2_9OaN9yFZgUPp8ApBGpHautnVBs50pkoM

**Future plans:**

Beyond the initial scope, we have plans to implement additional features such as saving, loading, and sharing IDE prototypes, session sharing within the IDE, and more cross-functional integration between different pages and modules. We'll gather feedback from the community to ensure the application meets the evolving needs of developers and users within the Polkadot ecosystem.

The success of the project will be measured based on the achievement of key deliverables outlined in the milestones, as well as metrics such as user engagement and feedback. We'll ensure transparency and ongoing communication with the community through regular updates and announcements.

**Conclusion**:

At LimeChain, we believe in the principles of interoperability and decentralization, which are fundamental to the Polkadot network. With our extensive experience in developing tools and infrastructure implementations across various ecosystems, we're confident in our ability to contribute to the growth and success of the Polkadot ecosystem.

Our team comprises experienced professionals with a strong background in software development, blockchain technology, and developer tooling. With a collective vision for enhancing the Polkadot ecosystem, we're committed to delivering impactful solutions that benefit developers and users alike.

In conclusion, our proposal represents a significant step towards building the future of developer tools within the Polkadot ecosystem. By leveraging the capabilities of PAPI and adopting a user-centric approach, we aim to create a next-gen application that empowers developers and accelerates the adoption of Polkadot.

Developer tools for Polkadot-API

**Introduction:**

We're happy to introduce our proposal aimed at fortifying the Polkadot ecosystem's decentralization and resilience by optimizing protocol compliance testing. Currently, Polkadot boasts five diverse host implementations—Polkadot by Parity, Smoldot by Smoldot, Kagome by Quadrivium, Gossamer by ChainSafe, and Fruzhin by LimeChain. While this diversity enhances decentralization, it also poses challenges, particularly regarding protocol compliance and robustness.

**Proposal Overview:**

Our proposal stems from extensive research highlighting the need for a comprehensive protocol compliance testing suite. We envision leveraging Zombienet—a framework designed to power host-agnostic Host Conformance Tests—to address these challenges effectively. By crafting test cases and integrating with Zombienet, we aim to establish a robust testing framework ensuring protocol compliance across all implementations.

**You can view our full proposal here:** https://docs.google.com/document/d/1mG7keQJHyq7LxLd9MISHXxPeVY4TE6YeVWS2cGa3nqU

**Here is how it’s gonna go:**

We'll kick off by crafting test cases, covering key functionalities like State Trie, Trie Host API, and SCALE modules, and creating host-agnostic test fixtures. Next, we'll build a custom Host Conformance Runtime, extending Polkadot's runtime and integrating it with Zombienet for automated testing. Finally, we'll focus on detailed documentation to ensure transparency and facilitate community involvement.

Our dedicated team, comprising a full-time Blockchain Developer, a full-time QA Specialist, a part-time Tech Lead, and a part-time Project Manager, is committed to delivering results within a 10-week timeframe. We believe this initiative will pave the way for enhanced protocol compliance and resilience within the Polkadot ecosystem.

For further details, please refer to our proposal document We're excited to contribute to the continued growth and decentralization of Polkadot and welcome feedback and collaboration from the community.

**Company background:**

LimeChain is a software development company founded in 2017. Positioned to handle end-to-end product development with the capability to manage projects from conceptualization and design to the complete implementation of a certain product. LimeChain specializes in blockchain technology, with an emphasis on developing blockchain-related and infrastructure solutions. In the context of the Polkadot ecosystem, the expertise is focused on developing infrastructure implementations, including [Gosemble, a framework for building Substrate compatible Runtimes in Go](https://github.com/LimeChain/gosemble), [Fruzhin, a Host implementation in Java](https://github.com/limechain/fruzhin), a framework for runtimes in AssemblyScript, a framework for runtimes in AssemblyScript. On top of that, Limechain has also implemented a [Parachain Validation Conformance Testing suite](https://github.com/LimeChain/polkadot-conformance).

Polkadot Conformance Testing

With <a href="618">Referendum #618</a>, LimeChain took over the development and maintanance of GiantSquid (fka as Subsquid), which is an indexing tool in the Polkadot ecosystem, providing access to on-chain data in the form of GraphQL gateways. Since then, we have delivered on the treasury proposal, proactively talked to users and ecosystem members, and published a detailed delivery report. More details on community feedback can be found in the progress report of <a href="618">Referendum #618</a> .
Based on user feedback, we&rsquo;ve scoped out a list of upgrades in a new proposal which we&rsquo;re calling a &ldquo;Phase 2 for Giant Squid&rdquo;.The full proposal document for Giant Squid Phase 2 can be read <a href="https://docs.google.com/document/d/1FkQY0erT2LsLbK03-AnJ9RrRnFDVtPxI/edit?usp=sharing&amp;ouid=113946912904115479410&amp;rtpof=true&amp;sd=true">here in google docs</a>.
TLDR:
In Phase 2 we plan to implement XCM transaction indexing, making cross-chain transfers easily searchable. By indexing nomination pools and conviction voting, we enable detailed tracking of staking and governance participation. A new &ldquo;History Elements&rdquo; table will consolidate all account-related events into a single dataset, simplifying queries for wallets and applications. Staking analytics will be improved with APR calculations and validator selection insights. NFT indexing will allow users to retrieve owned assets, while a feasibility study will explore cross-chain NFT tracking. Additionally, we will research real-time mempool indexing to provide better transaction visibility before finalization. Giant Squid will also boast a new homepage that greatly improves usability. These upgrades will make Giant Squid a more powerful and user-friendly indexer for the ecosystem.
The total treasury request for this proposal is 169,520 USDC, of which 94,520 are development costs and 75,000 are estimated infrastructure costs from March 2025 till December 2025 inclusive. The infrastructure estimation is based on historical infrastructure expenses (currently at about $7.5k a month)&nbsp; + an usage growth assumption from the delivery of Phase 2 onwards. The infrastructure up until now is being covered with remaining funds from <a href="618">Referendum #618</a>.
Any additional feedback or ideas for the upgrade of GiantSquid are greatly appreciated. We would love to hear the community feedback on this and potentially move it to a treasury proposal.

Giant Squid Phase 2

Hi everyone,

My name is Chris Veselinov, CTO of LimeChain, and I’m writing this thread to propose the phase 2 development and funding of [Gosemble](https://limechain.github.io/gosemble/) - a Framework for building Substrate-compatible Runtimes in Go.

The development of phase 1 was funded with [Motion 292](https://polkadot.polkassembly.io/motion/292) and successfully delivered with more details in [the treasury report](https://docs.google.com/document/d/1ExVDjj4xQm4OYLkvVoiHjx_NzEFaL3gj/edit) and [this article](https://limechain.tech/blog/gosemble-empowering-polkadot-parachains-development/).

As mentioned in the previous proposal, the only current option for developing runtimes is Substrate. We believe this lack of diversity inhibits the decentralization ethos that is inherent to blockchain technology. Additionally, Rust, the language in which Substrate is written, is known for its steep learning curve.

We are excited about Phase 2, as modularising the codebase and developing additional modules will enhance progress and allow for an alternative framework to Substrate in Go. This will increase developers adoption by making it more accessible to the broader Go development community and contribute to the decentralization and security of the protocol.

We’ve also outlined the value proposition of Gosemble in a document [here](https://docs.google.com/document/d/1gD_ImtmY-eOdNQ08vdYwqbh2-X5xXleur1WvvMQDoR4/edit). 

To sum it up: There are two main reasons why we’re building Gosemble:
- Firstly, we lower the barrier to entry for developers and empower developers proficient in Go to build runtimes. 
- Secondly, we contribute to the technical decentralization of the protocol. This means that Gosemble provides a viable alternative to the Substrate runtime and lessens the reliance on Parity as a software development company building the Polkadot infrastructure. In addition to that, our work on Gosemble is valuable for finding faults in the Substrate runtime, other runtime and host implementations, as well as the Polkadot spec itself.

For more details, including technical milestones, check out the [proposal document.](https://docs.google.com/document/d/14kJvpqNxh1pe_wbGKbJA1XcsesOF_agd/edit?usp=sharing&ouid=113946912904115479410&rtpof=true&sd=true)

Gosemble Phase 2 - a Framework for building Substrate-compatible Runtimes in Go (Parachains & Solochains)

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!

Proposal is canceled on that stage to clear some technical details and calculations

Vote NAY

Please vote NAY, we have resubmitted a new proposal with the correct amount in USDT - https://polkadot.polkassembly.io/referenda/1087