candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

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

big_spender

# Virto Team trial run: The Summa stack

**Total requested:** $USD 282,785.00 | **9,373.05 KSM**(EMA30)
**Proposed call:** [`0x12030f0044b643bd4c21004896aa6b146417590bd0191a7fe9677e64347e5d6f3d70bca9ded984c2c5c84e`](https://polkadot.js.org/apps/#/extrinsics/decode/0x12030f0044b643bd4c21004896aa6b146417590bd0191a7fe9677e64347e5d6f3d70bca9ded984c2c5c84e)

This proposal is the result of our learnings form [Ref. 47](https://kusama.polkassembly.io/referenda/47) and listening to the community's feedback in [Ref. 68](https://kusama.polkassembly.io/referenda/68). Compared to previous proposals, this time we are leaving out the development of out _hardware wallet prototype_ and the implementation of the _Local Incentives Protocol_ to have a narrower focus, a shorter timeline and smaller team to give the community a better feeling of how the team works and what it can accomplish.

Virto is a technical team of creative people aiming to become a mini "Latin American Parity" , focusing on creating user-friendly technology and tools to bring Polkadot technology to the masses. Our team's long term vision is to reduce social inequality and improve the efficient allocation of public resources by empowering local communities with autonomous micro-economies through our _Local Incentives Protocol_ (Not part of this proposal).

We are proposing to build a developer-friendly stack that brings the best of two decentralized ecosystems together, Substrate and Matrix, to create impactful infrastructure that empowers individuals and communities through user-friendly Web3 tools with minimal to no friction for the end user. We expect this technology to bring a whole new wave of users to the Kusama ecosystem that have no previous background or knowledge about blockchain or cryptocurrencies.

### Links

- [Full proposal](https://docs.google.com/document/d/1sh5w-d-0tiQjBg1nPj-9cl5LFFZ3s_M-9bl0Dko7y2Q/edit?usp=sharing)
- [Budget](https://docs.google.com/spreadsheets/d/1og1OMHyP4oarnK6inE9TrdYaOKltstT-DC6WExnsYq8/edit?usp=sharing)
- VirtoLIVE: [#2](https://youtu.be/wk-NWqBktV4) [#1](https://youtu.be/mX3_RcKsJvQ)

Deciding

Trial fund for Virto team

## UPDATE: Superseded by [Proposal 77](https://kusama.subsquare.io/referenda/referendum/77)
### Based on your feedback we won't be pursuing the current amount of funding, instead we will go for a "trial run" requesting less funds for a shorter period of time leaving out the parachain development and the hardware wallet. 

---

Hi, fellow community! Thanks for the feedback on [referendum 47](https://kusama.polkassembly.io/referenda/47), we learnt a lot and are now resubmitting our proposal to fund us The [Virto](https://virto.network) team. We are a group of creative and competent individuals with an extraordinary track record of building multiple projects in the ecosystem with funds from the treasuries and Web3 foundation. We aim to become the _"Latin American Parity"_ team of builders, focusing on creating user-friendly technology and tools to bring Polkadot technology to the masses.

We are proposing to build a **developer-friendly stack** to build impactful Web3 infrastructure for Kusama to empower individuals and communities through _user-friendly Web3 tools_ and **increase** decentralized technology adoption in the Kusama and Polkadot ecosystems. The team is requesting `20,000 KSM` in funding to continue our work towards reducing social inequality and improving the efficient allocation of public resources. Our team's vision is to reduce social inequality and improve the efficient allocation of public resources by empowering local communities with autonomous micro-economies through our Local Incentives Protocol (LIP).

Given our previous work helping 350k+ families in Venezuela to keep their money value using crypto, we have a deep understanding of the ecosystem and, most importantly, first-hand experience building and deploying real use case solutions using web3 technology. By making it accessible to regular users, we can solve real-world problems with social impact and reduce inequality by providing a more efficient allocation of public resources.

You can check a short slideshow where we expose the problem and our proposed solution [**here**](https://docs.google.com/presentation/d/1-W13YnDHDfen7KIC0vALXbvHupEomqhg9nYUaJyxy9g/edit#slide=id.gf87435e6da_0_183), and our full proposal document [**here**](https://docs.google.com/document/d/1b48eTa9GU7s0_Xf4hkyc7M1netZvNbGONJ8D_IgoknA/edit#).

**Edit - Extra content:**
- [First VirtoLIVE stream](https://youtu.be/mX3_RcKsJvQ) with team's intro and projects explainer
- [VirtoLIVE Q&A #1](https://youtu.be/wk-NWqBktV4) (17/01/23): Addressing Pokassembly questions.

Developer friendly stack to build Impactful Web3 Infrastructure for Kusama (funding the Virto team)

The substrate-api-client is a Rust-library for connecting to a substrate-based node via RPC. It is an alternative to subxt, which provides a similar functionality. RPC clients are needed in any software component, connecting to a substrate parachain. Therefore it is advisable, that there is more than one client available for Rust developers. Apart from that, the substrate-api-client fills a gap, providing the possibility to create extrinsics in a no_std-environment. Thereby facilitating extrinsic creation from within trusted hardware (like Intel sgx). This has a big potential for further usage in IoT environments. Last but not least, the substrate-api-client has an easy-to-use interface and comes with many practical examples, which makes it a good option for new developers.

This proposal aims to fund:

1. maintenance and support for the substrate api client over 3 months (Nov-22 until Jan-23).

2. evaluation and design of two new features:
     - CLI-wallet implementation
     - full no_std-compatibility

See the [discussion](https://kusama.polkassembly.io/post/1923) and our [full proposal](https://docs.google.com/document/d/1miIIMyHsNzdoZejVdBiV_u3NLyj7CHsr9uWBdKonrtQ/edit?usp=sharing) for the details.

Approved

Treasury Proposal: Maintenance for the substrate-api-client Nov-22 to Jan-23

Dear Community,

Ordum is a public good grants aggregator for the Polkadot and Kusama ecosystems. This proposal addresses the funding of R&D.

Introduction

There is no existing software besides Gitcoin to publish, apply for and manage grants. Gitcoin focuses on a quadratic funding model, while there is a need for an overall indexer and management software for grants in web3.

After reading the Builders Program post(https://forum.polkadot.network/t/builders-programs/226) on the Polkadot Forum and speaking with other members of the community (including councillors, Web3 Foundation, and members of Shokunin Network), it was evident that a grants aggregator is imperative for bringing projects into the ecosystem as well as scaling it.

In order to construct a rich and independent environment of public goods and DAOs, it is fundamental for teams to easily find and acquaint themselves with treasuries and foundations.

Problem

Treasuries / foundations(eg. Polkadot Treasury) are burning funds as there are not enough projects to support. 

Grants information and guidelines within the ecosystems are scattered and therefore difficult to find (there are only 2 places where we have a somewhat overview of these; Polkadot/Kusama documentation and Web3 Foundation Github). 

It is difficult to publicly track (grant) funding for different stages of project development. This has previously resulted in conflicts within the community.

There isn’t a unified public record to privately / publicly manage and display a grant recipient’s quality and outcome of delivery (scattered documentation). 

With GOV2 incoming, further research is required on tracking proposals and deliverables in order to determine the appropriate UX. 

Solution

Success for Ordum is the deliverance of all milestones and a V1 POC of a public goods grant aggregator.

1. A dapp which contains all grants from the ecosystems.

    Index data from treasuries in the ecosystem by building custom APIs(Subsquids) for tracking proposals 
    Integrate Github in the front end for tracking and submitting non-treasury grants 
    Building and maintaining light clients for quick data retrivals, security and low loading times 
    Enable log in with multiple DID services, Github and Wallets 

2. Minting of non-transferable NFTs as “certificates” for completed milestones. Each token would contain information on what was executed and how it was evaluated.

    Ordum will be built on Phala to leverege the chains privacy capabilities and Phat smart contracts 
    Create a connection between DID (foundation)–> Phala Smart Contract–> Non-transferable NFT–>DID (recipient) 
    Design a custom type of RMRK non-transferable NFT, stored on Crust, containing reports from the foundations on milestone delivery 

3. Delivery of milestones, grant applications and funding are displayed on a team’s profile for transparency.

    Front end displaying funding amounts and certificates within a roadmap

4. Issuing surveys and analyzing / feedback data for the purpose of aggregating and managing treasury grants in the most optimal way.

    Design the optimal UX through collaboration with other teams in the ecosystem(interviews, surveys)

Requested funding 78,804 USD 
Kusama rate EMA7 as per 24th of November 2022: 25.24 (and reimburstment of submission and decision deposit)

The full proposal can be viewed [here](https://hackmd.io/@XyloDrone/Ordum)

We look forward to hearing your feedback.

 Treasury Proposal: Ordum | Public Good Grants Aggregator for Polkadot and Kusama 


[Original treasury submission, that wont pass due to not applicable root call  (treasury.ApproveProposal) can be found [here](https://kusama.subsquare.io/referenda/referendum/2)] 

Hi Community,

We recently launched [Polkawatch decentralization analytics on Kusama](https://twitter.com/polkawatch/status/1578348493303083008), and [Nomination Pools](https://twitter.com/polkawatch/status/1583591038572036098) support.

The community is becoming more and more aware of the need for effective decentralization in our Ecosystem.

The interest peaked with a recent[ deplatforming event of Solana nodes](https://twitter.com/polkawatch/status/1588130270917627910) by a Network operator. 

We are been contacted by other teams of our community: Wallets, Parachains, Data Scientists, etc That want access to the data and help contribute to bringing awareness to the ecosystem. Which I think is good news.

Parachains are secured by the rely chain, but they are still vulnerable to censorship. Censorship could come from dishonest collators, deplatforming from network operators or sudden regulatory changes from hosting Countries. Despite been secured by the rely chain, parachains would benefit from decentralization analytics too.

On this proposal we aim to bring parachain support for Polkawatch, on top of continued operation of the service and other minor improvements.

The proposal has been for [discussion](https://kusama.polkassembly.io/post/1942) here.

We were invited to participate in [AAG#11](https://twitter.com/polkawatch/status/1595083537107009537) where an interesting discussion followed

Community feedback has been incorporated to the proposal.

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

Note: an extraordinary fee related to re-submission costs has been included.

[Replacement for Referenda #2] Polkawatch Decentralization Analytics Parachain Support and Continued Operation. 

Rejected

Funding the Virto team

Hello everyone! This referenda has been opened as a substitute for [Referenda 10](https://kusama.polkassembly.io/referenda/10)

 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!

Executed

Big Spender Proposal: Moderation Team Bounty Top-up

Hello everyone, I am Hitesh from Describedot. We create educational videos and weekly updates around the Dotsama ecosystem. We started this channel about a year ago and we have already published 34 videos on our youtube channel. Our weekly viewing growth had been over 28 percent which led us to approximately 30,000 views in a year. Recently we’ve also received great support from the Council Members of Polkadot and Kusama through tip endorsements. We are really thankful to the community members who supported us and assisted us in making great content.

Just last year we learned that people want to know about governance, about networks but they don’t have any resources to walk them through it. We decided to create basic videos during our early days and this has helped users to explore the Polkadot stack. They expressed their gratitude through likes and comments on our videos. Our main focus is to teach the Polkadot stack as well as governance in layman's terms to the Hindi audience.

Our first milestone was covered by WagMedia but we are looking to continue the work with a spending proposal.

You can learn more about our proposal from the document. Let the community know if you have any questions. We are happy to answer them

[Describedot](https://docs.google.com/document/d/1vnweYrk-ooQqfbha_EJUy9qYx3KDN3mk6PZVM7k0UPM)

Describedot Proposal: Production of 45 Dotsama ecosystem tutorial videos


[Referenda #5, contains an error. The parameter "after" was misinterpreted resulting in an enactment time of 2.8 years and will be cancelled with others in the same situation, it can be found  [here](https://kusama.subsquare.io/referenda/referendum/5)] 

Hi Community,

We recently launched [Polkawatch decentralization analytics on Kusama](https://twitter.com/polkawatch/status/1578348493303083008), and [Nomination Pools](https://twitter.com/polkawatch/status/1583591038572036098) support.

The community is becoming more and more aware of the need for effective decentralization in our Ecosystem.

The interest peaked with a recent[ deplatforming event of Solana nodes](https://twitter.com/polkawatch/status/1588130270917627910) by a Network operator. 

We are been contacted by other teams of our community: Wallets, Parachains, Data Scientists, etc That want access to the data and help contribute to bringing awareness to the ecosystem. Which I think is good news.

Parachains are secured by the rely chain, but they are still vulnerable to censorship. Censorship could come from dishonest collators, deplatforming from network operators or sudden regulatory changes from hosting Countries. Despite been secured by the rely chain, parachains would benefit from decentralization analytics too.

On this proposal we aim to bring parachain support for Polkawatch, on top of continued operation of the service and other minor improvements.

The proposal has been for [discussion](https://kusama.polkassembly.io/post/1942) here.

We were invited to participate in [AAG#11](https://twitter.com/polkawatch/status/1595083537107009537) where an interesting discussion followed

Community feedback has been incorporated to the proposal.

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

[Replacement for Referenda #5] Polkawatch Decentralization Analytics Parachain Support and Continued Operation.

The InvArch Network team seeks to provide the ecosystem with a new multi-signature solution, named Saturn, **available to every parachain & implementable throughout any dApp on those parachains**. This multi-signature solution will be made so that it can be **easily adopted by existing wallets in the ecosystem** & be immediately implemented to provide a superior multi-signature solution to the Dotsama ecosystem **compared to external solutions such as Gnosis Safe**.

Multi-party ownership solutions are the core of nearly every project being developed by the InvArch Network team, which has heavily influenced the design of the network’s infrastructure. While sharing our proposed multi-signature implementation with other builders & community members throughout the ecosystem, we have received tremendous interest & support. We also had a meeting with a member (Ricardo) from Parity Technologies in the past regarding our solution and received positive feedback on its capabilities.

The current multi-signature implementations available for builders in the ecosystem either rely on the current implementation used in the original multi-sig Pallet developed by Parity (which is limiting) or by developing their own custom solutions (which is time-consuming & costly). The ecosystem also lacks account-recovery capabilities & the ability to onboard & off-board new members of a multi-signature implementation. This is a very restricting problem, with concerns being shared across the Kusama community. We would like to change this current reality.

What we are proposing to build for the ecosystem is designed to service the entirety of Kusama & its parachains. We are providing it in a way that individuals will never need to purchase TNKR (optional, though) & can use KSM. **This is an open-source solution for Kusama and a solution that we truly believe will be a big boost for the ecosystem.** We are confident that if trusted by the community to deliver this solution, Kusama will go from having one of the worst multi-sig experiences in Web3 to one of the best, if not the best. Public interest in the potential for our multi-sig has been shared by the community in the past, and we would be extremely grateful if the community will signal their support for us to build this for Kusama.

- A full overview of the proposal & cost breakdown can be found [here](https://docs.google.com/document/d/e/2PACX-1vQLhnD3l0K5fYQN9_ECiHUeQZT_lTN4FvWkkPKIWy8mVGvhvKwmjwrMIlwHCVlitA0ovWyF2Qvaplfu/pub)

- A link to the public discussion previously posted regarding this proposal can be found [here](https://kusama.polkassembly.io/post/2031).

InvArch Tinkernet - Funding for a Multi-Signature Solution

Replacement of [Referendum #11](https://kusama.subsquare.io/referenda/referendum/11)

The substrate-api-client is a Rust-library for connecting to a substrate-based node via RPC. It is an alternative to subxt, which provides a similar functionality. RPC clients are needed in any software component, connecting to a substrate parachain. Therefore it is advisable, that there is more than one client available for Rust developers. Apart from that, the substrate-api-client fills a gap, providing the possibility to create extrinsics in a no_std-environment. Thereby facilitating extrinsic creation from within trusted hardware (like Intel sgx). This has a big potential for further usage in IoT environments. Last but not least, the substrate-api-client has an easy-to-use interface and comes with many practical examples, which makes it a good option for new developers.

This proposal aims to fund:

1. maintenance and support for the substrate api client over 3 months (Nov-22 until Jan-23).

2. evaluation and design of two new features:
     - CLI-wallet implementation
     - full no_std-compatibility

See the [discussion](https://kusama.polkassembly.io/post/1923) and our [full proposal](https://docs.google.com/document/d/1hJzzmimz_pjK-_4TunKvs-i2Zot2_9Ob3qUr7BlzaNo/edit?usp=sharing) for the details.


[Replacement of Referendum #11] Treasury Proposal: Maintenance for the substrate-api-client Nov-22 to Jan-23

Dear Community,

We are resubmitting our proposal due to issues with the UX indicating enacment 3 years from now. The previous proposal can be viewed [here](https://kusama.subsquare.io/referenda/referendum/4).

Ordum is a public good grants aggregator for the Polkadot and Kusama ecosystems. This proposal addresses the funding of R&D.

**Introduction**

There is no existing software besides Gitcoin to publish, apply for and manage grants. Gitcoin focuses on a quadratic funding model, while there is a need for an overall indexer and management software for grants in web3.

After reading the Builders Program [post](https://forum.polkadot.network/t/builders-programs/226) on the Polkadot Forum and speaking with other members of the community (including councillors, Web3 Foundation, and members of Shokunin Network), it was evident that a grants aggregator is imperative for bringing projects into the ecosystem as well as scaling it.

In order to construct a rich and independent environment of public goods and DAOs, it is fundamental for teams to easily find and acquaint themselves with treasuries and foundations.

**Problem**

Treasuries / foundations(eg. Polkadot Treasury) are burning funds as there are not enough projects to support. 

Grants information and guidelines within the ecosystems are scattered and therefore difficult to find (there are only 2 places where we have a somewhat overview of these; Polkadot/Kusama documentation and Web3 Foundation Github). 

It is difficult to publicly track (grant) funding for different stages of project development. This has previously resulted in conflicts within the community.

There isn’t a unified public record to privately / publicly manage and display a grant recipient’s quality and outcome of delivery (scattered documentation). 

With GOV2 incoming, further research is required on tracking proposals and deliverables in order to determine the appropriate UX. 

**Solution**

Success for Ordum is the deliverance of all milestones and a V1 POC of a public goods grant aggregator.

**A dapp which contains all grants from the ecosystems.**

- Index data from treasuries in the ecosystem by building custom APIs(Subsquids) for tracking proposals 
- Integrate Github in the front end for tracking and submitting non-treasury grants 
- Building and maintaining light clients for quick data retrivals, security and low loading times 
- Enable log in with multiple DID services, Github and Wallets 

**Minting of non-transferable NFTs as “certificates” for completed milestones. Each token would contain information on what was executed and how it was evaluated.**

- Ordum will be built on Phala to leverege the chains privacy capabilities and Phat smart contracts 
- Create a connection between DID (foundation)–> Phala Smart Contract–> Non-transferable NFT–>DID (recipient) 
- Design a custom type of RMRK non-transferable NFT, stored on Crust, containing reports from the foundations on milestone delivery 

**Delivery of milestones, grant applications and funding are displayed on a team’s profile for transparency**.

- Front end displaying funding amounts and certificates within a roadmap

**Issuing surveys and analyzing / feedback data for the purpose of aggregating and managing treasury grants in the most optimal way.**

- Design the optimal UX through collaboration with other teams in the ecosystem

Requested funding 78,804 USD // 2770 KSM
Kusama rate EMA7 as per 12th of December 2022, 11.00 (and reimburstment of submission and decision deposit)

The full proposal can be viewed [here](https://hackmd.io/@XyloDrone/Ordum)

We look forward to hearing your feedback.


[Resubmission proposal 4] Treasury Proposal: Ordum | Public Good Grants Aggregator for Polkadot and Kusama

After its first year as a common good parachain, Encointer has been granted another 48 weeks on Kusama. The Encointer Association seeks for financing of its planned activities for the new common-good parachain lease period, split into two proposals. The current proposal shall cover the funding for Q1 and Q2 2023 (until the end of June 2023). 

The amount of the proposed treasury spend is CHF 610’000 = 22’089 KSM.

Our [**Detailed Proposal**](https://docs.google.com/document/d/173FnUyaemsHD9wnGMipZWnanO23yZUVhco55RxBXKBw#) encompasses all of:
1. What is Encointer?
2. What have we achieved so far?
3. What are we planning to do in 2023?
4. How we funded our past activities
5. What we spent our funds for in the past
6. What we plan to spend in 2023 (Budget)
7. Proposal terms


[Big Spender] Encointer lease 2 Treasury Proposal

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

We will need to resubmit this proposal:

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

The proposal has now been [resubmitted here](https://kusama.subsquare.io/referenda/referendum/5). 

----

Hi Community,

We recently launched [Polkawatch decentralization analytics on Kusama](https://twitter.com/polkawatch/status/1578348493303083008), and [Nomination Pools](https://twitter.com/polkawatch/status/1583591038572036098) support.

The community is becoming more and more aware of the need for effective decentralization in our Ecosystem.

The interest peaked with a recent[ deplatforming event of Solana nodes](https://twitter.com/polkawatch/status/1588130270917627910) by a Network operator. 

We are been contacted by other teams of our community: Wallets, Parachains, Data Scientists, etc That want access to the data and help contribute to bringing awareness to the ecosystem. Which I think is good news.

Parachains are secured by the rely chain, but they are still vulnerable to censorship. Censorship could come from dishonest collators, deplatforming from network operators or sudden regulatory changes from hosting Countries. Despite been secured by the rely chain, parachains would benefit from decentralization analytics too.

On this proposal we aim to bring parachain support for Polkawatch, on top of continued operation of the service and other minor improvements.

The proposal has been for [discussion](https://kusama.polkassembly.io/post/1942) here.

We were invited to participate in [AAG#11](https://twitter.com/polkawatch/status/1595083537107009537) where an interesting discussion followed

Community feedback has been incorporated to the proposal.

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


Polkawatch Decentralization Analytics Parachain Support and Continued Operation. [this proposal will not enact successfully if approved: more info below]

Origin: BigSpender