Origin able to spend around 10,000 DOT from the treasury at once.

small_spender

Proposer: COINSIDER
Address: 16B44UW3iW8MBb7vHACpKriF7NNQ9cw4YMPT5n6wYJzfGySY
Contact: @joincoinsider on Twitter
Duration: Around 6 weeks
Amount: Around $20,000 including fees &mdash; 5,000 DOT with DOT price at $4.00
Team:&nbsp; 1 researcher, 1 editor, 1 thumbnail designer, and myself as the writer/host
About me:
Hey everyone! I&rsquo;m Kevin, the founder and host of the <a href="https://www.youtube.com/coinsider" target="_blank" rel="noopener">Coinsider channel on YouTube</a>. I&rsquo;m here today to propose to you a specialized content campaign for Polkadot and its ecosystem.
First, I know what some of y&rsquo;all are thinking: &ldquo;Sigh&hellip; yet another content creator doing a proposal?&rdquo; And I hear you! But I want to make the case that we&rsquo;re not your typical content creator and that we&rsquo;re worth working with.
So on our channel, we do around 1-2 videos per week, because each one takes 10+ hours to carefully research, script, and produce. If you watch some of our videos, I hope you&rsquo;ll notice how much care we put into them. Also, if you look at SocialBlade, you&rsquo;ll see that we&rsquo;ve still been growing during the bear market (albeit slowly), whereas other larger channels have stopped growing altogether. Furthermore, if you look at our views to sub ratio, you&rsquo;ll see that we&rsquo;re among the best in the crypto niche for channels above 100k subscribers. Anyways, I don&rsquo;t want to &ldquo;toot my own horn&rdquo; too much, I just want to share with you these stats that hopefully point to how high quality our content is.
But also, you might be thinking: &ldquo;Shouldn&rsquo;t you be covering Polkadot organically instead of getting funding for it?&rdquo; Well I have covered Polkadot in the past and plan on covering it in my upcoming series as well. But, the videos I&rsquo;m proposing are a bit more niche and don&rsquo;t fit into any of my upcoming series, so that&rsquo;s why I was thinking to do these in conjunction with Treasury funding and you guys in the community. And I&rsquo;m pretty confident that these will bring solid exposure to certain parts of Polkadot that will end up benefiting the project and the community.
Now the next question some of y&rsquo;all may be thinking is: &ldquo;Will you be able to make an impact during the bear market?&rdquo; Well I think so, and the reason why is because of the videos I&rsquo;m specifically proposing (see below). They are mostly evergreen videos that would still be relevant months later, so even if they don&rsquo;t go &ldquo;viral&rdquo; per se, they will still get more and more views as time goes on. Also, my existing audience likes Layer 1 blockchains, but I haven't really covered Layer 0s in-depth, so I think I can get some of them to start following Polkadot as well.
So yea, this is my first proposal and I just wanted to do a smaller campaign to see if yall like the idea, and if I&rsquo;m able to do a great job, hopefully we can work together again in the future.
Description:
This proposal asks the Polkadot Treasury for funding of a total of 3 high quality educational videos covering the following topics:
<ol>
<li>Why Polkadot Is The Most Decentralized Project Out There (OpenGov) </li>
<li>Top 5 Polkadot Ecosystem Projects You Must Know! </li>
<li>Why 2024 Will Be A Gamechanger for Polkadot $DOT!</li>
</ol>
The total requested amount for the production of these videos is 5000 DOT (Around $20k).
At the end of each video, I will refer people to the official Polkadot Discord channel and include the link in the description as well. And once the 3 videos are delivered, I'll post a comment in the Polkassembly article.
If you have any questions, drop a comment below and I look forward to your feedback!
Best,
Kevin

Deciding

Coinsider Media Campaign for Polkadot

Hello,
I'm Patrice, a French Polkadot ambassador and content creator. I manage the French blog Tendances Crypto. I am planning to submit a proposal to create a Polkadot content hub for the French community. Before submitting my proposal as a referendum, I would like to engage in discussions with the Polkadot community. You can find my complete proposal here, and I can provide additional details if needed.
&mdash;---------------------------
Proposer: Patrice - Tendances Crypto
Address: 152wswWPnwr1uLxqyENaesqjFtJcMwLT3dmrpb7KNt1PZ1PX
Contact: <a href="mailto:tendancescrypto@gmail.com">tendancescrypto@gmail.com</a>
Duration: 44 weeks
Amount: 5,233 DOT
Team: Tendances Crypto
About me:
Hello, I&rsquo;m Patrice, a French Polkadot Ambassador. I create content about Polkadot since two years on my website &ldquo;Tendances Crypto&rdquo;, on Twitter and with &ldquo;Polkadot Francophonie&rdquo; community on Twitch. I believe that we must all work together to create a decentralized web to protect our data and identities, and for me, Polkadot is the only way to build a decentralized space for everyone and every project.
Description:
France is showing increasing interest in the web3, and major French brands are developing strategies to integrate this new sector (Carrefour, Axa, Adidas, PMU, etc.). However, they have limited knowledge of Polkadot at the moment. There are two main reasons for this: there is very little regular content about Polkadot in the French media, and there is also a lack of support for companies looking to enter the Polkadot ecosystem.
To address this issue, it is necessary to create a true hub of French content to promote Polkadot and engage in a B2B approach to attract projects that can utilize Polkadot's technology. This approach will have five aspects:
<ol>
<li>A weekly newsletter on governance.</li>
<li>A monthly newsletter on ecosystem news.</li>
<li>A weekly thematic article.</li>
<li>A chatbot that will use information from the articles and official Polkadot documentation, as well as parachains, to answer readers' questions.</li>
<li>LinkedIn posts to build a B2B audience.</li>
</ol>
The goal of this content is to grow the Polkadot community in France, increase the readership of Polkadot-related articles, and expand the number of French companies willing to adopt Polkadot's solutions. This proposal will fund this content hub for ten months (44 weeks).
You can find the full proposal <a title="Proposal Tendances Crypto" href="https://docs.google.com/document/d/16VF8amEqKPz62f7fRRCMs2SsvUe0PD1QZxLMvfjFpMo/edit?usp=sharing" target="_blank" rel="noopener">here</a>.
Patrice

