[READY][GF: Phase 1 Proposal] Opti.domains | Interoperable domain name for the OP Stack

Basic Details

Project name: Opti.domains | Interoperable domain name for the OP Stack

Author name and forum name (please provide a reliable point of contact for the project):

Chomtana Chanjaraswichai
Forum name: @chom
Discord: Chom#1652
Email: chom@opti.domains

L2 recipient address: 0x8b6c27ec466923fad66Ada94c78AA320eA876969

Which Voting Cycle are you applying for?: Cycle 11 - Builders

I confirm that I have read the landing pages for the Builders 9 and Growth Experiments 11 Sub-Committees and that I have determined my proposal is best suited to be reviewed by the Builders Sub-Committee: [Yes/No]: Yes

Project Details

What are you going to build?:

Our team is currently focused on creating an interoperable domain name for the OP Stack, aiming to enable each deployed chain to deploy its own web3 domain permissionlessly independently. This approach will facilitate seamless user onboarding from the main Optimism chain to the deployed chains. We have spent considerable time designing the domain model, with the primary objective of optimizing benefits for the Optimism community.

As a forward-thinking initiative, our project is designed to be dynamic and responsive to evolving needs over time. Our plan involved creating an ENS fork, which evolved into an interoperable domain name service and, finally, a subscription-based public good service. These transitions are necessary to ensure the long-term sustainability of our domain service and ensure that the Optimism community continues to reap its benefits.

Given the recent announcement by Optimism regarding the OP Stack, we perceive it as a golden opportunity for our project. Our team has identified a distinctive feature of the OP Stack, which allows for the deployment of a domain system across OP stack-based chains in a permissionless manner, thereby enabling seamless interconnectivity among all chains.

Users can obtain their .op domains at no cost until 2025, along with the availability of optional supporter plans. Holders of .op domains can claim their .base and other domain names natively for each OP stack deployed chain without incurring additional fees. Chain operators may deploy opti.domains on their respective chains without requiring any permission, allowing for a wide range of customization options.

Domain whitelisting

As we offer free minting for our .op domains, we must prevent bots from minting and frontrunning the best domain names. Therefore, we have proposed a solution to this problem.

Participation in at least one of our campaigns is required to acquire a domain name. Additionally, we will leverage the current ENS domain holder database. To register a name in .op domains, one must be the rightful owner of the corresponding ENS domain at the time of the snapshot.

However, not all ENS holders have the right to mint their domain names, as some domains are reserved for special purposes, such as speculation or company branding.

Non-ENS holders can only register domain names not registered on ENS at the time of registration.

Why is what you are going to build going to succeed?:

Optimism recently unveiled the OP stack, and our product perfectly aligns with that technology. To ensure the success of the OP stack, it requires shared infrastructure across chains. Opti.domains is a critical infrastructure that enables the instant deployment of a web3 domain name with a bridge system to enable seamless movement of users across OP stack chains.

Compared to ENS, which has an existing user base of over 2.5 million domains minted, we can rapidly implement new innovations, such as bridges, without worrying about an existing user base. This agility allows us to move quickly toward our goal of building a cross-chain domain name system.

Based on this advantage, we’re in a good position to build a cross-chain domain name system. Additionally, we’re committed to being sustainable by sharing 80% of our revenue after 2025 to support developers in creating public goods that benefit both the Optimism ecosystem and Opti.domains holders.

Additionally, we value contribution over hype. We believe that this is a source of sustainable growth that drive the project to its goal.

Is your project likely to bring new builders to the Optimism ecosystem? If so, please describe how:

Upon reaching the community participation phase, our project will engage new builders from the community, starting with university students, to develop supporting components. These individuals are typically new builders, and incentivizing them with attractive rewards will motivate them to create more public goods in the Optimism ecosystem.

Is your project likely to improve the quality of developers in the Optimism ecosystem? If so, please describe how:

Indeed, our subscription model, which resembles that of Netflix, is specifically designed to motivate developers to strive for excellence to earn a larger share of the quarterly subscription fee distribution.

