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



\*\*Beneficiary address:\*\* 149mJjdQjEBMHHbWDjbLJ7X4e95ps6L35DZVaBzn1raR1EVQ



\*\*Short description:\*\* \*Gossamer was originally envisioned as a Go-based implementation of the Polkadot Relay Chain Validator, contributing to the decentralization and resilience of the network through client diversity. Our team, deeply committed to the Polkadot ecosystem, built Gossamer as an alternative full node and validator client to help ensure the robustness of the protocol.\*

\*\*However\*\*, as the ecosystem's needs have changed, it's become clear that alternative client development is not currently a top priority. In light of this, we’ve made a strategic decision to shift our focus from developing an alternative client to contributing directly to the existing Rust-based SDK implementation. This change aligns with both the direction of the ecosystem and our desire to maximize our impact on Polkadot’s core infrastructure.

Following consultations with Parity, we have defined a set of objectives that our team will focus on over the next six months. These efforts, in close collaboration with Parity, will leverage our experience to contribute to the Polkadot-SDK's most critical areas, helping to strengthen, optimize, and scale the protocol at its foundation.&#x20;





\*\*Project Category/Type:\*\* Software development



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





\# 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 and 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 collaboration of the Gossamer team and Parity to work on the Polkadot protocol's (polkadot-sdk) pressing needs. 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 2 (Scope of Current Proposal), we will dedicate resources to the needs of the polkadot-sdk by addressing key technical priorities identified in collaboration with Parity. Our focus will be on areas where our team’s expertise can deliver the greatest impact - enhancing scalability, performance, and protocol robustness. This marks a natural evolution of our role within the ecosystem, transitioning from client diversity through Gossamer to strengthening the core infrastructure that supports the Polkadot network. Our focus will be on areas where our team’s expertise can deliver the greatest impact - protocol development.&#x20;





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



\### Proposal navigation:

1\. \[Context of the proposal]\(https://docs.google.com/document/d/1vuJwHbSQcx001KPLBjLfYsMQZFZCWaI2azETVs2T6II/edit?tab=t.0#heading=h.1zo0zjb0dkcb)

&#x20;   1.1 \[About ChainSafe and the Gossamer Team]\(https://docs.google.com/document/d/1vuJwHbSQcx001KPLBjLfYsMQZFZCWaI2azETVs2T6II/edit?tab=t.0#heading=h.r1h6b13lq78y)

2\. \[Scope of Work]\(https://docs.google.com/document/d/1vuJwHbSQcx001KPLBjLfYsMQZFZCWaI2azETVs2T6II/edit?tab=t.0#heading=h.tedpurhasj4m)

&#x20;   2.1 \[Approval-checking rewards]\(https://docs.google.com/document/d/1vuJwHbSQcx001KPLBjLfYsMQZFZCWaI2azETVs2T6II/edit?tab=t.0#heading=h.x1josl2ojaib)

&#x20;   2.2 \[Parachain runtime upgrades off-chain R\&D]\(https://docs.google.com/document/d/1vuJwHbSQcx001KPLBjLfYsMQZFZCWaI2azETVs2T6II/edit?tab=t.0#heading=h.nqm39yktcxlf)

&#x20;   2.3 \[Optimizing the dependency footprint]\(https://docs.google.com/document/d/1vuJwHbSQcx001KPLBjLfYsMQZFZCWaI2azETVs2T6II/edit?tab=t.0#heading=h.my8bqjnnp9yw)

&#x20;   2.4 \[WebRTC transport for browser-based LightClients]\(https://docs.google.com/document/d/1vuJwHbSQcx001KPLBjLfYsMQZFZCWaI2azETVs2T6II/edit?tab=t.0#heading=h.kga70qtz590a)

&#x20;   2.5 \[Speculative Availability]\(https://docs.google.com/document/d/1vuJwHbSQcx001KPLBjLfYsMQZFZCWaI2azETVs2T6II/edit?tab=t.0#heading=h.15uubdryyvph)

&#x20;   2.6 \[Polkadot network chaos testing and DDoS protection]\(https://docs.google.com/document/d/1vuJwHbSQcx001KPLBjLfYsMQZFZCWaI2azETVs2T6II/edit?tab=t.0#heading=h.vho01ny786cg)

&#x20;   2.7 \[Smart Contracts Infrastructure Integration (Foundry-Polkadot)]\(https://docs.google.com/document/d/1vuJwHbSQcx001KPLBjLfYsMQZFZCWaI2azETVs2T6II/edit?tab=t.0#heading=h.5vx3cbqx85rw)

4\. \[Budget]\(https://docs.google.com/document/d/1vuJwHbSQcx001KPLBjLfYsMQZFZCWaI2azETVs2T6II/edit?tab=t.0#heading=h.a3ezu9wj57t)





\*\*Contact:\*\*



Kyrylo Pisariev, Senior Engineering Manager, [kirill@chainsafe.io](mailto\:kirill@chainsafe.io), @p1sar\:matrix.org

Peter Kalambet, Head of Protocol, [peter@chainsafe.io](mailto\:peter@chainsafe.io), @peter\:dod.ngo

Belma Gutlic, VP of Engineering, [belma@chainsafe.io](mailto\:belma@chainsafe.io), @morrigan.iv\:matrix.org



\*\*Progress and Updates:\*\*



\- Monthly progress reports (\[GitHub discussions]\(https://github.com/ChainSafe/gossamer-parity/discussions), \[X]\(https://x.com/ChainSafeth))&#x20;

\- GitHub code progress (\[Github Project]\(https://github.com/orgs/ChainSafe/projects/62))

\- Presentations at Polkadot events

\- Documentation updates

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.

#1688 # Gossamer's Contributions to Polkadot-SDK [Q3/Q4 2025]

No Active Proposals