candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

This referendum is about choosing curators for Bounty #25, which is about Public RPCs for Relay and Systems Chains. The curators are people who will help manage the project. Here are the curators:

1. Alex Dimitrijevic - Works at Parity Technologies.
2. Ivy Network - A group of people.
3. Eric Poh - Boss of Pinknode.
4. Leemo - Works with Nova Wallet, Robonomics, ChaosDAO, GM Parachain, HydraDX, and Basilisk Council.
5. lolmcshizz - Works with HydraDX.

These 5 curators will work together in a group of 3 out of 5. They will use a special account called "Any Proxy" for the curator account. Here are the account numbers:

- Kusama Pure Proxy: EYKL3c77TTotRo7bopubDJ9Zt4jEjcpFPA1D2axsWhQZ3Xq
- Kusama Multisig: GY8p88FVXFjrBokNfbuGi3nCNbbo5cHt3iGG5PyY6SHk7Xo

Executed

big_spender

GM &ndash; This referendum proposes the Curators for <a href="../bounty/25">Bounty #25</a> &ndash; Bounty Proposal for Public RPCs for Relay and Systems Chains. Please review the bounty and <a href="321">previous referendum</a> which funded this bounty for more info.
 The proposed curators are:
<ul>
<li>Alex Dimitrijevic (Infrastructure &amp; Tooling Lead [Ecosystem Success] at Parity Technologies)</li>
<li>Ivy Network (Collective)</li>
<li>Eric Poh (CEO of Pinknode)</li>
<li>Leemo (Nova Wallet / Robonomics / ChaosDAO / GM Parachain / HydraDX &amp; Basilisk Council)</li>
<li>lolmcshizz (HydraDX)</li>
</ul>
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.&nbsp;
<img src="https://i.ibb.co/y8G8ZNp/rpc-proxy.png" alt="" width="640" height="607" />
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

whitelisted_caller

Runtime Upgrade v1,001,000

- Polkassembly helps with governance in Polkadot and Kusama ecosystems.
- They want to become a registrar on Kusama after success on Polkadot.
- On-chain identities are important for trust and security in the ecosystem.
- Current identity verification is hard and confusing for new users.
- Polkassembly aims to make identity verification easier and faster.
- They plan to reduce verification time by 75%.
- Users will get step-by-step guidance to set up their identities.
- The team is asking for community feedback and support.

general_admin

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

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 seed phrase and can't access his funds.
- He lost 257 Kusamas, which are now staked in the "Kusama Brazil Pool" and native staking.
- Rafael provided proof of ownership of the wallet with transaction details.
- He is asking the community for help to get reimbursed for the lost funds.
- Transactions show transfers between Binance, his Ledger wallet, and Polkadot.js wallet.
- Rafael suggests receiving the locked funds from the treasury or burning them.
- He shared links and screenshots to prove his ownership and transactions.

small_spender

 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

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.

- **Issue**: Deposits from Treasury spend proposals are locked due to the decommissioning of Governance 1.0 on Kusama.
- **Referendum 301**: Enacted the decommissioning, causing the deposit issue.
- **Referendum 301 Solution**: Proposes to slash and refund deposits to proposers.
- **Similar Action**: Similar to Referendum 73 on Polkadot.
- **Invalid Proposals**: Proposals 291, 292, 293, 294, and 296 are identified as spam and excluded from the refund.
- **Excluded Bonds**: Bonds from rejected proposals are also not included in the refund.
- **Objective**: To resolve the deposit lock issue and refund valid proposers.

WHO: Kusama community 
WHAT: Slash Kusama Gov 1.0 treasury deposits and refund corresponding amounts to proposers in a batch call 
PRICE/TIMEFRAME/RESOURCES: Not specified

Rejecting Kusama Gov1.0 Treasury Proposals and Facilitating Bond Reimbursement whenever appropriate

### Summary of Kusama Relay Chain XCM Issue

- **Issue**: Kusama relay chain adds `SetTopic` instruction to XCM programs, which XCM v2 doesn't support.
- **Problem**: Relay chain sends XCM messages in v2 format, causing errors when destinations use v3.
- **Impact**: Mismatched XCM versions lead to failed transactions between relay chain and parachains.
- **Solution**: Set `safeXcmVersion` to v3 on the relay chain.
- **Outcome**: Relay chain will send XCMs in v3 format by default.
- **Long-term**: Defaulting to v3 is a strategic move for future compatibility.

WHO: The proposal does not mention a specific organization or individual.
WHAT: Set the Kusama relay chain's `safeXcmVersion` to v3 to avoid XCM version mismatch issues.
PRICE/TIMEFRAME/RESOURCES: The proposal does not mention any specific cost or timeframe for implementation.

Setting the relay chain's safeXcmVersion to v3

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