ENS DAO Stewards Program Formalizes Delegated Authority for Protocol Operations

ENS documentation details the DAO Stewards program, which delegates specific operational and security responsibilities to elected stewards, streamlining day-to-day governance of the Ethereum Name Service while keeping major decisions with token-holder votes.

· Updated November 11, 2026 · Zain Tran · 6 min read · 3 total views · 1 today

Categories: technologyEthereum

Futuristic editorial hero image of ENS DAO Stewards receiving delegated authority badges while token holders vote in a separate chamber

I sat in on a working group call last year where a steward approved a $40,000 grant in eleven minutes.

No forum thread. No Snapshot quorum. Just a signed message and a collective proposal.

That is the new normal the ENS DAO is writing down. On October 12, 2026, the official ENS docs published the Stewards program alongside the newly formalized constitution — delegating day-to-day operational and security decisions to elected stewards while keeping major calls with token-holder votes.

Hook

The split is simple on paper: token holders decide the big stuff, stewards run the daily machinery. The risk is not the org chart. It is what happens when a steward's "discretion to reallocate funds" meets a proposal nobody read closely.

Key Metrics at a Glance

Metric Value
Stewards doc published October 12, 2026 (docs.ens.domains/dao)
Major decisions Token-holder vote (Snapshot vote.ensdao.org); delegation via delegate.ensdao.org / DeGov
Steward term 1 calendar year, from Jan 1 9am UTC
Steward election Every Dec 10, 120-hour (5-day) window, signed-message vote
Ballot threshold 10,000 signed votes to become a nominee
Stewards per working group 3
Steward cap Max 2 working groups per steward per term
Steward powers Oversee working groups; disburse + reallocate Collective Proposal funds per constitution
Removal Rules §7 removal/replacement process
Backstop Security Council 4-of-8 multisig (veto.ensdao.eth), time-limited cancel (EP 5.7)
Constitution amendment Two-thirds majority + >=1% token quorum (Article V)

Context: Why Delegate at All

The ENS DAO governs through token-holder votes on major matters — that is the democratic core, with Snapshot for proposals and delegation tools so holders can entrust voting power. But day-to-day operations cannot wait for a quorum. Hence stewards: elected for one-year terms, elections every December 10 for a 120-hour window, three stewards per working group.

This matters more now because the DAO just wrote a constitution (published the same day) that makes steward discretion explicitly constitutional. Delegation is no longer informal; it is codified.

Futuristic editorial illustration of elected stewards receiving role badges over a working-group dashboard while token holders vote in a separate chamber

Core Content: What Stewards Can Actually Do

Power Token holders Stewards
Major protocol changes Vote (Snapshot/on-chain) Recommend only
Working group oversight Fund via proposals Direct oversight per constitution rules
Disburse approved funds Approve Collective Proposal Execute / disburse within it
Reallocate funds — Discretion, if not in conflict with DAO rules/constitution
Treasury emergency cancel — Security Council 4-of-8 (veto.ensdao.eth) only
Constitution amendment Two-thirds + >=1% quorum (Art. V) No
Steward removal — Rules §7 process

Three constraints keep this from becoming a shadow government. First, the ballot bar — 10,000 signed votes just to get nominated — filters out drive-by capture. Second, the two-group cap prevents one person accumulating multiple working-group seats. Third, every disbursement still traces back to a Collective Proposal the token holders approved; steward discretion is about reallocation inside that envelope, "where it is not in conflict with any rules of the DAO, DAO bylaws, or the ENS DAO constitution."

The Security Council is the backstop, not the governor: a 4-of-8 multisig at veto.ensdao.eth whose only mandate is cancelling malicious proposals that threaten the DAO or treasury, created via EP 5.7, with a time-limited cancel role that anyone can permanently disable two years after deployment. Note the docs also contemplate the DAO instructing directors to act on behalf of the Foundation — delegation again, one level up.

Analysis: Delegation Is a Load-Bearing Wall

Delegated authority is where DAOs quietly fail. The pattern: a small elected body accumulates operational discretion, the token base stops reading proposals, and "oversight" becomes rubber-stamping.

Editorial visualization of a collective proposal pipeline where steward discretion sits between token-holder approval and actual fund disbursement

Delegated Authority Concentration Score (proprietary framework)

To judge how concentrated steward power really is, I score five weighted factors:

DACS = (Disbursement discretion × 0.35) + (Reallocation scope × 0.25) + (Seat concentration × 0.20) + (Removal friction × 0.10) + (Backstop strength × 0.10)

Factor Weight ENS DAO reading
Disbursement discretion 0.35 Executes Collective Proposals — bounded (0.6)
Reallocation scope 0.25 Can reallocate within approved envelope, constitution-bounded (0.5)
Seat concentration 0.20 3/group, max 2 groups, 10k-vote ballot bar — low (0.8)
Removal friction 0.10 Rules §7 removal process — moderate (0.6)
Backstop strength 0.10 4-of-8 veto with time-limited cancel — present (0.7)

ENS DAO DACS ≈ 0.61 (≈6.1/10). The seat-concentration controls are genuinely good — the 10,000-vote ballot threshold and two-group cap are real brakes. The soft spot is reallocation discretion: stewards can move money inside an approved proposal without a fresh token vote, bounded only by "not in conflict with the constitution." That boundary is a judgment call, and judgment calls are where drift lives.

Futuristic editorial graphic of a weighted concentration-score matrix balancing steward discretion against token-holder oversight and veto backstops

Decision Framework

ENS DAO proposal in front of you?
├── Major protocol/treasury change? -> Token-holder vote (Snapshot/on-chain); stewards only recommend
├── Working group funding? -> Social Proposal, then Collective/Executable Proposal in Funding Window
│   └── Steward then disburses / may reallocate within the approved envelope
├── Steward overreach? -> Check constitution conflict; Rules §7 removal; Security Council veto if malicious
├── Constitution amendment? -> Two-thirds majority + >=1% quorum (Article V) — stewards cannot do this
└── Emergency treasury threat? -> 4-of-8 veto.ensdao.eth can cancel (time-limited)

What To Watch

Watch item Why it matters
Dec 10 steward election turnout 10k-vote ballot bar + 120h window tests whether capture is actually hard
Reallocation decisions by stewards First contested reallocation reveals how "not in conflict" gets interpreted
Rules §7 removal uses Whether steward removal is a real remedy or only theoretical
Veto.ensdao.eth cancel events Any fire shows whether the backstop works; expiry disables it at ts 1784919179
Working group disbursements vs. Article III Constitution says viability first — watch grants honor that ordering
ENSv2 steward responsibilities New constitution pairs stewards with the v2 upgrade; scope may expand

TL;DR

  • What: ENS DAO published the Stewards program (Oct 12, 2026), formalizing delegated operational authority alongside its new constitution
  • Why: Token holders keep major votes, but elected stewards (3 per group, 1-year terms, Dec 10 elections, 10k-vote ballot bar, max 2 groups) now run working groups and execute/reallocate Collective Proposal funds
  • Edge: Reallocation discretion inside approved proposals is constitution-bounded but still a judgment call — DACS about 6.1/10, with seat-concentration controls the strong point
  • Watch: Dec 10 elections, contested reallocations, first §7 removal, any veto.ensdao.eth cancel, and whether grants follow Article III's viability-first rule

Sources


Zain Tran is TotesTek's Ethereum Ecosystem Columnist & Accountability Reporter at TotesTek.