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

***
**NOTE ON REFERENDA UPDATE:**
This is a new proposal intended to replace [Ref 1688](https://polkadot.polkassembly.io/referenda/1688)
Following extensive consultations with Parity and the Polkadot community, we have introduced several key improvements.
- Payouts were split to bi-monthly retroactive milestones
- New sections were added: 
    - [Payout structure](https://docs.google.com/document/d/1kgR_3EzP6t6Jp3gdODPjfLtsSg3ys6b9h2nMHhvtlEI/edit?tab=t.0#heading=h.zihpmukcwwqo).
    - [Detailed milestone delivery description](https://docs.google.com/document/d/1kgR_3EzP6t6Jp3gdODPjfLtsSg3ys6b9h2nMHhvtlEI/edit?tab=t.0#heading=h.k50syyfoxl24)
    - [FAQ](https://docs.google.com/document/d/1cQIW1woTu_Sv0WWFOvvdqOtyE8pOjA6UCW8SJht3Ygg/edit?usp=sharing) with addressed and frequently asked questions from previous referenda
***

**Total Requested amount for 3 milestones:** 815 358 USDC
**Milestone 1:** *271 786 USDC*. Payout on: 10/09/2025
**Milestone 2:** *271 786 USDC*. Payout on: 10/11/2025
**Milestone 3:** *271 786 USDC*. Payout on: 10/01/2026


**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 and broader technological accessibility. 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. 


**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 **(equally split to bi-monthly milestones)** 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. 


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

### Proposal navigation:
1. [Context of the proposal](https://docs.google.com/document/d/1kgR_3EzP6t6Jp3gdODPjfLtsSg3ys6b9h2nMHhvtlEI/edit?tab=t.0#heading=h.1zo0zjb0dkcb)
    1.1 [About ChainSafe and the Gossamer Team](https://docs.google.com/document/d/1kgR_3EzP6t6Jp3gdODPjfLtsSg3ys6b9h2nMHhvtlEI/edit?tab=t.0#heading=h.r1h6b13lq78y)
2. [Scope of Work](https://docs.google.com/document/d/1kgR_3EzP6t6Jp3gdODPjfLtsSg3ys6b9h2nMHhvtlEI/edit?tab=t.0#heading=h.tedpurhasj4m)
    2.1 [Approval-checking rewards](https://docs.google.com/document/d/1kgR_3EzP6t6Jp3gdODPjfLtsSg3ys6b9h2nMHhvtlEI/edit?tab=t.0#heading=h.x1josl2ojaib)
    2.2 [Parachain runtime upgrades off-chain R&D](https://docs.google.com/document/d/1kgR_3EzP6t6Jp3gdODPjfLtsSg3ys6b9h2nMHhvtlEI/edit?tab=t.0#heading=h.nqm39yktcxlf)
    2.3 [Optimizing the dependency footprint](https://docs.google.com/document/d/1kgR_3EzP6t6Jp3gdODPjfLtsSg3ys6b9h2nMHhvtlEI/edit?tab=t.0#heading=h.my8bqjnnp9yw)
    2.4 [WebRTC transport for browser-based LightClients](https://docs.google.com/document/d/1kgR_3EzP6t6Jp3gdODPjfLtsSg3ys6b9h2nMHhvtlEI/edit?tab=t.0#heading=h.kga70qtz590a)
    2.5 [Speculative Availability](https://docs.google.com/document/d/1kgR_3EzP6t6Jp3gdODPjfLtsSg3ys6b9h2nMHhvtlEI/edit?tab=t.0#heading=h.15uubdryyvph)
    2.6 [Polkadot network chaos testing and DDoS protection](https://docs.google.com/document/d/1kgR_3EzP6t6Jp3gdODPjfLtsSg3ys6b9h2nMHhvtlEI/edit?tab=t.0#heading=h.vho01ny786cg)
    2.7 [Smart Contracts Infrastructure Integration (Foundry-Polkadot)](https://docs.google.com/document/d/1kgR_3EzP6t6Jp3gdODPjfLtsSg3ys6b9h2nMHhvtlEI/edit?tab=t.0#heading=h.5vx3cbqx85rw)
3. [Budget and payout structure](https://docs.google.com/document/d/1kgR_3EzP6t6Jp3gdODPjfLtsSg3ys6b9h2nMHhvtlEI/edit?tab=t.0#heading=h.a3ezu9wj57t)
4. [Progress, Updates, and Milestones Delivery](https://docs.google.com/document/d/1kgR_3EzP6t6Jp3gdODPjfLtsSg3ys6b9h2nMHhvtlEI/edit?tab=t.0#heading=h.k50syyfoxl24)
5. [Contacts](https://docs.google.com/document/d/1kgR_3EzP6t6Jp3gdODPjfLtsSg3ys6b9h2nMHhvtlEI/edit?tab=t.0#heading=h.iarcw3apjmva)
6. [FAQ](https://docs.google.com/document/d/1kgR_3EzP6t6Jp3gdODPjfLtsSg3ys6b9h2nMHhvtlEI/edit?tab=t.0#heading=h.3hloucbpfhjf) including the community questions and our answers from the previous referenda


**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](https://github.com/ChainSafe/gossamer-parity/discussions), [X](https://x.com/ChainSafeth), [polkadot forum](https://forum.polkadot.network/c/ecosystem/24/none)) 
- GitHub code progress ([Github Project](https://github.com/orgs/ChainSafe/projects/62))
- Presentations at Polkadot events
- Documentation updates

Send a batch of dispatch calls and atomically execute them.
The whole transaction will rollback and fail if any of the calls failed.

May be called from any origin except `None`.

- `calls`: The calls to be dispatched from the same origin. The number of call must not
  exceed the constant: `batched_calls_limit` (available in constant metadata).

If origin is root then the calls are dispatched without checking origin filter. (This
includes bypassing `frame_system::Config::BaseCallFilter`).

## Complexity
- O(C) where C is the number of calls to be batched.

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

No Active Proposals