candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

### Kusama Asset Hub Referendum Summary

- **Purpose**: Reduce existential deposit (ED) on Kusama's Asset Hub.
- **Fee Calculation**: Fees in `sufficient` assets are based on KSM fees, converted using the ratio of minimum balances.
- **Effect of Reducing ED**: Reducing KSM ED by 10x increases fees in `sufficient` assets by 10x.
- **Proposal**: Reduce minimum balance requirements for assets like USDT, RMRK, and DOT by 10x.
- **Metadata Update**: Includes updating metadata for bridged DOT.
- **Enactment Block**: Set at 21,570,500, before the Asset Hub's ED reduction.

Executed

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 being proposed to appoint curators for Bounty #25, which is about setting up public RPCs for relay and systems chains.
- The curators will be part of a 3/5 multisig group, meaning at least three out of the five curators need to agree on decisions.
- The curators include:
  - Alex Dimitrijevic (Parity Technologies)
  - Ivy Network (Collective)
  - Eric Poh (Pinknode)
  - Leemo (Nova Wallet, Robonomics, etc.)
  - lolmcshizz (HydraDX)
- The multisig group will manage a Pure Proxy account, which is a secure way to handle the bounty funds.
- The Pure Proxy account address is EYKL3c77TTotRo7bopubDJ9Zt4jEjcpFPA1D2axsWhQZ3Xq.
- The multisig account address is GY8p88FVXFjrBokNfbuGi3nCNbbo5cHt3iGG5PyY6SHk7Xo.

big_spender

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 is part of Polkadot and Kusama governance.
- It helps make governance transparent and encourages participation.
- They want to become a registrar on Kusama after success on Polkadot.
- On-chain identities are important for trust and accountability.
- The current identity verification process is complicated.
- Their goal is to make the process easier and more integrated.
- They aim to reduce identity verification time by 75%.
- They plan to educate users and provide a step-by-step guide for verification.

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

### Summary of Referendum Proposal

- **Purpose**: The referendum aims to test using a scheduler for managing bounty actions on the Treasurer track.
- **Bounty Lifecycle**: Actions include approving, funding, assigning a curator, and closing the bounty.
- **Funding Delay**: After approval, a bounty must wait for an independent spend period (6 days on Kusama) before being funded.
- **Curator Assignment**: A curator can only be assigned after the bounty is funded, requiring a delay.
- **Fund Disbursement**: If no objections, funds will be sent to a public validator payout bot and a script for OpenGov and the Fellowship.
- **Extrinsics Batching**: The referendum batches three actions: approving the bounty, scheduling curator assignment, and scheduling bounty closure.
- **Timing**: Curator assignment is scheduled after 86,400 blocks (6 days), and bounty closure after 14 days.
- **Adjustability**: Timings can be adjusted to reduce delays after funding and curator assignment.

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

### Summary of RPC Service Proposal

- **Partners**: BlockOps, Dwellir, LuckyFriday, OnFinality, RadiumBlock, RockX, Stakeworld.
- **Objective**: Improve public RPC services for Polkadot and Kusama ecosystems.
- **Key Goals**: High-quality, decentralized, and cost-effective services.
- **Applications**: Essential for Polkadot.JS and wallets.
- **Strategy**: Focuses on quality, cost, decentralization, and simplicity.
- **Budget**: $400,000 split between Polkadot and Kusama treasuries.
- **Tenders**: Providers can submit based on cost targets or predefined service levels.
- **Monitoring**: Independent monitoring to assess performance.
- **Community Involvement**: Curators evaluate and score providers, ensuring transparency.

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

### Summary

- **Rafael's Story**: Rafael, a newcomer to cryptocurrency, lost his wallet's seed phrase.
- **Lost Funds**: 257 Kusamas are now permanently staked in the "Kusama Brazil Pool" and native staking.
- **Proof of Ownership**: Rafael has provided evidence that the wallet in question was his.
- **Proposal**: Rafael is seeking community help and proposes a treasury reimbursement for the lost amount.
- **Verification**: Rafael offers to send a small amount to any address to prove ownership of the wallet.
- **Transfers**: Detailed records show transfers from Binance to Ledger and further to the Polkadot.js wallet.
- **Stake Details**: Proofs include participation in the Kusama Brasil Pool and native staking.

small_spender

 Reimbursement proposal after a seed phrase has been lost"

root

Deregister 2118

- **Stakeworld Services**: Stakeworld provides various services connected to its RPC nodes, including a database size overview.
- **Funding Issue**: Recent treasury requests for RPC services were not approved, leading to plans to scale down or stop these services.
- **Database Size Overview**: This service, which is referenced in the Polkadot Wiki, may be discontinued without funding.
- **Snapshot Service Revival**: Stakeworld revived its snapshot service, which had not been updated but was being used more frequently.
- **Beefy Introduction**: The recent introduction of Beefy led to increased use of the snapshot service, prompting updates.
- **RocksDB Consideration**: Stakeworld is considering including RocksDB in the snapshot service temporarily until warp sync is re-enabled.
- **Proposal**: A proposal for funding these services is available [here](https://github.com/stakeworld/stakeworld-treasury/blob/master/2023-Q4.kusama.md).
- **Images**: The post includes images related to the database size overview service.

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 Proposal Summary

- **Subscan** is a key block explorer and analytics tool for the Substrate ecosystem.
- The proposal seeks reimbursement from the Kusama treasury for Subscan's operation and maintenance costs from **January to September 2023**.
- Subscan has reduced its infrastructure costs significantly since July 2023, with a recent decrease of over 50% in GCP bills.
- The proposal aims to shift Subscan's development to a community-developer collaborative model starting from **November 2023**.
- This model will prioritize features based on community demand and feedback.
- A detailed plan for this transition will be announced in **December 2023**.
- The full proposal can be viewed [here](https://docs.google.com/document/d/1MJOhO645uJm5y5Axok_NJCGLxMK8ZiESw_qw7Ff2ldA/edit).

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 receive minimal rewards and transaction fees, which may discourage them from acting favorably or adequately resourcing their hosts.
- The proposal suggests long-term funding for collators, ideally provided by the chain itself, but in the medium term, funding can come from the respective Treasuries as bounties.
- This proposal is for the final monthly operating costs payment for Q4 2023, with future payments starting in January 2024 under a new bounty system.
- The proposal seeks 844.654 KSM for collators' services from October to December 2023.
- The Kusama community is encouraged to review and provide feedback on the proposal.
- The full proposal can be found [here](https://docs.google.com/document/d/1UQi_DFP99i-VE8tOEQQHR10xqbIPHLqGHNW0f1imuEE/edit?usp=sharing).

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.

- Kusama's Governance 1.0 was decommissioned, causing Treasury spend proposal deposits to remain locked.
- Referendum 301 was enacted to address this issue.
- This referendum aims to slash and refund Treasury deposits to proposers.
- The process is similar to Referendum 73 on Polkadot.
- Spam proposals (291, 292, 293, 294, 296) and older rejected proposals are excluded from the refund.
- The `forceBatch` call will handle the refunds.

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

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