[T] DOT #1533 - Faze x Vitality - Esport Meta Proposal.
Terminated 
terminated
Description

https://polkadot.subsquare.io/referenda/1533

  • A team of 11 people and 7 partners created a proposal for Polkadot.
  • They believe that Polkadot needs better ways to manage its public actions.
  • Lots of money is spent to promote Polkadot each year, but much of it goes to waste.
  • New users often struggle to understand how to interact with Polkadot.
  • The proposal combines 7 ideas to make Polkadot better and more efficient.
  • It aims to strengthen partnerships with big esports organizations.
  • The proposal includes creating new tools and apps to help users.
Appendants
1
#1
1mo ago

🟢 0 • 🔴 6 • ⚪️ 0
60% quorum not met.
Vote #1: NAY
No CoI reported. DV delegation exercised.
https://polkadot.subscan.io/extrinsic/25732508-2
https://polkadot.subsquare.io/referenda/1533#3

Optionssingle

Votes·8

12Hi...E9N3
12Hi...E9N3
12His7t3EJ38tjdBbivUzWQeaNCLKfMqtKp1Ed3xHMyCE9N3
Nay
# 2
My initial position on this one a very strong NAY for a myriad of reasons, please see the discussion below for details.
1ZSP...vx6w
1ZSP...vx6w
1ZSPR3zNg5Po3obkhXTPR95DepNBzBZ3CyomHXGHK9Uvx6w
Nay
# 2
For a proposal of this magnitude, we don't have an adequate track record of execution, and the treasury is taking too much execution risk, since the funds are delivered upfront. Ideally the esports orgs share in the upfront risk which will align the project for success. Alternately, another path with shared risk and better alignment for success is if the product(s) can be built independently, incubated as a business, and seek out esports organizations as customers or strategic partners.
14gM...deVb
14gM...deVb
14gMJV95zwxUsFEZDSC8mtBVifS6SypKJkfBKANkMsLZdeVb
Nay
# 2
I don't exposure and marketing is what polkadot need most. The ability to onboard more developers easily is. I see the main direction is contract platform support, infrastructures, developer tools, etc.
14Gn...YLEh
14Gn...YLEh
14Gn7SEmCgMX7Ukuppnw5TRjA7pao2HFpuJo39frB42tYLEh
Nay
# 2
I greatly appreciate that people outside Polkadot are interested in building on the network, however, the proposal seems to me overly ambitious and with a very high cost of execution to personally consider an AYE. I would like to see it broken down into clearer, more concise KPIs with more defined timelines, so that I can begin to evaluate the proposal in a more serious way.
12s6...nE8h
12s6...nE8h
12s6UMSSfE2bNxtYrJc6eeuZ7UxQnRpUzaAh1gPQrGNFnE8h
Nay
# 2
While engaging esports audiences through gamification, NFTs and creative user experiences has long-term potential, this proposal feels premature and overly ambitious. With a 1.5M DOT ask and limited clarity on measuring success, the treasury would be taking on all the execution risk, especially without milestone-based accountability or skin in the game from the execution team or esports partners. Instead of funding multiple esports teams simultaneously, we should focus on creating real, actionable user experiences based on Polkadot, which delivers tangible value and engagement. The Heroic partnership is already funded and provides a perfect testbed for many of the proposed ideas. Let's learn from this experiment first, refine our approach and only then consider scaling up to larger or more expensive collaborations. For these reasons, we vote NAY.
15fT...yBzL
15fT...yBzL
15fTH34bbKGMUjF1bLmTqxPYgpg481imThwhWcQfCyktyBzL
Abstain
# 3
Switching to abstain after my initial nay after our call with the team. I know this proposal cannot be allowed by the community due to the state of the treasury and the size of the ask, but I think e-sports is a very critical field for the success of the network, and this proposal offers a good structure. My comments from my first vote: It's a good idea to build a front with sufficient runway to operate in the e-sports field, and the language of the proposal aligns well with the cultural fabric of Polkadot. However, I think the collective should first gain credibility through smaller budgets and projects. I understand that smaller budgets may not allow for working with the biggest names in the field, but there should be ways to prove the concept before embarking on a grand programme.
13ED...KQbF
13ED...KQbF
13EDmaUe89xXocPppFmuoAZaCsckaJy3deAyVyiykk1zKQbF
Aye
# 1
12Kt...DCoJ
12Kt...DCoJ
12KtA8mtfsK1CyQb4utLiwG3ao22z77w2cM2GqnaL2RiDCoJ
Abstain
# 3
Despite having no direct affiliation with this referendum, to avoid any potential CoI, I am choosing to abstain due to my roll as a UX Bounty Curator (where I work report directly to one of the potential beneficiaries of the proposal).

