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 - a Framework for building Substrate-compatible Runtimes in Go.
The development of phase 1 was funded with Motion 292 and successfully delivered with more details in the treasury report and this article.
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.
To sum it up: There are two main reasons why we’re building Gosemble:
For more details, including technical milestones, check out the proposal document.
Gosemble is a Framework for building Substrate-compatible Runtimes in Go.
It is being developed by LimeChain and is currently in phase 2 of development.
Gosemble allows developers proficient in Go to build runtimes and contributes to the technical decentralization of the protocol.
It provides a viable alternative to the Substrate runtime and lessens the reliance on Parity as a software development company building the Polkadot infrastructure.
The work on Gosemble is valuable for finding faults in the Substrate runtime, other runtime and host implementations, as well as the Polkadot spec itself.
Threshold