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.


proposalId

Deciding

big_spender

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

As we navigate OpenGov, we discovered that [Referendum 1](https://kusama.polkassembly.io/referenda/1) and [Referendum 2](https://kusama.polkassembly.io/referenda/2)  wouldn't enact successfully because the call we used (treasury.ApproveProposal) will only be enacted successfully with root origin. Consequently, the teams have resubmitted their proposals:

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

As a result, the new submissions can be found using the following links:

- [Referendum 3](https://kusama.polkassembly.io/referenda/3) aiming to fund the development of **Snowbrdige**
- [Referendum 5](https://kusama.polkassembly.io/referenda/5) seeking to finance **Polkawatch's** decentralization analytics Parachain support and continued operations

This particular submission service utilises the Referenda Canceller track and tries to cancel referendums 1 and 2 (replaced by 5 and 6).


calls

referendum_canceller

Referendum aiming to cancel two invalid Referendums (1 & 2)

This referendum registers as remark on-chain: "Expect Chaos."

remark

general_admin

The First OpenGov Referendum: EXPECT CHAOS!


[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.

amount

beneficiary

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

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).


treasurer

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

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: [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`

