---
# System prepended metadata

title: Polkassembly learnings/outcomes

---

# Polkassembly learnings/outcomes

- There is a need for lower paced discussion platform. Riot isn't sustainable even for some council members. This was mentionned in the chat and summed-up in Chevdor's feedback: [here](https://kusama.polkassembly.io/post/65).
- Many users keep their keys in localstorage (asking for an account in the extension was a higher barrier than expected).
- There is a need for offchain polls to get the sentiment of council members and avoid wasting KSMs in treasury fees (feature requested several time [logged here by David from W3F](https://github.com/paritytech/polkassembly/issues/669)). Tracking such sentiment has been done on Riot in the past and led to complaints.
- Commonwealth is now [open source](https://github.com/hicommonwealth/commonwealth-oss).
- Strong wish to avoid silos and build an infra to share discussions on governance proposals.
- There is no good back-end for archive stats. Nomidot and Polkassembly teams built [node watcher](https://github.com/paritytech/Nomidot/tree/master/back/node_watcher), a graphql server for archive data. Many apps need such an infra, it needs to be robust. We can use the Polkascan api, longer term it'd be great to have an archive DB + graphql server (what Andrew P is building).