Apechain Name Service (ANS), Powered by ENS & using Ape.eth

Active Proposals AIP Ideas
,
1

PROPOSAL NAME:

Apechain Name Service (ANS), using Ape.eth:
EVM-Compatible Identity for the Ape Ecosystem,
(Interoperable, Cross-chain Identity; Powered by ENS & Apechain)

TEAM DESCRIPTION:

Currently, the core team consists of two dedicated members of the BAYC/MAYC ecosystem, both with significant expertise in Web3 technologies and decentralized identity systems:

  • GaryPalmerJr.eth (BAYC #3636)
    Gary Palmer Jr. is a leading advocate for Web3 identity and digital sovereignty, with extensive experience in blockchain technology, ENS, and decentralized protocols. As a recognized voting delegate in the ENS DAO and a community liaison for ENS Labs, Gary has contributed to numerous initiatives advancing the use of ENS in Web3 dApps. He has also hosted digital and IRL discussions with key industry leaders and is known for his thought leadership in Web3 domains and decentralized identity.

  • Ada.eth (MAYC #6007)
    Ada.eth (AKA: UnfoldedLife.eth) brings a background in project management and marketing-technology applications, with a particular focus on ensuring smooth interoperability between people, process, and infrastructure. With deep ties to the MAYC community, Ada.eth specializes in creating and deploying marketing-technology infrastructure that enables secure, scalable solutions. Her technical, people, and creative skills, combined with a passion for the NFT and Web3 space, have made her an essential contributor to this proposal.

Communication:
We primarily use Twitter (X) for real-time communication and updates.

We’re also active on Discord for more detailed project discussions and collaboration with team members and partners; and Signal App for secure communications.

As we are seeking funding for this proposal, we are fully prepared to adhere to the requirements, including signing grant agreements and completing KYC verification.

PROPOSAL DESCRIPTION:

Apechain Name Service (ANS), using Ape.eth: EVM-Compatible Identity for the Ape Ecosystem, (Interoperable, Cross-chain Identity; Powered by ENS/ape.eth & Apechain)

We propose launching the Apechain Name Service (ANS), a Web3 identity solution that leverages the power of the ENS protocol (EIP-137) to create .ape.eth subnames for the Apechain ecosystem. This will allow Apes to enjoy the benefits of sovereign, interoperable names that are cross-chain compatible and blockchain-agnostic—perfectly integrated across EVM-compatible chains, including Web2 and Web3 sites-apps.

Why ENS Matters for Apechain:
By using ENS, names like “gary.ape.eth” would be natively interoperable with existing Web2/Web3 services like MetaMask, Uniswap, Coinbase, OpenSea, PayPal, and Venmo—services that have already integrated ENS. Any other naming systems would be like a fork of ENS, meaning they would not benefit from ENS’s vast pre-existing network effect. These alternative systems would require extensive business development efforts to achieve the same integrations, whereas ENS names already work natively in the most widely used Web3 and Web2 services. As the adoption of the ENS protocol continues to grow, the network effect will exponentially increase the value and utility of ANS names, making them even more integral to the broader Web3 ecosystem.

Proven Model:
Similar to the .base.eth names on Basechain, which generated over $562,014 (214 ETH) in just ~30 days, this proposal seeks to create a dedicated naming system for Apechain. Base names like “gary.base.eth” are already functional on MetaMask, Uniswap, and even PayPal/Venmo, proving the demand and utility of these cross-chain identities. We aim to replicate this success within the Ape ecosystem by leveraging ENS’s existing tech and network effects.

Key Opportunity:
By acquiring the ape.eth ENS name (which is likely to cost in the six-figure range), Apechain would gain the ability to offer .ape.eth subnames. These names would be fully EVM-compatible, making them usable across Apechain, Ethereum, and other EVM chains, just as “gary.base.eth” works across Ethereum and Basechain today.

Why ENS Over Other Naming Systems?
Other naming systems will struggle to achieve the native integration ENS already has with widely adopted platforms. While some Ape-specific naming solutions may emerge, they will not be cross-chain compatible or EVM-compliant without direct integration with ENS. This means names not based on ENS would lack the utility to work seamlessly across MetaMask, Uniswap, Coinbase, OpenSea, PayPal, Venmo, and countless other services.

Next Steps:
This proposal seeks funding from the Ape DAO to acquire the ENS domain ape.eth and to develop a full suite of cross-chain compatible .ape.eth subnames for the Ape community. This initiative would establish Apechain as a leader in decentralized, sovereign identity, enhancing the Ape culture while unlocking interoperable identity for users across multiple chains.

Call to Action:
We need a team and community support to bring this vision to life. Whether you’re passionate about sovereign Web3 identity, ENS, or Apechain, we invite you to join us. Let’s collaborate, build a plan, and make .ape.eth names a reality for Apechain!

BENEFIT TO APECOIN ECOSYSTEM:

The Apechain Name Service (ANS) will provide significant benefits to the ApeCoin ecosystem by creating a native, interoperable identity solution for the Ape community. By leveraging the ENS protocol, we can establish .ape.eth subnames that are fully integrated with existing Web3 infrastructure, across Ethereum L1 and EVM L2s, bringing both short-term utility and long-term growth potential, critical for the ApeCoin ecosystem.

1. Increased Utility & Adoption:
With ENS-based .ape.eth names, Ape holders will gain a powerful, interoperable identity that works seamlessly across major Web3 platforms such as MetaMask, Uniswap, OpenSea, Coinbase, PayPal, and Venmo. This increases the visibility and utility of ApeCoin holders, empowering them to transact, interact, and showcase their identity in the broader Web3 space.

2. Strengthened Community Identity:
The .ape.eth naming system will foster a stronger sense of identity and belonging within the Ape community. It will allow users to establish unique digital identities tied directly to Apechain, enhancing their social standing and reinforcing ApeCoin’s cultural significance. Just as .base.eth names have driven engagement on Basechain, .ape.eth names will do the same for the ApeCoin ecosystem.

3. Cross-Chain Interoperability:
Unlike other potential naming systems that are limited to a single chain or require custom integrations, the ANS names will be cross-chain compatible and blockchain-agnostic, leveraging the existing ENS network effect. This means users will benefit from an identity that functions across Ethereum, Basechain, and other EVM-compatible chains—driving further adoption of ApeCoin in the larger blockchain space.

4. Revenue Generation for Ape DAO:
By acquiring and distributing ape.eth subnames, the Ape DAO will have an opportunity to generate long-term revenue from registration fees and renewals, similar to how ENS generates income. The funds raised from .ape.eth names can be reinvested into further development, marketing, and community-building efforts, benefiting the entire ApeCoin ecosystem.

5. Network Effects:
As ENS adoption continues to grow across Web3 and Web2 platforms, the network effect will drive even more value to ANS names. This increasing utility will make .ape.eth names more desirable, enhancing their role as a core component of the ApeCoin ecosystem.

We are requesting funding from the Ape DAO to acquire the ape.eth domain, which is critical to launching .ape.eth subnames and ensuring the ApeCoin community has access to EVM-compatible, sovereign Web3 identities; and for the dev team to develop and launch ANS, which will grow in value and utility as the ecosystem expands.

DEFINITIONS:

  • Apechain Name Service (ANS): A proposed naming system built on the ENS protocol specifically for the Apechain ecosystem, providing .ape.eth subnames for ApeCoin holders. These names will be interoperable across various EVM-compatible chains.
  • ENS (Ethereum Name Service): A decentralized domain name system built on the Ethereum blockchain, allowing users to register human-readable names like “name.eth” that can be used to receive cryptocurrency, interact with smart contracts, and integrate with Web3 services like MetaMask, Uniswap, OpenSea, Coinbase, and more.
  • .ape.eth Subnames: Custom, community-branded subnames (e.g., “yourname.ape.eth”) tied to the ape.eth domain, leveraging the ENS protocol for cross-chain compatibility and decentralized identity management. These names are EVM-compatible and will work across major Web3 applications.
  • EVM (Ethereum Virtual Machine): The runtime environment for smart contracts on Ethereum. EVM-compatible refers to blockchain networks that can run Ethereum smart contracts, such as Basechain, Polygon, and Apechain.
  • CCIP (Cross-Chain Interoperability Protocol, EIP-3668): A protocol that enables decentralized services, like ENS names, to work across multiple blockchains, ensuring that names such as .ape.eth are functional on multiple EVM chains.
  • Network Effect: The phenomenon where a product or service becomes more valuable as more people use it. In the context of ENS and ANS, the more platforms and users adopt ENS-based names like .ape.eth, the more utility and value these names will have in the broader Web3 ecosystem.
  • Basechain: A layer-2 Ethereum scaling solution that recently introduced .base.eth names as part of their integration with ENS. Basechain serves as an example of how Apechain can benefit from a similar naming system.
  • EIP (Ethereum Improvement Proposal): A standard used to propose changes or enhancements to the Ethereum blockchain. In this context, EIP-137 refers to the standard used by ENS for domain registration, while EIP-3668 refers to the cross-chain interoperability protocol (CCIP).

STEPS TO IMPLEMENT:

1. Acquisition of ape.eth ENS Name

  • Start Date: Upon approval of funding
  • End Date: Estimated 1-2 weeks post-approval
  • Description: The first step is to acquire the ape.eth ENS domain. This is critical to creating .ape.eth subnames under the ENS protocol. The domain will likely cost in the six-figure range based on current market value.
  • Associated Costs: Estimated at $100,000 - $250,000 (based on current ENS market prices for premium names).
  • Personnel: Coordination between the project lead, ENS marketplace experts, and the ApeCoin DAO for securing funds.
  • Platforms: ENS domain acquisition platforms like Vision/.io.
  • Request to APE Foundation: Funding approval to purchase the ape.eth domain.

2. Development of Apechain Name Service (ANS)

  • Start Date: Immediately following ENS acquisition
  • End Date: 3-4 months for MVP launch
  • Description: We will develop the ANS system to enable the registration and management of .ape.eth subnames. This will involve building a user-friendly interface, smart contracts, and integration with ENS protocols, based on the successful implementation of Base names.
  • Milestones:
    • Milestone 1: Smart contract development for .ape.eth subnames (2 months).
    • Milestone 2: Integration of CCIP (EIP-3668) for cross-chain interoperability (3 months).
    • Milestone 3: Initial launch of the ANS registration platform for Apechain users (4 months).
  • Key Performance Indicators (KPIs):
    • Successful deployment of .ape.eth subnames on the Apechain testnet.
    • Achieving 10,000+ registrations of .ape.eth names within the first 3 months post-launch.
  • Associated Costs:
    • Development and engineering team: $150,000 (covering development for smart contracts, user interface, and testing).
    • Integration and technical audits: $50,000 (security audits and interoperability testing).
    • Marketing & promotion of launch: $50,000 (campaign to raise awareness and onboard users).
  • Personnel:
    • Development team (smart contract engineers, front-end/back-end developers).
    • ENS protocol specialists.
    • Project manager and marketing team.
  • Platforms: ENS, Apechain testnet/mainnet, GitHub, project management tools.
  • Request to APE Foundation: Funding support for development, technical audits, and initial marketing efforts.

3. Launch and Growth Phase

  • Start Date: Post-development (Month 4)
  • End Date: Ongoing
  • Description: Once the ANS platform is live, we will focus on growing the ecosystem by promoting .ape.eth names through community engagement, partnerships, and incentives for early adopters.
  • Milestones:
    • Milestone 1: Initial launch of .ape.eth names on Apechain’s mainnet (Month 4).
    • Milestone 2: Reach 50,000+ .ape.eth registrations in the first 6 months.
    • Milestone 3: Marketing integration .ape.eth names into key platforms like Uniswap, MetaMask, OpenSea, and PayPal by leveraging ENS’s existing network effect. Note: Interoperability is already available for specific integrations or partnerships that are already integrated with the ENS protocol.
  • Key Performance Indicators (KPIs):
    • Sustained growth in .ape.eth registrations (targeting 50,000 registrations in 6 months).
    • Number of integrations achieved with ENS-compatible platforms.
  • Associated Costs:
    • Ongoing marketing and community-building efforts: $50,000.
    • Development of additional features based on community feedback: $25,000.
  • Personnel:
    • Marketing and partnerships team.
    • Ongoing development support for additional feature rollouts.
  • Platforms: ENS, Apechain, social media, and blockchain integration platforms.
  • Request to APE Foundation: Additional funding support for continued promotion and development of new features.

4. Long-term Sustainability & DAO Revenue

  • Start Date: After 6 months
  • Description: Post-launch, the focus will shift to ensuring long-term sustainability of ANS through community governance and a revenue-sharing model that benefits the ApeCoin DAO. We plan to generate revenue from subname registration fees and renewals, similar to ENS’s revenue model. The DAO will be an integral part of governance and fund allocation moving forward.
  • Milestones:
    • Sustainable revenue stream from subname registrations.
    • DAO-led decisions on how funds are reinvested into the ecosystem.
  • Key Performance Indicators (KPIs):
    • Revenue targets from subname fees (estimated at $100,000+ in the first year).
    • Increase in ApeCoin usage as .ape.eth names become a valuable part of the ecosystem.
  • Associated Costs: None (revenue generation phase).
  • Personnel: DAO members for governance.
  • Platforms: ApeCoin DAO governance platforms.

The timeline for the 3-4 month MVP launch and ongoing growth phase is flexible and will adapt based on community feedback and development progress, as we will be responsive to any unforeseen delays.

REPORTING EXPECTATIONS:

We are committed to maintaining transparency and keeping the ApeCoin community informed at every stage of the project. Below is our proposed reporting schedule for sharing progress updates:

  1. Initial Progress Report – 1 month after project approval
  • Details: This report will include updates on the acquisition of the ape.eth ENS name, initial team formation, and early development milestones for the Apechain Name Service (ANS). We will also outline any initial challenges or adjustments to timelines.
  1. Quarterly Progress Reports – Every 3 months post-project initiation
  • Details: These reports will provide detailed updates on:
    • Development milestones achieved (e.g., smart contract development, platform integration, CCIP implementation).
    • Ongoing costs and expenditures.
    • Key performance indicators (KPIs), via Dune dashboards, including the number of .ape.eth registrations and platform integrations.
    • Marketing activities, community engagement, and partnership developments.
  1. Beta Launch Report – At the time of ANS Beta launch (4th month)
  • Details: This report will focus on the launch of the .ape.eth subname registration platform, including:
    • Progress on technical development.
    • Early user feedback from beta testing.
    • Metrics on initial .ape.eth registrations via Dune dashboards.
    • Any required post-launch adjustments based on community input.
  1. Post-Launch Report – 6 months after the official platform launch
  • Details: This report will evaluate the success of the full platform launch and include:
    • Detailed metrics on .ape.eth registrations (targets: 10,000+ registrations within the first 3 months, 50,000+ within the first 6 months).
    • Revenue generated from registration fees via Dune dashboards.
    • User engagement data and community response.
    • Next steps for feature rollouts, integrations, and continued ecosystem development.
  1. Annual Reporting – 12 months after project initiation
  • Details: A comprehensive report summarizing the first year’s progress, including:
    • Total number of .ape.eth registrations via Dune dashboards.
    • Revenue generated for the ApeCoin DAO.
    • Successes, lessons learned, and recommendations for the next phases of the ANS project.
    • Proposals for additional features and enhancements based on community feedback.
    • The future roadmap beyond the first year will be expanded for the project’s longevity; adding further features and functionalities planned for ANS, which will continue to add new value for ANS after the initial launch phases.

Reporting Channels:

  • Reports will be shared via Snapshot, ApeCoin DAO forums, Dune dashboards, and Twitter (X).
  • Regular updates and key insights will also be discussed in community spaces, such as Discord and Twitter Spaces.

This reporting schedule ensures consistent communication with the community, allowing for feedback and adjustments throughout the project.

OVERALL COST:

Total amount requested from the ApeCoin Ecosystem Fund = $400,000.

This grant will cover the following areas to ensure the successful development, launch, and promotion of the Apechain Name Service (ANS):

Budget Breakdown:

  1. Acquisition of ape.eth ENS Domain
  • Estimated Cost: $100,000 - $250,000
  • Purpose: Secure the essential ape.eth ENS domain to enable .ape.eth subnames under the ENS protocol.
  1. Development of Apechain Name Service (ANS)
  • Total Development & Engineering Costs: $150,000
    • Smart Contract Development: $75,000
    • Front-End/Back-End Development: $50,000
    • Testing and Deployment: $25,000
  • Purpose: Build the core infrastructure to allow the registration and management of .ape.eth names via the ENS protocol. This includes integration of CCIP (EIP-3668) for cross-chain interoperability.
  1. Technical Audits & Security
  • Cost: $50,000
  • Purpose: Conduct security and functionality audits for the smart contracts and platform, ensuring the safety and reliability of the .ape.eth name service.
  1. Marketing, Promotion, and Community Engagement
  • Cost: $50,000
  • Purpose: Execute a marketing campaign to raise awareness and drive early adoption of .ape.eth names, including community outreach, partnerships, and incentives for early adopters.
  1. Ongoing Support and Feature Rollouts
  • Cost: $25,000
  • Purpose: Develop additional features based on community feedback, support new integrations, and handle ongoing platform improvements.

Additional Requests to APE Foundation:

  • Community Discussion Platforms:
    • Request for support in setting up a dedicated section on the ApeCoin DAO forums for discussion around the Apechain Name Service (ANS), facilitating community engagement and feedback.
  • Snapshot Promotion:
    • Request to feature this proposal on the Snapshot homepage to ensure visibility and encourage voting from the ApeCoin community.
2

Hey Gary,

I noticed a potential inconsistency between the ‘Steps’ and ‘Overall Cost’ sections. In ‘Steps,’ it’s mentioned that the name will likely cost in the six-figure range, but the estimated acquisition cost is listed as $100k-$250k. Could this be clarified or expanded?

Additionally, the seller hasn’t listed ape.eth for under $1 million in the past two years. This might suggest a higher acquisition cost than the current estimate.

image

3

Hey MX!

Thank you for pointing that out! To clarify, my ENS Broker is in contact with the seller of ape.eth, and they have indicated that a deal in the range of $100K–$250K (~75–100 ETH) may be within targets. While previous listing prices have been higher, this estimate reflects current negotiations.

That said, the proposal is indeed dependent on acquiring “ape.eth” for Apechain, but we are open to considering less perfect alternatives if the deal doesn’t materialize as expected.

I appreciate your attention to detail, and we’re working to ensure the best outcome for the project! Please consider upvoting this AIP idea :slight_smile: :apecoin:

2 Likes
4

Note about D3/ApeNames:
ApeNames/ (d3) is not EVM-compatible for pre-existing integrations with major Web3 platforms. This means that names from ApeNames/.com will not work natively on services like MetaMask, Uniswap, OpenSea, Coinbase, PayPal, or Venmo.

Alternatively, a *.ape.eth subname (e.g., “yourname.ape.eth”) that will leverage the ENS protocol will be fully EVM-compatible and will function seamlessly across all these other Web2/Web3 platforms. ENS-based names are already integrated into MetaMask, Uniswap, PayPal, Venmo, and many other dApps, making them widely usable in both Web3 and Web2 services.

My goal for Apechain is to ensure full cross-chain compatibility, which we can achieve by leveraging the proven infrastructure of ENS. This way, Apechain users can benefit from seamless integration of ENS/CCIP protocols, (across both Web2 and Web3 ecosystems). We are looking for maximum interoperability and utility, which the .ape.eth subnames idea, powered by ENS, is the way to go.

1 Like
5

The Apechain Name Service (ANS) goes beyond just ENS. ANS is designed to provide interoperable Web3 identities that are cross-chain and blockchain agnostic, allowing *.ape.eth subnames to work seamlessly across multiple blockchain ecosystems.

Similar but different to traditional ICANN domains, ANS leverages the ENS/.eth protocol to offer decentralized identities that function across Web3 apps (like MetaMask, Uniswap, OpenSea, PayPal, and Venmo), while being fully compatible with both Web2 and Web3 platforms. This ensures maximum utility for Apechain users. It is possible that we could leverage the ICANN gTLD “.ape”, but this is not necessary. What is more important (and CRITICAL) is that “Ape Names” are interoperable with EXISTING EVM chains & dApps.

2 Likes
6

First off, thanks for putting up this proposal. I have a few questions around the price the proposed ape.eth name product would cost interested users. I didn’t see any projected incomes mentioned nor the net inflows expected to flow into the DAO’s wallet, even if expressed as percentages or multiples of known costs.

You’ve stated a near term target of 50k uptakes in 2 quarters, do you have growth projections beyond Q2? Do you products extend to recurring cashflows?

I ask these questions because I’m a strong believer in strengthening one’s AIP proposal and highlighting the tangible value proposition and draw attention from just the “what AIPS cost the DAO” but, rather amplify the measurable benefits of the DAOs investment in an AIP opportunity.

Nevertheless, imho its a valuable product and a useful addition to the Apecoin eco-system.

1 Like
7

Apologies if this is in your proposal and I missed it, but who would own the ape.eth domain after purchase? Would it be the DAO’s property?

2 Likes
8

Hi Gary, will be signing up ofc if successful.

Just had a similar question to Matt. Who would be managing the names once fully operational. As am I right in thinking there would always need to be an ANS “account manager” as automation can only go so far or? Thanks

1 Like
9

First off, thank you very much for your thoughtful questions and support for the proposal!

Regarding the pricing for .ape.eth subnames, tentatively at this moment, the initial registration fee will be in the range of $10–$100, depending on the demand and length of the name.

  • Premium names, including very short names, will likely have higher prices, (but this is depended on the difficulty and complexity of the coding process), while typical subnames will fall on the lower end.
  • For renewals, we’re looking at an annual fee in the same matching range of $10–$100. This provides both immediate and recurring revenue streams for the project.

As for projected inflows into the DAO’s wallet, a portion of the registration and renewal fees (tentatively around 10%–25%) will flow directly to the ApeCoin DAO.

  • Based on our target of 50,000 registrations within the first two quarters, (at an average of $50 per initial registration),
  • this alone could generate approximately $2.5 million in registration fees,
  • with $250,000–$625,000 of that flowing directly to the APE DAO.

For growth projections beyond Q2, we anticipate continued adoption as the utility of .ape.eth names expands.

  • Our goal is to reach 100,000+ registrations in the first year, with increasing renewals as users continue to hold their names.
  • Over time, this will generate recurring cash flows from renewals.
  • We expect this to create a sustainable revenue model for the DAO, with long-term benefits as more users adopt Apechain and .ape.eth names.

I fully agree that highlighting the tangible value proposition and the measurable benefits to the DAO is crucial. This proposal doesn’t just cost the DAO—

  • it’s designed to provide significant financial returns and long-term value for the ecosystem, creating both one-time, AND, recurring revenue streams,
  • which will strengthen the community and its financial sustainability.

I appreciate your feedback and am happy to answer any further questions you might have!

PS: Ape names on ApeChain would be priced in $APE.

PPS: The attached graphic shows the pricing for Base names,
which is based on $ETH, (USD ~$2,500), and ranges from:

  • 0.1 ETH (3-Char. Names: ~$250/year)
  • 0.01 ETH (4-Char. Names: ~$25/year)
  • 0.001 ETH (5-9 Char. Names: ~$2.50/year)
  • 0.0001 ETH (10+ Char. Names: ~$0.25/year)

Ref.: https://dune.com/troyharris/basenames
image

1 Like
10

To add detail, the Apechain Name Service (ANS) project is designed to enhance the ApeCoin ecosystem by providing critical infrastructure that empowers users with sovereign, interoperable Web3 identities.

This initiative will drive growth in several key areas, from increasing user engagement and adoption to expanding the ecosystem’s technical and financial capabilities. Below are the ways ANS will contribute to the growth of the ApeCoin ecosystem:

1. Enhancing Decentralized Identity

The introduction of .ape.eth subnames will allow users within the ApeCoin ecosystem to create and manage their own decentralized identities, which can be used across various Web3 platforms.

By leveraging the ENS protocol (EIP-137), .ape.eth names will become a vital tool for identity, empowering users to:

  • Secure human-readable names that map to their wallets and digital assets.
  • Showcase their ApeCoin identity across platforms such as MetaMask, Uniswap, OpenSea, and Coinbase.
  • Foster greater personal branding and identity within the ApeCoin and broader Yuga Labs community.

This will create a stronger sense of belonging and community within the ApeCoin ecosystem while attracting new users seeking to establish a decentralized identity in Web3.

2. Expanding Cross-Chain Interoperability

Apechain Name Service will offer full cross-chain interoperability through CCIP (Cross-Chain Interoperability Protocol, EIP-3668).

This means that .ape.eth subnames will work not only on Ethereum Layer 1 but also across Layer 2 solutions like Basechain, Polygon, and other EVM-compatible chains.

  • This will encourage the growth of ApeCoin by making the ecosystem accessible across multiple chains, reducing gas fees and friction for users.
  • As new chains are integrated, .ape.eth names will ensure seamless interactions across decentralized applications, making ApeCoin more attractive to users in diverse blockchain environments.

By fostering multi-chain compatibility, ANS will significantly broaden the utility of ApeCoin, enabling it to interact with a wider network of decentralized apps (dApps) and services.

3. Increasing Ecosystem Engagement

ANS will serve as a catalyst for user engagement within the ApeCoin ecosystem by offering incentives for early adopters, marketplace activity, and name registration.

Through initiatives like:

  • Discounts and perks for early adopters.
  • Referral programs to drive user growth.
  • Exclusive NFT airdrops tied to .ape.eth subname registrations.

These programs will create a strong incentive for users to engage with the platform, boosting overall activity within the ApeCoin ecosystem. The marketplace for .ape.eth subnames will also create new opportunities for trading and collaboration within the community.

4. Strengthening Community Identity and Culture

The ApeCoin ecosystem is driven by a vibrant community that values identity, creativity, and belonging.

By offering personalized, culturally significant .ape.eth names, ANS will strengthen this sense of community by:

  • Allowing users to showcase their affiliation with BAYC, MAYC, and other Yuga Labs projects through unique, branded subnames.
  • Offering premium names that align with the cultural vibe of the ApeCoin community, further enhancing personal identity and engagement.
  • Providing users with tools to express their creativity and individuality in both Web2 and Web3 platforms, tying their names to their decentralized personas.

This will attract new users while reinforcing the community-driven nature of the ApeCoin ecosystem, helping it grow organically.

5. Encouraging Innovation and Ecosystem Expansion

By leveraging the ENS protocol, ANS brings ApeCoin into the broader Web3 identity movement, positioning it at the forefront of innovation.

The platform’s infrastructure will:

  • Enable developers to build new applications and integrations around .ape.eth names, encouraging the creation of novel dApps and services that tap into the ApeCoin ecosystem.
  • Foster partnerships with other Web3 platforms, ensuring that ApeCoin remains interoperable and well-integrated across emerging decentralized networks.
  • Open new avenues for collaborations with other NFT communities, decentralized finance (DeFi) protocols, and metaverse projects, all of which can further grow the ecosystem.

By contributing to the technical and economic expansion of ApeCoin, ANS will solidify the ecosystem’s standing as a leader in decentralized identity and Web3 infrastructure.

6. Increasing Adoption of ApeCoin

As more users register .ape.eth subnames and integrate them into their daily Web3 activities, the utility and demand for ApeCoin will naturally increase.

By creating a high-demand identity solution that requires interaction with the ApeCoin ecosystem, ANS will:

  • Drive up transaction volumes related to ApeCoin.
  • Encourage the use of ApeCoin within the broader Web3 space, as users seek to leverage their .ape.eth names across various dApps and blockchain networks.
  • Create a deeper connection between ApeCoin and the Web3 identity space, boosting its reputation and adoption among new users and developers.

In total, tangibly, Apechain Name Service (ANS) will contribute to the growth of the ApeCoin ecosystem by expanding its technical capabilities, fostering deeper community engagement, creating new financial opportunities for the DAO, and positioning ApeCoin as a leading player in decentralized identity and multi-chain Web3 infrastructure.

The combination of .ape.eth subnames and cross-chain interoperability will empower users, developers, and the DAO to drive the ecosystem’s continued expansion and success.

11

Currently, the proposal aims to acquire the ape.eth EVM domain name for the benefit of the ApeCoin DAO. After the purchase, the ape.eth domain would be transferred to the ANS Smart Contract, with rights be given to the ApeCoin DAO, making it DAO-owned property.

This ensures that the community retains full control over the “ape.eth” EVM domain name, and any future decisions regarding its use, including the management of .ape.eth subnames, within the Apechain Name Service (ANS).

Initially, our ANS dev team would manage (not own) the parent level name, only to update the ape.eth “IPFS content hash”, which would direct users to ApeCoin and ApeChain resources (IPFS + HTML); and to direct users to register or renew *.ape.eth names. Then, management of the domain would also be given to the DAO, or to a multi-sig team to manage IPFS updates.

Let me know if you have any more questions!

1 Like
12

See above…Once fully operational, the ANS platform will largely be automated when it comes to name registration, renewal, and management. The ownership of the domain will be given to the smart contract.

However, you’re correct that there may be need to be some ongoing oversight to handle non-automated tasks, such as managing IPFS content hash updates and addressing any technical issues or community-driven requests.

It is important to note:
The ENS domain names have two roles to assign:

  • Owner Address, which can transfer the name and update the manager address;
  • Manager Address, which can update data fields and the IPFS content hash.

In terms of the “owner/ownership”, after the purchase, AND, initial ANS systems’ setup, the ape.eth domain would be transferred to the DAO, making it DAO-owned property. This ensures that the community retains full control over the domain and any future decisions regarding its use, including the management of .ape.eth subnames within the Apechain Name Service (ANS).

Initially, the ANS dev team will manage these tasks. We will not own the domain but will have the ability to update the ape.eth IPFS content hash, which directs users to relevant ApeCoin and ApeChain resources and enables subname registrations.

In terms of the “manager/management”, in the longer term, this management can either transition to the ApeCoin DAO or a multi-signature (multi-sig) team, chosen by the community to ensure decentralization and proper oversight.

The goal is to automate as much as possible while having a flexible governance structure to handle any necessary manual interventions. Please let me know if you have more questions!

1 Like
13

Excellent stuff, I’m no AIP writer but I’d say the benefits to the DAO are explicitly clear for everyone to read. I expect to vote on this sometime soon. Goodluck.

1 Like
14

Hi everyone,

We want to take a moment to realign our focus as a community. We’ve been following the recent discussions and, while there are many interesting topics on the table, it’s critical to recognize the massive opportunity before us with ApeNames, as approved in AIP-395. ApeNames (the Real .APE TLD) is not just another project—it’s the future of identity for our ecosystem and beyond.

  1. EVM Compatibility + ApeChain - First, ApeNames are built by Apes, for Apes natively on ApeChain as a cross-chain and EVM-compatible identity solution. Claims that ApeNames are not cross-chain or EVM-compatible are simply in-accurate. ApeNames isn’t just another Web3 naming solution; it’s a cross-chain, EVM-compatible identity solution that bridges Web2 and Web3 ecosystems like nothing else in the market. Our DNS Connect resolver already supports ENS DNS integration. Once the .APE TLD is approved and launched, these domains will have native integration with both Web2 and Web3 platforms, including ENS. This means ApeNames will work seamlessly across the traditional web and Web3 ecosystems like Ethereum, ApeChain, and beyond. By launching on ApeChain with full Web2 and Web3 interoperability, ApeNames offers an identity solution that will remain relevant for the next century. For context: while there are less than 3 million ENS names, there are 362 million real domain names. This is the scale we’re playing at, and ApeNames is poised to take the lead.

  • TL;DR ApeNames are future-proofed and secure for the future of the internet (web2+web3) with .APE as a real domain extension.

    • For example, when you register “yourname.ape” with ApeNames, you’ll be able to use it in both traditional Web2 environments (like email and websites) used universally by 5 billion people across the Internet and Web3 (as “yourname.ape” or “yourname*ape” across multiple chains). This creates a truly interoperable digital identity—far more comprehensive than subnames like .x.eth, which are restricted by the ENS protocol and limited to specific chains.
    • Moreover, the .APE top-level domain extension will deliver real utility for ApeCoin holders and beyond. Imagine using your “mail@yourname.ape” to control access to every part of your digital self or “youname.ape” to send and receive assets across thousands of platforms including PayPal or Venmo, which support sending to email addresses already. This is the future of cross-chain identity—one that bridges both on-chain and off-chain worlds.
  1. ENS Subnames - We want to clear up some misconceptions regarding ENS subnames. Many of these subnames (e.g. “name.base.eth”) do not offer native resolution on their respective networks in the dApps and platforms that support ENS. For instance, if you attempted to send Ethereum on the Base network through MetaMask to a name.base.eth holder, it would return a ‘no resolution for domain provided’ error. The same would happen if these names were to launch on ApeChain and require every ENS integration to update their resolvers and add support for ApeChain. This limitation of the ENS system poses a barrier to true interoperability and would mean ape.eth subnames would work on Ethereum, but NOT ApeChain.
  • Should ICANN or the ccNSO release and delegate 3 character ISO-3166 alpha-3 country code TLDs (ccTLDs), then the real .eth on the DNS would be delegated to Ethiopia. This would allow a third party to register ape.eth on the DNS, creating critical name collisions across dApps or platforms using the multiple (at least 5) DNS resolvers Web3 projects are implementing. With ApeNames and the .APE TLD, there is no such risk because D3 and the ApeCoin DAO control the .APE TLD, ensuring security and long-term stability for the next 100+ years.
  1. Pricing Clarification - We’ve also seen data on pricing Subnames. For context:
  • ICANN subdomains (e.g. 123.yahoo.com) - Free,if issued by Yahoo, which can reach ~5B users globally.
  • UNI.ETH - Free, localized to ENS integrations.
  • LINEA.ETH - Free, localized to ENS integrations.
  • BASE.ETH - 0.0001 to 0.1 ETH (~$0.27 to $270)

Keep in mind that even with ENS integration, it only supports sending on Ethereum natively. Resolvers need to be updated manually by integration partners to work across other chains—a major obstacle for any service relying solely on ENS.

Of note, Ape.eth has been listed on Opensea by the owner for ~$1.75M as recently as 11 month ago (during the bear).

  1. Official approval - Finally, ApeNames and our AIP-395 proposal were officially approved by the ApeCoin DAO as the official identity provider for ApeCoin and ApeChain ecosystems. This is a unified solution, not a fragmented one. As a community, we should focus on building cohesive experiences and avoid confusion by promoting separate, less integrated options.
  • If you wish to submit an AIP to request funding to purchase the ape.eth name on ENS, then we are totally fine with that. However, please don’t confuse Apes with another Web3 naming service proposal with critical security vulnerabilities, lack of technical depth, and minimal long-term commercial viability.
  1. DAO Direct Benefits - With ApeNames, the DAO directly benefits through annual recurring revenue share from domain sales, which would return value to the DAO and the community in perpetuity. Yes, even 20 years from now. As a comp, .COM has been around for 39 years now. Moreover, we are ensuring that the DAO manages and controls the .APE project with transparency around the development and marketing plan, along with the management of smart contracts by the D3 team and trusted developers. This projects, as stated before, is built for Apes, by Apes, ensuring that our ecosystem remains secure and community-driven.

The Focus is Simple: ApeNames is the Future
This is where our focus must be: ApeNames is a comprehensive, secure, and commercially viable solution that delivers real utility to ApeCoin holders. The distraction of pursuing short-term, fragmented options only weakens the long-term success of ApeCoin and our community.ApeNames built on ApeChain are the official identity solution for the ApeCoin ecosystem, and our focus is on building a comprehensive ecosystem, long-term solution that ensures ApeCoin holders have full control over their digital identities, website, emails, and assets across both traditional and decentralized ecosystems. Our team has created and managed over 300 real TLD extensions such as .xyz, .cash, .finance, .network and many more over the past 20+ years.

Together, we can build something that brings lasting value—not just today, but for generations of Apes to come.

Let’s keep our eyes on the prize and stay focused. The unprecedented potential of the .APE TLD presents a massive opportunity to elevate the ApeCoin DAO onto the global stage, backed by a proven, reliable, and sustainable revenue model.

Apes First, Not ETH First.
By Apes.
For Apes.
On ApeChain.

Best,

Fred @ ApeNames

15

Hi Fred, (and for everyone reading),

Fred, thank you for your insights, and I appreciate the work you and your team are doing with ApeNames via AIP-395.

However, I’d like to address a few key points and clarify some misunderstandings in your post, particularly regarding ENS, cross-chain compatibility, and the overall strategy, critical for the ApeCoin ecosystem and the success of Apechain.

1. EVM Compatibility and Cross-Chain Solutions

While ApeNames may claim cross-chain and EVM compatibility, it’s important to note that ENS, which powers the Apechain Name Service (ANS), is already fully EVM-compatible. The .ape.eth subnames are interoperable across all EVM-compatible chains and work natively today on Ethereum, Layer 2s (like Polygon and Basechain), and across Web2 and Web3 platforms such as MetaMask, Uniswap, Coinbase, PayPal, and Venmo.

In your specific example for MetaMask mobile, MetaMask-mobile has a known issue with their “CCIP implementation” for mobile, and I encourage everyone to test via MetaMask desktop, or Rainbow mobile, or Coinbase wallet mobile, where there is proper CCIP implementation. (This is not an issue with Base chain, base names, or CCIP, itself–Which the technical people and users-testers understand.)

What sets ANS apart is that it builds on the proven infrastructure of ENS, which already has over 2+ million active registrations and is widely integrated across Web3.

With ENS’s robust ecosystem and the CCIP (Cross-Chain Interoperability Protocol), ape.eth subnames can operate across multiple chains without additional manual resolver updates or custom integrations for each chain.

This creates a more scalable and interoperable system from the start, avoiding the fragmented integration challenges highlighted in your proposal.

2. ICANN .APE TLD vs. ENS

Your focus on the ICANN TLD .ape is interesting, but it’s important to clarify that ANS is not limited by Web3. There’s nothing stopping ANS from also applying for the Web2 ICANN TLD “.ape” while leveraging ENS for Web3 identities. This means that .ape.eth subnames could eventually bridge both Web2 and Web3 via ICANN TLDs, just as you envision with ApeNames.

However, the critical distinction is that ENS is already widely adopted across Web3.

The ENS protocol ensures that .ape.eth subnames are natively supported by the most important platforms, today. Launching .ape.eth subnames through ENS enables immediate utility, while pursuing an ICANN .ape TLD would require significant time, regulatory approvals, and additional integrations before achieving comparable utility.

3. ENS Subname Resolution

There’s a misunderstanding in your post about how ENS subnames like .ape.eth resolve on their respective networks.

You mention potential resolution issues with base.eth subnames; however, ape.eth subnames under the ENS protocol are designed to resolve natively on Ethereum and any EVM-compatible chain.

The infrastructure already exists, and ape.eth subnames can leverage this existing network effect without needing custom resolvers for every new chain. It is a mistake to limit Apenames to the Apechain ecosystem, and to have to rebuild thousands of business development relationships, which will technically create domain collisions and name conflicts.

4. Scalability and Ecosystem Alignment

The suggestion that ENS is somehow limited to specific chains is not accurate.

The ENS protocol is built to be blockchain agnostic and cross-chain compatible, meaning it can adapt to future Web3 environments, including Apechain. (Apechain is aligned with Ethereum.) By using ENS, we are aligning with Ethereum, which continues to be the leading Web3 ecosystem in terms of both developer activity and dApp usage.

This ensures that Apechain remains interoperable with the broader Web3 space, while still allowing us to pursue Web2 integrations through potential ICANN TLD efforts in the future.

Again, it is a critical mistake to limit Apenames to the Apechain ecosystem, and to have to rebuild thousands of business development relationships, which will technically create domain collisions and name conflicts, and build misalignment with Ethereum L1.

5. Security and Long-Term Stability

You raised concerns about security vulnerabilities in ENS-based subnames. However, ENS has undergone rigorous security audits and is widely regarded as one of the most secure naming protocols in the Web3 space.

ENS protocol is backed by years of development and contributions from the Ethereum community and is not prone to name collisions or security risks compared to newer, untested protocols.

By leveraging the ENS system, ape.eth subnames benefit from this well-established security infrastructure, ensuring long-term stability and trust.

6. Community and DAO Alignment

At the heart of the ApeCoin ecosystem is the community, and our goal with ANS is to provide a solution that is decentralized, interoperable, and community-driven.

By using ENS, we are building on a system that already aligns with the values of Ethereum, decentralization, and Web3 principles.

ANS gives control over the ape.eth domain and revenue-sharing to the ApeCoin DAO, ensuring the community has direct governance over its use and future developments.

7. Pricing and Revenue Model

Regarding pricing, the .ape.eth subnames will follow a sustainable revenue model that not only supports the ApeCoin DAO, but also generates recurring cash flows through registrations, renewals, and marketplace transactions. We are open to reviewing the final pricing model.

While your comparison to traditional Web2 subdomains is valid, the reality is that ENS names are decentralized, and their value comes from providing sovereign, self-owned digital identities, a concept that is fundamentally different from Web2 domain names issued by centralized entities. We believe Apes desire decentralized names, with their decentralized NFTs, within a decentralized blockchain that is Apechain.

Why ANS is Critical for Apechain

The Apechain Name Service (ANS) powered by ENS is not just another Web3 naming service; it’s the best solution for ensuring that Apechain is fully interoperable, EVM-compatible, and aligned with the broader Web3 ecosystem.

ENS is already integrated into the thousand of platforms and applications that matter most, (including PayPal and Venmo), and by building on this foundation, (and not creating domain collisions and name conflicts), ape.eth subnames will immediately bring value to the community and the ApeCoin ecosystem.

Additionally, ENS can expand into ICANN TLDs if necessary, meaning we’re not limited by focusing on Web3, but are poised to bridge both Web2 and Web3 in a way that benefits all Apes.

I encourage the community to consider the scalability, security, and long-term interoperability that ENS provides. By choosing ANS, we’re ensuring that Apechain and the ApeCoin ecosystem are set up for success, not just today, but for decades to come.

16

Hi @GaryPalmerJr.eth,

The community feedback period for your proposal would be ending in less than 24 hours.

  • If you’re content with the feedback received, your next steps are to finalize your proposal using the AIP Draft Template.

  • A moderator will reach out to the author to finalize the AIP Draft. Upon receipt of the final Draft, we will review and provide instructions on the next steps.

  • Are you ready to proceed to the next phase or do you wish to extend community discussion for another 7 days?

We look forward to hearing from you.

-@Facilitators

17

Hi ApeCoin DAO Community,

@GaryPalmerJr.eth has requested to extend the community discussion period for this AIP idea. This topic will automatically close a further 7 days from now. We encourage the community to continue to engage in thoughtful discussions through constructive criticism, honest feedback, and helpful suggestions.

Follow this Topic as further updates will be posted here in the comments.

-@Facilitators

18

Love the idea, I’m not a big fan of .ape.eth though… why not just .ape.
I don’t think we need the DID to resolve to an ICANN supported domain, what we need is for it to be resolved when interacting with onchain applications - and ENS has solved for this successfully.

I believe that having an ENS contract, running on Apechain, resolving on .ape, and managed by ENS through their existing stack would be awesome, and probably way easier.

19

Thanks for the feedback!
Here are the key points to answer your question:
ENS already provides the cross-chain and onchain interoperability,
which already works natively across thousands of Web3 platforms today,
(including, but not limited to: MetaMask, Uniswap, Coinbase, PayPal, Venmo, etc.).

While .ape sounds appealing for branding,
this would require someone to create an entirely new protocol;
and creating a new protocol would require custom integrations, additional resources, and new business development relationships, (to achieve the same level of functionality, which .ape.eth ALREADY has, with using the ENS protocol).

Starting with an entirely new protocol would set-back Apechain names, and would start with zero on Day One, (instead of starting with everything that ENS has already achieved, on Day One).

By Apechain using .ape.eth, we collectively tap into ENS’s existing stack, ENS’s existing BizDev relationships, and ENS’s existing network effect, (ensuring immediate utility, without needing to reinvent the wheel).

We want Ape names to work with Uniswap, Coinbase, PayPal, Venmo, etc. on Day One!

Hope that makes sense! Plz LMK if you have any other questions. :seedling: :gorilla:

PS: Apps/dApps on Apechain could be able to display “.ape.eth” names as “.ape”,
…but technically, (based on my proposal), they would be “.ape.eth” ENS subnames.

20

PPS: The [not yet released] ICANN gTLD (.ape) is also an ENS TLD,
…and can work 100% as an ENS Name; with the only downsides are:
the lack of 1. decentralization, 2. immutability, and 3. public viewability.