The Spanish language is becoming increasingly relevant within the Polkadot and Kusama ecosystem. The community from both Latin America and Spain has been steadily increasing and this has been reflected in an increase of the incorporation of new ambassadors, candidates and people who promote the development of ideas and initiatives for the ecosystem that is constant and growing.

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

The **scope of work** of this bounty is divided into the following categories:

1.Translation of content into Spanish

1.1 Translation of written content

1.2 Dubbing

1.3 Subtitling

Creation of Spanish language content

Organization of events oriented to the Spanish-speaking community

Again, with this bounty we want **to create a mechanism for the curation of both Spanish content and events** created by the community with a focus on speed, effectiveness and control for content audits.

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

Original discussion post can be found [here](https://kusama.polkassembly.io/post/1895).

Spanish Content and Event Production Bounty

Dear community,

I am proposing the creation of a bounty for funding an incentive for the moderation team.  We have opened disucssions on our [proposal](https://kusama.polkassembly.io/post/1644) for two months and have received no community objection. 

**Summary**
Reddit, Discord, and Element are three Social Media platforms that Polkadot/Kusama ecosystem use to communicate and educate older and newer users alike as well as builders, content creators, and even those who fund projects. Social media can be quite a hectic place to have discussion, with everyone being able to put their opinion out there. 

These avenues also open up new ways to scam users or commit fraud. This is where the moderation team comes in. The moderation team acts as a first line of defense against scams for all the platforms and ensure conversations stay on topic as well as stay respectful and follow the rules. Moderators not only act as a defense against hostile actors, but they act as educators as well. 

For most users on the server, the moderators were the first people in the ecosystem to give guidance on finding out more information regarding Polkadot/Kusama. This bounty aims to reward those moderators and perhaps future moderators for ensuring the safety of the server as well as educating users. It is not meant to act as income, but as a token of appreciation for the hard work that goes into moderating. 

For more information, please refer to the proposal, which can be found [HERE](https://docs.google.com/document/d/17bjVgOOprGsz8DGn6D6_thEQyNZRaMSYZbDpsTOud2w/edit#heading=h.kl7lv0cg56u1)

Moderation team bounty

On behalf of the community, we propose the creation of an **Infrastructure Maintenance Bounty** that will work to aid teams that have been funded by the treasury before for the development of their ideas, to maintain infrastructure and to perform continued operations to reduce the work or resubmitting the treasury proposals and time constraints associated with it, as well as model a way in which the community can achieve more agency and support in directing how on-chain treasury funds are spent. 

Hence, the Maintenance Bounty is meant to be open-ended, with the funds being distributed through child bounties that cover teams continued development of the essential infrastructure. The following proposed child bounties contain mainly the recurring tasks for block explorers, governance forums and applications, snapshots and validators service providers, open-source and community wallet services, and other projects aiming to cover maintenance costs with treasury funds.

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

See the Original discussion post [here](https://kusama.polkassembly.io/post/1545)


Bounty Proposal: Infrastructure Maintenance Proposal 

Chrawnna Corp. is working to solve the ***Dotsama Info Distribution problem*** with **WagMedia**.

See the Original discussion **[Here](https://kusama.polkassembly.io/post/1499)**.

More community feedback can be considered on this **[Tweet](https://twitter.com/GldnCalf/status/1521116803279523843)**.

*tl;dr*

**Problem**:
1. Network growth diminishes stakeholder ability to make informed, productive decisions.
2. Few and privately funded Media outlets distort network narrative.


**Solution**:

Decentralize the Story of Dotsama.


**How**:
- Efficient distribution of Treasury Bounty to Researchers & Content creators via Incentivized Discord.
- Custom bot allows dedicated Content Directors to incentivize with custom "value emojis"
- Participants are paid out weekly to share sourced information or turn it into original content.
- All are welcome. Completely transparent.
- Public Dashboard for all stakeholders to see bounties awarded in real time.
- Multiple project treasuries can incentivize a common pool of research and content talent.

**PoW**:
- Trial phase Jan 10 - April 10
- 11 participating treasuries.
- 495 unique pieces of content
- Several participants have since become full or part-time builders. 🥳
- Much more info in the complete Proposal **[here](https://docs.google.com/document/d/1m9Bo8fH408BV5t2ODvindl4S0W2BfbtDxrwAl9j71k0/edit#)**.

We would love your questions, feedback, and suggestions.

See [WagMedia](https://treasury.bright.dev/bounties/discord.gg/YUXqjVXWtp) for yourself!

Thank you. 🙂

Bounty for Content Development and Incentivization

Dotsama has more rich features compared to 1st generation state transition blockchains like Ethereum and UTXO based chains like Bitcoin, but at the same time it's more complicated for people to understand them. We propose to implement a group of **business oriented** explorers and Dapps to help users better understand and work with dotsama. 

The implementation will be done through bounties and child bounties, and we propose ourself OpenSquare to be the curator. We will split the work into child bounties, build a site for curator and external developers to collaborate on child bounties, and report back the development progress to the council.

So this proposal has following motivations:
1. Implement a group of **business oriented** explorers and dapps.
2. Educate more developers by implementing the explorers and dapps features with child bounties.
3. Seek ways to facilitate collaborations between projects and external developers in the polkadot ecosystem. We will experiment the way `bounty -> curator(OpenSquare) -> child bounties -> developers` in this proposal.

## Problems statement

### Rich features need visualization
No doubt polkadot has more rich features compared to 1st generation state transition blockchains like Ethereum and UTXO based chains like Bitcoin，such as forkless upgrade, on-chain governance mechanism, treasury, para-chains, etc. But to be honest it’s more complex too, which means it will cost more for people to understand them. We need better UIs to demonstrate them. They should show the participating roles, workflows, business life cycles, and to a user, it should tell the steps to complete a business.

### Dapps with more contextual info
[Polkadot/Substrate portal](https://polkadot.js.org/apps) is great, but it has problems too.
1. Most shown data is on-chain, while we have to check the contextual info from a explorer to complete some operations.
2. Too advanced to some non-technical users, while they expect simpler ones.

The proposed business oriented explorers can provide the contextual data, and it will be perfect if we can complete our business just on these business explorer pages.


### More builders, more collaborations
We need more developers, designers, educators and other roles to build web3 based on substrate/kusama/polkadot. The best way to enroll more builders is collaboration. Bounty & child bounties will be good ways to start collaborations, between curators, child bounty curators and implementers.


## Solutions & Implementations
OpenSquare proposes the big bounty, becomes the curator and then creates child bounties, assigning them to external developers. Deliveries will include:
- Identity pallet business explorer and user interfaces to register and request judgement.
- Vesting pallet business explorer and user interfaces to `vest_transfer` and `vest`.
- Basic block/extrinsic/event pages for relay chain.
- A bounty collaboration site where curator can collaborate with child bounty hunters.
 
There will also be other business implementations in the future plan, including governance, society, para-chains, etc. For more detailed proposal context, milestones, budget, deliverables and plans, please check the [full proposal](https://hackmd.io/@WIq3uV0rRwS6W3GGj2pmyA/Sy9-nCF9t).

---
We are [OpenSquare](https://www.opensquare.network/team/) team, dedicated to facilitate the collaboration between projects and developers.

Visualize polkadot bounty program phase 1

Bounty proposal: Visualize polkadot bounty program phase 1

This is a bounty proposal whose proposer address (HCXLYCD5h4q5dST4XeepsYsnXAHUz6GYiYZ3BH6BKisBK1Y) is shown in on-chain info below. Only this user can edit this description and the title. If you own this account, login and tell us more about your proposal.

Hello all Kusama decentralized eco system lovers...

orcun.io

As we experience a continued growth in the Kusama ecosystem, it becomes imperative to find ways to communicate with stakeholders in an efficient manner, making sure all information is distributed for informed decisions to be taken, especially in the case of Council and Technical Committee members. 

The goal of this proposal is to develop a **basic app that listens to on-chain calls and notifies Council members when their review and vote is needed**. An app to help councillors know once they are needed to push forward emergency mechanisms on-chain as well as other proposals would help mitigate the risk in the network. The app:

- would connect to rpc node;
- would connect with different networks;
- would notify about events;
- would watch wallet accounts and tell the user when pending;
- would have different alert levels;
- would recognise a "batcall" remark from council or TC members, with a `system.remark` "alertCouncil" that would trigger an alarm.

This proposal is submitted for discussion as a bounty and should be understood within efforts to increase council participation on the overall governance process and increase transparency in the governance process. The full bounty proposal, including tasks, budget and roadmap can be found [HERE](https://docs.google.com/document/d/1zsYYWWvbOXRZjez_N3lRl8memBEbhfTIj3JUP-CvAZQ/edit?usp=sharing).

Leave your comments and questions on the post! I would already like to suggest Mario (Polkastats) as curator and Ana (La Colmena - Bitcoinera) as implementer, but is up for Council to decide. They both have been crucial in the development of this proposal. 

Bounty Proposal: Kusama Council Alert App

saer

calmar

game UnicornGopro

While we already have a diverse field of mobile wallets in the ecosystem, they all attempt to be complete solutions, and we have a distinct lack of mobile equivalents to our browser extensions. 

Where we have solutions like Subsocial and Kodadot with mobile-ready UIs, users cannot use these applications with the same amount of security on mobile as they can on desktop, due to lack of an injected signer being available on mobile. 

In the longer term, the best-in-class mobile and desktop experiences come from toolkits like Web3Modal which allow developers to build experiences agnostic of the underlying signing solution used by a given user. While Polkadot Signing solutions are significantly lighter than Ethereum's - the signer doesn't require any connection to a node endpoint, the precedent is that the application provides that - it would still be interesting to explore the feasibility of remote signing solutions (portis), relayed signatures (walletconnect), and if the existing tools in the space may be reused, or if new tooling can be created within the scope of this bounty. 

One direction that is in research within the ecosystem that could lead to novel work deployed to Kusama and Polkadot is the concept of a page that stores encrypted keys in localstorage, with dapp developers loading it in an iframe and communicating with it for signatures - the idea being that the page that is loaded is specified by the user, based on their security model, up to and including a page that is hosted on localhost with a self-signed certificate as the most secure option, and a hosted wallet providing traditional username signup as the least secure option. 

REQUEST FOR CURATOR:

The Curator for this proposal should be someone at least familiar with the equivalent ecosystem components in the Ethereum ecosystem - Mobile Wallets, (ie, Metamask mobile, Trust, etc) Walletconnect, Portis, and in general the Web3Modal ecosystem. And either the ability to independently verify the safety/veracity of proposals and teams applying for this bounty, or connections to individuals that can do so (who's verification work is to be funded by subbounty, presumably).

It will be the Curator's primary responsibility to deliver a mobile-first signing solution, preferably an open standard, for Polkadot, preferably without requiring users to install an additional application on their devices so that it is platform agnostic, "as secure as possible". 

It should be clear that a Curator cannot directly be involved in the development of, or directly connected to the groups or individuals making proposals for, this bounty - although in this case knowledge of the ecosystem and relationships with the teams should probably be considered a positive factor in curators selection, so there will likely be a grey area between the two criteria. 

REQUEST FOR PROPOSALS:

I'd be excited to see the aforementioned teams and projects extending their tools to Polkadot, but ideally any team that is capable of providing a solution that satisfies the curator selected for this bounty should apply.

It is ultimately up to the curator to determine, but I would suggest using part of this bounty to fund several PoC sub-bounties that allow self-hosted solutions for app devs and users, and use the remainder to audit and polish the most promising solution(s) - Bounties can be extended via making treasury proposals to their address, and I will support increasing this bounty's funding after the first stage of PoCs

@Polkadot/extension-inject on Mobile and/or walletconnect deeplinking equivalent 

Mobile Signers / Injectors / Walletconnect equivalent 

shiden

**Proponent:** RTTI-5220 (GLVeryFRbg5hEKvQZcAnLvXZEXhiYaBjzSDwrXBXrfPF7wj)

**Date:** January 2021

**Requested allocation:** 1530,00 USD / 18.43 KSM

**Proposed Curator Reward:** 2% of total - USD 30,00 / 0.37 KSM.

**Short description:** The idea of a sub-bounties extension aims to give more flexibility in the use of the pallet for curators to reward completed tasks without closing the parent bounty. This will contribute to achieve one of the ultimate goals of the pallet: to budget the networks' treasuries allowing bounties to extend their life cycles.
______________________________________________________________________________________


## **Context Of The Bounty & Problem**

In its current implementation, the bounty pallet allowed us to experiment with delegating the Council's responsibilities to a curator, defined as an expert in the topic the bounty touches. You can find more information about the current implementation [here](https://polkadot.network/kusama-and-polkadot-now-reward-curators-helping-to-scale-councils-functions-join-the-force-moving-the-community-forward/). 

However, the pallet does not allow the creation of **sub-bounties** by the curator (the address with agency over the funds of active bounties): if a bounty includes in its scope of work an N number of tasks, the payout to the implementers can only be executed once all tasks have been completed by awarding the bounty and closing it. This restricts the use of the pallet to small-sized bounties for a short amount of time.

The idea of a sub-bounties extension aims to give more flexibility in the use of the pallet for curators to reward completed tasks **without closing the parent bounty**. This will contribute to achieve one of the ultimate goals of the pallet: to budget the networks' treasuries allowing bounties to extend their life cycles. Other goals of this extension include:

1. To minimize tracking & execution management overhead to council members & improve governance efficiency.
2. To allow tracking & granularity in high budget allocated funds.
3. To allow iterations by starting a big proposal with a minimal viable fund and top-up based on progress if needed.

In the model we envision, a sub-bounty can only be opened using funds from an **active** bounty. This model allows the curator to allocate a specific amount of funds from the active bounty to a sub-bounty, and reward the task after completion by calling `award_subBounty`. After the call is confirmed, the sub-bounty is closed and the specific amount of it is deducted from the total allocation from the bounty (that stays open).

For a detailed description of the extension specification, budget and tasks included in the bounty, please visit the full proposal [**HERE**](https://docs.google.com/document/d/1_rsY5rSG5vkQJRIHSYB3161MMFreYKk00gKygY_L8QU/edit?usp=sharing). 

## **Notes**

Although the Kusama Council has the responsibility of deciding on the curator who will take the role if this bounty proposal is approved, we would like to suggest Bryan Chen (the original implementer of the bounty pallet) to review and evaluate the tasks' completion; this is the main reason why this extension proposal is submitted for discussion as a bounty proposal: Bryan has shown expertise in all necessary topics related to the bounty in order to develop this role. 

You can find the current implementation, along with the original ideas and discussions by the community in the links below:

- Original idea - [here](https://github.com/paritytech/substrate/issues/5713)
- Current implementation - [here](https://github.com/paritytech/substrate/tree/master/frame/bounties)
- Community discussion - [here](https://kusama.polkassembly.io/post/86)
- Bounties implementation spending parameters - [here](https://kusama.polkassembly.io/post/151)
- Final review on current implementation by the community - [here](https://kusama.polkassembly.io/post/237)

### Proposed Sub-bounty API & Signature

- Sub-bounties Extension: design discussion notes #7959 - [here](https://github.com/paritytech/substrate/discussions/7959)

Bounty Proposal: Sub-Bounties Extension Implementation

At the moment, there is no way for users to see bounties on Apps: this development would greatly allow users to make use of the bounty extension. A first bounty for building a bounty UI on Apps, including design front and dev front needed to develop and implement the Bounty UI on Apps. Jaco Greeff, given his work and experience, is the curator of this bounty and the EthWorks team is working as implementer.

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