Hello, I have two questions:

1. What will happen with the Gosaamer client? Will they continue to provide maintenance or will that require additional funding?

2. I'd like to know if Parity already has staff assigned to cover the ongoing development of the existing Rust-based SDK implementation and what your specific relationship will be with that team?

 Thanks

A few questions:
1. The proposal requests $815K, which should cover the work of **9 engineers** for 6 months with the an average hourly rate of ` $94.37/hour, reflecting the team’s expertise and responsibilities.`. I assume that these 9 engineers have worked on Gossamer in the past and therefore should have some expertise in Polkadot. However, according to the [Gossamer github statistics](https://github.com/ChainSafe/gossamer/graphs/contributors?from=7%2F27%2F2024) in the past 12 months only **7 people** contributed more than 100 lines of code to Gossamer. So, do you really have 9 engineers with the necessary `expertise` to be working on the scope of proposal or you just increased engineering count to make a higher request to the treasury? 
2. According to Bill's comment in the last [referendum](https://polkadot.subsquare.io/referenda/1590) you have failed to deliver the promised scope in the past. In general, despite working on Gossamer for several years and spending a lot of treasury money ([$2mln](https://polkadot.subsquare.io/treasury/proposals/168) + [$2.9mln](https://polkadot.subsquare.io/referenda/709)), there were no significant results (Gossamer validator never went line on any network). Now, you are going to work on the Polkadot-SDK, which is written in Rust instead of Go, so this work should be even harder for your team. Why do you think you are a good fit for the given scope and community should keep supporting you?

PolkaWorld votes NAY

1.	According to Bill’s comment in the last referendum, the team previously received $4.9M from the Treasury ($2M + $2.9M) to develop Gossamer, yet the client has never gone live. And since Gossamer is written in Go while Polkadot-SDK is written in Rust, does the team truly have the capability to take on core Rust SDK development?

2.	Is any of this work duplicating efforts by Parity? Or is this work something that Parity should be doing in the first place?

I’m struggling to understand the rationale behind this proposal.

The Polkadot-SDK repository is owned by Parity, which itself is founded by the Web3 Foundation. Part of that funding is explicitly meant to cover the maintenance of this repository.

If Parity wishes to delegate certain areas of the maintenance to an external team, the logical and accountable approach would be for Parity to **hire that team directly** and establish a formal agreement (e.g., an SLA) to ensure these responsibilities are properly fulfilled. This would provide clear oversight and maintain alignment with Parity’s ownership of the repo.

If Parity believes its current funding from the Web3 Foundation is insufficient, then **it should be Parity submitting an OpenGov proposal** to request additional resources. However, that seems inconsistent with reality, as Parity is actively hiring, an indication that they have sufficient funds.

What doesn’t make sense, in my view, is for an external team to approach the treasury “on behalf of” Parity to secure a substantial sum for maintaining a repository that Parity owns and is ultimately responsible for. This approach bypasses accountability and creates an unnecessary layer of indirection between the treasury and the actual owner of the repo.


Dear Proposer,

Our vote on this proposal is **NAY**, as we understand it is being replaced by [#1699](https://polkadot.subsquare.io/referenda/1699).

Kind regards, Permanence DAO Decentralized Voices Cohort IV Delegate 📅 [Book Office Hours](https://cal.com/permanencedao/office-hours) 💬 [Public Telegram](https://t.me/permanencedao) 🌐️ [Web](https://permanence.io) 🐦 [Twitter](https://twitter.com/permanencedao) 🗳️ [Delegate](https://{}.subsquare.io/user/{}/votes)

beneficiary

***

**NOTE ON REFERENDA UPDATE:**
This  proposal was replaced with [Ref 1699](https://polkadot.polkassembly.io/referenda/1699)

***

assetKind

amount

validFrom

Rejected

Submitted

DecisionDepositPlaced

DecisionStarted

big_spender

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

**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. 
[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)
    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)
    2.1 [Approval-checking rewards](https://docs.google.com/document/d/1vuJwHbSQcx001KPLBjLfYsMQZFZCWaI2azETVs2T6II/edit?tab=t.0#heading=h.x1josl2ojaib)
    2.2 [Parachain runtime upgrades off-chain R&D](https://docs.google.com/document/d/1vuJwHbSQcx001KPLBjLfYsMQZFZCWaI2azETVs2T6II/edit?tab=t.0#heading=h.nqm39yktcxlf)
    2.3 [Optimizing the dependency footprint](https://docs.google.com/document/d/1vuJwHbSQcx001KPLBjLfYsMQZFZCWaI2azETVs2T6II/edit?tab=t.0#heading=h.my8bqjnnp9yw)
    2.4 [WebRTC transport for browser-based LightClients](https://docs.google.com/document/d/1vuJwHbSQcx001KPLBjLfYsMQZFZCWaI2azETVs2T6II/edit?tab=t.0#heading=h.kga70qtz590a)
    2.5 [Speculative Availability](https://docs.google.com/document/d/1vuJwHbSQcx001KPLBjLfYsMQZFZCWaI2azETVs2T6II/edit?tab=t.0#heading=h.15uubdryyvph)
    2.6 [Polkadot network chaos testing and DDoS protection](https://docs.google.com/document/d/1vuJwHbSQcx001KPLBjLfYsMQZFZCWaI2azETVs2T6II/edit?tab=t.0#heading=h.vho01ny786cg)
    2.7 [Smart Contracts Infrastructure Integration (Foundry-Polkadot)](https://docs.google.com/document/d/1vuJwHbSQcx001KPLBjLfYsMQZFZCWaI2azETVs2T6II/edit?tab=t.0#heading=h.5vx3cbqx85rw)
3. [Budget](https://docs.google.com/document/d/1vuJwHbSQcx001KPLBjLfYsMQZFZCWaI2azETVs2T6II/edit?tab=t.0#heading=h.a3ezu9wj57t)

**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)) 
- GitHub code progress ([Github Project](https://github.com/orgs/ChainSafe/projects/62))
- Presentations at Polkadot events
- Documentation updates

Please Vote NAY. Replaced with https://polkadot.polkassembly.io/referenda/1699

root

whitelisted_caller

wish_for_change

staking_admin

treasurer

lease_admin

fellowship_admin

general_admin

auction_admin

technical_maintenance

prosperity_emergency

referendum_canceller

referendum_killer

small_tipper

big_tipper

small_spender

medium_spender

Origin able to dispatch a whitelisted call.

Origin for signaling that the network wishes for some change

Origin able to cancel slashes and manage minimum commission.

Origin for spending up to 10,000,000 DOT from the treasury as well as generally administering it.

Origin for managing the composition of the fellowship.

Origin able to spend around 250 DOT from the treasury at once.

Origin able to spend around 1,000 DOT from the treasury at once.

Origin able to spend around 10,000 DOT from the treasury at once.

Origin able to spend around 100,000 DOT from the treasury at once.

Origin able to spend up to 1,000,000 DOT from the treasury at once.