Introducing the Cosmos Governance Working Group

I’ve created a Telegram group here: https://t.me/hubgov

2 Likes

I would like to suggest an idea for the proposal to be initiated from multisig account. This way there will be some accountability to funds and they could be sent back to the community pool if the efforts hault

5 Likes

I suggest an alternative version of your proposal with below adjustment

  1. removing gwg(some of us think it is too centralized). Instead, all discussions on governance should be reorganized in forum posts.

  2. reduce hourly payment price 30%(to prevent excessive spending of pool in future)

  3. add additional work on “community pool spending governance committee” white paper including rough mechanism inside sdk(not technical)

Purpose of this suggestion is to increase the probability of grant pass by negotiating contents so that more members of community can agree on.

I want to make sure that it is gavin’s entire decision whether accept/negotiate/decline my suggestion.

1 Like

Fantastic work Gavin! I love it. I will continue to dig in, but at first glance I am in full favor.

1 Like

Hey Mira, interesting idea, particularly for large, multistage proposals. If this proposal was for a period greater than a single quarter, i would be exploring a multisig option. My preference is to push the proposal without multisig since the amount and time period seem small enough that I think the voting community will trust me and my team to deliver.

Would you be interested in working on exploring how future proposals could benefit from a multisig option? We would first need to explore how to create a secure multisig. I imagine that we’d need to explore selection criteria for trusted signatories, potential processes for deciding to release the funds or not. There should be a process for returning the funds if need be, since my understanding is that funds cannot currently be deposited into the community pool. I envision the GWG lobbying protocol developers to design and implement this particular functionality.

Hyung, thanks for further feedback!

  1. The GWG is the name of the community, which should not be limited to the Telegram channel that I’ve created.

My plan is:

a) to encourage high quality discussions to happen here, on All in Bits’ Cosmos Discourse forum (which is currently a somewhat centralized option), and I’d love to encourage other, more decentralized platforms. For now I’m trusting the employees at All in Bits to safeguard our discussions.

b) to use the Telegram group for real-time chat (and alerts to nee forum replies). I’m making a published list of participants so that everyone involved can reorganize in another channel that I don’t control if needed.

I will update the proposal to reflect this plan clearly, since I overemphasized the Telegram group. Thank you for pointing this out.
I think the GWG community component of this proposal is one of the most valuable parts, so i’m not prepared to remove it from the proposal. Please feel free to openly engage with me further about this, though.

  1. Is the only reason that you’re asking us to reduce the amount of our community spend proposal is prevent future community spending in excess? My prior understanding was that you agreed that this was a reasonable amount. Would be grateful for a more detailed explanation.

  2. I can see a need for a committee to make value-judgment-based recommendations about proposals, but I think it’s too soon for this. My initial position is that the basic framework for governance should be developed first. I would love to explore this further with you and others, and I could see it as a potential deliverable for Q2. Thoughts?

Thanks again, I always value our discussions.

Figment should not cut down on the hourly payment. Gavin’s time is being valued at $1000 per day for an 8 hour working day (assuming atom exchange rate of $4.25). That looks well aligned for contract work.

In a different post, BHarvest mentioned they were proposing to take a loss on some project. That is the wrong approach - work should be profitable for every grantee. If we establish a culture where work is expected to be unprofitable, the best teams won’t come forward with proposals.

My bias is to fund well thought-out, high value (to the Hub), properly compensated work.

3 Likes

I’ve pushed this proposal live on mainnet: https://hubble.figment.network/cosmos/chains/cosmoshub-3/governance/proposals/23

It’s open for deposits. Please help spread the word: https://twitter.com/FigmentNetworks/status/1217341645735284736

I agree with you that our approach was too conservative for its price. That is partly caused by relatively high risk of governance proposal rejection loss on deposit. We compare the pricing with ours, which is 1/4 of Gavin’s pricing. If we double our pricing, it is still twice expensive than ours.

So this makes us feel quite unrealistic about the grant pricing. Maybe I am not quite familiar with US grant pricing standard. Hope other 3rd parties can provide more opinions on pricing.

1 Like

Hi. Reorganization of Telegram discussion is a heavy job, so it should be paid to do that. I think it would be wonderful if you can reorganize such communication and share it on forum. I think it should be core reason why community pass this grant, rather than just opening a telegram chatroom because most of us will not read entire threads, and a lot of community members will not be in the telegram chatroom.

2 Likes

Thanks Hyung. This does raise an important question: Global rates for contract work are different.

$1k a day is fine for the US. My other experience is in India where $200 per day is an amazing offer. What kind of rate is admissible for the Cosmos Community Pool? Do we adjust geographically?

1 Like

My thinking is that we should evaluate the proposed work and also the reputation of the recipient. Doesn’t make sense to me to pay organizations and their people differently based upon where they live.

This is currently how I plan to evaluate community spends when I vote: is this proposal worth the cost? If so, vote yes. If not, vote no. If very much the latter, no with veto. No idea? Abstain.

2 Likes

This proposal is live and in the voting period: https://hubble.figment.network/cosmos/chains/cosmoshub-3/governance/proposals/23

I guess US is good enough for standard pricing. Because it is global community without any national barrier, geographical adjustment is not necessary.

Accepting Meherroy’s reference on US consulting pricing, I now can accept the pricing on this governance. Also, we would like to vote yes on this governance to not block high quality contribution intention.

But I still hope Gavin does some summary work from discussions on Telegram and posts on forum, to prevent centralization and intransparency of governance discussion. Definitely nobody can do it without funding.

1 Like

The Telegram channel is only there to serve as real-time, fluid chat. I think that anything substantial should be detailed on the forum, and I’ll encourage participants to do that. If they don’t, I will endeavour to on their behalf. Really appreciate your feedback.

Participating discussion itself is enough contribution. We cannot ask them to write down in forum for free. Some might do for free, but I think rest is the responsibility of who is funded. Could you clearly state the respond because it will affect my vote.

Detail explanation is to read All threads in telegram chat and reorganize opinions in forum post.

It is what dogemos has been done to community for entire topic for about a year with much less funding.

2 Likes

My priority will be completing the deliverables, and I intend to go above beyond those. I think that documenting on the forum is a good suggestion (thanks!). I’ll endeavour to do this, but I can’t update the proposal to reflect that and I cannot guarantee that I will able to keep up with transcribing from the Telegram channel to the forum.

Some comments on the milestones:

  • Proposal is focused around best practices for proposals on parameter changes and community spend. There are other possible types of proposals, such as chain upgrades, vision for hub etc. Will best practices for such proposals be tackled at a later stage or will we also attempt to address these?
  • The milestones come with very specific deadlines, which will probably be hard to maintain due to general lag in getting feedback (including this specific feedback). Some of the deadlines occur before the voting for the proposal is actually over and before the date for the first GWG call. I would suggest that as part of the best practices we should account for this by ensuring that deliverable dates start after the proposal has passed, to allow for meaningful feedback to be incorporated.
1 Like

Yes, though I imagine that chain upgrade proposals will become much simpler once the module for on-chain upgrades is active on the Cosmos Hub. I don’t know what role the GWG should have in terms of the Hub’s vision–I look forward to discussions about the GWG’s political role.

Would love to chat more with you about deadlines vs voting period & feedback. I see these deliverables as living documents that will likely need many revisions as the culture and technology develop.

I don’t think we need adjust by geographically. but there should have a competition, for example, if my budget is 10k for a project and other team can do this project in extremely low price, say 5-6k, then they will get funding.

3 Likes