One of the struggles of remote, open source coding is that if there’s not a key product manager, it’s hard to figure out how to prioritise tasks. A “Recommendation Market” on issues could be extremely meaningful in this context, allowing participants to rank features, issues and bugs.
A maintainer could pick and choose to graduate issues to work on, rewarding curators for their service. In doing this maintenance, the maintainer can also earn from doing this work (if the graduating also earns them tokens).
Through this, open source projects can more effectively use its long-tail of contributors to help coordinate around work online & remotely.
A variation on graduating token bonding curves is to add multiple graduations before it could be sold. It can follow the traditional development life-cycle.
eg, a “buy token” starts a level one: ranking to-dos. Then it graduates to: ranking wip & testing. Then it graduates to: implemented.
Only once the token has graduated several stages to “implemented” does it turn into a “sell token” in order to claim a reward from the communal collateral in the bonding curve.
Source: Verified Curation Markets & Graduating Token Bonding Curves, Simon de la Rouviere, February 15, 219