candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

This project is about making graffiti art with the Kusama logo in big cities, starting with Barcelona. Here's what they will do:

1. Design a template of the Kusama logo.
2. Paint the template with black spray paint in cities.
3. Take a photo of each graffiti piece.
4. Turn the photos into special digital items called NFTs.
5. Put the NFTs on the Kusama blockchain.

In the future, people can use the template to make their own graffiti in different cities. They will be paid by the treasury and upload their work to the blockchain. Each graffiti spot will be marked on a map, so people can visit them like special places during their travels. They should also show respect by kneeling in front of the Kusama logo.

The project is inspired by ideas about power and how people can use art to challenge the way things are. The graffiti will be a symbol of rebellion and change in public spaces.

Here's what they need to do:

- Make a quick template of the Kusama logo.
- Create graffiti, take a photo, and put it on StateMine.
- Mark the graffiti spot on a map for others to visit and kneel.

They have some rules for the first 10 cities:

- Each city must have more than 2,000,000 people or be the most populated city in the country.
- They can't repeat cities.
- They need to take a photo of the NFT, upload it, and mark it on the map.

Executed

small_spender

The project involves creating graffiti artworks featuring the Kusama logo in various cities, commencing with Barcelona. The process encompasses designing a template, and paint it with black spray in urban locations. Each graffiti piece will then be photographed and transformed into a non-fungible token (NFT), minted on the Kusama blockchain.

In the future, we anticipate individuals utilizing our template to make their own graffiti in different cities, financed by the treasury and upload it to the blockchain. Each graffiti point needs to be geolocated, enabling visits to these locations as if they were sanctuaries during travels. A symbolic gesture of reverence—bending the knee in front of the Kusama logo—is encouraged. Cities must have a population exceeding 2,000,000, and once a city is adorned, it cannot be repeated.

Inspired by Foucault's analysis of panopticism as a power mechanism, we propose subverting this paradigm. Placing the Kusama logo strategically in urban settings transforms it into a symbol of rebellion—an inversion of the panoptic gaze. Each graffiti piece disrupts passive surveillance, converting public spaces into active sites of resistance. Drawing further inspiration from Paul B. Preciado, our graffiti project becomes a performative act challenging conventional discourse surrounding public space.

To sum up: A swift template of the KSM logo, creating graffiti, capturing it in a photo, uploading the NFT on StateMine, and geolocating it for others to visit and bend the knee.

Allocation:

·        Idea: 69 KSM

Risk+Expenses: 42 KSM (spray, template, time etc..)

We propose these rules for participants in this Project for the first 10 cities:

·        42 KSM (max allocation)

·        City must be >2,000,000 population or the most populated city in the country. (for example: Vatican City)

·        Can’t repeat cities

·        Photo of the NFT. Upload it and geolocate it.

