**Requested amount:** **815 358 USDC**

**Beneficiary address:** 149mJjdQjEBMHHbWDjbLJ7X4e95ps6L35DZVaBzn1raR1EVQ

**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.&#x20;

**Project Category/Type:** Software development

**GitHub**: [Gossamer](https://github.com/ChainSafe/gossamer)

**Website**: [ChainSafe](https://chainsafe.io/)

**Previous treasury proposals:** 

* [Treasury Gossamer grant in 2022 (passed)](https://polkadot.polkassembly.io/treasury/168) 
* [Treasury grant in 2024 (passed)](https://polkadot.polkassembly.io/referenda/709)

# 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.

[Read Full proposal](https://docs.google.com/document/d/1QU5LzL2IsvLjii-mu2UVyVvddvSs2d8csMkLACFzIaA/edit?usp=sharing)

# **Proposal navigation:**

1. [Context of the proposal](https://docs.google.com/document/d/1QU5LzL2IsvLjii-mu2UVyVvddvSs2d8csMkLACFzIaA/edit?tab=t.0#heading=h.1zo0zjb0dkcb)
2. [Problem Statement](https://docs.google.com/document/d/1QU5LzL2IsvLjii-mu2UVyVvddvSs2d8csMkLACFzIaA/edit?tab=t.0#heading=h.x9cj65g4fve)
3. [Correlation with JAM](https://docs.google.com/document/d/1QU5LzL2IsvLjii-mu2UVyVvddvSs2d8csMkLACFzIaA/edit?tab=t.0#heading=h.yy988bnjt4g2)
4. [Scope of Work](https://docs.google.com/document/d/1QU5LzL2IsvLjii-mu2UVyVvddvSs2d8csMkLACFzIaA/edit?tab=t.0#heading=h.tedpurhasj4m)
5. [Budget](https://docs.google.com/document/d/1QU5LzL2IsvLjii-mu2UVyVvddvSs2d8csMkLACFzIaA/edit?tab=t.0#heading=h.a3ezu9wj57t)



**Contact:**

* Kyrylo Pisariev, Senior Engineering Manager, [kirill@chainsafe.io](mailto:kirill@chainsafe.io), @p1sar:[matrix.org](https://matrix.org)
* Peter Kalambet, Head of Protocol, [peter@chainsafe.io](mailto:peter@chainsafe.io), @peter:[dod.ngo](https://dod.ngo)
* Belma Gutlic, VP of Engineering, [belma@chainsafe.io](mailto:belma@chainsafe.io), @morrigan.iv:[matrix.org](https://matrix.org)

**Progress and Updates:**

* Monthly progress reports (GitHub [discussions](https://github.com/ChainSafe/gossamer/discussions), [X](https://x.com/ChainSafeth)) 
* GitHub code progress (see [insights](https://github.com/ChainSafe/gossamer/pulse))
* Presentations at Polkadot events
* Documentation updates (see [docs](https://chainsafe.github.io/gossamer/))

Propose and approve a spend of treasury funds.

## Dispatch Origin

Must be [`Config::SpendOrigin`] with the `Success` value being at least
`amount` of `asset_kind` in the native asset. The amount of `asset_kind` is converted
for assertion using the [`Config::BalanceConverter`].

## Details

Create an approved spend for transferring a specific `amount` of `asset_kind` to a
designated beneficiary. The spend must be claimed using the `payout` dispatchable within
the [`Config::PayoutPeriod`].

### Parameters
- `asset_kind`: An indicator of the specific asset class to be spent.
- `amount`: The amount to be transferred from the treasury to the `beneficiary`.
- `beneficiary`: The beneficiary of the spend.
- `valid_from`: The block number from which the spend can be claimed. It can refer to
  the past if the resulting spend has not yet expired according to the
  [`Config::PayoutPeriod`]. If `None`, the spend can be claimed immediately after
  approval.

## Events

Emits [`Event::AssetSpendApproved`] if successful.

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

No Active Proposals