Discussions·3

I see absolutely no value in this kind of gigaproposals, this will not only make measuring the success of such a campaign practically impossible, it also leaves no room to vote on any of the campaigns individually on their own merits as it's a blanket AYE or NAY. In the upcoming days, I'll try to organize my thoughts in this discussion section on each of the individual campaigns that make up this gigaproposal.

The first thing I'd like to write about is the closing statement of the proposal, so in a way I'm starting at the end and will circle around and talk about the individual campaigns.

We believe this proposal doesn’t just solve a problem—it defines how they should be solved and how problems should be approached in OpenGov: with coordination, strategy, and unity. It positions the hive mind as a unified front, making it more effective, sustainable and suitable to address global corporations and bug institutions. This is OpenGov 2.0.

In my opinion, this is absolutely the wrong direction for OpenGov, I believe that this kind of treasury spending and marketing campaign should be put into action by first putting the long-term strategy to a vote with a preliminary action plan, all of which can then be put individually into proposals with individual proposals to be judged their own merit.

These grandiose gigaproposals will only result in overwhelmingly one-sided sentiment in the community due to everything conveniently packaged into one big box and put forward to the community as some kind of master plan when in reality it doesn't seem to be anything more than a bunch of loosely related marketing campaigns.

There's a few issues I see with this proposal:

  1. The Treasury is bearing all of the execution risk in this proposal, because the payment is upfront and quite large. The ideas here and ability to execute on them are unproven, and while they could potentially be good, the execution should be proven out in successive stages - e.g. similar to how a business goes from idea stage to product-market fit to growth.
  2. There needs to be skin in the game for all participants, for a venture like this. Success here requires product-market fit for the product that's being developed, in order to avoid a "build it and they will come" mentality. That has more aspects of a business than a common good venture, so I wonder if a business is a better structure here. Skin in the game for the execution team might be sweat equity where they demonstrate initial traction / proof points, and skin in the game for the esports organizations could be co-investment, which would indicate they strongly believe the idea will have a return for them. The ideal might be that the product(s) proposed here are good enough that the esports organizations adopt them without needing to pay an IP fee, and they contibute their own IP because it serves their own self interest.
  3. The incentives are not aligned regarding the incentive payments. If there are commissions or rewards, they should be paid based on success and impact generated from the proposal. Upfront commissions may make sense to bring established businesses (e.g. already with blockchain users or transactions) to Polkadot, but large upfront commisions for idea stage proposals seem to be just rewarding the ability for someone to imagine and write a large proposal, without checks on execution.
  4. Given the size of the ask, there is naturally an opportunity cost to consider. In the same conversation, we should consider focusing direct funds on developers and builders (e.g. rather than "IP" or retail). Hopefully this kickstarts the conversation around that.
Information
Snapshot
Timestamp
Created
Apr 18 2025 19:48
Start date
Apr 18 2025 00:00
End date
May 18 2025 00:00
Results
Voters
8
one-person-one-vote
Aye
1 VOTE
 
Nay
5 VOTE
 
Abstain
2 VOTE
 
© 2025 OpenSquare. All Rights Reserved.