Provide a narrative description of the purpose of the project.
Disclaimer: This Token Transparency Filing is prepared by ENS Labs Ltd., a Singapore company limited by guarantee, speaks as of August 4, 2026, and is provided for general informational purposes only. Neither ENS Labs Ltd. nor Blockworks makes any representations or warranties, express or implied, regarding the accuracy, completeness, or timeliness of the information provided, and each disclaims liability for any errors or omissions in the content or for any actions taken in reliance on this content.
This filing does not constitute an offer to sell or a solicitation of an offer to buy any securities, tokens, or other financial instruments, and should not be construed as investment, legal, tax or other professional advice.
ENS Labs Ltd. undertakes no obligation to update or revise this filing except as required by applicable law.
(a) Problem the project solves
ENS is the most widely used decentralized naming protocol on Ethereum that maps human-readable names such as alice.eth to machine-readable identifiers including Ethereum addresses, other cryptocurrency addresses, content hashes, metadata, and more, which improves the usability of blockchain addresses and online identity (https://basics.ensdao.org/about-ens; https://docs.ens.domains/learn/protocol/).
(b) Operational priorities
Public materials show that ENS prioritizes operating a durable naming system, funding ongoing development, and supporting community-led growth. ENS says more than 35 million names have been registered directly (e.g., .eth domains) or through ecosystem name systems like Base, Uniswap and World. The ENS constitution says income generated to the ENS treasury is to be used first to ensure the long-term viability of ENS and to fund continuing development and improvement of the ENS system, with excess funds available for other web3 public goods (https://basics.ensdao.org/about-ens; https://docs.ens.domains/dao/constitution/).
(c) High-level project overview
ENS is a distributed, open, and extensible naming system on Ethereum in which top-level domains such as .eth are managed by registrar smart contracts, registrations are executed through smart contracts, and ownership is secured by Ethereum (https://docs.ens.domains/learn/protocol/). The ENS registry is the core contract at the heart of ENS resolution; all ENS lookups start by querying it, and the registry records the owner, resolver, and TTL for each domain (https://docs.ens.domains/registry/ens/). ENS also supports reverse resolution and importing DNS names through DNSSEC, while .eth names can be used for websites and web3 sign-in flows (https://docs.ens.domains/learn/protocol/; https://basics.ensdao.org/about-ens).
(d) Primary token functions
The $ENS token is an ERC-20 governance token on Ethereum used to govern key components of the ENS protocol, and each token represents one vote in the DAO (https://basics.ensdao.org/ens-token). Holders can delegate voting power of their tokens to delegates, who can submit and vote on proposals related to protocol changes, governance and treasury management (https://basics.ensdao.org/ens-token; https://docs.ens.domains/dao/governance/process/). The only official governance token for ENS DAO is token.ensdao.eth on Ethereum mainnet (https://docs.ens.domains/dao/token/).
(e) Control surface reliance
ENS is governed through the ENS DAO, which governs the ENS protocol and treasury (https://docs.ens.domains/dao/). ENS holders cannot vote or create proposals until they delegate their voting rights, and delegation does not lock tokens. Submission of social proposals requires a minimum of 10,000 delegated ENS through off-chain Snapshot voting, while submission of executable proposals requires a minimum of 100,000 delegated ENS through the on-chain Governor contract. Executable proposals are subject to a seven-day voting period and a minimum two-day timelock (https://basics.ensdao.org/proposals; https://docs.ens.domains/dao/proposals/submit/). Public sources also show treasury and registry control concentrated in DAO-linked contracts: the ENS Registry is owned by the ENS Root, which is owned by the ENS DAO Wallet, and registration revenue goes to smart contracts controlled by the ENS DAO (https://docs.ens.domains/registry/ens/; https://basics.ensdao.org/protocol-revenue).
The ENS governance model may continue to evolve through tokenholder-approved proposals submitted through the ENS DAO’s public governance process. The relevant proposal was approved by tokenholders on August 8, 2026, Next Era of ENS DAO: Empowering the ENS Foundation(https://discuss.ens.domains/t/draft-executable-next-era-of-ens-dao-empowering-the-ens-foundation/22329). The proposal transferred administrative control of the ENS DAO’s endowment to the ENS Foundation, together with related intellectual property arrangements, while the operational wallet, DAO-held ENS tokens, and protocol control remain with ENS tokenholders.
For each existing entity: Labs/DevCo (e.g., Founder, CEO, CTO, COO), Foundation (e.g., President, Executive Director, CFO, COO), and DAO / onchain governance leadership (if applicable) list the:
For any non-existent entity, explicitly mention it does not exist. External links may be included but they will not factor into the score.
Full Name | Official Title | Prior Experience |
|---|---|---|
Nick Johnson | Founder | Nick Johnson founded ENS in 2017 (https://basics.ensdao.org/about-ens). He was a software engineer at Google, became a core contributor at the Ethereum Foundation, and worked on Swarm before developing the naming system that became ENS (https://ens.domains/blog/post/beginners-guide-to-ethereum-and-ens). |
Jeff Lau | CTO | Jeff Lau is a cofounder of ENS and CTO at ENS Labs. He joined the ENS team in 2017 building and leading the first two iterations of the ENS app. From there he has contributed to the core ENS smart contracts before transitioning into leadership and technical strategy for ENS. |
Katherine Wu | COO | Katherine Wu is the Chief Operating Officer of ENS Labs, where she oversees the company’s growth initiatives, strategic direction, and operations. Previously, she was the Senior Lead at Coinbase Ventures, where she led investments and played a key role in establishing it as one of the most active corporate venture funds. Katherine has over a decade of experience spanning legal, investment, and advisory roles, working with premier projects and industry-leading companies in the web3 space. Before Coinbase, Katherine was a Principal at Notation Capital, an early-stage venture capital firm, and was the first business hire at Messari, a leading provider of crypto market intelligence products. |
Full Name | Official Title | Prior Experience |
|---|---|---|
Alex Van de Sande | Director | Alex Van de Sande was an early member of the Ethereum Foundation, where he worked on design and user experience for Ethereum (https://vandesande.design/) |
Kevin Gaspar | Director | Kevin Gaspar (validator.eth) is a long-time Ethereum and ENS contributor, involved with Ethereum since 2014 and ENS since its launch. He works on ecosystem and community initiatives at ENS Labs, runs ENS Fairy, and serves on the ENS DAO Security Council (https://discuss.ens.domains/t/6-47-social-proposal-for-a-new-security-council/22219/14). |
Nick Johnson | Director | Nick Johnson was a software engineer at Google, later joined the Ethereum Foundation as a core contributor, and worked on Swarm before spinning ENS into an independent organization (https://ens.domains/blog/post/beginners-guide-to-ethereum-and-ens). |
Full Name | Official Title | Prior Experience |
|---|---|---|
Nick Johnson | Council Member | Founder of ENS |
Hudson Jameson | Council Member | Ethereum Foundation (2016–2021): coordinated network upgrades; emergency response team for on/off-chain security events. |
Pablo Sabbatella | Council Member | Founder, Opsek — operational security audits/training for Web3 orgs (Optimism, Electric Capital, Sky, and 50+ others). |
Colton Liberacki | Council Member | Governance Lead KPK |
Alex Van de Sande | Council Member | ENS Foundation director for several years. |
Griff Green | Council Member | Previous member, ENS Security Council. |
Alex Netto | Council Member | Previous member, ENS Security Council. |
Kevin Gaspar | Council Member | ENS Foundation director since Oct 2021 (4+ years); fiduciary responsibility for the DAO's legal entity, executing DAO instructions and signing agreements on its behalf. |
Provide a structured description of the DAO's governance, powers, and economic rights. If a DAO does not exist, state so for each sub question. Even if there is no DAO, there must be an answer to (d). Address the lettered items below.
ENS DAO exists and exercises governance authority over specified ENS protocol contracts and ENS DAO treasury through tokenholder-approved proposals (https://docs.ens.domains/dao/).
The ENS trademark portfolio is held by ENS Labs Ltd. on behalf of the DAO (see Item 5(b)), and the core ENS repositories are maintained by ENS Labs and published under open-source licenses. Control of the protocol's core onchain assets rests with the DAO as described in Item 3(b): the ENS Registry is owned by the ENS Root, which is owned by the ENS DAO Wallet, and registration revenue flows to contracts the DAO controls. The core ENS contracts and libraries are published under open-source licenses (principally MIT), as described in Item 3(b). Under the active on-chain executable proposal, Next Era of ENS DAO: Empowering the ENS Foundation (see Item 1(e)), registered intellectual property associated with the ENS project, including trademarks currently held by ENS Labs Ltd., is anticipated to be consolidated in the ENS Foundation, subject to approval through the DAO governance process.
Pause roles: none exist. The core ENS contracts contain no pause function.
Upgrade roles: none exist as admin keys. The core contracts are not upgradeable proxies; protocol changes are made by the DAO replacing components (for example, adding or removing .eth registrar controllers or changing resolvers) through an executable proposal, which requires 100,000 delegated ENS to submit, a 1% quorum, majority approval, a seven-day voting period, and a minimum two-day timelock (https://docs.ens.domains/dao/governance/process/).
Powers of the named contracts: wallet.ensdao.eth is the DAO's timelock and treasury wallet; it executes passed proposals, holds DAO operating funds, and owns the ENS Root, which owns the ENS Registry, giving the DAO control of TLD ownership and .eth registrar configuration, including pricing. token.ensdao.eth is the $ENS token contract; as its owner, the DAO may mint up to 2% of total supply no more than once per year, and no other party can mint (https://basics.ensdao.org/ens-token). governor.ensdao.eth is the Governor contract; it receives proposal submissions and delegate votes and queues passed proposals into the timelock, and holds no funds or protocol powers of its own. The Security Council is a 5-of-8 multisig whose sole power is cancelling queued timelocked proposals it deems malicious; it cannot propose, amend, or initiate governance actions (https://docs.ens.domains/dao/security-council/).
ENS holders cannot vote or create proposals until they delegate, and delegation does not lock tokens. Tokenholders may delegate voting power to themselves or another address and may change their delegate. Voting and proposal-submission rights depend on delegated voting power and the applicable governance thresholds (https://docs.ens.domains/dao/governance/process/). No locking or staking mechanism confers additional rights.
ENS governance is proposal-based. Executable proposals are proposals for smart contract operations executed by accounts the DAO controls, and they have a 1% quorum requirement, with minimum of 50% approval to pass (https://docs.ens.domains/dao/governance/process/). Social proposals also have a 1% quorum requirement, with minimum of 50% approval, and constitutional amendments require a two-thirds majority and at least 1% of all tokens participating (https://docs.ens.domains/dao/governance/process/; https://docs.ens.domains/dao/constitution/).
Delegates use delegated $ENS to submit and vote on proposals related to protocol changes and DAO treasury spending, while registration revenue goes to smart contracts controlled by the ENS DAO and the constitution says treasury income is used first for ENS viability and ongoing development (https://basics.ensdao.org/ens-token; https://basics.ensdao.org/protocol-revenue; https://docs.ens.domains/dao/constitution/). Public sources reviewed did not identify any tokenholder right to dividends or revenue distributions.
The ENS governance model may continue to evolve through tokenholder-approved proposals. A relevant proposal was approved by tokenholders on August 8, 2026, Next Era of ENS DAO: Empowering the ENS Foundation(https://discuss.ens.domains/t/draft-executable-next-era-of-ens-dao-empowering-the-ens-foundation/22329). The proposal transferred administrative control of the ENS DAO’s endowment to the ENS Foundation, together with related intellectual property arrangements, while the operational wallet, DAO-held ENS tokens, and protocol control remain with ENS tokenholders. submitted through the ENS DAO’s public governance process. The proposal was approved by token holders on August 8, 2026 [https://www.tally.xyz/gov/ens/proposal/80619211450810140112687536515944199882433060764177806587986222097717655810120](https://www.tally.xyz/gov/ens/proposal/80619211450810140112687536515944199882433060764177806587986222097717655810120))
The ENS Foundation materials say the DAO may instruct the directors to take action on behalf of the Foundation and that the Foundation's Articles of Incorporation give significant powers to the ENS DAO, while the token allocation post says tokenholders have the right to appoint and dismiss directors and to instruct the Foundation to take real-world actions (https://docs.ens.domains/dao/foundation/; https://paragraph.com/%40ens/ens-token-allocation-claiming-opens-nov-8). The corporate documents further provide that ENS tokenholders constitute the "Council" and that the Foundation must be wound up if the Council delivers notice to the Foundation declaring that it is to be wound up. Following satisfaction of the Foundation's debts and liabilities, any surplus assets must be transferred to one or more charitable objects selected by the Council and may not be distributed to members or directors.
For the Primary Foundation do the following independently. If a Foundation does not exist, state so for each sub question. Items (a)–(f) apply only if that entity exists; state explicitly that the entity doesn't exist. Definition: The primary Foundation can be explained as the entity which was directly/indirectly involved in the issuance of the native token at launch. If the original Foundation has been dissolved and in its place a "new Foundation" was created, then detail the "new Foundation".
The ENS Foundation is an exempted foundation company incorporated in the Cayman Islands, limited by guarantee, with no share capital and limited liability (https://docs.ens.domains/dao/foundation/).
The ENS Foundation currently holds no registered intellectual property. The privacy policy for ens.domains identifies the site as operated by the Foundation. Under the active onchain executable proposal, Next Era of ENS DAO: Empowering the ENS Foundation (see Item 1(e)), it is anticipated that registered intellectual property associated with the ENS project, including the ENS trademarks, would be held by the Foundation, subject to approval through the DAO governance process and completion of the related restructuring steps. The Foundation has no subsidiary entities.
The ENS Foundation holds no powers over DAO governance, treasury actions, protocol-controlled resources, token administration, or reward parameters, except that under the proposal described in Item 1(e), approved by ENS tokenholders on August 8, 2026, the Foundation Board holds administrative control of the ENS DAO's endowment, with all transactions subject to a nine-day timelock and Security Council cancellation.
ENS Labs Ltd. and the ENS Foundation are separate legal entities. The ENS Foundation serves as a key counterparty to ENS Labs and provides grant funding to support ENS Labs' software development activities pursuant to DAO-approved funding arrangements. Foundation directors will have funding control over ENS Labs, which requires a majority approval from independent directors.
The Foundation holds no contract or admin powers over the protocol.
The Foundation is a non-profit and cannot pay out dividends to its directors or members (https://docs.ens.domains/dao/foundation/). Public sources also say directors may ask the DAO for reimbursement of listed Foundation operating fees when incurred (https://docs.ens.domains/dao/foundation/).
For the Primary DevCo do the following independently. If an entity does not exist, state that explicitly across each sub-question. Items (a)–(f) apply only if that entity exists; state explicitly that the entity doesn't exist. Definition: The primary DevCo can be explained as the entity which was directly/indirectly involved in the issuance of the native token at launch. If the original DevCo has been dissolved and in its place a "new DevCo" was created, then detail the "new DevCo".
The primary DevCo-like entity identified in public sources is ENS Labs Ltd., formerly True Names Ltd. (renamed 12 September 2022). Public sources identify True Names Ltd. as the original ENS development company incubated at the Ethereum Foundation in 2017 before being spun out as an independent organization in 2018 (https://ens.domains/blog/author/enslabs.eth; https://basics.ensdao.org/ens-labs; https://docs.ens.domains/dao/proposals/2.1/).
ENS Labs Ltd. is a Singapore company limited by guarantee, responsible for core ENS software development.
ENS Labs Ltd. owns the public ENS code repositories in the ensdomains GitHub organization (https://github.com/ensdomains), including ens-contracts (the core ENS contracts), ens-app-v3 (the ENS Manager app), ensjs, ens-metadata-service, and docs, each published under the open-source licenses listed below.
Public sources indicate that ENS Labs owns or controls the ENS trademark portfolio, including registrations for the ENS name and logo in multiple jurisdictions. These include the ENS trademark and logo registered in Singapore under registration number 40201821218Y (registered on 18 October 2018) and in the European Union under registration number 019141121 (registered on 20 September 2025) (https://digitalhub.ipos.gov.sg/FAMN/eservice/IP4SG/MN_TmSimilarMarkSearch; https://euipo.europa.eu/eSearch/).
ENS public repositories use the following open-source licenses: MIT License (https://github.com/ensdomains/ens-contracts/blob/master/LICENSE.txt), BSD 2-Clause License (https://github.com/ensdomains/ens/blob/master/LICENSE), Creative Commons CC0 1.0 Universal (CC0 1.0) (https://github.com/ensdomains/docs/blob/master/LICENSE), The Unlicense (https://github.com/ensdomains/name-reservations/blob/master/LICENSE), and GNU General Public License v3.0 (GPL-3.0) (https://github.com/ensdomains/pancake-frontend-candidate-010/blob/main/LICENSE).
ENS Labs reserves none of the above powers.
ENS Labs Ltd. has no influence over the ENS Foundation. It holds no role in Foundation governance and no power to appoint, remove, or instruct Foundation directors; those powers rest with ENS tokenholders. ENS Labs Ltd. and the ENS Foundation are separate legal entities, and the Foundation serves as a key counterparty to ENS Labs, providing grant funding for ENS Labs' software development pursuant to DAO-approved funding arrangements.
ENS Labs reserves none of the above powers.
Currently active: a DAO-approved grant stream to ENS Labs totaling $9.7m annually (https://docs.ens.domains/dao/proposals/2.1/; https://docs.ens.domains/dao/proposals/5.22/). No other mechanism currently directs protocol-controlled resources, treasury assets, fees, revenue, rewards, or token distributions to ENS Labs, its members, or its contributors. Historically, ENS Labs was founded with a $1 million Ethereum Foundation grant, later received grants from Chainlink, Protocol Labs, and others, was funded by ETH raised in the short-name auction, and has never received VC funding (https://basics.ensdao.org/ens-labs).
Definition (for this section): An Affiliated Protocol Contributor (APC) is a non-issuer company - not the protocol's primary Foundation or DevCo - that materially contributes to the protocol's code, operations, governance, or funding. For example, Blockworks Advisory would be considered an APC of Ethena because it materially contributes to its operations through Ethena's risk council. Provide a structured description per APC. If no APCs exist, state that explicitly across each sub-question. Items below apply per APC.
There are no APCs as described under the definition above, however, there are teams who have received annual funding from the ENS DAO via grants for specialized projects.
There are no APCs as described under the definition above, however, there are teams who have received annual funding from the ENS DAO via grants for specialized projects.
There are no APCs as described under the definition above, however, there are teams who have received annual funding from the ENS DAO via grants for specialized projects.
There are no APCs as described under the definition above, however, there are teams who have received annual funding from the ENS DAO via grants for specialized projects.
Download the Worksheet, enable macros, complete the Initial Allocation sheet, then use Convert To CSV to export the file for import here. To make edits after importing, update the worksheet, use Convert To CSV again, then re-import the new CSV. The table is the final answer.
Ticker | Date | Allocation Category Name | Recipient Type | Allocation % | Allocation Tokens | TGE Unlock % | TGE Unlock Tokens | Cliff Months | Cliff Unlock % | Linear Vesting Months | Cadence Months | Circulating Treatment | Notes on what each category is used for | If applicable: Contract / Wallet address |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ENS | 10/31/2021 | Community Treasury (Unlocked) | Community Treasury (Unlocked) | 0.05 | 5000000 | 0.05 | 0 | 0 | 0 | n/a | n/a | No | ||
ENS | 10/31/2021 | Community Treasury (Locked) | Community Treasury (Locked) | 0.45 | 45000000 | 0.45 | 0 | 0 | 0 | 48 Months | 1 | Conditional | ||
ENS | 10/31/2021 | Airdrop | Airdrop | 0.25 | 25000000 | 0.25 | 0 | 0 | 0 | n/a | n/a | No | ||
ENS | 10/31/2021 | Core Contributors | Core Contributors | 0.18955 | 18955000 | 0.18955 | 0 | 0 | 0 | n/a | n/a | No | ||
ENS | 10/31/2021 | Select Integrations | Select Integrations | 0.025 | 2500000 | 0.025 | 0 | 0 | 0 | n/a | n/a | No | ||
ENS | 10/31/2021 | External Contributors | External Contributors | 0.0129 | 1290000 | 0.0129 | 0 | 0 | 0 | n/a | n/a | No | ||
ENS | 10/31/2021 | Future Contributors | Future Contributors | 0.0125 | 1250000 | 0.0125 | 0 | 0 | 0 | n/a | n/a | No | ||
ENS | 10/31/2021 | Launch Advisors | Launch Advisors | 0.0058 | 580000 | 0.0058 | 0 | 0 | 0 | n/a | n/a | No | ||
ENS | 10/31/2021 | Keyholders | Keyholders | 0.0025 | 250000 | 0.0025 | 0 | 0 | 0 | n/a | n/a | No | ||
ENS | 10/31/2021 | Active Discord Users | Active Discord Users | 0.00125 | 125000 | 0.00125 | 0 | 0 | 0 | n/a | n/a | No | ||
ENS | 10/31/2021 | Translators | Translators | 0.0005 | 50000 | 0.0005 | 0 | 0 | 0 | n/a | n/a | No |
If there are no post-TGE token compensation plans, state explicitly they do not exist across each sub-question. If there are, explain each of (a)–(b) below.
No post-TGE token compensation plans exist. 0% of total supply is currently locked attributable to post-TGE employees.
No post-TGE token compensation plans exist, so no standard vesting terms (cliff, vesting frequency, or duration) apply.
Disclose current token-based compensation for external advisors and service providers (e.g., legal, marketing, technical, growth) funded from the on-chain treasury. Do not disclose individual payments to advisors receiving fiat-only compensation. If there are no advisors contracted in tokens then state across each sub-question that no token-based advisory compensation exists.
Token-based advisory compensation does not exist
Token-based advisory compensation does not exist
Token-based advisory compensation does not exist
Token-based advisory compensation does not exist
Disclose ongoing KOL/influencer relationships that partially or fully received tokens for payment. You do not need to disclose KOL/influencers that do not receive tokens for payment. If no KOL engagements exist, state for each sub-question that no KOL engagements exist.
No KOL engagements exist.
No KOL engagements exist.
No KOL engagements exist.
For each wallet that holds Unissued Tokens or is essential to operations (e.g., foundation, operations, treasury, investor reserve), disclose:
Definition: Unissued Supply = tokens authorized by the contract but not yet issued to any party; where they sit (treasury or mint authority) does not change that they are unissued. For instance: if a token has a total supply cap of 1B, and 400M tokens have been issued to investors, the team, and users (whether vested or unlocked), then those 400M count as issued supply. The remaining 600M are authorized but unissued supply, even if they are already minted into a DAO treasury wallet.
Title | Primary Function | Chain | Address | Control Mechanism | Explorer Link |
|---|---|---|---|---|---|
ENS DAO Treasury (DAO Wallet) | DAO operating funds | Ethereum | 0xFe89cc7aBB2C4183683ab71653C4cdc9B02D44b7 | Safe Multisig | https://etherscan.io/address/0xfe89cc7abb2c4183683ab71653c4cdc9b02d44b7 |
ENS Endowment | Long-term reserve fund | Ethereum | 0x4f2083f5fBeDe34C2714aFfb3105539775F7Fe64 | Historically a Safe multisig managed day-to-day by karpatkey under a DAO mandate. | https://etherscan.io/address/0x4f2083f5fbede34c2714affb3105539775f7fe64 |
ENS Labs Wallet (Cold Wallet) | Entity operating funds | Ethereum | 0x690F0581ecECcF8389c223170778Cd9D029606f2 | Controlled by ENS Labs | https://etherscan.io/address/0x690f0581ececcf8389c223170778cd9d029606f2 |
ENS Token Lock | ENS DAO Community Treasury | Ethereum | 0xD7A029Db2585553978190dB5e85eC724Aa4dF23f | Non-custodial linear-vesting contract | https://etherscan.io/address/0xd7a029db2585553978190db5e85ec724aa4df23f |
Projects must disclose all material terms of market-making arrangements that affect token liquidity. If the project has no agreements or deals with market makers, state that explicitly. For each market maker, include in a table:
If no native tokens were loaned or allocated to market makers, state that explicitly; cash/fiat retainers or fees are not required for (b).
Market Maker Name | Token Allocation Committed | Term Duration | Structure Name |
|---|---|---|---|
None. ENS Labs confirms there are no market maker agreements. | None. ENS Labs confirms there are no market maker agreements. | None. ENS Labs confirms there are no market maker agreements. | None. ENS Labs confirms there are no market maker agreements. |
Projects must disclose all material terms of centralized or decentralized exchange listings that affect token liquidity. For each listing, include in a table:
If the project has no agreements or deals with CEX or DEX, state that explicitly; doing so earns full credit; cash/fiat fee amounts are not required for this item.
Exchange Name | Token Allocation Committed | Term Duration | Native Token Listing Fees |
|---|---|---|---|
ENS Labs confirms there are no CEX or DEX agreements involving token allocations, lockups, liquidity commitments, or native-token listing fees. $ENS is available on centralized and decentralized exchanges (https://basics.ensdao.org/ens-token) | None. | N/A. | N/A/ |
If a category does not exist or is not applicable, make that clear in plain language.
Not applicable. No investor token sale occurred.
Not applicable
None
None
Disclose all prior token sales by the Project — including fundraising rounds, any material OTC sales to investors, and any discounted market-maker sales. For each sale, provide:
If no prior sales occurred, state that explicitly (e.g., "No prior fundraising, OTC, or discounted MM sales have occurred.").
Series Name | Investment Instrument | Date Of Sale | Number of tokens sold | Vesting Schedule |
|---|---|---|---|---|
Investor allocation | Investor allocation | Not applicable. No investor token sale occurred. | Not applicable. | Not applicable. No investor token sale occurred. |
Provide a narrative description of the Project's material funding sources, economic flows, and operational provisioning, broken out by entity: Foundation, Lab/DevCo, and DAO. If an entity does not exist, state that explicitly.
The ENS Foundation, ENS Labs, and ENS DAO exist.
ENS DAO
The ENS protocol generates revenue from the registration of .eth ENS names.
.eth ENS names can be registered on app.ens.domains, as well as third-party registration platforms, such as ENS Fairy, ENS.vision, and Rainbow wallet.
All revenue generated by the registration of .eth ENS names goes to smart contracts that are controlled by the ENS DAO.
Realtime protocol revenue can always been seen on Google Data Studio and Dune.
ENS DAO funding may be distributed in accordance with Article III of the ENS DAO Constitution, which provides:
Any income generated to the ENS treasury is to be used first of all to ensure the long-term viability of ENS, and to fund continuing development and improvement of the ENS system. Funds that are not reasonably required to achieve this goal may be used to fund other public goods within web3 as ENS governance sees fit.
ENS governance will not allocate funds to a team or individual who does not commit to uphold the same principles outlined in this constitution in their use of the allocated funds.
ENS Labs
Public governance materials also say True Names Ltd. requested a daily $11,500 USDC grant stream for calendar year 2022, backdated to January 1, 2022, and that ENS DAO later approved an additional daily 15,075.33 USDC stream to ENS Labs starting January 1, 2025, for a total 26,575.34 USDC/day (https://docs.ens.domains/dao/proposals/2.1/; https://docs.ens.domains/dao/proposals/5.22/). | ENS Labs also says it was funded by ETH raised in the short-name auction and has never received VC funding, while public sources continue to say no investor token allocation was made at launch. Public governance materials also say ENS proposed converting 6,000 ETH to USDC for operating expenses tied to ENS Labs, service-provider streams, and DAO working groups (https://basics.ensdao.org/ens-labs; https://paragraph.com/%40ens/ens-token-allocation-claiming-opens-nov-8; https://docs.ens.domains/dao/proposals/6.1/). | Not applicable. These grants and budget streams did not involve token vesting.
ENS Foundation
Funding for the foundation
More details about the foundation and funding can be found in the proposal here.
ENS DAO - Security, ecosystem support
ENS Labs - Development of core protocol, operations, security.
ENS Foundation - Operations, grants
The ENS Foundation:
ENS Labs:
ENS DAO:
If any, list prior exploits or incidents that directly affected the token, token supply, tokenholder balances, token contract, minting controls, burn mechanics, or custody of token supply. This question is not asking about general protocol, application, or smart contract exploits unless the incident directly affected the native token itself. If no prior incidents, state this explicitly (e.g., "No exploits affecting tokenholders or protocol funds as of YYYY-MM-DD").
There is no record of exploits or incidents that directly affected the token, token supply, tokenholder balances, token contract, minting controls, burn mechanics, or custody of token supply as of 2026-08-25.
There is no record of exploits or incidents that directly affected the token, token supply, tokenholder balances, token contract, minting controls, burn mechanics, or custody of token supply as of 2026-08-25.
There is no record of exploits or incidents that directly affected the token, token supply, tokenholder balances, token contract, minting controls, burn mechanics, or custody of token supply, as such there has not be loss of funds.
There is no record of exploits or incidents that directly affected the token, token supply, tokenholder balances, token contract, minting controls, burn mechanics, or custody of token supply as of 2026-08-25.
There is no record of exploits or incidents that directly affected the token, token supply, tokenholder balances, token contract, minting controls, burn mechanics, or custody of token supply as of 2026-08-25.
There is no record of exploits or incidents that directly affected the token, token supply, tokenholder balances, token contract, minting controls, burn mechanics, or custody of token supply as of 2026-08-25.
Provide a single income statement, expense summary, or comparable operating statement for the primary Foundation or Developer Company. A consolidated or entity-level presentation is acceptable. Balance Sheet and Statement of Cash Flows may be included but are not required. This item is intended to provide transparency into offchain operating resources and expenditures only.
This Token Transparency Filing is provided for general informational purposes only. Blockworks reviews completeness only and does not verify or warrant the accuracy of individual answers. Ethereum Name Service is solely responsible for the content, accuracy, and legality of its disclosures.
