candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

Untitled - public proposal #115

There are some problems with the submitted runtime code. We need to update the genesis information

Deregister this paraID and apply for a new paraID #112


justifications;

-No product
-No tokens
-Block users on Social Media
-People stay away from joining Parachains because they despise people joining Parachain
-https://twitter.com/zachxbt tweets about Omar

I demand that Picasso Network and Composable Finance be prevented from buying Parachain again.

Untitled - public proposal #116

Team [Polkascan](https://polkascan.org/) has had conversations with the people from [Subsquid](https://subsquid.io/) in which we agreed that their blockchain data archivers and public API's (Squids) are a good fit for our [Polkascan Explorer](https://github.com/polkascan/explorer). We would like to combine their efforts with ours and expand our data library and explorer with the public Subsquid services. After doing research, we've created a new proposal to make this possible. We would like to discuss this plan with the Kusama community.

You can find all details in our [proposal document](https://github.com/polkascan/social-contract/blob/master/kusama/treasury-proposal-subsquid-integration-polkadapt-abstraction.md). We're happy to answer your questions.

Subsquid integration with Polkascan block explorer (upcoming Treasury Proposal)

Approved

This 6-month proposal is to renew funding for the NFT Content Creators initially funded by Bounty 12.

Supporting young creators is crucial to educating early adopters of the Polkadot and Kusama ecosystems. Decentralization is equally critical, and this effort by each Director to independently build a plan of action best suited to their units will help take content creation to the next level.

This proposal does not only aim to continue funding NFT content creation, however.

It seeks to build the prototype of an NFT system of accountability and reputation. This prototype will lead to higher quality content and lower expenditure long term, as well as provide indicators of trustworthiness to content consumers.

Please consider the full proposal [here](https://docs.google.com/document/d/1jGJzzQYUcHmSLUYnwrxsY_5uwB7Tgi6CvomSOZseV5s/edit?usp=sharing). 

Prior discussion can be found [here](https://kusama.polkassembly.io/post/2101)


Pnin

Confirming

medium_spender

6 Month Funding for NFT Content Creation Guild

Dear community,

Based on the recent experience with the increasing number of treasury proposals, I am presenting the following proposal aiming to improve the Governance 2.0 experience through a series of referenda proposal audits.

[The original discussion.](https://kusama.polkassembly.io/post/2138)

**Governance 2.0 Referenda Audits**

**1. Problem**

Since the launch of Governance 2.0 on Kusama I spent many hours reading, reviewing, and trying to understand many treasury discussions and proposals. I try my best to understand every proposal before forming an opinion and voting. For the majority of the proposals, I try to provide feedback to the proposer explaining the reasons for either supporting or rejecting the proposal. So far I feel like proposals are sort of a wild game at the moment.

Most proposals are not very well structured, lack information, and include budgets that seem very hard to defend. Proposals can also be very diverse with a focus on different areas that not everyone can be familiar with. For all these reasons it is significantly time-consuming for voters to truly understand the proposal and cast an educated vote on it.

With the given time constraints, it is not surprising that proposals are receiving very little or no feedback at all. The feedback is often provided in a free form and is not always clear and precise. Such insufficient information has little use for other voters. It provides low assurance to other community members that the reviewer has objectively formed an objective opinion on the presented proposals.

**2. Available solutions**

The official Polkadot treasury page, Kusama and Polkadot Wiki provide a good source of information and documentation. Most of this information and guidelines explain the “old” Governance 1.0 system or in other words, it relates to the very specific set of proposal reviewers – Councilors. With the Governance 2.0 introduction, the set of reviewers dramatically increased from a limited set of councilors to a much wider Dotsama community. For this reason, all the documentation needs to be adjusted so it can be better presented to the wider audience where not everyone needs to be an expert in the field to have a good understanding of the proposal content.

**3. Proposal Solution**

This proposal aims to create a clear and precise framework for creating and presenting the proposals. This framework is not meant to be a strict requirement but more as a set of guidelines for the proposers to successfully present their project and increase their chance to defend the proposal and win community approval.

As the counterpart to the proposal framework, the equally important audit framework will be created as guidance for the reviewers. This audit aims to provide more precise feedback to the proposer and give a sufficient and educated review that can be later used by other voters to form their opinion on the proposal.

In a young system like this, creating these guidelines is simply not enough. To create a better treasury proposal system, a great level of engagement is required. For this reason, I propose a temporary Project manager/auditor role for a period of 3 months. The main task of the PM is to actively follow the governance tracks, objectively check and audit the proposal content according to the proposal guidelines and produce and publish the audit according to the created framework. The task of the PM is to be available to the community and gather feedback and accordingly adjust the framework.

**4. Key deliverables:**

Proposal template – a document with predefined categories and as many pre-filled and guided data (examples) as possible.

Feedback template – directly related to the proposal template. Possible checklist for each category with additional room for the feedback

Produce a minimum of 30 one-page audits with included feedback on active treasury proposals or proposal discussions

**5. Key objectives/ Success criteria**

Reduce the time required to write a detailed and comprehensive proposal – measured by the proposal owner's feedback

Higher community involvement in the governance – measured by the number of members involved in discussions, number of provided feedback, and number of interactions with one-page reviews

All these points are taken from the full proposal document.

[Full proposal](https://docs.google.com/document/d/1-Ze8Z_f9Pa3kjALGnhu-58DNdajFQ74ONbuDeWcaFoU/edit#heading=h.5x0d5h95i329)






Governance 2.0 Referenda Audits

Team [Polkascan](https://polkascan.org/) has had conversations with the people from [Subsquid](https://subsquid.io/) in which we agreed that their blockchain data archivers and public API's (Squids) are a good fit for our [Polkascan Explorer](https://github.com/polkascan/explorer). We would like to combine their efforts with ours and expand our data library and explorer with the public Subsquid services. After doing research, we've created a new proposal to make this possible.

You can find all details in our [proposal document](https://github.com/polkascan/social-contract/blob/master/kusama/referendum-83-treasury-subsquid-integration-polkadapt-abstraction.md).

Deciding

Subsquid integration with Polkascan block explorer

Help Bring The Ruggables Real Governance 

Catching #KSM Scams And Buying And Burning Rug Nfts

This bounty is the Program Milestone 2 inception of the Infrastructure Builders Program that can be found at the link below:

https://docs.google.com/document/d/16USQYVhlyAlrU829EUB2TRoqUC0nnfoS_uCdZ84HT8k





Infrastructure Builders Program

Further info can be found [here](https://crustipfs.info/ipfs/QmWx4KQANhYrTPCbQWH2gvSMdv7UoLRMEFT8bBW9oArnsp)

https://crustipfs.info/ipfs/QmWx4KQANhYrTPCbQWH2gvSMdv7UoLRMEFT8bBW9oArnsp

Polkashots maintenance Q3-Q4 2022

This is a treasury proposal whose proposer address (Eovc1HjhjVDi4xwrJUgCjhHgqS78s4kDoFgSAxoaw7VkXeA) is shown in on-chain info below. Only this user can edit this description and the title. If you own this account, login and tell us more about your proposal.

Testing - Please Reject. Thank you!

**Proponent**: Subsquid Lab Official - FAyqRVLZmXVUU9pNeG8w8SxS5xRgN8FRGeWLL6u9S32TMHc

**Short description**: Ongoing costs for the running of high performance, scalable, and reliable data indexing infrastructure for most of the Polkadot and Kusama ecosystem (and growing).

**Raw data**: [Archive Infrastructure metrics - July, August, September](https://docs.google.com/spreadsheets/d/e/2PACX-1vQBQPYlsB-2JLecP-0OXxfFEzlbPZsGGaFR5aCFLB1-KA7g6TqUnmHNM34dHl_yj9Xf9VWhw_gfUN58/pubhtml)

**Requested KSM**: 1,340.48 KSM

**Previous proposal**:

https://kusama.polkassembly.io/treasury/171

https://polkadot.polkassembly.io/treasury/134

# Motivation
Archives are an important piece of Polkadot and Kusama data infrastructure provided by Subsquid. They provide access to on-chain data in GraphQL format for all major parachains on Kusama and Polkadot, with more chains getting support as the ecosystem grows. They are being used as a data source for Squids and for efficient data exploration and ad-hoc queries. An up-to-date list of Archives is kept in a public Archive Registry
# Achievements
At the end of Q2 Subsquid released a new generation of Archives, together with a major version of the SDK, both code named “Fire Squid”.
The improvements brought by this release include:
- Substantial performance increase, with the ability to deploy a new Archive for a chain as big as Kusama, and the indexing to be ready in roughly a day
- Fire Squid Archives support batch requests, which lead to a hundredfold increase in performance of indexing project connecting to them (squids)
- Fire Squid Archives expose two separate gateways, configured and tuned for different uses (one for data exploration by humans, the other one specifically for programmatic and batch access)
- Fire Squid Archives “unwrap” proxy, sudo and batch calls, tracing the origin, but making them much easier to access them
Subsquid has also engaged in continuously improving the product, iteratively working on adding features, such as EVM Transactions indexing, and subscriptions to queries in the Graphql endpoints of indexing projects created with the Subsquid SDK (commonly called squids).
# Statistics
Between 2022-09-03 (when tracking has started) and 2022-09-30 Subsquid’s Archive infrastructure has collectively:
- Served a total of 129,468,038.2 (~129 million) queries in the month of September alone
- Our 7 day average peaks above 5 million queries and adjusts around 3.3 million queries per day at the end of the period
Data from the month of October confirms the linear trend, allowing us to make assumptions for the months of July and August, given the steady growth of queries over time shown.

Full report [here](https://docs.google.com/document/d/e/2PACX-1vQji6zUckBRq3Q8H0xOSLjmFDUkKHckt9SiSIIMdCw_Ck_qpiAhFltGxnNavCmFJcebiBznKO_dleis/pub)

Subsquid - Public data indexing Infrastructure for Polkadot and Kusama (Q3 2022)

Hello Kusama community,

This proposal is for a retroactive grant of my two open source, free tools. One for selecting the best validators and another for gathering staking income in a spreadsheet. You can try the validator selector [here](https://james-sangalli.github.io/dot-validator-selector/) and the staking income spreadsheet generator [here](https://james-sangalli.github.io/dot-staking-income-web/).

I originally set out to create these tools because I was struggling with staking. Selecting the best validators and tracking your staking income were unsolved issues at the time and they are still causing confusion for many. Therefore, I decided to solve my own problems and the problems of others by creating simple, easy to use tools that would get the job done. 

You can read the full proposal [here](https://docs.google.com/document/d/1YT2qssdH12AtWFRloRnBanK6H1sGuE6EaX782d4qK40/edit?usp=sharing).

Thank you for taking the time to consider this proposal!

