Polkassembly Logo

Head 1
Head 3
Head 4
Head 2
Create Pencil IconCreate
TRACKS
ORIGINS
Report an issueNeed help with something?
Foot 1
Foot 2
Foot 3
Foot 4
OpenGov
View All Big Spender
Requested:815.36K USDC
Rejected

Gossamer: Core Contributions to Polkadot [Q3/Q4 2025]

inBig Spender
2 months ago
BeneficiaryBeneficiary:

(815.36K USDC)

Short description: Gossamer is a team dedicated to implementing the Polkadot Relay Chain Validator, which was 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, the heart of Gossamer is its team. This is not just a group of developers writing lines of code. It’s a dedicated team of Polkadot protocol engineers and Web3 enthusiasts who have a broad portfolio of projects and have spent years building toward a shared vision: the importance of creating a truly decentralized Web3 future.

Requested amount: 815_358 USDC

Beneficiary address: 149mJjdQjEBMHHbWDjbLJ7X4e95ps6L35DZVaBzn1raR1EVQ

Project Category/Type: Software development

GitHub: Gossamer

Website: ChainSafe

Previous treasury proposals:
Treasury Gossamer grant in 2022 (passed)
Treasury grant in 2024 (passed)

Discussion post:
forum.polkadot

Context of the Proposal

The Gossamer team at ChainSafe is a group of technical experts, engaging in protocol-level implementations for the Polkadot ecosystem. The team has formerly received funding from the Web3 Foundation, the Polkadot Treasury and has also been temporarily self-funded through ChainSafe.
This proposal is a request for six months of funding from the Polkadot Treasury for the continued work of the Gossamer team. The ecosystem is rapidly evolving, and a lot of change is to be expected. We are therefore adopting a six-month proposal cycle to maintain agility and responsiveness to best serve the ecosystem.
In this funding period, as detailed in Section 4.2 (Scope of Current Proposal), we will dedicate resources to critical ecosystem needs, specifically, continue building alternative implementations of Polkadot validator, JAM implementation and enhancing Collator functionality to improve Parachain resilience. We understand the team's commitment as a fundamental technological pillar for advancing the Polkadot ecosystem.
Even though this proposal describes concrete development milestones for our alternative Polkadot client, we're already weaving in bridges into the future. The team is dedicated to fundamentally accompanying and supporting the journey and development of the ecosystem, from Polkadot to Polkadot 2.0 to required JAM implementations, now and in the future.

Proposal navigation:

  • Context of the proposal

  • Problem Statement

  • Correlation with JAM

  • Scope of Work

  • Budget

Contact:

Kyrylo Pisariev, Senior Engineering Manager, kirill@chainsafe.io, @p1sar:matrix.org

Peter Kalambet, Head of Protocol, peter@chainsafe.io, @peter:dod.ngo

Belma Gutlic, VP of Engineering, belma@chainsafe.io, @morrigan.iv:matrix.org

Progress and Updates:

Monthly progress reports (GitHub discussions, X)
GitHub code progress (see insights)
Presentations at Polkadot events
Documentation updates (see docs)

Comments (8)

2 months ago

aren’t some members of the team part of the Tech Fellowship and already receiving compensation based on their ranks?

2 months ago

PolkaWorld voted AYE.

Unanimous support.

Currently, the main client for the Polkadot Relay Chain is the Rust implementation developed by Parity. Gossamer, a Go implementation, provides client diversity—a principle that holds significant value within the Polkadot ecosystem. The team has also indicated that they plan to upgrade their client to support JAM when Polkadot transitions, ensuring long-term alignment with the network’s evolution.

While the budget breakdown is relatively brief, it still provides enough detail to assess its reasonableness.

Overall, we support the development proposed in this submission.

View the full feedback here.

Load more comments
PleaseLogin to comment

Confirmation Period

3

of 3

Decision Period

28 / 28 days

Confirmation Period

0 / 7 days

Summary

0%

Aye

AyeNay

0%

Nay

Aye (30)0.0 DOT

Support0.0 DOT

Nay (39)0.0 DOT

Voting Data

Approval%

Support%

Threshold0.00%

Threshold0.00%

Help Center

Report an Issue
Feedback
Terms and Conditions
Github

Our Services

Docs
Terms of Website
Privacy Policy

A House of Commons Initiative.

Polka Labs Private Limited 2025

All rights reserved.

Terms and ConditionsTerms of Website
Privacy Policy