Aggregation & atomization: dependency funding round dynamics

New article: Aggregation & atomization: dependency funding spherical dynamics

>>>>>>>> learn the full piece, abstract beneath

The time period “public items” has been diluted – “dependency” is likely to be higher. Spherical-based funding mechanisms incentivize atomization – how can we keep away from this?

We’ve did not develop requirements of rigor for using the "public items" time period. When it applies to all the pieces, it describes nothing. “Dependency” is best for the Ethereum software program ecosystem: essential bits of infrastructure in a roundabout way maintained by an actor.

Recurring Funding Rounds include tradeoffs

– consideration video games
– eligibility scoping
– excessive expectations of evaluators
– atomization incentive

Reflecting on OP Retro Spherical 5

– incentivizing atomization
– Legibility just isn’t affect
– Stewardship is much less legible – for good motive
– Misconceptions about ranges of PG funding

https://preview.redd.it/zlkqaqpd2cyd1.png?width=3720&format=png&auto=webp&s=74616256a8524d67ed4bb9c4314835f3cc0047bd

Doable modifications for rounds

– Take away caps on allocations
– Give particular consideration to tasks with numerous beneficiaries
– Cap tasks per spherical
– Explicitly weight the variety of beneficiaries within the allocation system

matters embrace: public items vs dependency, affect, allocators, commons, u/Optimism Retro Spherical 5, @ProtocolGuild, Ethereum core protocol, @gitcoin, @OctantApp + extra