memoscan

0x5346…42cf

All memos sent from and to 0x5346…42cf.
0x534631bc…42cfsent to0x323a7639…b7e3·#24,293,146·0x4133e1a8…b49bd7
# [Executable] Collective Working Group Funding Request (Oct 2025) # \[Executable] Collective Working Group Funding Proposal (Oct 2025) ## Abstract This proposal executes all three Working Group funding requests for the October 2025 funding window, as approved in social proposals [**EP 6.24.1**](https://snapshot.box/#/s:ens.eth/proposal/0xc689edd77def6b9f6be6ca7fa1729e597c85ee12ae96e134d995a8b9fd78a21f), [**EP 6.24.2**](https://snapshot.box/#/s:ens.eth/proposal/0x9b3f5463e52aadc35155e686f8416297b24e6c7e30cb527747e61cf17b42a5f6), and [**EP 6.24.3**](https://snapshot.box/#/s:ens.eth/proposal/0x7b603c5ada65cfcdbdfec9a33352edf731615fe96fbcc09daa7aa97b327e15ce). Each was ratified via Snapshot and follows the ENS DAO’s standard funding process. This executable aggregates the transfers into a single transaction set. ## Proposal Components | Working Group | Destination (Multisig) | Amount | | --------------- | --------------------------------------------------------------------------------------------------------- | --------------------------- | | Meta-Governance | [ENS Meta-Gov Main Multisig](https://etherscan.io/address/0x91c32893216dE3eA0a55ABb9851f581d4503d39b) | 379,000 USDC (0 ETH, 0 ENS) | | Ecosystem | [ENS Ecosystem Main Multisig](https://etherscan.io/address/0x2686A8919Df194aA7673244549E68D42C1685d03) | 470,000 USDC (0 ETH, 0 ENS) | | Public Goods | [ENS Public Goods Main Multisig](https://etherscan.io/address/0xcD42b4c4D102cc22864e3A1341Bb0529c17fD87d) | 110,000 USDC + 15 ETH | Total requested: **959,000 USDC + 15 ETH** ### Meta-Governance Working Group **Funding Request (EP 6.24.1):** The Meta-Governance Working Group requested **379,000 USDC** from the ENS DAO treasury to fund its operations through April 2026. This funding covers anticipated expenses for the term, including stewardship compensation, contract audits, DAO tooling, and discretionary initiatives, while maintaining a prudent reserve to ensure continuity if future funding is delayed. ### Ecosystem Working Group **Funding Request (EP 6.24.2):** The Ecosystem Working Group requested **470,000 USDC** to support its operations through April 2026. The working group is responsible for growing and improving the ENS ecosystem by funding ENS-specific or ENS-centric builders and projects. The budget will support hackathons, grants, ecosystem support (including bug bounties), and community events to strengthen ENS tools and community growth. ### Public Goods Working Group **Funding Request (EP 6.24.3):** The Public Goods Working Group requested **110,000 USDC and 15 ETH** from the ENS DAO treasury to fund its initiatives through April 2026. The funding will be used for strategic grants and builder grants that support impactful public goods, developer tools, and ecosystem projects aligned with ENS’s long-term vision. This allocation, combined with the working group’s existing balance, will cover expected expenses for the term while leaving a small reserve to ensure continuity if future funding is delayed. ## Specification This proposal includes three USDC transfers via the `transfer(address,uint256)` function on the USDC token contract and one direct ETH transfer from the ENS DAO treasury. **Transfers:** 1. **Meta-Gov Safe** – 379,000 USDC `0x91c32893216dE3eA0a55ABb9851f581d4503d39b` 2. **Ecosystem Safe** – 470,000 USDC `0x2686A8919Df194aA7673244549E68D42C1685d03` 3. **Public Goods Safe** – 110,000 USDC + 15 ETH `0xcD42b4c4D102cc22864e3A1341Bb0529c17fD87d` ## Calldata **Transaction 1 – Meta-Gov (379,000 USDC)** {   "target": "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48",   "value": 0,   "calldata": "0xa9059cbb00000000000000000000000091c32893216de3ea0a55abb9851f581d4503d39b000000000000000000000000000000000000000000000000000000583e290e00" } **Transaction 2 – Ecosystem (470,000 USDC)** {   "target": "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48",   "value": 0,   "calldata": "0xa9059cbb0000000000000000000000002686a8919df194aa7673244549e68d42c1685d030000000000000000000000000000000000000000000000000000006d6e2edc00" } **Transaction 3 – Public Goods (110,000 USDC)** {   "target": "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48",   "value": 0,   "calldata": "0xa9059cbb000000000000000000000000cd42b4c4d102cc22864e3a1341bb0529c17fd87d000000000000000000000000000000000000000000000000000000199c82cc00" } **Transaction 4 – Public Goods (15 ETH)** {   "target": "0xcD42b4c4D102cc22864e3A1341Bb0529c17fD87d",   "value": 15000000000000000000,   "calldata": "0x" }
0x534631bc…42cfsent to0x323a7639…b7e3·#23,520,356·0x8bac09c0…08317a
# [Executable] Set Primary Names for Core DAO Addresses ## Abstract Several ENS DAO contracts lack primary names. This proposal establishes reverse records for core DAO addresses. ## Motivation By setting reverse records for core DAO addresses: * ENS DAO demonstrates best practices by using its own protocol fully, serving as an example for other DAOs * ENS DAO contracts become easier to identify and navigate * Names will resolve on sites that list the contracts like [enswallets.xyz](https://www.enswallets.xyz/) ## Details Executing this proposal will set primary names for 1. The [ENS DAO wallet](https://etherscan.io/address/0xFe89cc7aBB2C4183683ab71653C4cdc9B02D44b7) 2. The [ENS token](https://etherscan.io/address/0xC18360217D8F7Ab5e7c516566761Ea12Ce7F9D72) 3. The [ENS Endowment wallet](https://etherscan.io/address/0x4F2083f5fBede34C2714aFfb3105539775f7FE64) ## Specification Call `setName("wallet.ensdao.eth")` on the Reverse Registrar (reverse.ens.eth) to set the reverse record of 0xFe89cc7aBB2C4183683ab71653C4cdc9B02D44b7. Call `setNameForAddr(0xC18360217D8F7Ab5e7c516566761Ea12Ce7F9D72, 0xFe89cc7aBB2C4183683ab71653C4cdc9B02D44b7, 0xF29100983E058B709F3D539b0c765937B804AC15, "token.ensdao.eth")` on the Reverse Registrar to set the reverse record of 0xC18360217D8F7Ab5e7c516566761Ea12Ce7F9D72. Call `execTransaction()` on the Endowment multisig (endowment.ensdao.eth) with the encoded calldata for `setName("endowment.ensdao.eth")` to set the reverse record of 0x4F2083f5fBede34C2714aFfb3105539775f7FE64. The Safe transaction looks like this: ``` To: 0xa58E81fe9b61B5c3fE2AFD33CF304c454AbFc7Cb Value: 0 Data: 0xc47f002700000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000014656e646f776d656e742e656e7364616f2e657468000000000000000000000000 Operation: 0 SafeTxGas: 0 BaseGas: 0 GasPrice: 0 GasToken: 0x0000000000000000000000000000000000000000 RefundReceiver: 0x0000000000000000000000000000000000000000 Signatures: 0x000000000000000000000000Fe89cc7aBB2C4183683ab71653C4cdc9B02D44b7000000000000000000000000000000000000000000000000000000000000000001 ```
0x534631bc…42cfsent to0x323a7639…b7e3·#23,069,088·0xef2dcbb6…dabbb9
# [Executable] Transfer .locker TLD to Orange Domains LLC ## Abstract Orange Domains LLC is requesting the transfer of ownership of the “locker” Top Level Domain (TLD) in the ENS ecosystem. As the ICANN-accredited registry operator of the .locker TLD and controller of the .locker namespace on the Bitcoin Naming System (BNS), Orange Domains operates a comprehensive Web2-to-Web3 bridge that launched in general availability on October 23rd, 2024. Our .locker solution enables seamless connection between traditional DNS domain names and Web3 digital identities, with Web2 domains registered through over 50 ICANN-accredited registrars (including GoDaddy and NameCheap) and corresponding Web3 identities minted on Bitcoin’s Stacks L2. Currently supporting Bitcoin, Stacks, Ethereum, and Solana address resolution, we seek ENS integration to provide .locker users with full utility across Ethereum’s vast ecosystem through native ENS resolution and reverse resolution capabilities. This proposal aligns with ENS’s mission to integrate with existing internet infrastructure while bringing millions of Web2 users into Web3 through trusted, familiar registration channels. ## Proof of Ownership To demonstrate our legitimate ownership of the .locker TLD and authorization for this transfer request, Orange Domains has set a TXT record on the official .locker DNS infrastructure: DNS Record: \_ens.nic.locker Value: dotlocker.eth Verification Command: dig TXT \_ens.nic.locker This record confirms our control over the .locker DNS namespace and our intention to delegate ENS management to our designated Ethereum address, following the same verification pattern established in previous TLD transfer proposals. ## Specification ### Primary Transfer Action This proposal transfers ownership of the “locker” TLD to Orange Domains LLC by calling setSubnodeOwner on the ENS Root contract at root.ens.eth, passing keccak256(“locker”) as the label parameter and dotlocker.eth as the owner parameter. ### Technical Implementation Architecture Multi-Chain Resolution System: Orange Domains will implement a hybrid resolver architecture that coordinates resolution across our existing multi-chain infrastructure (Bitcoin, Stacks, Solana) with new ENS capabilities on Ethereum. Offchain Resolver with CCIP Read: We will deploy an ENS resolver utilizing EIP-3668 (CCIP Read) to enable gasless resolution while maintaining synchronization with our existing Web2 DNS infrastructure and multi-chain Web3 systems. This approach ensures consistency across all supported blockchain networks. Gateway Implementation: Our existing resolution infrastructure will be extended with an ENS-compatible gateway that can serve Ethereum addresses, text records, and other ENS-standard data types while coordinating with our Bitcoin/Stacks resolution services. ### Community and Ecosystem Benefits Web2 User Onboarding: This integration enables millions of users registering .locker domains through familiar Web2 channels (GoDaddy, NameCheap, etc.) to automatically gain ENS functionality, significantly expanding ENS adoption beyond crypto-native users. Cross-Chain Utility: .locker domains will serve as universal identifiers resolving consistently across Bitcoin, Stacks, Ethereum, and Solana, providing users with unified identity across major blockchain ecosystems. Infrastructure Alignment: Following ENS’s stated goal that “for ENS to succeed, it must integrate with existing infrastructure,” this proposal bridges traditional DNS registration with ENS functionality through established ICANN processes. Registrar Network Expansion: Leveraging our relationships with 50+ ICANN-accredited registrars creates new distribution channels for ENS-compatible domains through traditional domain registration workflows. ### Migration and User Experience Seamless Integration: Existing .locker domain holders will automatically gain ENS resolution capabilities without requiring additional registration or migration steps. Backward Compatibility: All existing .locker functionality (Bitcoin, Stacks, Solana resolution) will be preserved and enhanced with new Ethereum capabilities. Subdomain Management: Orange Domains will implement subdomain registration and management that maintains consistency across all supported blockchain networks while providing gasless updates through our offchain infrastructure. ## Governance Alignment This proposal directly supports ENS’s constitutional principles by: * Expanding Access: Bringing Web2 users into Web3 through trusted, familiar registration channels * Infrastructure Integration: Building bridges between traditional internet infrastructure and decentralized naming * Utility Enhancement: Providing cross-chain resolution that increases the practical value of decentralized naming * Responsible Stewardship: Leveraging established ICANN accreditation and regulatory compliance to ensure professional namespace management ## Transaction Details This proposal transfers the ownership of the “locker” TLD to Orange Domains by calling `setSubnodeOwner` on root.ens.eth (0xaB528d626EC275E3faD363fF1393A41F581c5897) with `keccak256("locker")` as the label, and `dotlocker.eth` as the owner. ## Conclusion Orange Domains’ management of the .locker TLD in ENS represents a significant opportunity to bridge Web2 and Web3 naming infrastructure while maintaining the highest standards of professional registry operation. Our ICANN accreditation, existing multi-chain infrastructure, and extensive registrar partnerships position us to bring unprecedented scale to ENS adoption through traditional domain registration channels. We respectfully request the ENS community’s support for this proposal, which will enhance utility for millions of potential users while advancing ENS’s mission of universal, decentralized naming.
0x534631bc…42cfsent to0x323a7639…b7e3·#21,424,762·0x029b6df7…418e12
Unruggable did a good job improving the EVM gateways, originally developed by ENS Labs. However, this proposal fails to demonstrate that Unruggable is the best team to manage global infrastructure. After all, the best sports car drivers aren’t typically the engineers who designed them.
0x534631bc…42cfsent to0x323a7639…b7e3·#21,088,469·0x1b06f95c…173c14
Expanding to L2 is required to scale ENS. ENS Labs has demonstrated that resources allocated to them produce results. Further comments: https://discuss.ens.domains/t/temp-check-ep-5-22-ensv2-development-funding-request/19762/3
0x534631bc…42cf·#19,307,363·0x7d6b51e0…9a5ef8
namehash: Junk at end of namereadLabel: Index out of boundsECDSA: invalid signatureECDSA: invalid signature lengthECDSA: invalid signature 's' val`DInvalid string lengthPPPPPPPPV[cNH{q`
0x534631bc…42cfsent to0x4976fb03…ba41·#16,976,925·0x726cf5d4…7c1d54
network.dm3.profiledata:application/json,{"profile":{"deliveryServices":["beta-ds.dm3.eth"],"publicEncryptionKey":"J8/l2afGhfNZ+2NKUCD8LO0vtMvOLFXfEmTDIPcUATk=","publicSigningKey":"bMv5OHgengNCfcelx6BjsOnYW04VsC38Y+Eof+M5wBI="},"signature":"0xad123787c0a5feaf68d013748de51707935a04fffbb842ebe83e81048810ff4465833453b31498a3d080490278377fa2eba2a15e47ac612df7bdb4d19065dd071b"}
1-50 of 57