![](https://i.ibb.co/g6JmpF7/OIG-E8-Wc2pi-CDWKip.jpg)

Descentralized art project

- This referendum is about lowering the minimum balance needed for assets on Kusama's Asset Hub.
- When you pay fees with certain assets, the system still calculates the fee in KSM and converts it.
- If the minimum KSM balance is reduced by 10 times, fees in other assets will increase by 10 times.
- The proposal lowers the minimum balance for assets like USDT, RMRK, and DOT by 10 times.
- It also updates the metadata for bridged DOT, which had an issue before.
- The change will happen at block 21,570,500, just before the Asset Hub updates.

whitelisted_caller

The proposal aims to reduce the minimum balance requirement for all sufficient assets by a factor of 10, preserving the ratio, and update metadata for bridged DOT. The enactment block is set just before the Asset Hub upgrades to the lower ED. No information provided on price/timeframe/resources.

Update Sufficient Asset Minimum Balances

- A referendum is happening to choose curators for Bounty #25 about Public RPCs for Relay and Systems Chains.  
- 5 people are proposed as curators:  
  - Alex Dimitrijevic (works at Parity Technologies)  
  - Ivy Network (a group)  
  - Eric Poh (CEO of Pinknode)  
  - Leemo (works with Nova Wallet, Robonomics, and others)  
  - lolmcshizz (from HydraDX)  
- They will work together using a 3/5 multisig (3 out of 5 must agree).  
- The multisig controls a Pure Proxy account for managing funds.  
- The Pure Proxy account address is provided.  
- The multisig address is also shared.

big_spender

GM – This referendum proposes the Curators for [Bounty #25](../bounty/25) – Bounty Proposal for Public RPCs for Relay and Systems Chains. Please review the bounty and [previous referendum](321) which funded this bounty for more info.

  
The proposed curators are:

-   Alex Dimitrijevic (Infrastructure & Tooling Lead \[Ecosystem Success\] at Parity Technologies)
-   Ivy Network (Collective)
-   Eric Poh (CEO of Pinknode)
-   Leemo (Nova Wallet / Robonomics / ChaosDAO / GM Parachain / HydraDX & Basilisk Council)
-   lolmcshizz (HydraDX)

The 5 curators are part of a 3/5 multisig which is set as an Any Proxy for the Pure Proxy account which is being proposed as the curator account. 

![](https://i.ibb.co/y8G8ZNp/rpc-proxy.png)

Kusama Pure Proxy: EYKL3c77TTotRo7bopubDJ9Zt4jEjcpFPA1D2axsWhQZ3Xq

Kusama Multisig: GY8p88FVXFjrBokNfbuGi3nCNbbo5cHt3iGG5PyY6SHk7Xo

WHO: Alex Dimitrijevic, Ivy Network, Eric Poh, Leemo, lolmcshizz.
WHAT: Proposed as curators for Bounty #25 for Public RPCs for Relay and Systems Chains.
PRICE/TIMEFRAME/RESOURCES: Not specified.

Proposing Curators for Bounty #25

Runtime Upgrade v1,001,000

- Polkassembly helps with governance in Polkadot and Kusama.  
- It wants to make identity verification easier and faster.  
- On-chain identities build trust and accountability.  
- The current system is hard to use, especially for new users.  
- Polkassembly plans to simplify the process in 4 steps.  
- Verification time will drop from 25 minutes to 5 minutes.  
- The team asks for community feedback and support.

general_admin

Polkassembly is an integral part of Polkadot and Kusama governance. It is dedicated to fostering transparent governance and active participation within the Kusama and Polkadot ecosystems. The team is excited to announce its application to become a registrar on Kusama **after our registrar application and success on Polkadot.**Please refer to this tweet for details on our [Polkadot Registrar Statistics](https://twitter.com/polk_gov/status/1735702644965122179). Why are identity verifications important?

— On-chain identities in the Polkadot ecosystem are crucial for trust, accountability, and interoperability. An on-chain identity fosters a reliable and verifiable framework for participants within the Kusama ecosystem. It enables seamless integration and collaboration between different projects and stakeholders.

— It also builds accountability as the participants are vetted and there are multiple points of contact for an individual/team. Hence, when requesting funds or proposing changes, the network and its resources have an additional layer of protection via the verification process.

— The goal of setting an on-chain identity is to enhance transparency, security, and the overall ease of interaction between the participants of the Kusama ecosystems.  
Problems in current on chain identity system

-   — The current process for verifying the identity is extremely fragmented
-   — The process requires a heavy reliance on navigating through PolkadotJS, which can be overwhelming to those who are new to the ecosystem
-   — The process is also broken away from the governance and proposal creation interface, which makes it difficult for a lot of the community as they need to adapt to multiple tools for serving different use cases.

**Objective for Registrar Application**

-   — The primary objective of creating the registrar application is to build an easy and integrated governance experience for all users within Polkassembly.
-   — This involves building for automation of proposal creation, addition of education nudges on proposal evaluation, verification of on chain identities and comprehensive user level profiling with leaderboards and gamification for governance participants
-   — Taking the onus for ensuring verification of users and building security for funds requested from treasury
-   — All teams requesting funds should be able to create an onchain identity, verify themselves and use our product suite to create a multisig (via Polkasafe or any other publicly available multisig SDK) when requesting for funds

As mentioned in our Polkadot Proposal, which went live earlier this year

-   — The time required for identity registration and verification will be reduced by more than 75%, enhancing the adoption of the feature and enabling a more robust and secure treasury management.
-   — The number 75% was deduced by using the average time difference between the two methods for 3 unique users
-   — The time required by the earlier method was 20-25 mins, and via Polkassembly will be approximately 5 mins

**How will Polkassemby enable users to apply for on chain identity verification?**  
Attached below is a step wise explanation of how Polkassembly plans to receive and process on chain delegations  
Step 1 -

-   — Discovery on on chain identity setup
-   — Users will be provided with contextual nudges on Polkassembly for setting up on chain identity

![](https://i.ibb.co/hKpMxLb/Screenshot-2023-12-16-at-2-30-30-PM-1.png)

Step 2 -

-   — Educating users on what is on-chain identity and why is it important
-   — Explaining the process of setting up and on chain identity and how verification works
-   — Helping users understand how to identify users with a valid on chain identity
-   — Clear communication on the total amount required (Please note the amount mentioned is representative and may vary based on market conditions)
-   — The breakdown of the feed will also be provided

![](https://i.ibb.co/87pmx0B/image-47.png)

Step 3 -

-   — Providing the user with an interface to share all their social and contact information
-   — The user will be allowed to choose any one of their address which they want to verify
-   — They can choose their legal and display name
-   — They can identify their social handles for further communication with the community
-   — They are informed about the bond, which is mandatory while setting up an on chain identity
-   — They are also informed about the fees charged for setting up or changing the social handles, which will be the fee per handle \* # of handles being verified

![](https://i.ibb.co/ysBfFdX/image-48.png)

Step 4 -

-   — Confirming the fees and initiating the step by step identity verification process
-   — Each social handle will need to be independently verified after the input is provided
-   — Once all verifications are completed the success states will be provided

![](https://i.ibb.co/nwPY5HJ/image-49.png)

![](https://i.ibb.co/0fRV6vv/image-51.png)

Other detailed steps and complete proposal can be found [here](https://docs.google.com/document/d/1wYkC09wMjC6KstW2E9VtHLgoRd1bV_GLhYoTOQ8gv8U/edit). We look forward to feedback from the community, suggestions to improve the product flow and support on our efforts to challenge the complex UX challenges of the Kusama ecosystem.Stats regarding our performance and details can be found in our latest tweet [here](https://twitter.com/polk_gov/status/1735702644965122179)

Regards,  
Polkassembly Team

WHO: Polkassembly Team
WHAT: Application to become a registrar on Kusama for on-chain identity verification and building an easy and integrated governance experience for all users within Polkassembly
PRICE/TIMEFRAME/RESOURCES: Not specified.

Polkassembly Registrar Application for kusama

Rejected

treasurer

Onboard Brale and Glo Dollar to Kusama AssetHub

small_tipper

Dear Kusama Community, I'm not sure how we didn't have a Kusama version of Flappy Bird until now, but we do now: https://kusama-fly-ksm.vercel.app. The requested tip amount is 1.989, which makes perfect sense considering that this is the year when Yayoi Kusama's artwork 'Bird' was created.

KusamaFly

### Summary of Recent Developments

- **Issue Identified**: A discrepancy was found in the opening block number for Lease Period 37 (LP37) during the Kusama auctions in 2024.
- **Incorrect Block Number**: The intended opening block number was #22,118,400, but it currently shows #21,118,400.
- **Proposed Solution**: Remove LP37 from the current scheduler and introduce a new one with the correct start time.
- **Correct Start Time**: The new LP37 should start at the originally planned block number, #22,118,400.
- **Additional Information**: For more details on the 2024 auctions, refer to the linked document [here](https://docs.google.com/spreadsheets/d/1BGjZlOdcj4Jmwn7AToByRVh54RW5s0Rpthj5M3jNoeY/edit#gid=1201445856).

auction_admin

**WHO: Kusama community**
**WHAT: Remove LP37 from current scheduler and introduce a fresh one adhering to the initially planned start time**
**PRICE/TIMEFRAME/RESOURCES: Not specified**

Addressing LP37 Opening Block Error in Kusama Auctions

- This referendum tests using a scheduler for managing bounties on the Treasurer track.
- Bounties need approval, funding, curator assignment, and closing, with specific delays between steps.
- Funds will be disbursed to a specific account used for validator payouts and cleanup scripts.
- The referendum uses a batch of three actions: approving a bounty, scheduling curator assignment, and scheduling bounty closure.
- The curator assignment is delayed by 86,400 blocks to match the funding period.
- The bounty closure is scheduled 14 days after approval, allowing time for claims.
- Adjustments to timing can reduce delays, but careful planning is needed.

WHO: Will, Paradox

WHAT: Test use of the scheduler on the Treasurer track by scheduling actions through the lifecycle of a bounty

PRICE/TIMEFRAME/RESOURCES: Not specified.

Proof of Concept - Using the Scheduler on the Treasurer Track

### System Parachain Collator Bounty on Kusama

- **Purpose**: Fund System Parachain Collators on Kusama, similar to Bounty 20.
- **Coverage**: Asset-Hub and Bridge-Hub System Parachains.
- **Goal**: Incentivize efficient performance, minimize censorship, and ensure ongoing activity.
- **Funding**: Covers infrastructure costs and staking rewards.
- **Duration**: 6 months, starting from 1 January 2024.
- **Amount**: 1954.46 KSM for the two System Parachains.
- **Details**: Available in a [Google Document](https://docs.google.com/document/d/14pRUj8WZPO75DuwDl4HoZU97v_Rmfx0bZ2KFqFW-qkE/edit).
- **Discussion**: Open on [Polkassembly](https://kusama.polkassembly.io/post/2613).

medium_spender

System Parachain Collators propose funding for Kusama's Asset-Hub and Bridge-Hub System Parachains. They request 1954.46 KSM for infrastructure costs and staking rewards for a 6-month period starting on January 1, 2024.

Funding of Kusama System Parachain Collators

- A group of companies (BlockOps, Dwellir, LuckyFriday, OnFinality, RadiumBlock, RockX, and Stakeworld) proposed a plan for better public RPC services in Polkadot and Kusama.
- RPC services are important for apps like Polkadot.JS and wallets to work well.
- The plan aims to make these services high-quality, decentralized, and affordable.
- There are two ways for RPC providers to apply: one focuses on cost, and the other on service quality.
- The budget is $400,000, split between Polkadot and Kusama treasuries.
- Providers will be monitored, and their performance will be shared publicly.
- The plan includes a 6-month operations phase where providers must meet service standards.
- Feedback and suggestions from the community are welcome to improve the proposal.

A joint-proposal by several RPC providers outlines a procurement strategy for public RPC services in Polkadot and Kusama ecosystems. The proposed budget is $400,000, split between Polkadot and Kusama treasuries, and aims to ensure high-quality, decentralized, and cost-effective services for essential applications like Polkadot.JS and wallets. RPC providers will be evaluated based on predefined standards and will be paid monthly in arrears based on the EMA7 day average price of DOT/KSM. The proposed budget provides a 12-month runway for assessment.

Bounty Proposal for Public RPCs for Relay and System Chains

- The proposal outlines a schedule for Lease Periods 36 and 37, each with seven auctions.
- It considers the potential integration of Agile cortime.
- If Agile cortime is integrated before the planned auctions, the remaining auctions may be canceled.
- Detailed auction configurations for 2024 and the call hash are available in a linked spreadsheet.

WHO: Not specified
WHAT: Establish a defined schedule for Lease Periods 36 and 37, consisting of seven auctions, with the potential integration of Agile cortime. Option to cancel remaining auctions if Agile cortime is integrated before planned dates.
PRICE/TIMEFRAME/RESOURCES: Not specified.

Proposed Kusama Auction Schedule 2024 on Auction Admin Track

- Rafael lost his crypto wallet's seed phrase.  
- He lost 257 Kusamas (KSM) staked in the Kusama Brazil Pool.  
- He provides proof of ownership with transaction records.  
- He asks the community for help to get his lost funds back.  
- He shows transfers from Binance to his Ledger wallet.  
- He also shows transfers to his Polkadot.js wallet for staking.  
- He offers to send a small amount to prove wallet ownership.  
- He suggests the treasury could reimburse him for the lost funds.

My name is Rafael, I  was new to crypto and lost my wallet seed phrase.

 TLDR:

\- I was new to crypto and lost my seed phrase.

\- 257 kusamas will be staked forever in the "Kusama Brazil Pool and in the native stake."

\- I have provided proofs below that this wallet was mine.

\- I'm seeking help and understanding from the community; this proposal to the treasury will reimburse me with the same amount that I lost forever.

\-I provide a series of documents with links related to transactions and activities in my wallets, highlighting transfers of Kusamas between the Binance exchange, my Ledger hardware wallet (G62xoBWMxZJsMXVUpjNFp4hdDZSza56ku9MhmxJTe8WRzbF), the Polkadot.js wallet (EVLbNe7gU3wHJ4jL8n5qQ1dvjrQxPGkq5WUriwoWiGAoERt), and my participation in the Kusama Brasil Pool and native staking.

\-To prove ownership of the G62xoBWMxZJsMXVUpjNFp4hdDZSza56ku9MhmxJTe8WRzbF wallet, I offer to send a small amount to any address. I suggest the proposal of receiving from the treasury, in my hardware wallet, the amount of Kusamas that are "locked" in the EVLbNe7gU3wHJ4jL8n5qQ1dvjrQxPGkq5WUriwoWiGAoERt wallet, leaving the decision to either revert these coins to the treasury or burn them in the hands of the governance, without compromising its reputation

**These are the transfers**

1-   Two transfers on 2023-08-04 of KUSAMA from my account on the BINANCE exchange, identified with my first name in the upper left corner, to the address of my LEDGER **G62xoBWMxZJsMXVUpjNFp4hdDZSza56ku9MhmxJTe8WRzbF**. The amounts were 14.936037KSM and 1.99 KSM, as indicated on page 1.

![](https://i.ibb.co/742qhw4/1.png)

2-   Two transfers from my LEDGER to the wallet **EVLbNe7gU3wHJ4jL8n5qQ1dvjrQxPGkq5WUriwoWiGAoERt**, followed by staking.

![](https://i.ibb.co/GnDkbSn/2.png)

![](https://i.ibb.co/KqdtK47/2-1.png)

3- Wallet **EVLbNe7gU3wHJ4jL8n5qQ1dvjrQxPGkq5WUriwoWiGAoERt** on Polkadot.js, where I performed unbonding to send the funds to my ledger wallet.

Link:  [https://kusama.subscan.io/account/EVLbNe7gU3wHJ4jL8n5qQ1dvjrQxPGkq5WUriwoWiGAoERt?tab=unbonding](https://kusama.subscan.io/account/EVLbNe7gU3wHJ4jL8n5qQ1dvjrQxPGkq5WUriwoWiGAoERt?tab=unbonding)

![](https://i.ibb.co/L0JCg2t/3.png)

4- Wallet **EVLbNe7gU3wHJ4jL8n5qQ1dvjrQxPGkq5WUriwoWiGAoERt** on Polkadot.js, where I performed unbonding.

Link: [https://kusama.subscan.io/account/EVLbNe7gU3wHJ4jL8n5qQ1dvjrQxPGkq5WUriwoWiGAoERt?tab=extrinsic](https://kusama.subscan.io/account/EVLbNe7gU3wHJ4jL8n5qQ1dvjrQxPGkq5WUriwoWiGAoERt?tab=extrinsic)

![](https://i.ibb.co/H7xjnyn/4.png)

![](https://i.ibb.co/fqyVDJV/4-1.png)

5- Ledger Wallet **G62xoBWMxZJsMXVUpjNFp4hdDZSza56ku9MhmxJTe8WRzbF** extract showing recent entry into the Kusama Brasil Pool.

Link: [https://kusama.subscan.io/account/G62xoBWMxZJsMXVUpjNFp4hdDZSza56ku9MhmxJTe8WRzbF?tab=extrinsic](https://kusama.subscan.io/account/G62xoBWMxZJsMXVUpjNFp4hdDZSza56ku9MhmxJTe8WRzbF?tab=extrinsic)

![](https://i.ibb.co/7k4Cs7B/5.png)

![](https://i.ibb.co/RhJYdBy/5-1.png)

6- Ledger Wallet **G62xoBWMxZJsMXVUpjNFp4hdDZSza56ku9MhmxJTe8WRzbF** extract showing my participation in the Kusama Brasil Pool.

![](https://i.ibb.co/T838bvK/6.png)

![](https://i.ibb.co/TY5Krdd/6-1.png)

![](https://i.ibb.co/8DMSgXs/6-2.png)

7- Polkadot.js Wallet **EVLbNe7gU3wHJ4jL8n5qQ1dvjrQxPGkq5WUriwoWiGAoERt** extract showing my participation in the Kusama Brasil Pool.

Link: [https://kusama.subscan.io/nomination\_pool/member?poolId=87](https://kusama.subscan.io/nomination_pool/member?poolId=87)

![](https://i.ibb.co/6RPF6nq/7.png)

![](https://i.ibb.co/M9tSYDD/7-1.png)

8 and 9- Extract from the explorer showing the transactions mentioned in item 1, indicating that the funds left my BINANCE account and were sent to my hardware wallet.

Link: [https://kusama.subscan.io/extrinsic/19092720-2](https://kusama.subscan.io/extrinsic/19092720-2)

Link: [https://kusama.subscan.io/extrinsic/19092759-4](https://kusama.subscan.io/extrinsic/19092759-4)

![](https://i.ibb.co/DfPL8Hq/8.png)

![](https://i.ibb.co/X23b8dC/9.png)

10- Transaction statement extracted from the Talismã wallet:

10.a- Transfer from my Binance account to my Ledger wallet **G62xoBWMxZJsMXVUpjNFp4hdDZSza56ku9MhmxJTe8WRzb**F.

10.b- Transfer from Ledger wallet **G62xoBWMxZJsMXVUpjNFp4hdDZSza56ku9MhmxJTe8WRzbF** to my **EVLbNe7gU3wHJ4jL8n5qQ1dvjrQxPGkq5WUriwoWiGAoERt** wallet, where there is staking through the Kusama Brasil Pool and native staking.

10.c- Same situation as the previous item (10.b).

![](https://i.ibb.co/RbtDS55/10.png)

![](https://i.ibb.co/Y0cJwx7/10-a.png)

![](https://i.ibb.co/jfp77Bp/10-b.png)

![](https://i.ibb.co/ZMG1Vyc/10-c.png)

 Reimbursement proposal after a seed phrase has been lost"

root

Deregister 2118

- Stakeworld runs services connected to its RPC nodes, like a database size overview.
- The database size service gets data from archive RPC nodes and is mentioned in the Polkadot wiki.
- Funding for RPC services was not approved, so Stakeworld might stop or reduce these services.
- Stakeworld revived its snapshot service, which helps users sync their nodes faster.
- The snapshot service is useful because Beefy, a new feature, temporarily disables warp sync.
- Stakeworld is considering adding RocksDB support to the snapshot service for a few months.
- They hope to continue these services but need funding to do so.
- More details and a funding proposal can be found in their GitHub repository.

Stakeworld plans to scale down/stop some services due to lack of funding, including the database size overview service. They are seeking funding to continue this service and revive their snapshot service, which will include rocksdb for a few months until warp sync gets re-enabled with beefy. See their proposal for more details.

Database size service and temporary snapshot service revival

- Subscan is a tool that helps people explore and understand the Substrate ecosystem.
- It needs money to keep running, like for servers and people who work on it.
- They are asking for money from the Kusama treasury to help from January to September 2023.
- They have worked hard to make it cheaper to run, and costs have gone down a lot.
- They want the community to help decide what new things to work on starting in November 2023.
- They will share more details about this plan in December.
- You can read more about their plan in a special document they made.

WHO: Subscan team

WHAT: Proposing reimbursement of operation and maintenance fee for Subscan for the period January to September 2023 from the Kusama treasury, and a gradual shift towards a community-developer collaborative model starting from November 2023.

PRICE/TIMEFRAME/RESOURCES: Not specified.

Subscan | Infrastructure Costs of Subscan for Kusama & Statemine Networks (from January to September 2023)

### Referendum Summary

- **Purpose**: To promote 6 collators to invulnerables on Asset-Hub Kusama.
- **Previous Referendum**: Referendum #308 intended to promote TurboFlakes, LuckyFriday, ParaNodes, Polkadotters, Stake.Plus, and IcebergNodes.
- **Execution**: Successfully executed on block #20691161, but not all collators were promoted.
- **Issue**: Mistake in creating the preimage led to duplication of two collators and omission of two others.
- **Proposed Fix**: New referendum to correct the error and promote LuckyFriday and ParaNodes to invulnerables.
- **Apology**: Apologies to LuckyFriday and ParaNodes for the oversight in the previous referendum.
- **Community Involvement**: Request for community support and votes to correct the issue.

staking_admin

WHO: Paulo

WHAT: Proposing a new referendum to fix the issue of not promoting LuckyFriday and ParaNodes to invulnerables on Asset-Hub Kusama as intended in the previous referendum.

PRICE/TIMEFRAME/RESOURCES: Not specified.

[Fix 308] Expand invulnerables set on Asset-Hub Kusama

TimedOut

Please vote nay

Please ignore

Vote Nay

big_tipper

BigTipper

- Collators on Kusama System Parachains get small rewards for their work.
- They need more funding to do their job well and not cut costs too much.
- A long-term solution is needed to pay Collators fairly.
- For now, the Treasury can help by giving them money through a bounty system.
- This proposal asks for 844.654 KSM to pay Collators for their work from October to December 2023.
- Starting January 2024, a new bounty system will handle payments.
- The community is asked to review and share thoughts on the proposal.

Dear Kusama community,
Collators on System Parachains are provided with minimal rewards for block production and small incentives in terms of transaction fees. This reduces incentives for Collators to act in a favorable manner and they may also be inclined to under-resourcing their hosts to save costs. Collators should receive funding for the provision of their services. Ultimately, this should be provided by the chain in a preferably sustainable manner. Implementation of such a system is a long-term solution. In the medium term, funding for collators can be provided by the respective Treasuries in the form of a bounty. This allows funding to be pre-allocated and independently managed.
This proposal is the final monthly operating costs payment for service providers in Q4 2023. Future cost compensation will be done under the <a href="../post/2613">Kusama System Parachain Collators Bounty 20</a> starting from January 2024.
<a href="https://docs.google.com/document/d/1UQi_DFP99i-VE8tOEQQHR10xqbIPHLqGHNW0f1imuEE/edit?usp=sharing">Full Proposal</a>
The proposal aims to secure 844.654 KSM for Collators on the Kusama System Parachains network for services delivered for 3 months - 10-12/2023.
<img src="https://example.com/your-image.png" alt="" /><img src="https://i.ibb.co/W5Jdk2r/Screenshot-2023-11-21-at-23-52-39.png" alt="" width="640" height="629" />
We encourage the Kusama community to review this proposal and provide any feedback or suggestions.
Thank you!

WHO: Collators on System Parachains.

WHAT: Proposal to secure 844.654 KSM for Collators on the Kusama System Parachains network for services delivered for 3 months - 10-12/2023.

PRICE/TIMEFRAME/RESOURCES: 844.654 KSM for 3 months - 10-12/2023. Future cost compensation will be done under the Kusama System Parachain Collators Bounty 20 starting from January 2024.

Kusama System Parachain Collators - Tips Q4/2023

### Referendum Proposal Summary

- **Purpose**: Fix a failed XCM instruction from Referendum 224.
- **Background**: Referendum 224 aimed to decentralize collator sets on Bridge-hub Kusama and Asset-hub Kusama.
- **Issue**: One XCM instruction failed due to missing session keys on a collator.
- **Solution**: Propose a new referendum to add new invulnerables using a new extrinsic.
- **Expected Outcome**: Add 6 new invulnerables, increasing the total from 2 to 8.
- **Collators Added**: TurboFlakes, LuckyFriday, ParaNodes, Polkadotters, Stake.Plus, IcebergNodes.
- **Impact**: 3 out of 9 active permissionless collators will become invulnerables.

WHO: Paulo, proposing a referendum to the Kusama community.
WHAT: Fixing the only XCM instruction that failed to execute from the successful outcome of referendum 224.
PRICE/TIMEFRAME/RESOURCES: Not specified.

[Fix 224] Expand invulnerables set on Asset-Hub Kusama

This is a ReferendumV2 post. It can only be edited by the proposer of the post .

Jungle Inc. and Minus Wells aim to create a video discussing Polkadot mechanics, future vision, and insights into Polkadot 2.0. They will do it in exchange for 3 DOT, challenging the trend of big influencers seeking $51k for average content. The goal is to elevate understanding and awareness for everyone who tunes in. No timeframe or additional resources mentioned.

wish_for_change

lease_admin

fellowship_admin

referendum_canceller

referendum_killer

OpenGov Referenda

Origin for signaling that the network wishes for some change

Able to spend up to 333,333.3333 KSM from the treasury at once

Managing the composition of the fellowship

Able to spend up to 8.3333 KSM from the treasury at once

Able to spend up to 33.3333 KSM from the treasury at once

Able to spend up to 333.3333 KSM from the treasury at once

Able to spend up to 3,333.3333 KSM from the treasury at once

Able to spend up to 33,333.3333 KSM from the treasury at once

OpenGov Referenda

Referenda Tracks