candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

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

treasurer

Hello everyone!

 With this post, we are requesting a top-up to the Moderation Team Bounty to continue funding their contributions and support to our community.

 Due to the current market conditions, we are requesting this top-up earlier than we expected.

 In addition, somes changes have been made to the initial proposal.

 All of these changes and the details of the proposal, along with spending analysis, can be found [HERE](https://docs.google.com/document/d/1aFniLjcaNHc4ehJyIy0zQbWJJsEHqWuCRxX0szggPxk)

 Original Bounty Top-up Post can be found [HERE](https://kusama.polkassembly.io/bounty/14#a22a560c-fc0d-4d3c-8ff3-5890e08b79af) 

 Thank you for your attention!

- The post is requesting more money to support the Moderation Team Bounty.
- The request is being made earlier than expected because of current market conditions.
- Changes have been made to the original proposal.
- More details about the proposal and spending analysis can be found in a Google document.
- The original post about the Bounty Top-up can be found on a website called Polkassembly.

Approved

Treasury Proposal: Moderation Team Bounty Top-up

Due to an issue in the recent [decommissioning of Governance 1.0 on Kusama](https://github.com/paritytech/polkadot/pull/7314), which was enacted via [Referendum 301](https://kusama.subsquare.io/referenda/301), deposits associated with Treasury spend proposals remain locked. This referendum seeks to slash Kusama Gov 1.0 treasury deposits and refund the corresponding amounts to their respective proposers in a batch call similar to [Referendum 73](https://polkadot.subsquare.io/referenda/73), which was previously submitted on Polkadot.
Please note that spam proposals numbered 291, 292, 293, 294, and 296 have been identified as invalid submissions. Consequently, any bond associated with these proposals, as well as older proposals rejected by the council, are not included in this `forceBatch` call.

- There was a problem with a recent change to Kusama's governance system.
- This caused deposits for spending proposals to be locked.
- A new referendum has been proposed to refund these deposits to their proposers.
- Some proposals were identified as invalid and will not be included in the refund.
- This is similar to a previous refund on Polkadot.

Executed

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

Dear Community,

I am proposing the closure of bounty 14 on Kusama as it is now replaced by [bounty 24](https://polkadot.polkassembly.io/bounty/24) on Polkadot.  The bounty originally funded the Moderation Team but the team has since moved their source of funding from Kusama to Polkadot.

The action of closing the bounty would return any remnant funds on the account to the treasury and remove the curator.  In this case the Curator was already removed.  This occurred because the curators did not extend their expiration date and it elapsed.  When such occurs it leaves the Curators open to a permission-less extrinsic to remove them.

Kind Regards,
Will | Paradox | Ecosystem Janitor

- A person named Will wants to close a bounty on Kusama.
- The bounty was for a Moderation Team, but they now get funding from Polkadot instead.
- Closing the bounty would give any leftover money back to the treasury.
- The Curator was already removed because they didn't extend their expiration date.
- This means the Curator can be removed without permission.

Closing Bounty 14 - Moderation Team Bounty

Bounty 24 was created as a test by the W3F Tech Ed team.  This referendum seeks to remove it as part of good chain housekeeping.

Cleanup on aisle 24 - Tech Ed test bounty

TimedOut

Dear community, This referendum falls under the purview of janitorial activites.&nbsp; It seeks to close bounty 23 which was submitted in error.&nbsp; The submitter is attempting to do so with <a href="266">referendum 266</a> but is using a track with the wrong origin.&nbsp;&nbsp; I am also taking the opportunity to close bounty 22 which was submitted by Bill 27 days ago with no affirmative movements since. Regards, Will | Paradox | RCJ (Relay-Chain Janitor).

- A person named Will wants to close two bounties.
- The bounties are called bounty 23 and bounty 22.
- Bounty 23 was submitted by mistake and needs to be closed with referendum 266.
- Bounty 22 was submitted 27 days ago but no one has done anything about it.
- Will is a Relay-Chain Janitor.

To close erroneous and spam bounties

Proponent Address: F7fq1jMmNj5j2jAHcBxgM26JzUn2N4duXu1U4UZNdkfZEPV (parachain 2001) 
Requested Amount: 50,000 KSM 
Date: 19.06.2023
***
Product Link: [https://bifrost.app/vstaking/vKSM](https://bifrost.app/vstaking/vKSM) 
vKSM mechanism: [https://wiki.bifrost.finance/staking-liquidity-protocol-slp/vksm](https://wiki.bifrost.finance/staking-liquidity-protocol-slp/vksm) 

# Summary

[Bifrost](https://bifrost.finance) is a substrate based Kusama and Polkadot parachain that provides non custodial decentralized cross-chain liquid tokens for staked assets. By leveraging on Polkadots cross-consensus message format (XCM) it provides standardized cross-chain liquid staking services for various networks notably Polkadot (vDOT), Kusama (vKSM) and the first LST solutions on both Moonbeam (vGLMR), Moonriver (vMOVR) as well as other multiple chains (currently 6+ chains).

This proposal would request the Kusama treasury to lend a total of **50,000 KSM (repaid with interest)** as base liquidity for the KSM and vKSM (liquid staking token for KSM) pair. 

This proposal is identical to **our successful proposal of last year**- for reference [https://kusama.polkassembly.io/post/1606](https://kusama.polkassembly.io/post/1606) 
The execution timeline of the proposal: [https://kusama.subscan.io/treasury/177](https://kusama.subscan.io/treasury/177) 
The repayment of last years liquidity loan will happen on the **20th of July, 2023** (1 year following the loan receipt in 2022).

In terms of Repayment details, before the 20th of July, Bifrost will post under this proposal comment. The general steps will be the following: 
6/20 | Withdraw vKSM/KSM liquidity from Zenlink and Mangata DEX. 
6/25 | Initiate Bifrost referendum proposal to redeem borrowed vKSM + one year interest. 
7/3 | Start KSM unstaking process on Kusama relay chain. 
7/10 | Gather borrowed KSM + interest in Bifrost Kusama sovereign account. 
7/11 - 7/20 | Initiate Kusama referendum proposal to repay KSM from Bifrost paraid2001 to Kusama treasury. 

> **Bifrost had done the repayment of the last liquidity subsidy proposal, at July 11th, 2023. Check our latest comment under the last proposal:** https://kusama.polkassembly.io/post/1606#uyr5UGFRsOIFcPN2olpP

# Why Bifrost?

This Initial liquidity subsidy is fundamental in keeping the liquidity backing and support for broader utilities and use-cases across various DeFi applications and scenarios within the Kusama and Polkadot ecosystem and driving KSM related economic growth and adoption on both Substrate and EVM parachains.

This liquidity loan will keep driving the benefits achieved from our previous Kusama treasury liquidity proposal of last year for the broad Kusama ecosystem and for the community (below are **comparisons between last year's proposal and presents in terms of achievements and present developments**):

(**Past**) Provide liquidity for staked KSM and promote the capital utilization of KSM in various DeFi scenarios and applications. This initial liquidity subsidy provides backing to vKSM being a catalyst in driving the expansion of KSM’s multichain economy.

(**Present**) Liquidity subsidy helped us to growth KSM-vKSM capitalizations across:
- [Zenlink](https://dex.zenlink.pro/#/info/pools/2001-eCSrvaystgdffuJxPVYKf8H8UYnHGNRdVGUvj1SWSiatWMq)
- [Mangata](https://app.mangata.finance/)
- [DIA Oracle price feed](https://app.diadata.org/liquid-staking)

On-going developments and collaborations (check more details in Section #Motivation - application scenarios)
- vKSM vault collateral for Kintsugi kBTC
- vKSM on Kintsugi DEX for KSM LST Pool (to launch this quarter)
- vKSM deployment on HydraDX OmniPool (upon Bridge Hub DOT <> KSM completion).
- vKSM on Pablo AMM on Picasso Kusama (potentially first vKSM/vDOT pair via Composable Polkadot - Picasso Kusama IBC).
- vKSM as xcvKSM on Moonriver EVM Parachain for native utility:
- xcvKSM-xcKSM on Solarbeam DEX 
- xcvKSM as collateral for lending-borrowing on potential protocols such as Moonwell Apollo, Orbiter Finance.
***
(**Past**) Bifrost will develop the SLP pallet (vKSM minted pallet) SDK and Stable Asset Pool SDK for cross-chain vKSM mint/redeem calling convenience. The remote SDK call will facilitate cross-chain liquidation for vKSM/KSM.

(**Present**) The vKSM minted pallet has been developed and it is called the “XCM-Action Pallet” in [Bifrost Runtime - XcmAction](https://github.com/bifrost-finance/bifrost/tree/xcm-action/pallets/xcm-action), it currently works for EVM-compatible chains (Astar and Moonbeam have tested) contract ([https://github.com/bifrost-finance/xcm-action-contracts](https://github.com/bifrost-finance/xcm-action-contracts)) calling vToken minting/redemption/swap to Bifrost via XCM. It wlll be launched expected at the end of July of 2023.
***
(**Past**) Further improve the incentives for users to nominate and pledge tokens;

(**Present**) Bifrost has incentivized vKSM, vDOT single-token farming for over a year to drive users to use Bifrost and to deploy vKSM on other parachains and protocols.
***
(**Past**) Improve the enthusiasm of KSM holders to participate in staking;

(**Present**) The growth of KSM staked with Bifrost in the past year:
**from 70’108.1841 KSM to 347'823.6972 KSM with a growth rate of 396.12%**.

![](https://i.ibb.co/37PNyKc/image-10.png)

***
(**Past**) Borrow 50’000 KSM from the Treasury and pay back with interest, increasing treasury funds utilization.

(**Present**) Bifrost will repay 54,750 KSM with interest on the 20th of July, 2023. In using this liquidity loan, Bifrost has driven KSM liquidity use cases and continues to do so as mentioned in the section “Application scenarios”.

## The significant improvements of Bifrost in the past year

- Bifrost Substrate vToken growth in the past year: 
Stimulate vKSM market share and use cases, launch 5 more vTokens: vDOT, vMOVR, vGLMR and vFIL.
 
![](https://i.ibb.co/VW5Z9WK/image-8.png)

- XCM V3 improvements on Bifrost 
The implementation of XCM V3 on Bifrost replaced many off-chain services for SLP and SALP pallets, which simplified Bifrost’s ability to verify the message status sent to the other chain, streamlining the communication process. 
Learn more details at: [https://wiki.bifrost.finance/learn/libraries/xcm-v3-in-bifrost](https://wiki.bifrost.finance/learn/libraries/xcm-v3-in-bifrost)
- Treasury liquidity moved to Zenlink DEX: 
[https://bifrost.subsquare.io/post/5](https://bifrost.subsquare.io/post/5)
- Treasury liquidity moved to Mangata DEX: 
[https://bifrost.subsquare.io/post/25](https://bifrost.subsquare.io/post/25) 

# Motivation

As our original intention stated in our first proposal remains unchanged, Bifrosts long-term goal is underpinned by the following objectives:

- Facilitate Capital Flow of KSM staking

KSM, as the governance token of Kusama, about 50% of the total amount of KSM is currently in staking. **Bifrost hopes to activate the capital utilization of staked KSM while empowering the security of the Relay-chain consensus, and promote the activity of Kusama Staking.** Thus, Bifrost has enhanced [liquidity derivative protocol](https://github.com/bifrost-finance/bifrost/tree/develop/pallets/slp) with XCM V3 for Staking KSM: vKSM, a liquid staking token that is anchored 1:1 with staked KSM and comes with KSM staking income. Bifrost hopes to borrow 50,000 KSM from the Kusama Treasury as the base liquidity.

- Enhance the consensus security of Kusama network and reduce the threshold for users to participate in staking

Bifrost's KSM liquidity pledge agreement (staking liquidity protocol-SLP) completes the cross chain nominating of KSM by calling XCM at the runtime level, and SLP pallet completely controls and casts vKSM. In the whole process, the SLP protocol selects the validator with no security risk and reasonable rate of return through the governance on the chain to help users complete the one-stop nominate, and complete the final voting through the “[Sequential Phragménd Method](https://wiki.polkadot.network/docs/learn-phragmen#off-chain-phragmen)“ on the Kusama chain. 

vKSM validators (108 validators now): [https://bifrost.app/vstaking/vKSM?tab=validators](https://bifrost.app/vstaking/vKSM?tab=validators)

Bifrost uses a hybrid mechanism of community governance + automatic scoring to select Validators behind vKSM, making the validator election process diversified, more efficient and transparent. 
Bifrost divides the seats of entrusted validators into two parts, the Validator White List (VWL) and Validator Boost List (VBL). A set of clear validator rating selection rules will generate the former, while the active application of nodes will render the latter and the Bifrost community votes on their application submission for approval. The SLP protocol will only entrust the assets staked by the user to the validators in these two Lists.

VBL Discussions at Bifrost Forum: [https://bifrost.subsquare.io/discussions](https://bifrost.subsquare.io/discussions)

![](https://i.ibb.co/CVmV89f/image-9.png)

More details at: 
[https://bifrost.finance/news/vet-validator-election-track-based-on-bifrost-open-gov-for-the-multichain](https://bifrost.finance/news/vet-validator-election-track-based-on-bifrost-open-gov-for-the-multichain)

In Q3 of 2023, Bifrost will launch a governance voting track dedicated to validator elections: Validator Election Track (VET) in conjunction with OpenGov. The VWL and VBL need to pass the VET voting process before officially taking effect.

Therefore, vKSM can help any user willing to stake, complete the pledge without knowledge threshold, and use governance screening to improve the overall staking quality. Staking with mobility will be integrated with rich DeFi scenes to stimulate more users to participate in the nominated proof of stake.

## vKSM utility “implementation plan”
### Application scenarios

XCM-action: take KSM staking to Multichain

The function of XCM-Action is to deploy the vToken's mint, redeem, and Swap entry on Multi-chain, making it easier for users from different ecosystems to participate in "Stake KSM with Bifrost" or "Stake DOT with Bifrost". 
At the current stage, XCM-Action has completed several stages of development work:

1. Bifrost XCM-Action Pallet Development; 
2. XCM-Action Contract and SDK deploy on EVM-compatible chains: Astar and Moonbeam; 
3. Testing XCM-Action runtime logics with Astar Alpha and Moonbase testnets; 

Next Steps:

- May 2023 | Register xc-vKSM and xc-vDOT on Moonriver and Moonbeam, launch XCM-Action runtime on Moonriver and Moonbeam production.

- May 2023 | List vKSM on Pablo DEX on Picasso and create the first vKSM/vDOT pair using Composables’ Centauri IBC bridge (Polkadot ⇔ Kusama).

- May-June 2023 | Test the cross-chain settlement function of vKSM and vDOT for XCM-Action using DIA vKSM PoR + Market price feed and Astar lending protocol.

- June 2023 | List vKSM on Kintsugi DEX for KSM LST Stablepool and enable vKSM as a new vault type collateral for kBTC.

- June 2023 | Launch the Bifrost xc-vKSM Mint & Redeem page on Moonriver ecosystem, guiding Moonriver ecosystem users to stake KSM directly in the EVM environment without manually cross-chain to Bifrost.

- June 2023 | List xcvKSM on Solarbeam DEX on Moonriver and launch the xcvKSM-xcKSM pool.

- June 2023 | Upon the successful completion of the native Polkadot ⇔ Kusama bridge via Bridge Hub, list vKSM on HydraDX Omnipool.

- June-Aug 2023 | Use price feeds such as DIA + Chainlink price feed to promote xcvKSM as a lending and borrowing collateral on protocols such as Orbiter Finance, Moonwell Apollo (TBC).

- Aug-Dec 2023 | Enable xcm-action contract and SDK on Ethereum mainnet and L2s (rely on Polkadot ⇔ Ethereum bridge), promote vKSM utilities and Bifrost LSTs Hackathon in Ethereum.

# Proposal

**Amount**: 
We apply to borrow 50,000 KSM liquidity subsidy from the Kusama Treasury.

**Liquidity subsidy**: 
For a detailed description, please see the section “Liquidity Loan and Repayment Process” below.

## On-chain instruments used to provide liquidity to this proposal 
1. **Zenlink DEX** 
Zenlink is an underlying cross-chain DEX protocol based on Polkadot, deployed on Bifrost parachain and Moonbeam EVM. 

Why Zenlink?
- Bifrost native DEX, provides basic AMM exchange functionality for vKSM native users of Bifrost.

Additional Information 
Website: [https://zenlink.pro/](https://zenlink.pro/) 
Github: [https://github.com/zenlinkpro](https://github.com/zenlinkpro) 

2. **Mangata DEX** 
Mangata is a next-generation DEX that makes tokens from all ecosystems tradable on a single exchange. It features gasless swaps, prevents front-running and MEV without additional fees, and secures the network with the revolutionary proof-of-liquidity consensus.

Why Mangata?
- No Front-running/MEV
- Gasless swaps
- Proof of Liquidity staking, stake is used as liquidity in Mangata DEX.
- Liquidity bootstrapping

Additional Information 
Website: [https://www.mangata.finance/](https://www.mangata.finance/) 
Github: [https://github.com/mangata-finance](https://github.com/mangata-finance) 

3. **Kintsugi** 
Kintsugi is a blockchain network that allows bitcoin holders to utilize their assets within the Kusama network. Kintsugi’s kBTC aims to open the value of bitcoin to Kusama by enabling bitcoin based transactions across other Kusama parachains such as Bifrost, Karura, Shiden and Moonriver.

Why Kintsugi? 
- Use BTC across Kusama ecosystem
- vKSM as kBTC valut collateral
- vKSM as part of the KSM LST pool
- KSM stakers can utilize kBTC in border DeFi use cases

Additional Information 
Website: [https://www.interlay.io/kintsugi](https://www.interlay.io/kintsugi) 
Github: [https://github.com/interlay](https://github.com/interlay) 

# Managing the funds and Repayment process

Tracking Borrowing and Repayment Process

Bifrost will complete the borrowing/repayment process of the 50,000 KSM subsidy through a fully open and transparent process on Kusama and Bifrost governance.

**Borrowing Process**

- Kusama side 
1. Apply to Kusama treasury to borrow 50,000 KSM to the ParaId2001 (F7fq1jMmNj5j2jAHcBxgM26JzUn2N4duXu1U4UZNdkfZEPV) beneficiary through the (Treasury::propose_spend) method of the treasury module on Kusama.

- Bifrost side
1. Generate Bifrost treasury derived address via Utility::derivative_account_id method;
2. Through the Tokens::set_balance method, an additional 50,000 KSM will be issued on Bifrost treasury derived address;
3. Transfer 50,000 KSM from Bifrost treasury derived address to the treasury (eCSrvbA5gGNYdM3UjBNxcBNBqGxtz3SEEfydKragtL4pJ4F) address via the Tokens::force_transfer method;
4. Mint 25,000 KSM into about 25,000 vKSM via VtokenMinting::mint method;
5. Add 25,000 KSM and corresponding minted 25,000 vKSM trading pairs to Zenlink and Mangata to provide liquidity.
- Additional
1. In the actual transaction, steps 4 and 5 need to be called through the utility.dispatchAs method.
2. In the actual transaction, steps 1-5 need to be packaged into one transaction through utility.batchAll.

**Repayment process**

- Bifrost side
1. Remove liquidity from DEXs, retrieve the liquidity of the KSM-vKSM trading pair to the treasury account;
2. With the VtokenMinting::redeem method, almost 25,000 vKSM is converted back to more than 25,000 KSM;
3. Transfer 50,000 KSM from Bifrost treasury address to treasury derived address via Tokens::force_transfer method and set_balance to 0;
4. Transfer 4,750 KSM (one year 50,000 KSM staking rewards from vKSM) from Bifrost Treasury to Bifrost Sovereign account on Kusama via the XCM;
5. Initiate a proposal on Kusama, repay 54,750 KSM to the Treasury.

- Kusama side
1. Return roughly 54,750 KSM from ParaId2001 to Kusama treasury address (F3opxRbN5ZbjJNU511Kj2TLuzFcDq9BGduA9TgiECafpg29).

About redeem LPs on DEXs:

For non-Substrate DEXs: 
Since XCM currently does not support remotely calling Solarbeam's contract from Bifrost to complete the provide/redeem LP operations, Bifrost can only use the multisig solution of Bifrost Council members to operate xcKSM and xcvKSM on Solarbeam.

For Substrate DEXs: 
We will execute though governance via HRMP transactions, below are past cases: 
- Treasury liquidity moved to Zenlink DEX: 
[https://bifrost.subsquare.io/post/5](https://bifrost.subsquare.io/post/5)
- Treasury liquidity moved to Mangata DEX: 
[https://bifrost.subsquare.io/post/25](https://bifrost.subsquare.io/post/25)

Bifrost is a substrate based Kusama and Polkadot parachain that provides non-custodial decentralized cross-chain liquid tokens for staked assets. They are requesting a loan of 50,000 KSM from the Kusama treasury to lend as base liquidity for the KSM and vKSM pair. Bifrost's long-term goal is to facilitate the capital flow of KSM staking and enhance the consensus security of the Kusama network. They have achieved significant growth in the past year, including the development of the vKSM minted pallet SDK and stable asset pool SDK for cross-chain vKSM mint/redeem calling convenience. Bifrost will repay the loan with interest on the 20th of July, 2023. They will use Zenlink DEX, Mangata DEX, and Kintsugi to provide liquidity to this proposal. The repayment process will be transparent and open through Kusama and Bifrost governance.

Treasury proposal: KSM liquidity subsidy for KSM liquid staking token - vKSM

Dear community,

### **EDIT: The proposal now seeks $32,640.00 for RPC monitoring only.**

I am resubmitting [a proposal](https://docs.google.com/document/d/1us8glHDEaXeqNp0Ex8Z5sffy4GTfhrvHzGNzNvp-juw/edit?usp=sharing) for Monitoring of public RPC/WSS Endpoints & Node Database Analytics.  This proposal was previous submitted as [referendum 175](https://kusama.subsquare.io/referenda/referendum/175) but failed due to HANC's interference.

Unable to gauge his feedback, I have made the followings revisions:

- I am funding provision of servers for the DB Analytics/Restoration, this reduces the overall cost of the proposal by ~25%
- Reduce the slippage from 10% to 5% in light of a recent market correction

Do note that slippage as well as any excess KSM beyond the asking USD amount is refundable to the treasury.

The goals of the proposal remain the same:

- To become an independent monitor of all WSS providers, displaying key metrics in a visual manner (Dashboard)
- To monitor DB growth, sizes, bloat and restoration times for various DB configurations.

Kind Regards,



SubSquare has resubmitted a proposal for monitoring public RPC/WSS endpoints and node database analytics. The proposal was previously rejected due to interference. The revised proposal includes funding for servers for DB analytics/restoration, reducing the overall cost by 25%. The slippage has been reduced from 10% to 5% in light of a recent market correction. The proposal aims to become an independent monitor of all WSS providers and monitor DB growth, sizes, bloat, and restoration times for various DB configurations. Any excess KSM beyond the asking USD amount is refundable to the treasury.

Rejected

Monitoring of public RPC/WSS Endpoints

Dear community,

I present to you [a proposal](https://docs.google.com/document/d/1us8glHDEaXeqNp0Ex8Z5sffy4GTfhrvHzGNzNvp-juw/edit) which aims to develop a technical solution to: 

- Monitor and report on the uptime, performance and integrity of public WSS (RPC) relay-chain endpoints. The data could be used to guide funding of said services, to encourage a service standard or to provide existing providers with a second take on key metrics from a third-party.
- Monitor and trend database growth rates for twenty-four database configurations. This is something that I started and self-funded > 16 months ago. Upon launch it gained interest by technical parties and is now referenced within the Polkadot Wiki. I would like to expand on the project to include growth charts and offer a wider range of database configurations. Further to this, I intend to monitor the restoration times of some of the more popular database configurations.

Additional: Providing that the original scope is met, I'll consider monitoring of database bloat, trend average RAM or CPU usage as well as monitor availability and integrity of bootnodes.

Both major items are not found within any existing public resources and are in my opinion well aligned to Kusama's experimental nature. Full details including budget details can be found in [the proposal document](https://docs.google.com/document/d/1us8glHDEaXeqNp0Ex8Z5sffy4GTfhrvHzGNzNvp-juw/edit). This document was circulated to members of the 1KV/IBP for a week and was open for [public discussion](https://kusama.polkassembly.io/post/2546) for > 2 weeks.

 
Disclosure: As it relates to WSS monitoring, I am presently employed by LuckyFriday which as of last week is now listed as a public RPC provider. I also share good professional relationships with most of the RPC providers. The proposed solution is open sourced such that anyone can operate in-tandem and compare/challenge results. Once up and running these `audits` will be operated and presented without any human intervention. 
 

Kind Regards, 
Will | Paradox

- Will has a plan to make sure that public WSS (RPC) relay-chain endpoints are working well and can be checked by others.
- He also wants to keep track of how fast different databases are growing and how long it takes to restore them.
- Will's plan is not found in any other public resources and he thinks it fits well with Kusama's experimental nature.
- Will's proposal is open source, which means anyone can use it and compare the results.
- Will is employed by LuckyFriday, which is now a public RPC provider, but his plan is unbiased and will be operated without any human intervention.

Proposal for Monitoring of public RPC/WSS Endpoints & Node Database Analytics

After multiple considerations, the community's decision was to disapprove of the top-up request submitted as [Referendum 144 ](https://kusama.polkassembly.io/referenda/144) and officially mark the end of **[Infrastructure Maintenance Bounty #13](https://kusama.polkassembly.io/bounty/13)**, which worked to aid teams that have been funded by the treasury before to maintain infrastructure and perform continued operations to reduce the work of resubmitting the treasury proposals and time constraints associated with it - the bounty funded teams that provided common goods to the community, including RPC endpoint providers, indexers, governance forums and block explorers. 

This proposal aims to formalise the community decision and close the bounty on-chain. All the remaining funds will be sent to the treasury, and the curator deposit will be unreserved if possible. 

*Please note that as a result of this new approach, all the core essential infrastructure providers are now asked to submit their maintenance requests via [OpenGov](https://scribehow.com/shared/Submitting_a_Referendum_to_the_Kusama_Network__BZxcgSYkRCaCVvm5Sxjp9g).*

- The community decided not to approve a request for more money for a project called Infrastructure Maintenance Bounty #13.
- This project helped teams that were already funded by the treasury to keep things running smoothly.
- The project funded teams that provided things like RPC endpoint providers, indexers, governance forums, and block explorers.
- The remaining money from the project will be sent back to the treasury.
- Now, essential infrastructure providers need to make their maintenance requests through a new system called OpenGov.

Formalise the community decision and close the Bounty #13

Imbue was started with the vision of accountability empowered by the blockchain. We as an ecosystem can do better!

Imbue at its core is milestone-based vesting powered by democracy. Proposals are submitted on the network with milestones and their respective %s. Only funders get to vote on the progress of a project since they have the most to lose, while project initiators are incentivised to continue delivering so they get more of their project’s funds unlocked.

What we want to build is a platform where creatives, developers, researchers and anyone with talent can utilize their expertise to get paid securely and safely regardless of where they are in the world. To give people options that do not exist where they live and get funded in whatever substrate native token they wish

We believe this resonates strongly with the ethos of Kusama, and will be a great outlet to bridge over other ecosystems that can leverage Imbue and hence Kusama as a vehicle to achieve their dreams or improve their lives. Thereby pushing more adoption onto Kusama and definitively answering the popular misconception that Web3 lacks utility

The team reached out to the community and described what we wanted to do. A promise was set that - given the team's expertise to deliver on this - there will be no external funding until a usable product is produced. We decided to build it in an open-source manner with volunteers

Imbue is one of the very few(GM perhaps being the only other) that remains to this day open source and not funded with the sole purpose of protecting the community. As such, the team are also exploring ways to migrate towards a common good chain

We strongly believe that Imbue can add much-needed utility and value to Kusama beyond just DeFi, as well as help us reach beyond the Polkadot ecosystem and clearly and definitively answer "Why Kusama?" or "How does this make my life better?" and bring in users and adoption

Please feel free to look at the [proposal](https://docs.google.com/document/d/1X-zlnNZ5zD9wZhNf-Prb3a5zv_HW_7aYrfcNBmPg9I4/edit?usp=sharing) and we look forward to your feedback

- Imbue is a platform that uses blockchain to make sure people are accountable for their work.
- People can propose projects on the platform and only the people who give money to the project get to vote on how it's going.
- Imbue wants to help people all over the world get paid for their talents in a safe and secure way.
- The team building Imbue promised not to take any money until they have a working product.
- Imbue is open source, which means anyone can help make it better, and the team is looking for ways to make it even better for everyone.

Imbue Treasury Proposal. Freelance Marketplace

**Spanish Content and Event Production Bounty** is created to reward the community's content creators for their efforts in creating content in Spanish, as well as to ensure that the content created is of quality and kept in line with the needs of the ecosystem, incorporating defined criteria for each area of assessment.

This bounty was approved on Governance V1 as you can check [here](https://kusama.polkassembly.io/motion/568). Now we submit this referendum to assign the curators to that bounty.

 You can read the full **Bounty Curator Candidacy** [here](https://docs.google.com/document/d/1gqtnH5riuLg4XEDEmUP0e3_VR6Lll-ujVUkBRYl2aq0/edit?usp=sharing).

Multisig (4/6): [GdWeP4eyjEqsb2QEDcG8jcaJCwL4owDdkTvES5vJJo54W8Q](https://kusama.subscan.io/account/GdWeP4eyjEqsb2QEDcG8jcaJCwL4owDdkTvES5vJJo54W8Q)

- A bounty has been created to reward people who create content in Spanish.
- The content must be good quality and meet certain criteria.
- The bounty was approved on Governance V1.
- A referendum is being submitted to assign curators to the bounty.
- A multisig account is being used for this bounty.

Assign curators to Spanish Content and Event Bounty (Bounty #16)

Dear community,

**Summary:**  This proposal seeks to test the Treasurer's origin in its ability to cancel bounties and slash tips.  The bounties are SPAM and the tipping system is no longer receiving the attention of the Council.  If these actions are successful I am seeking a payout of 32 KSM (8 KSM per item) for use with my public staking rewards payout bot.

**Details:** The Treasurer track has been used to primarily fund recipients using `treasury.spend()`; it has also been used to fund and assign curators to bounties.  I would like to further test its ability to close two SPAMMY bounties entitled "[Catching #KSM Scams And Buying And Burning Rug Nfts](https://kusama.subscan.io/bounty/17)" and "[Help Bring The Ruggables Real Governance](https://kusama.subscan.io/bounty/18)".  I would also like to test use of an extrinsic that hasn't been used often, `tip.slashTip()`, this extrinsic removes a tip and slashes the user's deposit (0.033 KSM x 2) returning it to the treasury.  These are items of house keeping and it is best administered by the public in an open and collective manner.

As a reward, I am proposing a payout of 32 KSM (8KSM x 4) made payable to an account used by my public KSM staking rewards payout bot.  Rewards are divided into two independent branches, 16 KSM if both bounties are indeed closed and another possible 16 KSM if both tips are slashed.  If neither extrinsic is successful then no reward would be issued.

Regards,

- The proposal is to test the Treasurer's ability to cancel bounties and slash tips.
- There are two SPAMMY bounties that need to be closed and a tipping system that needs attention.
- The proposal suggests using an extrinsic that hasn't been used often, `tip.slashTip()`.
- The reward for successful closure of both bounties and slashing both tips is 32 KSM.
- If neither extrinsic is successful, no reward will be given.

Testing Treasurer Track - Close Bounties & Slashing Tips

This referendum is to assign the Administrative Curators to the IBP program. It will assign the following proxy address controlled by the following multisig account. Please note, originally, per our proposal we were supposed to have Art from Purestake act as one of the curators. Unfortunately due to time restraints we replaced Art's multisig slot with Coinstudio.

Pure Proxy: DDzazS9qxXPmm4t8vX8zpCBzFcDuhKD3BNKqmXxtbJYoHte

Multisig (3/5): DmHG4r2oKs6CkWYjS8WrSPgUAV84VnzgbrshqLakHk1xsCg

Multisig Members: Cbbsb4t8Uq5KDaWeg12f2LMwTg6RGjei29bVo2ei4ZkFN1g (Will) D8DtYYJUUBoACJwJrLNyn8aYArumdViVWAcZRUKcxnSoV9D (Otar) G78epYd9YJUGnLDNzKPx9mrMTCUtRHgrDVzB7Ucu5UAJVbK (Anaelle) EUbLd8Vc2PepZKz9onPDfRzzE2GqsUtLjUy8yDunZu7xndz (bLd) GCMGu8sjEuEZuMZavo5PLvAhr8fJXAty76jDV1YPquG9erp (Coinstudio)

1. This is a referendum for the IBP program.
2. The referendum is to assign Administrative Curators.
3. The curators will control a proxy address and a multisig account.
4. One of the original curators was replaced due to time restraints.
5. The multisig account has 5 members who will control it.

Assign Administrative Curators to Infrastructure Builder Program (Bounty #19)


This proposal seeks to enact the will of Ref 35 which failed due to "Bad Origin" on the proposeBounty() call. 

https://kusama.subsquare.io/referenda/referendum/35

[Treasurer] Referendum #51

**Proposal Summary**

On behalf of the community and ecosystem, we propose the creation of the **Infrastructure Builders Program** that will work to create a decentralized network of infrastructure services providers working as an autonomous organization to provide mission critical services. With recent issues in the crypto space regarding centralization around single providers for core network services; it is critical that the ecosystem work to decentralize all aspects of operations. By putting too much trust in any one entity we put the entire network at risk. We believe this program will work toward the goal of creating a more trustless environment with better collective oversight of network infrastructure and a high quality of service. 

**Service Details**

Existing members of the 1000 validators program will be able to apply to this program after having achieved the necessary rankings set forth in the proposal. Accepted applicants will deploy owned server hardware in enterprise datacenter environments to provide necessary bootnodes, rpc services, snapshots, and other critical infrastructure services. These services are expected to be 100% powered by renewable energy or 100% offset by other carbon reduction strategies. Members will be paid in an Infrastructure-as-a-Service format for the various nodes they run and operate decentralized health checks for all other members as well as other aspects of network infrastructure. 

We have already begun deploying and have a limited proof of concept as outlined in Program Milestone 1.  Stake Plus has teamed with 3 other 1000 validators program members located in the US, Turkey, Czech Republic, and Portugal. We are currently providing support for Westend, Kusama and Polkadot and are currently working to bring up services for Westmint, Statemine, Statemint, Encointer and Collectives. Existing services are deployed at the following locations:


- wss://rpc.dotters.network/polkadot
- wss://rpc.dotters.network/kusama
- wss://rpc.dotters.network/westend


**Funding Details**

We are requesting $1,300,000 for funding of the program milestone 2. The funds will be held in an Administrative Curator controlled 3 of 5 multi-sig wallet. The expected utilization of these funds is broken down as follows:


- Member One-Time Payments: $300,000 
- Member RPC Service Payments: $500,000 
- Member Snapshot Payments: $100,000
- Member Services/Monitoring Infrastructure: $75,000
- Janitorial Advisors Payments: $45,000
- Administrative Curator payments: $26,000
- Software Development Fund: $254,000


You can view the full **Infrastructure Builders Program** proposal here:

[https://docs.google.com/document/d/16USQYVhlyAlrU829EUB2TRoqUC0nnfoS_uCdZ84HT8k/edit?usp=sharing](https://docs.google.com/document/d/16USQYVhlyAlrU829EUB2TRoqUC0nnfoS_uCdZ84HT8k/edit?usp=sharing)






- A group of people want to create a program called the Infrastructure Builders Program.
- This program will help make sure that important parts of the internet are not controlled by just one person or group.
- People who are already part of a group called the 1000 validators program can apply to be part of this new program.
- The people who are accepted will use their own computer servers to provide important services for the internet.
- They are asking for $1,300,000 to help pay for this program.

[Treasurer] Referendum #35

As we navigate OpenGov, we re finding new things again, a second time: referendum #1 would not have enacted succesfully, because the call we used (treasury.ApproveProposal) would have only be enacted successfully with root origin. Additionally, we have now discovered that referendum #3 will also not be enacted successfully due to a polkadot-js UI issue whereby it used the expected enactment block as the enactment duration rather than particular given time, so the proposal would take many years to enact.

This has since been fixed in the polkadot-js UI.

This is the (hopefully final) resubmission of the proposal:

- on Treasurer track (same one)
- with the call treasury.Spend (including the amount in KSM for the allocation)

Original replaced treasury submission: [HERE](https://kusama.polkassembly.io/treasury/229)
Second replaced treasury referenda: [HERE](https://kusama.polkassembly.io/referenda/3)

This proposal is now up for vote! aiming to cover the development of **Snowbridge** by the Snowfork team: a fully trustless, permissionless and general purpose bridge between Kusama/Polkadot and Ethereum. The bridge will launch on the Bridge Hub, a common-good parachain that is being developed by Parity for Kusama and Polkadot. This proposal is a funding request for 28 months worth of long term runway for all operations for the Snowbridge team (16 months retroactive, 12 months in future), with the goal to launch as a common-good bridge on the Bridge hub on both Polkadot and Kusama.

The full proposal can be reviewed on [the post](https://kusama.polkassembly.io/treasury/229) and includes extensive additional details related to further motivation for supporting and promoting Snowbridge, a long term roadmap, governance and economic plans as well as long term economic incentives for successful execution, launch and running of the project. Please note that both networks are voting on the project: the Polkadot proposal (up for vote by the council as external motion and later by the community if approved) can be found [here](https://kusama.polkassembly.io/treasury/229).

- A previous proposal would not have worked because it needed a special permission to work.
- Another proposal also had a problem with the time it would take to be enacted, but it has been fixed.
- There is a new proposal to fund a project called Snowbridge.
- Snowbridge is a bridge between Kusama/Polkadot and Ethereum.
- The proposal is for 28 months of funding for Snowbridge to launch on the Bridge Hub.

[Replacement for Referenda #1 and #3] Treasury Proposal: Snowbridge Funding Proposal

As we navigate OpenGov, we re finding new things: it seems referendum #1 wont enact succesfully, because the call we used (treasury.ApproveProposal) will only be enacted successfully with root origin.

This is the resubmission of the proposal:

- on Treasurer track (same one)
- with the call treasury.Spend (including the amount in KSM for the allocation)

Original treasury submission: [HERE](https://kusama.polkassembly.io/treasury/229)

This proposal is now up for vote! aiming to cover the development of **Snowbridge** by the Snowfork team: a fully trustless, permissionless and general purpose bridge between Kusama/Polkadot and Ethereum. The bridge will launch on the Bridge Hub, a common-good parachain that is being developed by Parity for Kusama and Polkadot. This proposal is a funding request for 28 months worth of long term runway for all operations for the Snowbridge team (16 months retroactive, 12 months in future), with the goal to launch as a common-good bridge on the Bridge hub on both Polkadot and Kusama.

The full proposal can be reviewed on [the post](https://kusama.polkassembly.io/treasury/229) and includes extensive additional details related to further motivation for supporting and promoting Snowbridge, a long term roadmap, governance and economic plans as well as long term economic incentives for successful execution, launch and running of the project. Please note that both networks are voting on the project: the Polkadot proposal (up for vote by the council as external motion and later by the community if approved) can be found [here](https://kusama.polkassembly.io/treasury/229).


- A proposal for funding the development of Snowbridge by the Snowfork team is up for vote.
- Snowbridge is a bridge between Kusama/Polkadot and Ethereum that is fully trustless, permissionless and general purpose.
- The proposal is for 28 months worth of funding for the Snowbridge team, with the goal to launch as a common-good bridge on the Bridge hub on both Polkadot and Kusama.
- The full proposal includes details related to motivation, roadmap, governance, economic plans, and incentives for successful execution.
- Both networks are voting on the project: the Polkadot proposal can be found on the Polkadot website.

#3 [Replacement for Referenda #1] Treasury Proposal: Snowbridge Funding Proposal

Original treasury submission: [HERE](https://kusama.subsquare.io/treasury/proposal/229)

This proposal is now up for vote! aiming to cover the development of **Snowbridge** by the Snowfork team: a fully trustless, permissionless and general purpose bridge between Kusama/Polkadot and Ethereum. The bridge will launch on the Bridge Hub, a common-good parachain that is being developed by Parity for Kusama and Polkadot. This proposal is a funding request for 28 months worth of long term runway for all operations for the Snowbridge team (16 months retroactive, 12 months in future), with the goal to launch as a common-good bridge on the Bridge hub on both Polkadot and Kusama.

The full proposal can be reviewed on [the post](https://kusama.polkassembly.io/treasury/229) and includes extensive additional details related to further motivation for supporting and promoting Snowbridge, a long term roadmap, governance and economic plans as well as long term economic incentives for successful execution, launch and running of the project. Please note that both networks are voting on the project: the Polkadot proposal (up for vote by the council as external motion and later by the community if approved) can be found [here](https://kusama.polkassembly.io/treasury/229). 

Hash: `0xfae1763e293099ff7858ddf848255fb05efb10b973f49886b5b213b2981fb111`



- The Snowfork team wants to create a bridge between Kusama/Polkadot and Ethereum.
- They need money to work on this project for 28 months (16 months already passed and 12 months in the future).
- The bridge will be launched on the Bridge Hub, which is being developed by Parity for Kusama and Polkadot.
- Both networks are voting on the project.
- The full proposal has more details about the project's plans and goals.

[11] Origin: Treasurer