Is your project likely to improve the commitment of developers in the Optimism ecosystem? If so, please describe how:

Indeed, our project is specifically designed to enhance the dedication of developers to public goods. Typically, these developers receive a substantial one-time payment, making it difficult to remain committed to their development projects. However, in the final phase, we adopt a Netflix subscription model to compensate developers on a quarterly basis. This approach ensures that developers are more likely to remain dedicated to their work and prioritize quality without worrying about the business aspects of their projects.

Provide us with links to any of the following for the project:

Do you have any metrics on the project currently? (TVL, transactions, volume, unique addresses, etc. Optimism metrics preferred; please link to public sources such as Dune Analytics, etc.):

As we have not commenced any marketing yet, we currently do not have any current traction to report.

The value of a domain name itself is negligible, as anyone can fork ENS and launch it. The execution is what gives it value, much like NFTs. Our first campaign, an Ideathon, is designed to benefit both our project and the Optimism ecosystems in the long term. Apetimism, Bored Town, and Zonic OG NFT holders are the initial group invited to participate in the campaign. The response from these NFT communities has been positive, with the community and founders supporting this campaign.

We will then collect these ideas and submit them to GitHub - ethereum-optimism/optimism-project-ideas: Ways to contribute to the Optimism Collective

(Zonic NFT Marketplace Community)

(Apetimism NFT Community)

(Bored town NFT Community)

The campaign will be conducted in several phases, with the ultimate target being to reach 2000 high-quality users by the end of April.

Who are your competitors?:

Our direct competitors in the market are Opnames.org (ONS), OPNS, and Punk Domains.

However, we also see the potential for partnership with other parties offering similar solutions, such as ENS, Space ID, and ARB ID.

What differentiates you from your competitors?:

When considering the skill sets of our competitors, it is noteworthy that many of them tend to be led by business-oriented individuals with a strong emphasis on marketing. In contrast, our team at Opti.domains is spearheaded by a development expert who possesses a unique and unparalleled skill set in the realm of cross-chain technology.

Furthermore, it has come to our attention that our competitors are not currently prioritizing permissionless deployment on OP stack chains, which we believe to be a crucial area of focus for both our and the Optimism ecosystem as a whole.

In essence, If marketing prowess is a top priority, ONS (Opnames.org) is your choice. However, if you prioritize innovation and cutting-edge technological solutions, then Opti.domains is a clear choice.

Will your project be composable with other projects on Optimism? If so, please explain:

  • Our domain name service is fully composable with any project operating on the Optimism and OP Stack, facilitating the use of domain names instead of wallet addresses.
  • Our offering is particularly well-suited to multi-chain dashboard applications, providing a means to aggregate data from both Optimism and OP Stack deployed chains.
  • Upon completion of our project development, we anticipate that our solution can play a pivotal role in supporting Optimism governance grants. Specifically, we plan to share 80% of the revenue generated from domain name sales after 2025 towards supporting relevant projects.
  • Our domain name service is also ideally positioned for marketing collaboration with any NFT projects on Optimism and OP stack.


Who are your founders?:

Chomtana Chanjaraswichai
Github: Chomtana (Chomtana) · GitHub
Discord: Chom#1652

What makes your founders well-positioned to accomplish your goals with this project (1-2 sentences on each)?:

I have significant experience in cross-chain development and, last year, successfully developed a cross-chain domain prototype utilizing Axelar technology.

Tell us about the rest of your team (if there are more teammates):

Currently, I am working independently on this project. However, I have devised a plan to collaborate with NFT communities to facilitate marketing efforts, as well as partner with universities to enable student involvement in development.

Is this your first Web3 project?:


If not, what else have you built? (Share links, Github repository, or any other useful information.):

I have built many web3 projects. Let’s share the notable ones.

Axelar Domains


