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)

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)

Treasury

Propose and approve a spend of treasury funds.

- `origin`: Must be `SpendOrigin` with the `Success` value being at least `amount`.
- `amount`: The amount to be transferred from the treasury to the `beneficiary`.
- `beneficiary`: The destination account for the transfer.

NOTE: For record-keeping purposes, the proposer is deemed to be equivalent to the
beneficiary.

- Chris Veselinov is proposing the phase 2 development and funding of Gosemble, a framework for building Substrate-compatible runtimes in Go.
- Phase 1 of Gosemble was successfully delivered and funded with Motion 292.
- Gosemble aims to provide an alternative framework to Substrate in Go, making it more accessible to developers and contributing to the decentralization and security of the protocol.
- The value proposition of Gosemble includes lowering the barrier to entry for developers proficient in Go and providing a viable alternative to the Substrate runtime.
- For more details, check out the proposal document.

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

No Active Proposals