Introduce quadratic funding to the polkadot treasury spending

Wish For Change
23d ago
6 Comments
TimedOut
Content
AI Summary
Reply
Up 1
Share
Tally
0.6%Aye
100.0%Threshold
99.4%Nay
Aye
216.19KDOT
Nay
37.24MDOT
  • 0.0%
  • 0.0%
  • 0.0%

Threshold

Support(0.01%)
115.91KDOT
Issuance
1.51BDOT
Votes
Nested
Flattened
Calls
Call
Metadata
Timeline2
Votes Bubble
Statistics
Comments

So where does the funds from the pool/bounty come from? The treasury? If so, how much of the treasury funds will be transferred to this new funding model bounty/pool? Quadratic funding on EVMs usually comes from direct donations and own funds so no native treasury is involved which is why these questions become relevant for Polkadot.

As for the implementation itself we don't like the social media auth as these companies by design require heaps of data, and profit from your data (when the entity is legit) and are opposite of what web3 should be like. So the weight increments for these sounds extremely detrimental for legit parties specially considering that including them won't penalize detrimental proposals/entities as these accounts can be created and verified easily while helping perpetuate these data gathering mechanisms for legit parties.

Additionally, the history of on-chain behavior must also be very well studied, debated and decided first otherwise we'll end up penalizing new or old participants or whatever combination of the factors that these on-chain activity requires.

The idea that "The more donors and the more funds an applicant project receives, the more a project will share the pool." will definitely translate to sybil attacks (specially the number of donors part) as we don't have robust ways to determine identity for on-chain activity yet. So ending at the amount donated directly sounds like the best approach. If there are identity mechanisms like the passports of EVMs that are meant to be applied to Polkadot we should be discussing those first instead of jumping to sybil risk mechanisms with a large amount of treasury funds right away. Preferably, ways of determining identity that are native not invasive, voluntary or leak-risky. Also, don't give these options a high weight as these are still prone to errors.

Considering these issues which Gitcoin took years to iron out only to circle back to a centralized approach to identity verification, we'd like to also hear about the idea of this being tested extensively first on Kusama so that we can see an operational QF mechanism for the treasury first instead of jumping straight away on Polkadot's runtime and start fixing issues on the way.

Reply
Up 1

As much i'd love to see quadratic funding in action, i still agree to the points mentioned by @Saxemberg Governance. Would love to see it first being experimented on Kusama, getting some hands-on experiences before thinking about bringing it to Polkadot

Reply
Up