How ENS Community Call Works: Everything You Need to Know

The Ethereum Name Service (ENS) ecosystem relies on decentralized governance, and the ENS community call is a critical mechanism for aligning stakeholders, discussing proposals, and steering protocol upgrades. Unlike traditional corporate meetings, ENS community calls operate on transparent, permissionless principles, enabling any token holder, delegate, or developer to participate. This article provides a methodical breakdown of how these calls function, what to expect, and how to maximize your involvement.

ENS community calls are not optional rituals—they are the primary forum where governance proposals transition from ideas to executable smart contract actions. Understanding their mechanics is essential for anyone holding ENS tokens, running a subname resolver, or building on the protocol. Below, we dissect the call lifecycle, participation requirements, voting integration, and technical infrastructure.

Call Scheduling and Agenda Formation

ENS community calls occur bi-weekly on a fixed schedule, typically announced via the ENS governance forum (forum.ens.domains) and the official ENS Discord server at least one week in advance. The schedule aligns with major ecosystem events, such as EIP implementations or the release of new registrar features. Each call uses a standardized time slot—14:00 UTC on Thursdays—to accommodate global participation, though special emergency calls may be convened for time-sensitive issues like security patches.

The agenda is crowdsourced from the community. Any delegate or token holder can submit a topic by posting a thread in the "Community Call Proposals" category on the forum. The ENS Foundation team curates submissions based on relevance, urgency, and alignment with the current governance cycle. Typical agenda items include:

• Review of pending ENS Improvement Proposals (ENSIPs)
• Updates on registrar contract upgrades
• Subname rental pricing adjustments
• Integration discussions with Layer 2 solutions

Once finalized, the agenda is published as a pinned message on Discord and mirrored on the ENS blog. Participants are expected to review pre-read materials—smart contract diffs, forum discussion summaries, or draft documentation—before joining the call. Failure to prepare can result in inefficient discussions, as the call prioritizes decision-making over education.

Technical Infrastructure and Access

ENS community calls use a decentralized, censorship-resistant stack. The primary call platform is a customized instance of Jitsi Meet, hosted on a dedicated server operated by the ENS Foundation. This choice avoids reliance on centralized providers that could throttle or log communications. Participants join via a direct URL distributed through the ENS Discord and governance forum. No registration or KYC is required—only a Web3 wallet (e.g., MetaMask, WalletConnect) for identity verification during voting segments.

For accessibility, the call also streams live to a public YouTube channel with an embedded chat interface. Viewers watching via YouTube cannot directly speak but can submit text questions, which the moderator reviews during Q&A segments. The ENS Foundation recommends using a wired internet connection and a modern browser (Chromium-based or Firefox) to avoid WebRTC compatibility issues. Audio quality is critical, as many participants rely on real-time updates during protocol transitions. If you miss a live call, full transcripts and archives are published on the ENS documentation portal within 48 hours.

An important governance feature integrated into the call stack is the ability to lock subname rights or delegate voting power during the session. For example, if a delegate wants to ensure their vote on a specific proposal remains consistent, they can use the ENS lock subname feature to prevent any accidental transfers or changes to their name record while the call is in progress. This lock is temporary—typically lasting until the call ends or the related proposal timer expires—and is automatically released after 24 hours or upon manual unlock via the ENS app.

Call Structure and Participation Rules

Each ENS community call follows a rigid structure to maintain focus and prevent dominance by loud minorities. A typical 60-minute call is divided into five segments:

1. Opening (5 minutes): The moderator—usually a member of the ENS Foundation or an elected steward—reviews the agenda, confirms quorum, and states the ground rules. Quorum requires at least 15 verified delegates or addresses holding a total of 100,000 ENS tokens in voting power.
2. Proposal Presentations (25 minutes): Each agenda item gets a 5-minute presentation from the proposer, followed by a 5-minute open discussion. Proposers must share their screen or link to a pre-prepared deck. Discussions are time-boxed; the moderator enforces a 90-second speaking limit per participant using a "stack" system—similar to a doorkeeper in parliamentary procedure.
3. Voting and Signaling (15 minutes): For binding votes, the call transitions to an on-chain polling phase. Participants cast votes via a dedicated Snapshot space linked from the call UI. Only votes from wallets with locked ENS tokens or delegated voting power count. Off-chain signaling (thumbs up/down in Jitsi) is used for non-binding suggestions.
4. Open Floor (10 minutes): Unstructured Q&A where any participant can request the floor. The moderator prioritizes delegates who have not spoken during the call. This segment often involves technical deep dives, such as gas optimization strategies for name registrations.
5. Closing (5 minutes): Summary of decisions, action items, and deadlines for the next call. The moderator announces the next call date and any emergency procedures.

