🏛️📞 MetaGov Working Group – 2025 Meetings: Tuesdays at 2pm UTC (Currently 10:00 am ET)

cap · June 24, 2025, 5:18pm

Time: Tuesdays at 10:00 am ET (2pm UTC).
Google Meet Link: meet.google.com/bms-grvp-jbw

Stewards:

—

Endowment at $87M – 28% stables, 72% eth
Last week was a volatile week, mainly driven by geopolitical tensions between Israel and Iran.
Bitcoin dominance keeps climbing. It’s above 65% and steadily growing day after day.
Exited the Rocket Pool aura pool because it was yielding less than the LSTs
Sky keeps being the highest allocation of the endowment right now
Weekly commentary:

A lot of discussion was done on this topic
Proposal to establish a committee to do due diligence on the deal
Committee will investigate Openbox’s plans, financials, and open-source aspects and come back with a report on whether we should invest or not.

TL;DR – Tally proposes a formal enterprise-level service agreement that elevates ENS governance UX, broadens the distribution of ENS primitives across all governance users on Tally, and furnishes the DAO with battle-tested uptime, reporting, and support guarantees.
Three scopes of work: webhooks, deeper ENS integration/distribution, and enterprise support levels.
Tally’s proposal is complementary and more in-depth than Denison’s post on programmatic tooling rewards.
It was suggested that MetaGov could request funding from the DAO to pay Tally, similar to how they request funding for other needs.
The suggestion of an RFP (Request for Proposal) was brought up.
- The DAO could work with Tally for a year or so, similar to the arrangement with Agora, and then potentially collaborate with other providers.
The title of the proposal may be misleading, as “dedicated governance provider” does not imply exclusivity.
Funding should follow clear DAO signals and focus on proven needs, not assumptions or features without demonstrated demand.
Proposals should be motivated, evidence-based, and distinguish genuine community needs from self-promotion, as setting the wrong precedent could invite low-signal ideas.

Hats Protocol enables onchain role management using programmable “hats” to build secure, cost-efficient DAOs and manage dynamic organizational structures.
Integration with Safe allows DAOs to control multisigs via Hats modules, automating onboarding, compliance, and signer status programmatically.
Enforceable Requirements, like ENS token holdings, can be used to automate access and removal of multisig signers, enhancing accountability and flexibility.
DAO Control is emphasized—DAOs can update multisig roles onchain, minimizing risks of stuck multisigs and allowing responsive governance.
Role Reusability across multiple multisigs simplifies transitions; a single “hat” can represent permissions across systems without managing separate addresses.
Additional Permissions through hats (e.g., forum badges, Telegram access) extend utility beyond just multisig signing, enabling trusted coordination.
Risk Mitigation includes concerns over multisig lock-in or collusion when one person holds multiple hats—Hats offers mechanisms to adjust signers.
Fractal Hat Structure allows nested roles and delegated admin control.
Future-Proofing includes immutable smart contracts, decentralized indexing, DAO governance of Hats, and potential for ENS to white-label the UI.