Ongoing Development of Gossamer (16 months)
Short Description
Gossamer is an implementation of the Polkadot Host, developed using Go. As an alternative client implementation, it serves decentralization and robustness of the network by being a full node and a validator node. Ultimately, Gosammer is a framework for building within the Polkadot ecosystem, uniquely positioned to accelerate Golang development and offer additional advantages and capabilities.
Gossamer is built by ChainSafe Systems, a blockchain R&D company specializing in protocol engineering and web3 infrastructure that has been building within the Polkadot ecosystem for years, along with Filecoin and Ethereum.
Full proposal: Gossamer Full Proposal (IPFS) | Gossamer Full Proposal (GDrive)
Context of the Proposal
This proposal requests to continue supporting Gossamer development for the next 12 months. With years of dedication, the team's expertise has gained significant traction. This continued support would leverage their extensive experience to sustain and enhance the project’s development, building on successful foundations.
The next 12 months will be crucial for Gossamer as it reaches significant user-facing milestones like full node and validator node capabilities while discovering its potential and value within the Go development ecosystem.
Larger milestones that Gossamer will achieve in the estimated period:
Q2/Q3/Q4 2024
- Achieve Full node capability
- Increasing Full node reliability; reaching robust and performant production state
- Product discovery to validate Gossamer's potential beyond just serving a basic set of node features
- Setup infrastructure and run Gossamer nodes
Q1/Q2 2025
- Achieve Validator node capability
- Participate in both SASSAFRAS and BEEFY consensus
- Run additional QA and interop testing to ensure network reliability
- Run Gossamer validator nodes on Paseo testnet and Polkadot
Timeline and milestone details can be found in the Gossamer Full Proposal document.
Payment Details
Requested Funding: 368,016 DOT
Beneficiary Account: 149mJjdQjEBMHHbWDjbLJ7X4e95ps6L35DZVaBzn1raR1EVQ
—
We are always open for conversation, so for any questions, thoughts, or feedback, feel free to reach out! You can always contact us at [email protected].
Thank you,
Gossamer Team
Comments (7)
Requested
Proposal Passed
damn, no joke. tomaka is literal 10x engineer.
gossamer is now 5 years in the development and you still estimating to be one year away from a client that is production ready to validate onchain. gossamer development is a bit like trying to sync chain with 100mhz cpu. its able to grow in block height, but will it be ever able to catch the head and validate?
lets say Q2 2025, we finally have validators running gossamer clients to participate securing the network, but thanks to referendum 682 we change host spec to match JAM that requires changing the whole WASM motor in the client to PVM, it means that ChainSafe would need to implement PVM in Golang and then rebuild the client on its host functio to be able to validate and secure the network again.
who is going to write pvm in Golang?
I think currently proposed timeline was something around Q4 2025 for the JAM to replace current relays. this all makes me wonder if there is much point in continuing to fund gossamer development of current host spec if most of that tech is going to be rendered meaningless just a few months later that is unlikely to be enough for validator adaption especially with uncertainty about future compatibility.
@ROTKO.NET reading your comments, are you sure you are aye'ing it?
https://jam.web3.foundation/
@Colorful Notion
Thank you for sharing. We are aware of the JAM initiative and want to support this as early as possible. That link and announcement express the need for support teams and programming languages such as OCaml, Go, and Zig. That confirms what’s stated above, as a Go protocol team, we are in a good place to contribute to JAM (both specification and implementation) and increase network security through client diversity. The timeline is unfortunately unclear and so far we do plan to continue with the current Polkadot development, getting ready for JAM and working on JAM core implementation.