-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Evolving OpenGov #2324
Evolving OpenGov #2324
Conversation
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
I have read and hereby sign the Contributor License Agreement. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @monsieurbulb, thanks for the application. This sounds generally interesting, but I have a few questions/requests:
- Have you considered requesting funding for this from OpenGov? If not, why?
- Are you planning to fund the subsequent research through grants as well?
- Why are you focusing on Kusama only? I'm sure much of it would apply to Polkadot as well.
- You say that the paper is going to be largely qualitative. I understand that a lot of the work will be hard to measure, but I'd still be interested in at least trying to substantiate the work with data. Perhaps this could be structured beforehand (see next point)?
- The deliverables are not well defined. The specs of the
0x
deliverables should be adapted to your specific project (you have not mentioned any data or artifacts to be delivered). The remaining deliverables are rather vague. It might make sense to structure these differently, e.g. by separating them into a bibliography, data and analytical tools and resulting paper.
Hi @semuelle thanks for the comment.
Short answer Yes. However... I decided to submit this due to @anaelleparity's RFP Action Research for OpenGov... in conversations with her after she submitted the RFP that W3F preferred to see these go via the treasury as (paraphrasing) this would give contributors chance to learn about the system on which they are reporting. Ultimately I want to assess the viability of this particular RFP - and indeed learn from the responses from people such as yourself... not to get too meta, but in some ways this proposal is just another active part of the 'Evolving OpenGov' paper. You get different signal from W3F dedicated grants people such as yourself, KSM / DOT holders would be different, DV different again. Not saying one is better than the other, since all have a different perspective. "The parable of the Blind Men and an Elephant is a story of a group of blind men who have never come across an elephant before and who learn and conceptualize what the elephant is like by touching it. Each blind man feels a different part of the elephant's body, but only one part, such as the side or the tusk. They then describe the elephant based on their limited experience and their descriptions of the elephant are different from each other. In some versions, they come to suspect that the other person is dishonest and they come to blows…" This is from the Decred paper Forks in the Road. I've spent an unbroken 6 years deep in the weeds of on-chain governance / treasury funding at decred, edgeware, kabocha, kusama and polkadot with my main curiosity related to how we create more collaborative, productive and sustainable funding environments compared to current incentives/structures/processes and the second order effects they produce on culture, politics and output. That necessitates seeing the elephant from as many perspectives as possible.
Perhaps, i wouldn't commit to a single route. We're launching a new community oriented stablecoin with Brale on Kusama AH and they are taking their integration fee in KAB, the native token of Kabocha (which W3F has a 7.5% stake). The yield from that project is designed to create an alternative funding model to W3F grants and KSM/DOT treasuries, though we do see ways to involve them in the economic opportunity. We are also working on onboarding alternative financing structures - see Introducing an alternative financing strategy, structure and partnership for maximising the potency of Kusama’s treasury.
Since this is a W3F stablecoin grant, I tend to think more holistically about the behaviour + output, rather than a particular brand narrative - please see Is Polkadot a brand? for further context. Were the grant funded by DOT or KSM directly, then it would ensure the narrative would feature either Polkadot or Kusama more strongly. Though Kusama and Polkadot are technically similar, they are not technically identical - ie there are different parachains running on each network and the treasuries fund different things, the token holdings are different and ultimately the cultures are different in obvious and non-obvious ways.
Well I imagine much of this may come together with existing research that is more quantative that frames current ecosystem orthodoxy. I did a lot of work outlining data around Kusama treasury spending and modelling Coretime income.
The output is a single paper working title Evolving OpenGov that brings together historical analysis to present a strategic rationale for structuring support and spending across the full innovation cycle. This is is not theoretical analysis, but pragmatic and actionable work (that we are actioning). In many ways I see this paper as a way of better communicating the strategy we are currently executing on, allowing a larger group to contribute to what is in effect a grass-roots rethinking of current ecosystem orthodoxy. Maybe I've misunderstood the deliverables aspect of the grant template - would you like to see this section with more info?
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the application. But at the moment the deliverables contain not a lot of details. For example, what kind of existing papers would you aggregate? Also not sure that our grants program should support: “‘thinking in public”. And just to mention it here: an RFP doesn’t necessarily be funded via the grants program. You could also apply for treasury funding with this.
Thanks David.
at the moment the deliverables contain not a lot of details. For example, what kind of existing papers would you aggregate?
The RFP I’m responding to relates to action research (ie applied) within the OpenGov domain which is itself a novel area of analysis.
To be clear on language here, when I reference “existing papers” I’m considering only those that relate directly to this domain - intrinsic rather than extrinsic such as academic papers on onchain governance / voting and the like.
As a long term onchain contributor, researcher and analyst of novel governance systems, I’m referencing my own work - and indeed those of participants within these new political arenas.
Also not sure that our grants program should support: “‘thinking in public”.
Perhaps this is just semantics, but this means to me open source research released in public to better understand the systems of which we are part. It is self referential. All work produced in an opengov analysis capacity by those operating within its domain are by definition works that seek to “think in public”.
just to mention it here: an RFP doesn’t necessarily be funded via the grants program. You could also apply for treasury funding with this.
Yes I’m absolutely aware of that. This submission is in part a test of the
viability of this RFP.
|
Research grants provided by the Grants Program have always been focused on small, well-defined questions and topics that allow (or rather, require) a thorough description of questions, methods, metrics and expected results. I think the OpenGov RFP also points in this direction. Your current proposal sounds more like a critique, which would be extremely difficult to evaluate. As such, I think it would be better suited for the treasury in its current form. |
I’ll add more detail related here. Quoting RFP;
The challenge with the nature of this framing is that operating within OpenGov is a subjective experience that leads to strategic insights that are by definition opinionated rather than neutral. In part, as someone who has lived / worked under the system for a few years, we have an interesting collision where the W3F assess the validity of this experience without being party to it.
This is where the discussion becomes much more interesting - “what metrics matter in OpenGov” is an open question and is a part of the intended output. We also connect back into the point of the submission which is a review of the system related to how innovation works. How are we to assess the output of the system?
Let me do one more round of changes based on your feedback, this is a useful feedback loop for all sorts of reasons. |
Thanks @monsieurbulb feel free to ping us once we should take another look. |
Hey you can close this application - will be approaching this stuff in a
different way going forward.
Thanks for the feedback to date.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for the update here. I'm going to close the PR.
Project Abstract
Whilst influential, large ‘public good’ treasuries are just one component in what can be understood as a phased innovation process that should be structured through the full life cycle of R&D, productisation and go to market, with motivations, oversight, rewards and ROI contingent on the phase and the entity involved.
To encourage an innovative culture, we need to understand just how to identify, support and scale that culture through a phased approach that approaches talent, focus and outcomes independently but as part of a cohesive whole, evolving technical, social and meritocratic structures as we go.
The aim of this initial paper is to set context for, and a hopeful path towards a more structured approach to innovation in the ecosystem - beginning at the lowest levels of creative endeavour.
Grant level
Application Checklist
evolving_opengov.md
).