[idea] Namada public goods funding interface

While reading some of the PGF discussion topics over the weekend, I was thinking that it would be really nice to have an interface specifically designed for interactions with Namada’s PGF systems – both read (tracking historical PGF events, current flows, future planned events, CFPs, etc.) and write (crafting proposals, maybe we come up with a protocol for nominations, etc.). Currently, in both Namadillo and block explorers, we have a “proposal governance interface” very similar to that of Cosmos chains. This works just fine for viewing proposals as proposals, but it isn’t particularly oriented towards the specific needs of public goods funding, and I think Namada could greatly benefit from building an interface specifically for PGF management (which is a critically important task for the network’s future).

Here are a few aspects that I imagine such an interface might provide:

  1. A detailed historical database of past PGF (both continuous and retro, specific usage patterns e.g. Donor Drops, and any new mechanisms or more specific usage patterns we might develop in the future), allowing users to see what Namada has done historically, trace related outputs (e.g. the work that was funded), and even maybe export specific data related to public goods funding history (e.g. public goods producers, proposal voters, stewards, donor drop participants, etc.) for future airdrops or other purposes.
  2. A dashboard and detailed overview of current PGF flows: ongoing CPGF proposals, ongoing or planned projects like the Donor Drop, PGF inflow (issuance) vs outflows (CPGF and future planned RPGF), current specific public goods being funded and where to find out about their statuses, etc. – we can almost think about this as the “Namada public goods economy management dashboard” (if you haven’t heard of it before, the Wikipedia page on Project Cybersyn is worth a read).
  3. Some “write interfaces” for users to provide inputs to PGF. These inputs could take various forms, such as nominations, votes on the usefulness of previously funded public goods to them, and voting on the actual Namada CPGF/RPGF proposals (but, in general, I think we should aim to reach consensus before the formality of proposal voting). Ideally these interfaces should collect data (that users wish to share) in a way which will give PGF stewards confidence that they have a clear picture of what public goods are most important to the community. Of course, a structured interface is merely a complement to discussions occuring in various community venues (e.g. Discord, these forums), but I think it could be a helpful one.

I’m not sure yet whether this interface should live in Namadillo, a block explorer, a dedicated app, etc. – I wanted to first describe the idea a bit and solicit input – thoughts?

4 Likes

I totally agree, PGF interfacing should “fork” from governance proposals to have its own dedicated cultural track.

How best to begin?

Rather than a master plan, my inclination is toward small, quick iterations of the most immediately useful components initially, assuming we are in experimentation & discovery mode.

For example, an existing explorer could separate PGF proposals from its “governance” tab: add a few basic metrics (eg. outflows), include a feature or two (eg. latest “PGF Ops” topics labelled “Proposal”), label a proposal distinctly if it’s a steward-launched proposal, make it easy for the user to reason around expectations (eg. voting threshold metrics; event timings).

Technical vs Social

I imagine that indexing the info to support a 10-thousand-foot view being different than enabling and indexing social interactions (current & historical) around PGF proposals, and it makes me wonder if these would be different (inter-related) projects.

@cwgoes wdyt the “lead domino” is here? Like if we were to the focus efforts on one part of this, which would you bet on getting the most impact in ROI.

2 Likes

I’m not sure that I follow the scope of your question (is it related to technical vs social, or the overall idea)? As a first iterative step, I like your proposal a lot:

and I could see it being valuable to develop dedicated dashboards or dashboard features for common PGF patterns (e.g. potentially Donor Drops), as those aren’t otherwise easy to visualize (maybe @zenodeapp’s work could be extended here).

1 Like

In general support of this, would be great if done well! (please note I am sometimes in support of things :sweat_smile:)

I plan to create a separate page for pgf in explorer75
So far the following is planned:
1 PGF current size (amount)
2 PGF inflation ratio
3 List of PGF proposals
4 PGF Spent amount

5 I will add tags to account information and will assign tags to PGF receiver accounts, like existing genesis comments tag ( this will allow you to navigate among the recipients’ accounts )


Fig. Genesis tags

some of the data can be presented graphically, e.g. shares of funds spent by projects (proposals)

3 Likes

it goes something like this

@cwgoes @Gavin

Until a table of grantees is added. And support for Continuous Funding has not yet been implemented. But it doesn’t look complicated.

2 Likes

This is already awesome, the pie chart is great! Do you think it would be possible to also visualize PGF issuance and spending over time (both historically and perhaps projected into the future)?

2 Likes

I think so. It’s true that a pie chart may not be the most convenient. We need a time diogram to see the moment of spending. historical data on pgf size can be collected. we can also extrapolate the future PGF (we know inflation rate, effictive nam supply etc)

1 Like