$CREAM MetaGovernance Delegation

[Kiba]

Delegate Address

My bad, I assumed we could delegate per space since Snapshot enables that functionality. Getting delegation strategy added can be done easily if Coop wants to move forward with this, CREAM hasn’t had the need yet but we are updating governance params anyway so can slide in with other updates. Is your governance bot open-source so I can figure out a way to add multiple sources for vote decisions?

Committees

Sub-committees is how almost every part of the Coop is run already. I gave some reasons why this model is suited specifically for metagovernance in the original IIP post - IIP-8 Meta Governance Module - #2 by Kiba.

@dylan

We have the Treasury Committee structured similarly for some of the same reasons. Having a fairly autonomous sub committee subject to checks and balances makes it much simpler to interface with the coop as a third party. We’ve seen similar sub committees when interfacing with Maker DAO for example.

We have so much voter apathy that we are trying to pay people to vote. Even then they say sub-committees are a good option to consider over INDEX holders

@DarkForestCapital

Governance structure including committee/council/delegates to have the most motivated and closest to the project accrue voting power

Wallet Security

@ncitron

Delegating these votes to a normal metamask account that exists on someone’s personal computer would be a massive security risk

Lol definitely not holding 5k INDEX tokens on metamask. I have multiple hardware wallets of which this is my designated “governance wallet” for the most recent DAOs I joined. Most people would agree a hardware wallet is more secure than a hot wallet (which I assume your bot is using). Moot point either way since not possible to have multiple wallets (yet).