# Agenda and Minutes for Meta-Gov Meeting, November 7th, 2023

### Details

Time: Tuesdays at 11am ET (3pm UTC).
Google Meet Link: [meet.google.com/ihz-hdvb-bbq](http://meet.google.com/ihz-hdvb-bbq)

Stewards: @katherine.eth ([ENS](https://app.ens.domains/katherineykwu.eth) | [Twitter](https://twitter.com/katherineykwu)), @nick.eth ([ENS](https://app.ens.domains/nick.eth) | [Twitter](https://twitter.com/nicksdjohnson)), @5pence.eth ([ENS](https://app.ens.domains/5pence.eth) | [Twitter](https://twitter.com/5pence_eth))

### Agenda

1. General DAO Updates
a. EPs (Executable Proposals)
1. Karpatkey #3
2. WG Funding

b. Social Proposals
1. Expand Terms for Stewards
2. Stream for Service Providers

2. Weekly Endowment Updates
3. Open Discussion
a. Role + Scope for: DAO Engineer
b. DAO Bylaws?

---
Notes by @don.nie (New note-taker, please reach out if you have feedback on the notes)

---
## 1. General DAO Updates

Two Executable Proposals (EPs): Onchain voting which cause on action to occur voted on in Agora! Spread the word for participation please! If you know delegates, please make sure they know.

#### Endowment permissions to karpatkey
Voting for [Endowment permissions to karpatkey](https://agora.ensdao.org/proposals/15706104363492914432572227540113855373051896881975394006732444538096386655538) is live.

#### Working Group Funding
[October 2023 Working Group Funding](https://agora.ensdao.org/proposals/97815480450036429026998617227498389389237567897899533433380564585906006968770) is live!

Will payout grant recipients and ensure that discretionary funding exists to support working groups.

---

Two Social proposals: Social proposals are a temp check!

#### Expand Terms for Stewards

The [Expand Terms for Stewards](https://discuss.ens.domains/t/temp-check-ens-invalid-name-refund-proposal/16824) is here. Biggest change is expanding steward terms to 1 year.

*Discussion:*

A discussion occured on the pros and cons of the length being moved to 1 year. Was acknowledged that it takes time to step into a role and understand the workings of the DAO. 1 Year both ensures continuity and ensures stewards have enough time to fully get into their role. Also noted that if someone steps down as a steward it will trigger an immediate election.

Also discussed was the possibility of staggering elections in the future so the overhead for steward voting occurs every six months.

#### Stream for Service Providers

The [Stream for Service Providers](https://snapshot.org/#/ens.eth/proposal/0x5748982aed143f51333befbc6cc490116648b85a2b0212fdfaf3ab848932c7ae) closes tomorrow!

*Discussion*

Broad discussion around needing to think through who has responsibility for the $3.6m allocated for service providers as well as the governance of allocating the funds.

Nick recommends allocation fall under ecosystem, but changes to the rules fall under Meta-gov. This also gets into having a proper state of bylaws. Nick also recommends, if this passes, the DAO should create a meta-set of rules for governing this allocation of capital. And this could be second set of bylaws after DAO Bylaws. (See notes on bylaws below)

Broadly acknowledged that there should be/ should have been more thinking aroud dates, espcially deadlines given to service providers for submissions.

---
## 2. Weekly Endowment Updates (@karpatkey)


Waiting for stakewise to be on mainnet.
Good news: Published in detail payload decoder script here: https://github.com/karpatkey/payload_decoder_v1 can chat through telegram. Idea is to input json and receive human-readable, auditable, description of transaction.


Still increasing rETH exposure. Capital Utilization up from last week. Working to get to 100% capital utlization. Any questions feel free to ask

---
## 3. Open Discussion
**Role + Scope for: DAO Engineer**

Team wanted someone to help out Greg as felt was asking him to do too much.
Update: Testing out-sourced dev resources to support Greg 1x Day/week for 3 months as part of a trial.

**DAO Bylaws**

Discussion centered around the need to create Bylaws to help the DAO govern itself. This so everyone in the DAO knows the current state of rules, potential changes to rules, and has a broad set of rules to follow in the responsibilities of their job.

This GovNerd from Optimism was given as an example: https://github.com/ethereum-optimism/ecosystem-contributions/issues/109

Nick both recommended creating an RFP to have a service provider (legal) create a set of bylaws for the DAO to vote on. Nick agreed to create a simple RFP as an action item following the call.

A discussion also centered around the need for a role (part-time) to handle the governance of the bylaws.

---
#### Stay up to date on active ENS DAO proposals by subscribing to the 'notification-only' [Telegram channel](https://t.me/ensdao_notifications).