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 Treasurer
Executed

Closing Bounty 49. Technical Support Bounty.

inTreasurer
6 months ago

The discussion was kickstarted on December 15th 2024 with this discussion: https://polkadot.polkassembly.io/post/2630

The main concern is the lack of activity and deliverables of this bounty. As expressed by the original discussion, this bounty was meant to be reactive to other external business development efforts seeking to integrate technical solutions but in 10 months it's had no activity and only 1 child bounty has been granted.

https://polkadot.subsquare.io/treasury/child-bounties/49_2672

There were several comments pointing out that this bounty could be useful for certain support activities but we have not seen any initiative to move in any direction.

The remark on the bounty extension on 2024-10-02 (4 months ago) was “We have been setting up the bounty's operation. In the next bounty period, we expect an start increase in activity.”

https://polkadot.subscan.io/extrinsic/22797894-3

A second extension occurred on 2024-12-18 around the same time the discussion about closing the bounty occurred. No on-chain activity other than that has been recorded.

https://polkadot.subscan.io/extrinsic/23893006-2

Saxemberg will be voting in favor of the closure of bounty 49 as BD on Polkadot is composed of different DF, BD, dApp teams with a diverse set of skills, goals, locations/geographies and activities so each effort has sought their own solutions for technical integrations, usually independently and on their own conditions without having interact with this bounty.

Given that during the discussion period there were some voices that mentioned some solutions, we waited and postponed this referendum for last to see if there was any initiative with respect to any of the previously mentioned solutions but neither a new solution initiative, change or child bounty was initiated so we understand that the current status quo of the bounty will remain.

Comments (6)

6 months ago

Comments posted here

6 months ago

From my recent experience providing technical support through this bounty to external teams building on the Polkadot stack, I have seen its practical value.

The support process typically operates on a monthly cycle:

  • Teams submit their queries and receive technical assistance.
  • After a month, the work is reviewed and, if requirements are met, a child bounty is granted.
  • If the team wishes to continue, they propose a new support request to the curators.

I am currently working with one such team and have been actively engaged for several weeks now. Given this ongoing engagement and the structure in place, I believe this bounty serves an essential function in supporting teams navigating technical integrations.

Closing it prematurely could limit valuable technical assistance for teams that rely on this structured support system. Instead, it may be worth considering ways to improve its visibility and efficiency to maximize its impact.

Load more comments
PleaseLogin to comment

Proposal Passed

3

of 3

Summary

0%

Aye

AyeNay

0%

Nay

Aye (91)0.0 DOT

Support0.0 DOT

Nay (14)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