Marketing Bounty Proposal
PROBLEM STATEMENT
Some current issues related to marketing proposals:
● Insufficiently robust investment in marketing about the Polkadot ecosystem diminishes the general crypto community's interest in the ecosystem, as well as reducing the appeal for developers to engage in building projects.
● Diverse marketing qualities and perspectives within the ecosystem, especially among significant stakeholders, generate unwarranted negativity.
● Varying values presented in different proposals create significant disparities when balancing budgets.
● Low-quality proposals and lack of verification lead to the potential for fraudulent activities.
Furthermore, there are certain risks and potential benefits directly impacting the Polkadot ecosystem behind these proposals, which the general community might not spend much time researching, and still make voting decisions, resulting in inefficiencies.
PROPOSAL OBJECTIVES
The goal of marketing bounty is to reward marketing teams/entities for their effort and bring enormous traction for the whole Polkadot ecosystem, push Polkadot back to the top list and become a real “community protocol".
In this proposal, we are proposing a set of 8 main curators who will be responsible to curate marketing-related proposals with different categories:
(1) Approach new target audience/users.
(2) Retain Polkadot ecosystem lovers, daily users.
(3) Educate, and produce tutorial contents for users/developers.
(4) Manage local communities (ecosystem update/users support/developers engagement).
(5) Amplify branding for high-trusted ecosystem agents.
(6) Sponsorship for specific occasions (F1 Race, Super Bowl, etc).
(7) One time campaign (1 specific event generated by several influencers).
In this proposal, we are proposing a set of 8 main curators who will be responsible to curate marketing-related activities with multisig using pure proxy via MultiX. We also propose a compensation rate for weekly management. However, within the curator set, some individuals will hold positions as significant investors and they will have the option to return a portion of their received reward from the multisig fund after a specified period.
All 8 curators will manage the funds using a multisig with pure proxy via MultiX. The threshold is set to 4 out of 8 for a child-bounty to get released. Conflicts of interests are addressed in the proposals with feedback from various Polkadot core contributors.
FULL PROPOSAL HERE: https://docs.google.com/document/d/1_hkZ6-N-8yt7JVF_ITHKL4tpsC-ZWSSrgT0Sce255RY/edit?usp=sharing
Main contact: [email protected]
Comments (4)
Hey everyone, this is Ryan from SubWallet, Dotinsights, and DOTinVietnam.
I'm strongly supportive of this proposal. As money inherently loses value, the same holds true for DOT, which experiences an annual inflation rate of over 7%. Similar to the development of a country, I think funds need to be invested wisely in building essential infrastructure, marketing & branding, education, and ecosystem growth activities. This helps the ecosystem grow.
With the launch of OpenGov, we anticipate an influx of marketing proposals. To ensure the integrity and effectiveness of these proposals, it's crucial to enlist knowledgeable and trusted experts who can verify submissions and provide valuable guidance on Polkadot insights.
I'd like to offer feedback on the proposal threshold. Instead of a uniform threshold for all proposals, I suggest considering tier-specific thresholds to better cater to varying spending levels. For instance:
This tiered approach would provide a more nuanced evaluation process, aligning the threshold with the scale of the proposal and fostering a fair and effective review system. The above is just an example. More details should be discussed further.
In principle, in favor. Can lead to more strategic and efficient decision making. However, it's very centralised. Would it be better if it was e.g. five multisigs ("political parties") and 3/5 Ayes to pass? This could develop into a full-fledged Marketing Fellowship in time to come. Outlined some thoughts here: https://docs.google.com/presentation/d/1chg-OWs1Zam6BnRowbx7ObfipelHOjjGSQzFvUQKOik/edit?usp=drivesdk