Thanks for the mention @cap. This is something that has come up in several Meta-governance calls. Here’s the general context from the calls:
TL;DR: Meta-governance strongly supports increasing delegated vote count and involving more responsible stakeholders.
However, the proposed change would require specific modifications to our OZ governor contract, so we’ve been deliberately measured in our approach to ensure delegates can properly evaluate this potential change. This thread should provide a good opportunity for that discussion.
There have been several proposed changes to the ENS governor discussed over the last 12-18 months:
1. Adding an $ENS token bond as an optional alternative to the 100k $ENS requirement
- Received initial pushback from delegates, though largely based on misunderstandings. Link to discussion
2. Increasing block delay between propose() and vote() functions
- Has consistently received broad support
- Likely to be included in next upgrade
- Initially championed by @bendi and Scopelift
3. Adding implementation to enable Coinbase’s delegated token participation
- This is what we’re discussing in this thread
4. Various routine maintenance/security items from OpenZeppelin
- Specific items previously mentioned by @nick.eth on MG calls
Given that governor upgrades are sensitive operations that we need to minimize, we’ve tried to facilitate individual discussions of each proposed change to determine what should be included in the next upgrade.
This Coinbase delegation enhancement hasn’t yet had a chance for proper open discussion in the forum.
From my perspective as MG steward, I’d like to better understand:
- The technical implementation specifics or contract changes required to enable this feature
- Whether this solution has been successfully implemented on other governor contracts
- What alternative solutions might exist for the Coinbase delegation issue, particularly any that don’t require governor modifications
Personally, while I support the outcome Kent is seeking, I want to understand any risks surfaces it would create before supporting the specific approach.
As always, thank you to @kent and the Agora team for the continued engagement. 