[T] DOT #1417 - Closing Bounty 49. Technical Support Bounty.
Terminated 
terminated
Description

https://polkadot.subsquare.io/referenda/1417

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.

Optionssingle

Votes·10

1xzc...1bX6
1xzc...1bX6
1xzcLSwo7xBFkJYZiL4EHaqFpuPTkH641E3V43W4cuk1bX6
Aye
# 1
This bounty has had very low activity. We support closing it.
15fT...yBzL
15fT...yBzL
15fTH34bbKGMUjF1bLmTqxPYgpg481imThwhWcQfCyktyBzL
Aye
# 1
I'm on the curator board. I can confirm that the bounty hasn't been active. There's probably going to be a requirement for a similar bounty, but this one is obviously not functioning.
12s6...nE8h
12s6...nE8h
12s6UMSSfE2bNxtYrJc6eeuZ7UxQnRpUzaAh1gPQrGNFnE8h
Aye
# 1
Okay then, if there is no demand for this bounty so let's close it.
13ED...KQbF
13ED...KQbF
13EDmaUe89xXocPppFmuoAZaCsckaJy3deAyVyiykk1zKQbF
Aye
# 1
We support closing this bounty if this hasn't been used adequately.
1433...pWXn
1433...pWXn
14333MZvbGkcq5CZ8fYHZiFYwHNDaW3uiErDKMb7oqnupWXn
Aye
# 1
Not being used...
1ZSP...vx6w
1ZSP...vx6w
1ZSPR3zNg5Po3obkhXTPR95DepNBzBZ3CyomHXGHK9Uvx6w
Abstain
# 3
As a curator, I will abstain, but generally support rebooting this
12Hi...E9N3
12Hi...E9N3
12His7t3EJ38tjdBbivUzWQeaNCLKfMqtKp1Ed3xHMyCE9N3
Aye
# 1
As the bounty isn't functioning, closing it is the correct call.
14gM...deVb
14gM...deVb
14gMJV95zwxUsFEZDSC8mtBVifS6SypKJkfBKANkMsLZdeVb
Aye
# 1
Support closing inactive bounties.
14Gn...YLEh
14Gn...YLEh
14Gn7SEmCgMX7Ukuppnw5TRjA7pao2HFpuJo39frB42tYLEh
Aye
# 1
This makes sense given its low activity.
167Y...TY9F
167Y...TY9F
167YoKNriVtP4Nxk9F9GRV7HTKu5VnxaRq1pKMANAnmmTY9F
Aye
# 1
Not used bounties shoud be closed.

Discussions·0

No current comments
Information
Snapshot
Timestamp
Created
Feb 06 2025 20:41
Start date
Feb 06 2025 00:00
End date
Mar 08 2025 00:00
Results
Voters
10
one-person-one-vote
Aye
9 VOTE
 
Nay
0 VOTE
 
Abstain
1 VOTE
 
© 2025 OpenSquare. All Rights Reserved.