(Original: https://axelar-domains.chom.dev)

Axelar domains is a cross-chain domains prototype I have developed last year during a hackathon. Having observed the potential of OP Stack, I have determined that Optimism is the most suitable chain to initiate with.

AxelarSea NFT Bridge

Our NFT bridging project, which leverages Axelar, has successfully attracted over 40,000 users, with more than 100,000 NFTs being minted on the testnet. Unfortunately, the project is currently paused due to the bear market in the NFT marketplace, where the cost is surpassing revenue.

However, if the Opti.domains project proves to be successful. We may resume the project and potentially rebrand it as a transport layer for bridging any asset that can be wrapped with an NFT.

I understand that Builders grants are subject to a 1 year lock-up, as explained further in this post 2: [Yes/No]:**


Is your project funded? If so, provide an estimate of how many months of funding runway your project has:


Grant Request

What is the size of the grant request? (50k OP max):

50000 OP

How do you justify the size of the grant?

  • Salary and cost reimbursement: 20k OP, given 12 months = approximately 1600 OP/month, which is fair for such an advanced development and managing hackathon to use it for the long-term benefit
  • Marketing budget: 10k OP, given 12 months = approximately 800 OP/month. Necessary for bootstraping the initial marketing campaigns. If not, then decentralized work and developer hackathons are not gonna happen.
  • Decentralized work: 10k OP. I will break down tasks and analyze their dependencies. Given an average of 200 OP per task, we can have 50 tasks which are enough for bootstrapping the profile feature with a medium-sized group of university students.
  • Hackathon reward: 10k OP. Hackathon is designed especially for developers to learn and develop creative mini public goods with rewards from multiple parties. We plan to reward 2000 OP per hackathon for 5 hackathons.


Describe in discrete steps your plan for accomplishing your project:

We’ve structured our plan into phases, yet each one is capable of running concurrently.

Please provide any additional information that will facilitate accountability:(smart contracts addresses relevant to the proposal, relevant organizational wallet addresses, etc.)

Testnet 1 Optimism goerli contract address

BaseRegistrarImplementation - 0x5884BBF32FDB51f383B1d230Ba97AB2C9f0BF81f
ENSRegistry - 0x796b0264191273C44e714ba546F6C3fdee76a4cE
ETHRegistrarController - 0x2eAbd2A3d33B76B93866e365126373C510eBc676
NameWrapper - 0xeA926EB6996235c2b47F95B7BFF3F4058B988E35
PublicResolver - 0x84Fa9a6ce9DDD062A945D2BB6991f75216c167Da
ReverseRegistrar - 0x148a550805893F1f53Cf8EFE6FA52488298bDcD9
Root - 0x5831322c96C06c9e2005B77e9241F84Dad4CBB9c

Testnet 1 Base goerli contract address

BaseRegistrarImplementation - 0xBDD4c9b9581bFcf03A73117D2FF8c8e888F91DA8
ENSRegistry - 0x3560E97fd220668eBF9189a9695aA111be33Af67
ETHRegistrarController - 0xE11572B0F18DC78F30cDDf44c402a5B79511105A
NameWrapper - 0x88D711a0BAc694e7C2D71Fcd7AC7896A02970911
PublicResolver - 0x4815B81B96AB011F4559bF9A160f6Cd796c113E6
ReverseRegistrar - 0x89904370d9f2F2555Ff18a73cdAAe8e7a78EaA8e
Root - 0xa005B448633e89917741fdeA8A5Ed971545bab80

Does your plan depend on the receipt of OP tokens?:

Our core development plan doesn’t depend on it as I have my personal fund available for years.

However, decentralized work and hackathon are depend on it. We have devised a solution to address this challenge through the use of NFTs. Eligible participants in our decentralized work and new-gen hackathon campaigns will receive NFTs, and we will offer buyback opportunities for these NFTs on our partnered marketplace.

What is your plan for the use of the OP token after the 1 year lock-up?:

Our plan involves enabling NFT holders to claim their corresponding OP tokens. The remaining OP token will act as reimbursement for my cash paid and my salary in the development.

We plan to use remaining OP token for long-term self delegation to participate in the optimism governance. However, this approach is not the sole focus of our strategy.

Please provide benchmark milestones for this project. These milestones should guide the Optimism community on the progress of your project during the 1-year lock-up period.

31 April 2023

  • Discord members and Twitter followers: 2000
  • Partners: 3
  • Unique testnet participants: 1000
  • Source of truth: Discord, Twitter, Etherscan

31 July 2023

  • Discord members and Twitter followers: 10000
  • Partners: 10
  • Partner with Optimism, Axelar
  • Unique domain holders on mainnet: 3000
  • Source of truth: Discord, Twitter, Etherscan

30 September 2023

  • Discord members and Twitter followers: 30000
  • Partners: 20
  • Partner with Optimism, Axelar, Coinbase Wallet
  • Unique domain holders on mainnet: 10000
  • Decentralized work developers: 5
  • Source of truth: Discord, Twitter, Etherscan

31 January 2024

  • Discord members and Twitter followers: 100000
  • Partners: 30
  • Partner with Optimism, Axelar, ENS, Coinbase Wallet
  • Unique domain holders on mainnet: 50000
  • Decentralized work developers: 50
  • Source of truth: Discord, Twitter, Etherscan

Developer Hackathon

  • Coordinated by Chom, Work with partners
  • Organize once in Q4 2023
  • Developers participated: 20
  • Source of truth: Media

Please define critical milestones for this project. Critical milestones are meant to show good-faith efforts to accomplish the project. Non-completion of these milestones could lead to revocation of remaining grant rewards.

Testnet 1 - .op and .base domains prototype

  • Developer: Chom
  • Currently Live
  • Source of truth: Working prototype, Deployed contract address

Testnet 2 - Final testing for mainnet release

  • Developer: Chom
  • 1 - 2 weeks after Optimism bedrock merge
  • Source of truth: Working prototype, Contract address deployment

Mainnet release

  • Developer: Chom
  • 2 - 4 weeks after Optimism bedrock merge
  • Source of truth: Working product, Contract address deployment

Universal Registry Resolver integrated to forked Ethers.js and Metamask (Prototype)

  • Developer: Chom
  • By 31 May 2023
  • Source of truth: Github repositories and pull requests

Mainnet release on base

  • Developer: Chom
  • By 1-4 weeks after Base mainnet and Opti.domains mainnet both launched
  • Source of truth: Working product, Contract address deployment

Cross chain domain (Prototype)

  • Developer: Chom
  • Prototype by 30 June 2023
  • Continuously development
  • Source of truth: Working prototype

Permissionless deployment on OP stack ecosystems (Prototype)

  • Developer: Chom
  • By the end of the year 2023
  • Continuously development
  • Source of truth: Working prototype

UI Redesign

  • Developer: Decentralized work participants
  • By the end of the year 2023
  • Source of truth: Website

Profile system

  • Developer: Decentralized work participants
  • By the end of the year 2023
  • Source of truth: Working product

Kindly note that we intend to leverage our current UI design for initial deployment on the mainnet, prior to the anticipated redesign. This approach will provide us with ample time and resources to concentrate on other high-priority tasks, such as cross-chain smart contract development.

Optimism Relationship

Does your project solve a problem for the Optimism ecosystem?:

Yes, we solve two major problems for the Optimism ecosystems

  1. We provide domain name infrastructure for the OP stack ecosystems that enable each deployed chain to rapidly onboard users from the Optimism chain to their chain.
  2. We incentivize new builders to contribute to the Optimism and OP stack ecosystems by providing an ongoing and sustainable reward system. This approach ensures that the ecosystem continues to grow and thrive over time.

How does your proposal offer a value proposition for solving the above problem?:

While it is possible for other companies to develop similar domain name infrastructure, they may not be able to share 80% of their revenue with the community as we do. This is primarily due to the high expenses incurred by such companies. The revenue distribution is crucial for promoting the growth of the Optimism ecosystem and ensuring the sustainability of our project.

Why will this solution be a source of growth for the Optimism ecosystem?:

Undoubtedly, having interoperable domain name infrastructure for the OP stack ecosystems is critical for the Optimism ecosystem. With a domain name infrastructure, each chain in the OP stack can leverage it as a source of KYC or DID, which holds records of activities across chains. Additionally, we offer an 80% revenue-sharing model to accelerate the growth of the Optimism ecosystem. This approach incentivizes new developers to build on the Optimism chain and contributes to the overall growth of the ecosystem.

How committed are you (and your team) to building on Optimism?:

I am committed to building crucial infrastructures such as cross-chain domain infrastructure, as well as infrastructure to support ENS from all chains through ethers and MetaMask wallet. Additionally, I will facilitate decentralized work and developer hackathons to create other necessary supporting components, ensuring the scalability and sustainability of the project. That’s why we dedicate 80% of the revenue to the community.

Is your project Optimism Native?: Yes


I understand that I will be required to provide additional KYC information to the Optimism Foundation to receive this grant: [Yes/No]: Yes

I understand that I will be expected to following the public grant reporting requirements outlined here: [Yes/No]: Yes


Hey @chom, giving you a heads up that this will be the formal comms channel with the grant council builders subcommittee, which consists of @jackanorak @kaereste @danelund.eth, and myself. We’ll make sure we’re around to address any questions you have in this process.

Will you enable ENS owners to claim their .opti domains? Or will I have to buy Gonna.opti from a random bot?

We don’t know what the OP price will be in 1 year, or what happens if it’s double. Do you get half of the OP requested? What if it’s half, is this project still running? Maybe it’s better to remove USD and keep everything in OP tokens to avoid these questions.


Yes, it’s a great suggestion, which I was actually expecting just such a project in the Optimism ecosystem, which will definitely develop the direction of recognition

The domains specifically will be a useful project and an innovation, and I would like to highlight the point that it is just as important for the average user who will be using the ecosystem
But also for a lot of projects, facilitating interaction

But also yes, I think certain problems should be fixed in the proposal

1 Like

I have thought about this concern multiple times. In conclusion, until 2025, you must be whitelisted to mint the domain. To get whitelisted, you must participate in at least one campaign and hold an ENS domain to mint the same name as your .eth name but in .op. However, not all ENS domains can get whitelisted for the following reason.

  1. If we whitelist any ENS holders permissionlessly, we will have difficulty organizing marketing campaigns with our partners because we can’t give significant benefits (Whitelist slot) to their community.
  2. Company names should be forfeited. Given an example, the one holding scb10x.eth may not be SCB 10X. If we give a whitelist to that guys, we will have difficulty partnering with SCB 10X.
  3. Names that aren’t set as the primary name for a long time must be checked manually to ensure they are not used for speculation.
  4. Not only company and non-primary names, but we also need to reserve some rare names that are usually used for speculation, including
    4.1 Names shorter than four characters
    4.2 Names with repeating digits such as 888.op
    4.3 Names that are traded with high volumes

The criteria for the company name aren’t final yet. Here’s an example of how we classify these.

  1. We will pass names to Chat GPT to have them classify whether it is a company name.

  1. We will check whether that name matches a Twitter username. In case it matches, we will ask for Twitter login verification first.

This whitelist system is not yet developed in testnet 1, so in testnet 1, you can mint any name, but it won’t have any effect on the mainnet. Moreover, the testnet is subject to hard reset at any time.

After 2025, we plan to go permissionless. So, if you mint after 2025, you must do it FCFS basis.

1 Like

Thank you for your suggestion. The development is still ongoing regardless of the grant receipt. However, these factors significantly impact marketing and developer relation campaigns. We will revise it to prevent this problem in the future.

1 Like

I have just improved the UI

After discussing with my friend, I have decided to use .op instead of .opti as we shouldn’t worry about ONS if we can deliver actual value.


The innovation of the domain is not in the technology itself, as anyone can create and sell a forked version of ENS and then disappear with the money.

The innovation lies in the project owner’s execution, similar to NFT. Without the project owner’s support, the domain would be worthless.

Most domain projects since 2021 have relied on hype rather than contribution. We are the first to experiment with a contribution-based approach and see its effectiveness.

Here are some more updates I would like to share

I have changed the color of the hero section of the landing page to be more contrast



Looks better, right?

I have drawn a business positioning canvas to have you better understand our position

Whitelisting in Testnet 1

The registration criteria for Testnet 1 has been updated to allow only holders of the respective ENS name to mint a corresponding .op name. If an individual does not possess an ENS name or desires to mint a secondary name, they must select a name that has not been registered on ENS. This modification has been implemented to streamline the campaign process.

The initial contribution campaign

We are going to announce our first campaign, an Ideathon, is designed to benefit both our project and the Optimism ecosystems in the long term. Apetimism, Bored Town, and Zonic OG NFT holders are the initial group invited to participate in the campaign. The response from these NFT communities has been positive, with the community and founders supporting this campaign.

We will then collect these ideas and submit them to GitHub - ethereum-optimism/optimism-project-ideas: Ideas for projects to build on Optimism

(Zonic NFT Marketplace Community)

(Apetimism NFT Community)

(Bored town NFT Community)

The campaign will be conducted in several phases, with the ultimate target being to reach 2000 high-quality users by the end of April.

Can you please provide metrics in the form of a DUNE analytics chart that shows the on chain activity from your project?

We haven’t launched our first campaign officially yet. So, currently, we don’t have any traction to report. Give me a few days to launch the first campaign.

However, our campaign will never get as many users in a few days as ONS but it will benefit the Optimism ecosystems regardless of our project’s success.

Hi, this is Makoto from ENS team.

If I understand correctly, it’s a ENS fork. Are you going to divert from ENS smtart contract codebse and your own featureset, or keep syncing to upstream (=ENS)?

We will keep syncing upstream except for the ETHRegistrarController and XXXPriceOracle contracts. However, we don’t often sync it as it requires users to migrate their NameWrapper manually, which is a pain. We plan to do it quarterly if needed.

ETHRegistrarController is necessary to divert from the ENS codebase as we are adding feature such as interoperability that requires a considerable modification to ETHRegistrarController to grant access to the Transport layer to mint the domain.

Universal Registry Resolver integrated to forked Ethers.js, and Metamask (Prototype) will be developed in a separate repository connected with interfaces so that this feature won’t affect the ENS codebase.

I heard you will deploy the new NameWrapper to the ETH mainnet soon. So, we think that your NameWrapper should have enough stability when it comes to our time launching on the mainnet.

Thank you for your quick response. I have another quesiton.

In your business map, you positioned yourself as “build & contribute” category despite being mainly a fork to start from. What new aspect (other than maintaining the fork and keeping your own registrar for revenue) are you intending to build and what are you planning to contribute back to ENS?

Currently, we have three in the plan.

  1. Interoperability cross-chain domain. Once this has some maturity with enough use cases, this process takes years. ENS can utilize our solution to enable cross-chain capability to your .eth domains without risky experiments on the mainnet with your 2M+ user bases.

  2. Universal Registry Resolver. I see that currently, ethersjs is hardcoding for mainnet mapping to the official ENSRegistry only. However, now there are many domain names on each chain, such as .bnb by Space ID. As a result, one party must develop this solution.

  1. ENS Lightweight indexer - A solution to index ENS in multiple chains using a serverless solution and public fullnode provided officially by each chain. Currently, our testnet 1 is using it, and it costs us 0$ per month if there are a few users. Compared to the subgraph solution, this one is more cost-efficient and easier to scale cross-chain. However, we may still contribute to the subgraph solution.

Can you give us more detail about how your solution differ (or supplementary ) with ENS’s own L2 plan?

Are you developing on your own? Is there a github repo?

The main difference is that I believe each chain’s resolver should hold different data specialized to that chain independently. Let’s give an example

axlUSDC address is different on each chain. With an independent resolver on each chain, one just simply points the domain to the correct axlUSDC address on each chain.

Another use case, Starb*** chain may keep their membership information in their chain. Independent resolvers let Starb*** chain operator design their specialized resolver on their chain without worrying about any compatibility problems.

To query data on L2 or L3 (such as Base or Starb*** chain deployed with Op Stack if any) one doesn’t need to query a smart contract in L1 to get StorageHandledByL2 revert message to query smart contract in L2 / L3. Because the resolver in L3 is independent of L2, one can query data from the resolver in L3 directly.

If there is an important thing that must be done on the main Optimism chain, one can ask for the data from L3 chain and wait for the transport layer (Optimism bridge) to pass the data back and call necessary function without needing to use offchain gateway. Hope we don’t need to wait 7 days anymore in the future.

I don’t feel sure that I understand your L2 design correctly, as I mostly see that you are focusing on offchain things.

I have just made it public. But it is in development currently. It combines a whitelist system and indexer in a monolithic way. To have it used by others, I must separate the indexer from the whitelist system first.

If you have more questions I will answer tomorrow as I have to go sleeping now.

Thank you for all the answers @chom. I see you are a solo dev working on this, but in many places you talk about “WE”

Do you mind telling more about your team if you have one?

1 Like

I am developing this solo. But for marketing, I ask for advice from my friends and contact NFT communities in Thai. However, I haven’t hired them; now they are all busy. So, may need to shift to organic reach by talking about the project in the community first.

Sorry for confusing you with “WE”.

I am developing DiamondResolver as I have tried new alpha ENS, upgraded the resolver, and lost all existing records. I don’t think this is good as either can’t store data permanently or can’t upgrade the resolver but don’t sure what ENS thinks. Moreover, if ENS keeps adding functions, one day contract size will exceed the limit. Diamond (ERC-2535: Diamonds, Multi-Facet Proxy) is designed to solve these problems.

GitHub - Opti-domains/ens-diamond-resolver (Not completed yet)


Just a general observation as an ENS protocol delegate.

ENS has been working on Layer 2 plan for the past 2 years.

For Optimism related works, we have proof of concept level code and also dm3 team is working on Optimism resolver

As far as I understand, most of the work you have completed (apart from building your own indexer) is based on forking ENS contracts. It would be really nice if you can spend time and effort contributing to the ENS ecosystem, rather than doing your own (especially since there are already 3 different versions of name services on OP already).


Hi, I have done market research for several days and have understood that people usually just want to do a few clicks, except we have multi-million dollars invested from VCs (Because of airdrop).

The new flagship feature in testnet 2, according to market research, will accelerate the use case of ENS in the NFT field. After the success of Optimism, I can adapt it to NFT communities in Ethereum and greatly benefit the ENS ecosystem itself.

I have successfully deployed the first version of DiamondResolver at 0x6eE51AB6f1dA30D8B833aD234E406Fffc49D6813. It is a crucial component as one can develop just the part that we want to change (For example, OptimismResolverStubFacet → DiamondResolver). Not the entire resolver and is still compatible with PublicResolver standard.

However, there are many forkers with millions of dollars ready to steal the innovation, buy the hype and kill the developer. I choose to close the source of the upcoming DiamondResolver (The first version will remain open source) and other innovations until enough support and adoption.

I am happy to share the code with some of you @matoken.eth @Gonna.eth if you want.

I can’t reply to you in the ENS gov forum because I don’t have the write access. I have asked for it for almost 5 days and will open a support ticket tomorrow.

80% hasn’t been breakdown formally this year. It is intended to support individual developers and projects that contribute to Opti.domains (which is also ENS compatible, so almost every eligible projects benefit ENS DAO) and Optimism ecosystems.

It should indefinitely share revenue to all our early partners, especially ENS DAO, if we can cooperate. You may not trust me, but I think other super hype forks never share any revenue with you, and my project has the highest chance to implement it.

If you want me to contribute to the ENS ecosystem and lead the adoption on Optimism, I want to make sure that I will never be sued for developing .eth in the Optimism chain. There is a lot of drama in Optimism now.

Here is my current design for L2 .eth. It’s a merge of you and my idea about the cross-chain domain. Having minted .eth NFT in Optimism play a crucial role in driving adoption. And it must also be ERC-721 compatible, for unlimited compatibility with NFT marketplaces.

It designs to avoid the L1 gas fee and collect some small additional bridge fees to operate our infrastructure and share revenue with ENS DAO.

1 Like