Notice: Polkadot has migrated to AssetHub. Balances, data, referenda, and other on-chain activity has moved to AssetHub.Learn more
[Proposal retracted] Please vote nay
We’ve decided to retract this proposal after community feedback around the Fellowship UI RFP. The features we scoped here will still be built and shipped to users, this pause is only to restructure how funding aligns with the broader roadmap.
For now, we kindly ask you to vote NAY . Fret not, the work continues, the changelogs keep coming, and we’ll be back soon with a clearer, better-aligned proposal with some features shipped and concerns resolved in entirety.
Think of this as us hitting “refactor” on funding, not on delivery.
Thanks
Polkassembly Team
Comments (9)
Requested
Proposal Failed
Summary
0%
Aye
0%
Nay
Aye (10)0.0 DOT
Support0.0 DOT
Nay (51)0.0 DOT
Observations:
We're still waiting for these requests from 7 months ago (years if the original concerned comments were considered). The delegates page seemingly is completely lacks development interest and the ranking is broken despite it being a first level hyperlink.
https://i.ibb.co/7dTF8k29/meme.png)
https://i.ibb.co/xqB4JQ87/meme2.png
It was the top concern
https://polkadot.polkassembly.io/post/2772#comment-J3QVlguqNIOjLY2jjCrI
Curious to hear why the 100k fellowship work is charged here as well as on referendum 373
https://polkadot.subsquare.io/referenda/373
Didn't this referendum cover that already?
A claim that it doesn't overlap with 1463 is extremely confusing specially when you consider the title of "social contract" as this should be "new features"
This is the original comment regarding that:
"No overlap commitment Ref. 1463 covers platform maintenance and operations for the entire year ( Jan- Dec 2025)."
The global analytics page remains lacking
https://polkadot.polkassembly.io/gov-analytics
The bounty page displays erroneous information (0 child bounties):
https://i.ibb.co/nM73GT8y/bounty1.png
https://ibb.co/XfMbySwn
This one in particular has activity on chain
https://polkadot.subsquare.io/treasury/bounties/52
The same goes for bounty 63 and so on.
Other issues remain visible on the website, hopefully those get addressed first.
@SAXEMBERG Thanks for raising these points, let’s address each one clearly:
Ref. 373 (Dec 2023) funded the Fellowship MVP: activity feed, listing views, induction and referendum pages, member profiles, and core infra like pallet indexing, search, and hosting.
This proposal does not re-bill those. The scope here is the next layer: task & salary management workflows, collective analytics dashboards, BI alerts (deadlines, promotions/demotions), enhanced member profiles with salary/vote history, and IPFS documentation with Apillon. In short, 373 delivered the base product; this funds integration and transparency extensions.
Fair point on the title. We kept “Social Contract” for continuity, since the original annual scope was split into two milestones after community feedback. To avoid confusion, we’ll rename this proposal more explicitly around “Fellowship & Transparency.” None of the maintenance costs or subscriptions covered under 1463 are being re-billed here.
We’ve logged caching improvements and responsiveness fixes (overflow, minimised screen issues) as part of the ongoing revamp. These are tracked separately and will be improved in the next rollout by 11 September 2025. Thanks for pointing out the UX details.
The bounty revamp is mid-migration, and several planned features, including the curator view haven’t gone live yet. That’s why some fields like child bounties look erroneous today. These fixes are already in progress and were billed under previous scope, not here. You’ll see the completed bounty dashboards shipped as part of the revamp release this month, not from this proposal’s budget.
Please let us know if you have any other concerns. We will keep you and the community posted on all product updates including those here, as they go live in the coming few days.
Looking forward to your support!
Personally I don't see the need for another fellowship UI. There is no need to have 2 UIs for not that many people.
There is also a RFP to apply for funding for the Fellowship UI, so this doesn't need to go through main treasury.
@bkchr We fully recognise the great work Subsquare has done for Fellowship. Our goal isn’t to duplicate but to extend, giving Polkassembly’s existing users a seamless way to access Fellowship flows without switching platforms. In the first phase we prioritised core stability, wallets, and UX, which meant Fellowship wasn’t included then. Now, with that foundation in place, our users are asking for integrated Fellowship features. What we’re building is a different UI on top of the same underlying calls, designed as a continuation of governance workflows already happening on Polkassembly. We see this as complementary rather than competitive, and an important step to ensure ecosystem choice.