Another thing is that yes I understand asking funds for all milestones upfront definitely helping you to secure the runway. However you also need to understand this also a risk to the treasury that you could under deliver. The more you ask, the more work you need to do to proof you will make good use of those funds.

 

Have you had a chance to review our previous W3F grants? If you haven’t I'd ask you to have a look. 
We over-delivered every time. Why should this time be any different? 

The grants are references in the "Team Background" section:
- W3F Grant [Multi-token community contributions for verified creators —  Completed](https://github.com/w3f/Grants-Program/blob/master/applications/anagolay-project-idiyanale-multi-token-community-contributions-for-verified-creators.md)
- W3F Grant [Project Idiyanale Phase 1 —  Completed](https://github.com/w3f/Grants-Program/blob/master/applications/anagolay-project-idiyanale-phase-1.md)

Best,
D

I have to admit I did not read everything in your proposal so sorry if my question are already answered there. We should train ChatGPT to read proposal and answer questions.

You have a lot of repo in your Github org, which is good, but can you help me pointing out all the relevant repo regards to this proposal?

IMO every single treasury proposal should disclose how much % of the cost is expected to be covered by treasury. If the proposal is asking for 100%, then 100% of the outcome, including the brand, should belong to the public somehow. It should also be useful for the whole ecosystem. It could be obvious to you this is a very useful product, but your words are biased so it will be better if you can find others confirming that they really want to use your product. Note that this isn't specific for this proposal, but for all the proposals.

Hi there,

> I have to admit I did not read everything in your proposal so sorry if my question are already answered there. We should train ChatGPT to read proposal and answer questions.
> 

Why not train them to write a proposal in the first place? What matters are the deliverables, the rest is the skill of writing which is quite hard to learn for an individual but not for the AI. 

> You have a lot of repo in your Github org, which is good, but can you help me pointing out all the relevant repo regards to this proposal?
> 

The repos are in the proposal, I see no reason why to add them here.  

> IMO every single treasury proposal should disclose how much ….
> 

I hear your opinion and value your response. I ask you to check the Anagolay brand, and what we have done before ( including the W3F grants ) then please tell me what we have that is not public. All our code is open source, we didn’t hide or closed the source single pallet, single js library. 

> It could be obvious to you this is a very useful product, but your words are biased so it will be better if you can …
> 

Do you think our product and technology are not useful? 

Best,

D

Unfortunately, for the time being we will be voting no on this Motion.
The $400k being charged upfront for 4 milestones is too much, we understand that you might need a runway of funds, however this amount of funds upfront is excessive.
Furthermore, why should the treasury cover the 7% slippage? If the project is paid for in milestones, there will not be a need for such a high slippage allowance.

Thank you for your vote and the explanation provided. 
Indeed we request the upfront payment to secure some runway for the development team - to deliver all the 3 milestones in just 5 months. The faster we build it - the faster everyone in the ecosystem can start reaping benefits. Then again, the creative economy is a hot domain, the market is extremely dynamic, and there is a proven demand for our proposed solution, so timing is of the essence.
Creating a separate treasury proposal upon delivery of each milestone means delaying the implementation for at least 2-3 months.

As for the 7% slippage, based on what we've seen reviewing other (approved) proposals, it's pretty common to include a slippage (in the examples I saw, it's 10%). Some projects also include a % for tax and overhead costs on top of a similar or higher hourly rate. 
In our case, all expenses are included in the hourly rate provided. 7% is meant to account for the potential change in the exchange rate between the date of the submission and the funds released. If that won't be the case, we will return the extra amount to the Treasury.

Dear Councillors & community, we want to thank you for your feedback so far. Since we are getting quite a few questions, we've decided to put together a quick video walkthrough: [https://youtu.be/syklY7oCNFg?t=3](https://youtu.be/syklY7oCNFg?t=3)
I hope it will make the review process a bit easier and answer some of the questions you might have. 

P.S. My apologies for the jumpy edits, we really wanted to get it out asap. The video is not exactly award-winning material, but I hope it gets the job done.

What's your github repo?
Are you asking the treasury to support 100% of the development cost? If not 100%, what's the percentage?

Hi there,

> What's your github repo?
> 

The GitHub repos are provided in the proposal, in case you have missed it here is the organization link which contains all the repos:  [https://github.com/anagolay](https://github.com/anagolay)

Also, the links are in the description itself under the `Including, most recently:`  list. Unfortunately, due to the polkassembly UI bug, they are only visible on mouse over (hover).

> Are you asking the treasury to support 100% of the development cost?
> 

We have touched on this topic in the proposal too under the `Team's background`.  The project so far was funded 80% from our pockets ( Elena and me ) over the 3 years period, 20% comes from NGI(EU), and a few smaller grants from w3f.  In total, we invested around 500K EUR. We expected to have the project running and be self-sustaining in the economic sense last year, unfortunately, the market crashed and now we are forced to ask Your support to continue the development which, once done, irrefutably affects the whole ecosystem. 

What we propose is a unique use case with a huge scaling potential to bring new audiences to the ecosystem and drive wide adoption. The exact issues the ecosystem is currently struggling with.

I am really surprised to see comments focused primarily on the cost of the development.  No project has built what we are building in the ecosystem, we are first, so yes, there are expenses and they are calculated correctly without any hidden agenda of profit or other financial shenanigans. 

Please do not forget that this proposal includes seven people working with a time allocation of 5 months. Which is quite a short period of time to build something no other project has built.

I hope my answers are satisfactory. 


Best,

Daniel

I am wondering how do you plan to attract end users? whats your strategy here? how will you make this funding work in the sense of increasing adoption for the Polkadot ecosystem?

Hi Raul, thank you for a great question. 
While initially, we propose to unfold and test this for the ecosystem, the ultimate goal is, of course, to optimize and polish the experience for creators of original content who are still new to web3 (and that's about 90%).
Once we a ready to scale, a brief overview of the strategy is as follows:
- Outbound: direct reach-out to top creators (vocal about relevant topics). We'll recruit influencers aligned with our vision: streamers, musicians, visual artists, and photographers. We are already working out some partnerships in this regard. By inviting their communities to support them via Anagolay, our Ambassadors kick-start the network effect. 
- Inbound: running dedicated campaigns on each channel: Twitter, YouTube, Mastodon, etc., incorporating incentives and gamified onboarding. Our go-to target audience: creators verified with Brave (proven market), and content creators with mid-size well-engaged communities currently using Patreon or KoFi.
- Educational: we'll accompany the above with a content campaign focused on explaining the offer of the Polkadot ecosystem through Anagolay to the entry-level audience. For creators, by creators (a form of content that is still rare to come across): the functionality that we build allows us to engage creators and creative communities in the process by incentivizing them (a win-win 👾).

After completing the scope of this proposal, we will have a validated solution and much-needed data to optimize the user experience that will prepare us for the broader market reach out.    
Ideally, before scaling, we'd like to have the recurring contributions functionality available for all tokens on Polkadot and Kusama, which will mean an ecosystem-wide utility and much better functionality for the end user.

Worth noting that at the ecosystem level, we make the Anagolay extension compatible with the existing wallets, and others can integrate what we propose using our JS-SDK. This way, we can also bring additional functionality to the existing communities ecosystem-wide. 

@elena what are your success metrics to achieve this?

At the initial stage, our key metrics to monitor user adoption are the following:
- The number of verifications per channel (# of users who verified their Twitter, YouTube, Github, Website, etc.)
- number of tips sent (volume is not a defining metric, but we'll monitor this data for additional insight).

By the time all the key verification strategies and subscriptions tiers are rolled out, we'll start prioritizing 
- number of channels verified per user 
- recurring subscription volume (and dynamics).

UPDATE: We ask the Council to reject this proposal, and endorse the tip for the reimbursement of the deposit: [500 DOT](https://polkadot.polkassembly.io/tip/0x8fb68b374450ee4780db4770a44194d1fc0cc0ad6402c36d18d89ec5987e7783)

Hi everyone, Daniel of Anagolay is here. 

We believe monetizing and supporting creative work should be simpler, work across platforms, and be equally accessible to everyone. And we can make it happen with the web3 infrastructure developed on top of an excellent Substrate framework while adding value to the Polkadot ecosystem. 

Throughout 2022 and early 2023, the Anagolay team has been building the foundation to make our vision possible. 

Including, most recently: 

- [public identity Verification](https://anagolay.dev/blog/multi-token-community-contributions-for-verified-creators/milestone-1/) and [Tipping](https://github.com/w3f/Grant-Milestone-Delivery/pull/708) Pallets delivered under the [W3F grant](https://github.com/w3f/Grants-Program/blob/master/applications/anagolay-project-idiyanale-multi-token-community-contributions-for-verified-creators.md)
- [verification strategy and UI](https://bafybeiai2abe5y2nbgydjopuxhg6sdicim22gu4zgkpmcvu7apurpdlguq.ipfs.anagolay.network/verify-your-domain/) for web-domains verifications
- [Anagolay browser extension](https://anagolay.dev/blog/chrome_extension/installation-and-step-by-step-tutorial/), for sending tips to verified web domains.

For more details on what we accomplished last year, feel free to check [this post](https://anagolay.dev/blog/2022-retrospective/).

# Current Proposal Scope & Objectives

Our goal is to empower and support ***independent content creators*** and ***open-source developers***. 

With Anagolay, any verified online identity, like a web (sub)domain, a social media account (Twitter, YouTube, GitHub, etc.), or any Mastodon federated identity, can be used to send and receive funds: as community contributions to support a *verified creator* or their particular project (a repository or even a specific post).

We’ll start with bringing tip-as-you-go functionality to the ecosystem, making supporting quality work much easier: both from a personal account or by suggesting a tip from the Treasury. By doing so, we are creating additional incentives to contribute to the Polkadot community growth: for the existing members and for all the creators & builders in the digital space. 

From the get-go, in the current implementation, the tips can be sent in IDI (our native token). Eventually, our goal is to enable tips & recurring contributions in any DotSama token, scale Anagolay solution, and streamline creative workflow from publishing to monetization for all independent creators.

## Value

The value of Anagolay's solution is three-fold:

- Firstly, it provides content creators and open-source contributors with additional monetization tools.
- Secondly, it creates an additional incentive for the communities within Polkadot and Kusama ecosystems to make and encourage contributions. Tips from the community become a more accessible way to show appreciation for someone's work and can even serve as an alternative to treasury spending.
- Lastly, by bringing new users into the ecosystem, the solution enhances the ecosystem's overall value.

The range of communities benefitting from Anagolay will gradually expand as we develop and implement new features: 

![Anagolay_audience_map.png](https://ipfs.anagolay.network/ipfs/bafybeigsabemad2cctftxteqhogi44blnaxjyztemd7m376qu7xmnya6dy?anagolay_audience_map.png)

Initially, we aim to put community support & incentivization functionality to the test while adding value within the context of the Polkadot and Kusama ecosystem. This will allow us to collect valuable feedback and prepare for scaling: to onboard wider creative audiences and become their gateway to the ecosystem.

Please see the [FULL PROPOSAL HERE](https://kelp.notion.site/Anagolay-community-contributions-for-verified-creators-892fef98694b401c87ee2cb72bc885e7) for more details.

Anagolay proposal: enabling community contributions for verified creators

Treasury

Approve a proposal. At a later time, the proposal will be allocated to the beneficiary
and the original deposit will be returned.

May only be called from `T::ApproveOrigin`.

# <weight>
- Complexity: O(1).
- DbReads: `Proposals`, `Approvals`
- DbWrite: `Approvals`
# </weight>

#377 Anagolay proposal: enabling community contributions for verified creators