Participation rules are enforced by a bot that tracks speaking time and wallet verification. Any participant who interrupts or exceeds time limits receives a verbal warning. After three warnings, the moderator can mute the participant for the remainder of the call. The bot also logs attendance for governance rewards, which are distributed quarterly to active participants.

Voting Mechanics and Proposal Lifecycle

ENS governance operates on a two-phase voting system, and community calls serve as the bridge between phases. Phase 1 is "Temperature Check"—a non-binding vote on the ENS governance forum that typically precedes a call. Phase 2, "Consensus Check," occurs during or immediately after a community call. For a proposal to pass, it must achieve both a 10% participation threshold (measured against total delegated ENS supply) and a 60% majority. If the proposal involves smart contract changes, a third "Execution" phase follows, where a timelock contract enforces a 48-hour delay before implementation.

During the call, the moderator displays a live Snapshot dashboard showing real-time vote tallies. Participants can change their votes multiple times during the voting window, which typically stays open for 2 hours after the call ends. This flexibility allows delegates to adjust positions based on new information shared during discussions. The ENS Foundation provides real-time updates on vote progress via a dedicated Telegram bot and the ENS status page. These updates include granular data: vote share per delegate, yes/no percentages, and estimated time to quorum.

For technical proposals—such as modifying the subname registrar or adjusting pricing curves—the community call includes a mandatory code review segment. At least one auditor from the ENS Foundation or a third-party security firm (e.g., Code4rena) must attest that the proposed smart contract code has no critical vulnerabilities. This audit report is shared via a shared Google Doc during the call, and delegates can request a walkthrough of specific lines of code. This practice has prevented at least two critical bugs in the past year, including a flawed rental fee calculation for short-duration subnames.

Post-Call Actions and Accountability

After the call concludes, the Foundation publishes a formal decision log within 24 hours. This log includes vote results, action items, and links to related forum posts. Delegates who voted against a passed proposal can file a "Dispute Notice" within 72 hours, which triggers a special community call to reconsider—though this mechanism has only been used twice in ENS history. All call recordings, transcripts, and voting data are stored on IPFS for permanent, censorship-resistant archival.

For proposals that require code deployment, the ENS engineering team commits the changes to the ensdomains/ens-contracts GitHub repository within one week. A merge requires at least two approvals from core contributors and a successful run of the full test suite. The community can track deployment progress via the "Eth2" status board, which indicates whether the changes are in staging, on testnet, or on mainnet.

Accountability extends to participants themselves. ENS publishes a monthly "Delegate Scoreboard" that ranks delegates by call attendance, voting consistency, and proposal quality. Low-performing delegates risk losing their delegated voting power if they fail to meet a 30% attendance threshold over a six-month period. This system incentivizes active, informed participation and prevents governance capture by absentee token holders.

Best Practices for First-Time Participants

If you are new to ENS community calls, follow these steps to maximize your impact:

• Pre-register your wallet: Verify your ENS token holdings on the Snapshot space at least 24 hours before the call. Late verification may lock you out of voting.
• Review the agenda: Read the associated forum threads for each agenda item. Focus on "Consensus Check" proposals, as these determine binding outcomes.
• Configure your environment: Use a desktop browser (Jitsi on mobile does not support screen sharing). Close background applications to reduce bandwidth noise.
• Test your microphone: The bot performs a 10-second audio check at call start. Ensure your input device is unmuted and free of echo.
• Use the "stack" system: When you want to speak, type "/hand" in the Jitsi chat or raise your hand virtually. Wait for the moderator to call your name.

Remember that ENS community calls are not spectator events. Every participant has the power to shape the protocol's future—whether by proposing a new ENSIP, questioning a delegate's reasoning, or simply casting a vote. The system is designed to be transparent and meritocratic, but it requires your active engagement to function effectively.