A French content hub for Polkadot Ecosystem

For the last three years, Polkascan Foundation has been maintaining the Polkadot related Python libraries, such as [py-substrate-interface](https://github.com/polkascan/py-substrate-interface), [py-scale-codec](https://github.com/polkascan/py-scale-codec) and [several Python bindings](https://github.com/orgs/polkascan/repositories?q=&type=all&language=rust&sort=) for cryptographic RUST crates used by Substrate. With these libraries, Python developers can easily interact with any Polkadot, Kusama or other Substrate based chain.

As of writing [265 Github repositories and 21 Python packages](https://github.com/polkascan/py-substrate-interface/network/dependents?package_id=UGFja2FnZS04OTc2NTczNTM%3D) are depending on our libraries.

With this treasury proposal, we are asking retroactive funding for our activities in the period April until September 2023.  


## Overview of activities
* Implemented new [Polkascan Explorer](https://github.com/polkascan/py-substrate-interface-extension-polkascan) and [Subsquid](https://github.com/polkascan/py-substrate-interface-extension-subsquid) extensions to the py-substrate-interface [extension framework](https://polkascan.github.io/py-substrate-interface/extensions/). These utilize indexes from Polkascan Explorer and Subsquid API endpoints, so data can be queried and filtered that is not directly possible or very inefficient on the Substrate RPC.
* New [runtime interface](https://github.com/polkascan/py-substrate-interface/tree/az-runtime-interface): more intuitive approach to interface with the runtime functionality, this is planned to be available in the next major release.  
* Added [support for ink! v4](https://github.com/polkascan/py-substrate-interface/pull/347)
* Added [SCALE type definitions](https://github.com/polkascan/py-scale-codec/pull/112) for upcoming `MetadataV15` in Substrate. (Full support is still WIP)
* Added [multiple params as key support](https://github.com/polkascan/py-substrate-interface/pull/351) for `query_map()`
* Add support for runtime calls at other blocks than the most recent [#346](https://github.com/polkascan/py-substrate-interface/pull/346)
* Upgrade contract interface to support `WeightV2` [#337](https://github.com/polkascan/py-substrate-interface/pull/337)
* Updated [metadata docs](https://polkascan.github.io/py-substrate-metadata-docs/) for Polkadot & Kusama parachain and stand-alone runtimes
* Technical support on [Github](https://github.com/polkascan/py-substrate-interface/discussions) and in [#polkascan:matrix.org](https://matrix.to/#/#polkascan:matrix.org) and [substrate.stackexchange.com](https://substrate.stackexchange.com/questions/tagged/python) channels

For more details about deliverables see https://github.com/polkascan/py-substrate-interface/releases and https://github.com/polkascan/py-scale-codec/releases


## Activity report

Details about time spent and cost breakdown can be found in the [Q2 & Q3 activity report](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-2023Q2-Q3.md).

## Previous activity reports

* [October 2020](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202010.md)
* [November 2020](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202011.md)
* [December 2020](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202012.md)
* [January 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202101.md)
* [February 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202102.md)
* [March 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202103.md)
* [April 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202104.md)
* [May 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202105.md)
* [June 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202106.md)
* [July 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202107.md)
* [August 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202108.md)
* [September 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202109.md)
* [Quarter 4 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-2021Q4.md)
* [Quarter 1 2022](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-2022Q1.md)
* [Quarter 2 2022](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-2022Q2.md)
* [Quarter 3 2022](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-2022Q3.md)
* [Quarter 4 2022](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-2022Q4.md)
* [Quarter 1 2023](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-2023Q1.md)

Maintenance & Support Python Libraries (April to September 2023)

Dear Polkadot community,
Thank you all for your support and votes on the approved <a href="151">Referenda 151</a>. I want to address an oversight regarding the multiple batch calls assigned to the "big_tipper" track, where I assumed individual limits were checked relative to the track limits. However, the total spending of the call is checked relative to the track limits. As the result, the referenda failed to execute.
Due to my oversight, the previous Referenda was submitted under the "Big tipper" track instead of "small_spender." To rectify this, I am resubmitting the proposal to the correct track. I apologize for any inconvenience this may have caused.
--------------------------------------------------------------------------
Dear Polkadot community,
Collators on System Parachains are provided with minimal rewards for block production and small incentives in terms of transaction fees. This reduces incentives for Collators to act in a favorable manner and they may also be inclined to under-resourcing their hosts to save costs. Collators should receive funding for the provision of their services. Ultimately, this should be provided by the chain in a preferably sustainable manner. Implementation of such a system is a long-term solution. In the medium term, funding for collators can be provided by the respective Treasuries in the form of a bounty. This allows funding to be pre-allocated and independently managed.
Based on <a href="https://kusama.polkassembly.io/bounty/20">Kusama System Parachains Collator Bounty</a>, and <a href="https://github.com/polkadot-fellows/RFCs/blob/7eb2193a1a82818c83be4501c4b2a1e6d343dedb/text/0007-system-collator-selection.md">RFC-0007: System Collator Selection</a>, this proposal is a short-term solution aiming to post-pay monthly operating costs of service providers until a more suitable solution (Bounty) is established.
<a href="https://docs.google.com/document/d/1KjThkBTp3nJBF4CAV-Jn8fA0PUrd2Lbhy7DOrVHISX0/edit?usp=sharing">Full Proposal</a>
The proposal aims to secure 6,075.79 DOT for Collators on the Polkadot System Parachains network for services delivered for the period of 2 months - 08-09/2023.
<img src="https://i.ibb.co/SxYzWvZ/Screenshot-2023-09-11-at-10-25-19.png" alt="" width="400" height="262" /><img src="https://i.ibb.co/t2pJHWM/Screenshot-2023-09-15-at-12-53-37.png" alt="" width="400" height="259" /><img src="https://i.ibb.co/NN0c7zG/Screenshot-2023-09-15-at-12-52-13.png" alt="" width="640" height="480" />
This discussion will be open for a period of one week before submitting the proposal onchain. We encourage the Polkadot community to review this proposal and provide any feedback or suggestions.
Thank you!
*Update 11/09: Parity Collators excluded from the funding proposal. Updated the document with new verified identities.

Polkadot System Parachain Collators - Tips - Referenda #151 failed to execute

This is a new attempt to get funding for maintenance of the [substrate-api-client](https://github.com/scs/substrate-api-client). Note: we switched from Kusama to the Polkadot treasury, as this was proposed at our [failed Kusama proposal](https://kusama.polkassembly.io/post/2591#jYN6rM2z3pm0CE8MAPTX). Also, this is a significantly smaller proposal, which only funds the bare minimum of maintenance (updates, user support and small improvements). In case this proposal fails, we will cease all of our support activities.


The [substrate-api-client](https://github.com/scs/substrate-api-client) is a Rust library for connecting to a substrate-based node via RPC from a no-std environment, like trusted execution environments or IoT devices. An RPC client is a library, with similar features as [Polkadot-js](https://wiki.polkadot.network/docs/polkadotjs). With an RPC client developers can easily interact with any Polkadot or Kusama chain. There are [RPC clients](https://wiki.polkadot.network/docs/build-tools-index#rpc-and-api-tools) for different programming languages. For Rust, the most popular RPC client is [subxt](https://github.com/paritytech/subxt). The substrate-api-client uses core functionality of subxt and makes it available in a no-std environment.


This proposal is a continuation of our previous maintenance proposals: [Nov22-Jan23](https://kusama.polkassembly.io/referenda/26), [Feb23-Apr23](https://kusama.polkassembly.io/referenda/88), [May23-Jul23](https://kusama.polkassembly.io/referenda/182). See also our reports in the comments section of each proposal. We aim to seek ongoing funding.

Details can be found in our [full proposal](https://docs.google.com/document/d/1J-QMLZraKfYSxN00DPhI2QwuVSotuX48WnIk4Ak-fDA/edit?usp=sharing)


Executed

Maintenance for the substrate-api-client Sep-23 to Dec-23

After succesfully acomplished the delivery of [Kusama papercraft](https://kusama.polkassembly.io/treasury/283) project [report available [here](https://docs.google.com/document/d/1137x9LJZNcG3sNrqlHDHtgzxD7hNnImv4dy53OTIsRk/edit)] we are focusing on creating premium personalized notebooks for Polkadot and Kusama users. Our proposal aims to address two key issues: the lack of premium merchandise options related to blockchain technology, and the scarcity of personalized notebooks for storing seed phrases associated with these networks.

Through our project, we strive to deliver a unique and desirable notebook experience for Polkadot and Kusama users. We will produce 200 pocket notebooks. Each notebook will contain personalized stone paper refills, premium leather covers, Dotsama recycled guides, and recycled refills for extended use. Everything with aesthetically pleasing results. 

Over the course of the four-month project, we will dedicate our efforts to creating an exceptional product that exceeds expectations. We have carefully considered the financial aspect and we have determined that a minimum wage salary, approximately 975 € per month, will be enough for the design and production of the product. We will detail the other expenses carefully.

Additionally, we would like to highlight that we have already started working with samples, and the initial results have been phenomenal. We have also reached out to Japanese sustainable PU fabric manufacturers and explored alternative leather substitutes such as those derived from mushrooms (Mylo) and cactus (Desserto) but we think that classic leather will give us the best performance.

Every aspect of this project, from the design to the production, will be personally handled by us. We firmly believe that the aesthetic appeal, combined with the materials we are utilizing, will create a product that is simply irresistible.

Full proposal and details [here](https://docs.google.com/document/d/1K153Ao4eut0LuQDWtNhDIXOWjgLqEpkvUfi72c3JpRY/edit?usp=sharing)

Rejected

Polkadot journal: A Marketing Proposal for Polkadot/Kusama

Treasury Proposal: Artificial Intelligence for security monitoring on a network level 
Proponent: [Women in Blockchain Canada]
Date: [28.07.2023]
Requested DOT: [Approximate amount 35,000 USD - 6,686 - on August 1 ]
Short description: [Artificial Intelligence for security on a network level ]
Project Category/Type: Software Development - Security
Previous treasury proposals: Education https://polkadot.polkassembly.io/motion/206

Context of the proposal 
Our goal is to first build a proof-of-concept machine learning tool that conducts research and analysis on the network level which is able to find anomalies and enable early warning systems for security issues that start occurring. We would utilize adaptive A.I. and unsupervised machine learning algorithms to gather and process the incoming data in real time. Our system would ascertain baseline behavior and then auto-detect any changes that deviate from it in order to assess whether a warning signal is warranted. Once the system would identify real issues, we would create an early warning system that would flag the issues as they start occurring to those in the Polkadot network. This following document contains the background, rationale and development steps elaborating on reaching we will conduct in order to develop the PoC machine learning tool.

Project Team
We have a distributed team of frontend and backend developers along with a project manager. Our lead developer handles the primary workload as well as one full time developer working under him. The team has a combined 60+ years of experience with web and application integration. Our team is currently working on a web3 enabled website that uses the learn and earn model for the Stellar Foundation (Learnweb3.network). 
Please note that Danny Kovach has developed his own artificial intelligence as well as has over a decade of experience working in the field for both NASA and Citi bank. Please checkout https://github.com/quant-guy and https://github.com/0x0000d3ad for his work.
This is Daniel Kovach’s academic work.
https://www.researchgate.net/profile/Daniel-Kovach

For full proposal see: https://docs.google.com/document/d/1GBc8xCEFfxA_hGNCsmznwjgZ3YWtA4wislE6VlNIUJA/edit#heading=h.v6is2ta0txr1

=Artificial Intelligence for security monitoring on a network level 

DAO_Terminal: Enhancing User Involvement in Polkadot Governance.

AI-generated, unbiased, easy-to-digest event summaries from Polkadot governance across channels like Twitter, Telegram, and Email.



**Prototype**
Already ready to subscribe [https://twitter.com/PolkaTerminal](https://twitter.com/PolkaTerminal)

[Full proposal](https://docs.google.com/document/d/1c06QW39w064QLSd2HajX3-Zt_2JnI6flE7GCSlSIG1w/edit?usp=sharing)

Get presentation [here](https://drive.google.com/file/d/1vqDpMA8jGIR-Vecu0mj41yQv8MuiNaE4/view?usp=drive_link)! 


**Challenge**

![](https://web3files.live/ipfs/QmeJWgvFtsgctnhxKmSsHPXY4BguhHdHSJZTpRpYaHPDBn/Slide3.jpeg)
![](https://web3files.live/ipfs/QmeJWgvFtsgctnhxKmSsHPXY4BguhHdHSJZTpRpYaHPDBn/Slide4.jpeg)

**Overview**
DAO_Terminal is designed to streamline user engagement in Polkadot governance by delivering key event digests across user-preferred channels. This innovative solution significantly lowers the barriers of entry and encourages active participation in Polkadot governance.

![](https://web3files.live/ipfs/QmeJWgvFtsgctnhxKmSsHPXY4BguhHdHSJZTpRpYaHPDBn/Slide2.jpeg)
![](https://web3files.live/ipfs/QmeJWgvFtsgctnhxKmSsHPXY4BguhHdHSJZTpRpYaHPDBn/Slide5.jpeg)
![](https://web3files.live/ipfs/QmeJWgvFtsgctnhxKmSsHPXY4BguhHdHSJZTpRpYaHPDBn/Slide6.jpeg)

**User Benefits and Project Impact**
DAO_Terminal offers numerous benefits:

1. New users can quickly engage in voting processes.
2. Reduced churn rate for existing active users.
3. Allows experts or interested parties to monitor relevant topics.
4. Projects can efficiently find support through topic selection.
5. Rapid community response to potential abuse due to increased reach.

As a result, DAO_Terminal enhances audience engagement, expedites new member onboarding, encourages community involvement, reduces fraud and collusion through a wider reach, and minimizes audience dropouts from active participation.

Problem & Solution
The challenges of navigating separate Polkadot forum sites, sifting through numerous threads, and assessing feedback across multiple channels can discourage users from actively participating in governance. DAO_Terminal solves this by providing succinct, unbiased, AI-generated digests on governance events through Twitter, Telegram, and Email.

**Prototype**
Already ready to subscribe [https://twitter.com/PolkaTerminal](https://twitter.com/PolkaTerminal)

**Open Source Commitment**
Upon completion of the final stage, all codes and materials will be published as open source, enabling independent operation and future enhancements by the community.

**Benefits for DOT Holders**
 DOT Holders stand to gain immensely from DAO_Terminal:

1. Improved information accessibility.
2. Enhanced engagement and influence on governance.
3. Simplified governance tracking.
4. Real-world system improvements due to active participation.


[Full proposal](https://docs.google.com/document/d/1c06QW39w064QLSd2HajX3-Zt_2JnI6flE7GCSlSIG1w/edit?usp=sharing)

Supporting DAO_Terminal is voting for a more effective, more inclusive Polkadot governance. This not only benefits every DOT holder but also strengthens the entire Polkadot ecosystem. Let's make Polkadot governance accessible, engaging, and user-friendly with DAO_Terminal. Support DAO_Terminal today!

[Subscribe to the PolkaTerminal!](https://twitter.com/PolkaTerminal)


DAO_Terminal: Enhancing User Involvement in Polkadot Governance

**Introduction**

Polkadot hubs are community-operated spaces, where people who share their interest in the ecosystem meet and work together, learn from each other and organize events. Our research in Q1 2023 proves the interest of 10+ locations all over the world, that are interested in running permanent spaces of this kind (**similar to hackerspaces**).

We are proposing the next steps for this project and based on the **already established physical hub** in Indonesia's Denpasar region. We aim to share our knowledge on how we kickstarted the community, initiate the hub and convinced the local government to choose Substrate as their blockchain technology. Even local universities want to introduce Substrate in their curriculum from next year. **All content is to be dedicated to Polkadot.**

We hope you will appreciate our half year efforts, starting the community and the first physical hub in APAC region. **Our goal is to create a know-how on how to start and run such a hub.**

**Budget**

Based on community feedback, we have updated our budget details and extended the period until the end of the year.
**We support the becoming of all new hubs until the end of the year and our hourly rate is under $21**

**Achievements so far:**

- Head Ambassador Six and Ambassador Gabo secured the location in Denpasar, DNA Creative building, until the end of the year, with zero cost rent and utility for Polkadot.
- Establishment of the hub in Denpasar, called "Polkadot Sanctuary"
- Denpasar initial research is done and community growth is kickstarted. We have 130+ members already in the community.
- Convinced Denpasar government to choose Substrate as their blockchain technology.
- Got request from the collective of 14 universities in Denpasar, to provide blockchain education material, focusing on Polkadot and Substrate.

We already discussed this topic during the last 6 months in many events and started the public Polkassembly discussion as well: [Polkadot Hubs - Initiative case-study](https://polkadot.polkassembly.io/post/1774)

**Intro video**

We created a video about the story:
[https://www.youtube.com/watch?v=LTjL1weAShs](https://www.youtube.com/watch?v=LTjL1weAShs)

**Teams and locations that filled our research form, interested in becoming physical Polkadot hubs:**

- SubWork in Bled, by KodaDOT
- Vietnam, by Polkadot Ambassadors
- Ljubljana, by Apillon
- Budapest, by Mosaic/DLabs
- Berlin, by Parity Technologies
- Dubai, by CCTF

Notably, the Spanish "Polkadot Hub" already exists in a hybrid form.

**Details**

Proponent: 123LuJKS65HaBbLSdDS46ByeC7bvQwA1iUhTpmjigQAfUKpK

Requested DOT allocation: 7915 DOT

Proposal updated on: 27.06.2023

For details (the plan, milestones, deliveries, marketing, success metrics, research data, etc.), please refer to the detailed proposal document:
[https://docs.google.com/document/d/1NjOVn_id2Wy9BcSMBlieKZMVKukRQS_Tmi1SKMJwDSc/edit?usp=sharing](https://docs.google.com/document/d/1NjOVn_id2Wy9BcSMBlieKZMVKukRQS_Tmi1SKMJwDSc/edit?usp=sharing)

Polkadot Hubs - Initiative case-study, education and support for future hubs (12 months period)

## Tldr;

-   OnFinality has a proven track record providing RPC API support for 68 substrate networks
-   To help cash-starved parachains through the winter, we propose funded complete support for the entire Polkadot ecosystem - this will cover the existing 38 Polkadot parachains
-   Each parachain network will be allocated US$620 of base funding each month for this service which will be held by OnFinality to explicitly provide the service. In our experience, this is the average funding that we require to provision, run, maintain, and monitor a basic service for each small network. Unused prorated amounts will be refunded at the end.
-   Historic data has shown us that this should be sufficient to serve up to 5 million daily API responses with careful rate limiting and DDOS protection. 
-   For the few larger networks that exceed these requirements (e.g. Polkadot's RPC endpoint), those sovereign parachains will be responsible for all costs above the base $620 funding.
-   We will also start working with other ecosystem infrastructure providers to work on a more sustainable long term solution

## Background and Problem Statement

As Polkadot’s largest and most cost efficient infrastructure provider, since November 2020 we've provided access to dedicated node support and free public API service for over 68 networks in the Polkadot / Kusama ecosystems. **We’ve always made it our goal to provide complete support for the entire Polkadot  ecosystem.** For RPC API services, historically we have sought funding from the sovereign parachain teams themselves for funding the ongoing operating expenses of these services. However, as the crypto winter has hit hard, many teams are no longer able to fund core public good services like public RPC endpoints.

This has a detrimental effect on applications that serve the Polkadot ecosystem (many of which are our customers). Wallets (e.g. Talisman and Nova), explorers (e.g. Subscan and Polkaholic), account tools (e.g. Sub.ID), indexers (e.g. Subsquid and SubQuery), governance applications (e.g. Polkassembly and Subsquare), and thousands of other applications in each ecosystem struggle to find reliable, performant, and SLA supported RPC API endpoints for many smaller networks.

> “If we had some public good service that helps grass root teams it would be a tremendous help for teams such as ours” - Imbue

This is causing a divide in our ecosystem between highly funded parachains that can survive the winter, and new emergent chains that are struggling to get started - we’re seeing first hand that the number of growing new parachains in Polkadot is stalling.

## Proposed Solution

**We’re requesting globally accessible and equitable funding from the treasury to cover a basic RPC API service (full archive and trace node support included) for all active Polkadot and Kusama parachains to provide immediate relief until we can set up a *Parachain Infrastructure Bounty*.**

This proposal will cover US$620 of base funding each month for each parachain’s API service. To start with, we budget that there will be 38 parachains that take us up on this offer (all parachains with an active lease will be eligible). The total combined running cost for each month is estimated at USD $23,560.00 - all inclusive of capital and operating expenses, administration time from OnFinality DevOps, onboarding costs, backup costs, and all other monitoring and right-sizing by our team.

**The initial proposal is for July's cost only**

## Longer term solution

> “Teams need to coordinate/negotiate with all sorts of partners (block explorers, rpc node providers, wallets, other parachains). This slows down innovation for Kusama.” - Interlay

Multiple parachains have privately and publicly affirmed that one of the biggest challenges is dealing with all the tertiary providers needed to run a production parachain (RPC nodes, block explorers, indexers, governance pages, wallets integrations and more).

We propose that in the long term, we create a new “Parachain Infrastructure Bounty”, that provides basic public services for all active parachins for both ecosystems. The aim is to make the ecosystem more harmonious, unify processes and tools, speed up development progress, and will help all new teams get started.

But setting this bounty up and communicating with the large number of stakeholders will take a long time. At this stage, we expect at least 5 RPC providers, 4 wallets, 3 block explorers, 2 indexers, and 2 governance tools will want to be party to this bounty if it encompasses all “public good infrastructure”.

As a result, in order to establish precedent, and to provide quick pain relief to all parachains next week, our view is to proceed with the current immediate solution now. 

---

[Please read the full proposal here including a collection of feedback and discussion from community members here](https://docs.google.com/document/d/1_Sr8v7x81LvnZ62sW7zT3sWxEFTdfcQwfrElRbIGG0Q/edit?usp=sharing)

Funded High Performance Public Infrastructure for the entire Polkadot Ecosystem (OnFinality)

**Summary**

This proposal was submitted on-chain on 15th March 2023. [Motion](https://polkadot.polkassembly.io/motion/374) had all 7 positive votes from the council but was short of one active vote. Motion was further delayed due to the transition from Governance 1 to OpenGov. This is a claim on an expense that was made in Q4 of 2022 and will be the final one. 

Please note that we were advised to include the deposit made on the initial proposal (192.645 DOT) which will be slashed once this is approved.

Thank you for your support.  


Proponent: Pinknode
Date: 26/06/2023

Amount in USD: $20,093.46 

Proposal Amount in DOT:  4,053.55 DOT 

Deposit in Gov 1 Proposal: 192.645 DOT

**Total Claim in DOT: 4,246.19 DOT**

DOT Rate: $4.957 ([using EMA7 as of 26/06/2023](https://polkadot.subscan.io/tools/charts?type=price))

DOT Account: 13EAhGcpe93mqSFZQrQ4P2cfpdAo5txWc5UQVTfEKDoqZjhw

**Proposal Summary: Costs for running secure, reliable, and scalable public infrastructure for Polkadot, Statemint, and Westend**

**Project Summary**

Pinknode is a node-as-a-service platform focused on providing shared API endpoint and node operation services catering exclusively to the Polkadot ecosystem. We launched our MVP in June 2021 and have been providing free RPC services to the Polkadot ecosystem’s participants since Q3 2021. Our mission is to aid the Polkadot protocol in achieving its vision of a multi-chain future by providing easy-to-use, reliable, and scalable infrastructure services which remove an entire layer of complexities for developers to start building on Polkadot/Substrate.

Ecosystem participants can access our free API service by creating their own API Key on Pinknode Portal or using our public endpoints (listed at https://polkadot.js.org/apps). In a bid to reduce barriers to entry and attract more developers to the ecosystem, our premium plan, which includes archival data and higher rate limits, is also free for all builders and participants of Polkadot to utilize. We are not charging our users anything at this moment.

https://public-rpc.pinknode.io/polkadot
wss://public-rpc.pinknode.io/polkadot
https://public-rpc.pinknode.io/statemint
wss://public-rpc.pinknode.io/statemint
https://public-rpc.pinknode.io/westend
wss://public-rpc.pinknode.io/westend

**Service Details**

From 1 October 2022 to 31 December 2022,

Pinknode’s Polkadot RPC nodes have served an average of 7,259,280 requests per day, for a cumulative total of 675,113,094 requests for the quarter.

Pinknode’s Statemint RPC nodes have served an average of 213,150 requests per day, for a cumulative total of 19,609,835 requests for the quarter.

Pinknode’s Westend RPC nodes have served an average of 229,823 requests per day, for a cumulative total of 21,373,571 requests for the quarter.

Enhancements during Q4 2022:

-Added “Team API calls used’ on main dashboard for effective summary

-Moved request log storage to AWS S3 for faster UX

-Added toggle switch for live request viewer, to be initiated by users as opposed to default

-Upgrades to our proxy for more accurate logging

Pinknode achieved service reliability of 99.88% for Q4 2022 with one major downtime incident on 21 November 2022.

Our status page is publicly maintained.

Our full report including raw data and graphs can be viewed [here](https://docs.google.com/document/d/18m7e6IhuKjS8eGG7QYJSGBTjEx-vxgTuCYz_p5xi7VA/edit?usp=sharing).

Pinknode Public Endpoint for Polkadot in Q4 2022

Stakeworld offers a high availability infrastructure for [RPC nodes](https://stakeworld.io/docs/rpc) and [bootnodes](https://stakeworld.io/docs/bootnode). We also try to share our experiences as much as possible on the [polkadot wiki](https://wiki.polkadot.network/docs/maintain-rpc).


This is a request for funding of:

* Setting up and maintaining high availability RPC services for polkadot and polkadot commons (AssetHub, BridgeHub and Collectives).
* Setting up and maintaining a bootnode for polkadot.

The full proposal can be found [here](https://github.com/stakeworld/stakeworld-treasury/blob/master/2023-Q2-polkadot.md).

[Small Spender] Stakeworld's polkadot RPC and bootnode infrastructure - Q2 2023

This treasury proposal aims to retro-actively cover the first 28 person days of completed work on implementing privacy sidechains for any substrate based chain. This benefits Polkadot and Kusama relaychains but also all their parachains and even solochains - without the need to change a single thing in their runtimes!

[Detailed Proposal](https://docs.google.com/document/d/1ID9ZqTU-ukY1P2lDZi6P5wKwTMAC1X-hsk-67k07p_0/edit?usp=sharing) asking for **39’961 USD**

[Previous Discussion Thread](https://polkadot.polkassembly.io/post/1739)

[Blog post about why privacy matters and our longer term vision](https://medium.com/integritee/a-privacy-sidechain-for-all-polkadot-kusama-chains-1bb52dc9b0d7)

[brenzi's presentation at Polkadot Now India 2023 [video, 12min]](https://youtu.be/7he0Uqe9jps) brenzi will present this tech at decoded '23 as well

## Why should the treasury fund this?

Our offering is non-excludable, meaning we can’t limit this offering only to paying customers. So there is a free-rider issue at play: Once we release our privacy-sidechain solution, everyone can use the code to run their own sidechains, even multiple sidechains for a single parachain are possible and user fees are paid in the parachains’ native token, not TEER. Integritee invests in this important use case but will be met by competitors who just fork the code as soon as the business case works out. This is a very good thing for decentralization - but must be financed.

So, the question is not a generic “*shall parachain teams get funding from the Treasury to build what they would build with VC funds anyway?*”. What we offer is not a product on our parachain itself which we charge TEER for (see fee details in proposal document): We offer an L2 solution for anyone to deploy - anywhere. The question we’re asking with this proposal is, therefore: “**Do you want this privacy product to be available by the end of the year for Polkadot, Kusama and their parachains, or not?**”

Privacy Sidechains for all Substrate- Based Chains

[NAY THIS PROPOSAL, IT WILL BE SENT AGAIN WITH THE CORRECT FUNCTION, MORE DETAILS AND A NEW PLAN]


This proposal was previously discussed here: https://polkadot.polkassembly.io/post/1771#dxlnMcBvztbe1FN9Dc7m

The TLDR version:
English: https://ibb.co/L5bkgDK
Portuguese: https://ibb.co/jZ0qJsL

Hey everyone! After a few months taking feedback from all kinds of people on the discussion period, we came up with a new proposal!

We decided to focus all of our efforts into the onboarding experience for new users. With your support, we aim to drive on-chain demand from Brazil by:

Gamified User Onboarding: We will develop a tailored user journey in Portuguese, featuring interactive content and rewarding users with gamification elements, and PFPs NFTs, to encourage their active participation.

Connected Content Creation: We will create engaging content in Portuguese across various platforms, including social media, to raise awareness, educate, and connect with the community. All the content will be created with the help of Wagmedia this time!

Integrated Social Media: We will leverage social media platforms, such as Twitter, Discord, Telegram, Youtube, Instagram, and LinkedIn, to keep the community informed, engaged, and coordinated with regular updates, announcements, and campaigns.

Website Development: Our website will serve as a central hub for Polkadot Brasil's mission, providing information, resources, and coordination of community activities, while contributing to SEO efforts to promote "Polkadot Brasil" and the Polkadot brand.

Read the full proposal in english here:
https://docs.google.com/document/d/16LQXHb97d4yV2YZhCv3GqcseaSCC0hFaQEblwZd3Lco/
Leia a proposta completa em português aqui:
https://docs.google.com/document/d/1BmaoMM1KjRD_6fk2HjJauuB61UxW0S6LZcGDn5aQ794/

Restructuring of Polkadot Brasil

Dear Polkadot Community,

**[Polkashots.io](https://polkashots.io)** was the first snapshot service for validators and node operators available since Early 2021. During its time, it provided a valuable service to validators and Parity engineers alike, that ensured reliability of our network.

There is a new mechanism, [Warp Sync](https://spec.polkadot.network/chap-sync#sect-sync-warp), that makes this service redundant, therefore we stopped making new snapshots in April 2023. We are seeking the reimbursment of Google Cloud expenses for the Jan-Apr period as well as the deposit for the [Gov1 Proposal](https://polkadot.polkassembly.io/treasury/274) replaced by this. The total is **3,936.69 DOT**.

All details can be found in the proposal page:

https://hackmd.io/[@nicolasochem](https://polkadot.polkassembly.io/user/nicolasochem)/B19RK5lmh

Thank you very much for your consideration

Polkashots.io Cloud Costs January-April 2023

Dear community,

This OpenGov referendum seeks to re-submit the specifics of [motion 339](https://polkadot.subsquare.io/council/motion/339) which was rejected due to technical reasons, treasury.Spend would not work under the council approval.

In summary, the motion sought to reward 'high quality' nomination pools using a deterministic evaluation system.

The details are below:

An [incentive programme](https://polkadot.polkassembly.io/post/1352) was initiated to reward high quality nomination pools. The exercise was completed and reviews all pools prior to the expansion of the pool base which occurred shortly after block 13686541.

The programme seeks to reward pools which have met the following criteria:

- Has metadata
- Pool creator has verified identity
- Has nominees
- Is Open
- Has more than 10 members

The analysis is supported by an open source tool developed by Polkagate which allows for a more objective analysis. The results of the analysis was posted (see last post) for public scrutiny for which none was received. With this said, we would like to proceed with rewarding 22 pools with 250 DOT as well as issuing a payout to PolkaGate of 250 DOT as well for developing the tool. Please note that rewards would be shared among all pool members and isn't submitted to the pool creator.

Call data for this motion: [HERE](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.polkadot.io#/extrinsics/decode/0x1a005c13030b00a89c134602006d6f646c70792f6e6f706c73010100000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73010200000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73010400000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73010500000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73010600000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73010700000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73010800000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73010a00000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73010b00000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73010d00000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73010f00000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73011300000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73011400000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73011500000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73011c00000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73012700000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73012b00000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73012c00000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73013600000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73013d00000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73013f00000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73014000000000000000000000000000000000000013030b00a89c1346020004f3da939fa351c562c7e06e1e3716976b5e14230e83a45995cbad9086f49e17).




Nomination Pool Incentives - Fixing an issue with Motion 339

**Dear Polkadot community,**

On behalf of our team , we propose the maintenance bounty of a **common good** tool enhancing experience on the Polkadot ecosystem - ParaSpell XCM SDK & XCM UI. These funds will fund team that have been previously funded by **Kusama treasury** ([link](https://kusama.subsquare.io/referenda/referendum/123)) the **Basilisk Parachain team** ([link1](https://basilisk.subsquare.io/treasury/proposal/2), [link2](https://basilisk.subsquare.io/treasury/proposal/4)) and the **Web3 Foundation** ([phase1](https://github.com/w3f/Grants-Program/pull/1118),[phase2](https://github.com/w3f/Grants-Program/pull/1245),[phase3](https://github.com/w3f/Grants-Program/pull/1589)) which also proposed the idea of Treasury maintenance funding for this project here: [link](https://github.com/w3f/Grants-Program/pull/1541#issuecomment-1441342524) 

More information on previous project funding and achievements can be found in our official docs: [link](https://paraspell.github.io/docs/#project-achievements-so-far)

 **We created XCM SDK that connects all 46 currently compatible Parachains together into a tiny package that is very simple to implement and saves a ton of time for developers looking to integrate XCM support into their dApp.** As new Parachains keep integrating XCM support we need to keep XCM SDK maintained to satisfy the growing needs of developers that are integrating this package into their dApps.


This maintenance proposal is for maintaining repositories and performing continued operations to improve XCM SDK & XCM UI in many useful ways mentioned in our application document below.

We believe that this tool is needed in the Polkadot ecosystem and we are working very hard to prove this. Unification of XCM pallets which are currently very diverse can bring ease of integration and speed up dApp development significantly. This Polkadot forum post goes to show, that developers actively search for such tools. [link](https://forum.polkadot.network/t/grant-ideas-and-wishlists/399)

**Links that might interest you:**

We requested Kusama treasury funding for maintenance already (Although community supported us and we almost won together, we were HACNd all along the way with other cool proposals): [link](https://kusama.polkassembly.io/referenda/209)

We have also stopped by on **AAG** to explain ParaSpell in more detail - [link](https://twitter.com/TheKusamarian/status/1666094384629288961), [link2](https://www.youtube.com/live/cdsPbeFzOQw?feature=share&t=3565
)

XCM SDK - [link](https://github.com/paraspell/xcm-sdk)

An organization with all repositories - [link](https://github.com/paraspell)

Our previous Kusama treasury funding - [link](https://kusama.subsquare.io/referenda/referendum/123)

Delivery of Kusama treasury funded proposal - [link](https://docs.google.com/document/d/1lMY_8EtQ41IX7Zn9VIMAiG1k3oLYN0h_lVj8dWDwZ_k/edit?usp=sharing)

Our current metrics can be seen here - [link](https://user-images.githubusercontent.com/55763425/239685371-84a5214e-ccc6-41c8-b551-7ff655304501.png) , our SDK is also implemented by the biggest Polkadot NFT marketplace called KodaDot.

**Further information** on the maintenance mechanism, management of the funds and budget can be found in the [maintenance proposal document](https://docs.google.com/document/d/1_gxAJM_uUbMSOhqxD291w90wh7p97XK0GRH-Hzqu9cI/edit?usp=sharing).


ParaSpell XCM SDK Maintenance funding for 5months - Polkadot Treasury Proposal

Dear Polkadot community,
With the launch of OpenGov on Polkadot around the corner, we plan to use the knowledge and skills we have gained from Kusama OpenGov to help kick-start Polkadot's OpenGov. Our main goal hasn't changed: we want to make the governance proposals process within the Polkadot community better, more open, and more successful. 
This proposal outlines our plan to bring our successful proposal auditing process, first started on the Kusama Network, to the Polkadot Network. It builds on the work of the OpenCommunity Governance project, which has been running on the Kusama network for the past five months. In this period we delivered 80+ Audit reports on Kusama OpenGov treasury proposals.

**Problem**

With the launch of OpenGon on Kusama, it became apparent that proposals are not very well structured, lack information, and include budgets that seem very hard to defend. Proposals can also be very diverse with a focus on different areas that not everyone can be familiar with. For all these reasons it is significantly time-consuming for voters to truly understand the proposal and cast an educated vote on it. 

A significant challenge in the current proposal evaluation process is the lack of constructive feedback during the discussion phase. To address this, appointed auditors will focus on being more involved in the earlier phases of proposal development. This proactive approach will help proposers receive feedback and address potential weaknesses in their proposals before they are submitted onchain, giving them time to evaluate the feedback and make improvements.

**Milestone 0:  Prepare OpenCommunity Governance documentation**

Milestone 0 focuses on adjusting the governance documents currently used in the Kusama network to align with the needs of the Polkadot ecosystem. This involves adjusting the Proposal and Audit templates, updating necessary documents on treasury sites, wiki, and GitHub, and initiating the audit process to improve the quality and transparency of incoming proposals with the set standards and guidelines.

**Milestone 1: Implement OpenCommunity Governance**

In Milestone 1, the primary objective is to start proposal audits while they are still in the discussion phase and follow up the proposals onchain.

A major challenge in the current proposal evaluation process is the lack of constructive feedback during the discussion phase. To address this, appointed auditors will shift their focus by becoming more involved in the earlier phases of proposal development. This proactive approach will help proposers receive feedback and address potential weaknesses in their proposals before they are submitted onchain, ultimately improving the overall quality of submissions.

**Funding**
This proposal seeks funding of 2179.57 DOT split into 2 payments between auditors CoinStudio and Abdulbee.
**All details can be found in the** [Proposal document](https://github.com/CoinStudioDOT/OpenGov/blob/7a2d85a36661f7fad95eaa5d7a99d18c8376cd7f/Documents/Polkadot%20Referenda%20%231%20-%20OpenCommunity%20Governance%20Proposal.pdf)

All the documents, previous treasury proposals, deliverables and reports, audits are stored on our [GitHub](https://github.com/CoinStudioDOT/OpenGov/tree/main). We are also maintaining track records of auditor work and treasury proposals on the draft version of [Airtable](https://airtable.com/shr18QFRHOkoBgXxz).

We are community oriented initiative and we are open to onboard additional auditors from the community, more details can be found in the following [Kusama proposal.](https://github.com/CoinStudioDOT/OpenGov/blob/41368aa8ba47712ee0b655beffc22c3788f29c4e/Documents/Kusama%20Ref%20%2367%20-%20Governance%202.0%20Referenda%20Audits%20extension.pdf)

[Kusama ongoing project](https://kusama.polkassembly.io/post/2431)

Some examples of audit reports: [Example 1](https://github.com/CoinStudioDOT/OpenGov/blob/41368aa8ba47712ee0b655beffc22c3788f29c4e/Kusama/Discussion/2550/CoinStudio%20-%202023-04-12%20-%20Kusama%20Audits%20-%20%2330%20Nova.pdf), [Example 2](https://github.com/CoinStudioDOT/OpenGov/blob/41368aa8ba47712ee0b655beffc22c3788f29c4e/Kusama/Discussion/2577/CoinStudio%20-%202023-05-22-%20Kusama%20Audits%20-%20%2342%20Paraspell.pdf), [Example 3](https://github.com/CoinStudioDOT/OpenGov/blob/41368aa8ba47712ee0b655beffc22c3788f29c4e/Kusama/OpenGov/179/CoinStudio%20-%20Kusama%20Audits%20-%20%2337%20Sublab.pdf)

I am looking for feedback on this proposal so please feel free to ask questions and leave suggestions to help me further improve the presented project.  Your suggestions will play a key role in enhancing the transparency and efficiency of our governance process.
[Discussion](https://polkadot.polkassembly.io/post/1810)

Thank you!

[32] Origin: SmallSpender