ENS DAO Newsletter #124 - 11/15/2026
Weekly ENS DAO newsletter: two social proposals on the endowment policy and two executable proposals (a roughly 200k USDC working-group funding request and a DNSSEC upgrade) are in discussion, plus the October endowment report.
The newsletter lists two social proposals: IPS Amendment No.1 would let the endowment write fully collateralized options during required ETH/stablecoin rebalances, capped by exposure, tenor and runway safeguards, with Rysk as sole venue pending Board approval; IPS Amendment No.2 would let the ENS Foundation Board amend the endowment policy after a 7-day discussion, replacing MetaGov, while the DAO keeps runway and Section 3 powers. Two executable proposals are listed: funding the Meta-Governance Working Group through Term 7 with about 200k USDC from wallet.ensdao.eth, and upgrading the DNSSEC oracle, registrar and resolver after the 2026 root KSK rollover, adding KSK-2024 and DAO-updatable trust anchors. Reported figures: the October endowment report shows AUM at $90.71M versus $98.70M, ETH allocation down from 59.9% to 45.5%, and $289,177 of monthly yield. The ENS Foundation Board approved a restated 2026 operating budget of $423,028.40 (previously $382,641.04). ENS Labs reported about 29k names migrated to ENSv2. MetaGov logged four October payments totalling roughly $86.7k in USD terms. No temp checks, ENSIPs or commits this week. Open points: outcome of the pending votes and Board approval of the options venue.
Free: this site, which you have to remember to check. Paid: every Monday an email lists the votes closing in the next 7 days, sorted by deadline, then the week's items in full.
Sample of the weekly email
Closing in the next 7 days 1. [dao] Proposal title - vote ends 2026-11-16 - one-line summary 2. [dao] Proposal title - vote ends 2026-11-18 - one-line summary The week in full [dao] Proposal title: full plain-English analysis and flags
10 USDC on Base = 31 days.
- Send 10 USDC on Base to
0xdbe64890cbC58304815A865F63151c205F2C88B2 - Email the transaction hash to saleforce@agentmail.to, which is this project's own inbox. Send it from the address that should receive the digest.
- Access starts when the payment is confirmed on-chain.