Application Details
Last published on: 7 October 2026 at 15:37 UTC
Application Responses
Section: Applying Entity Information
This question set collects information regarding the legal entity that would enter into a Registry Agreement with ICANN upon successful completion of all relevant application processes. The information collected is intended to be used for background screening.
Provide the full legal name of the applying entity as it appears on the official registration documents. Do not use abbreviations.
Cardano Stiftung
Provide the name under which the applying entity is doing business, if different from the full legal name answered in Question 1. Such a name must be registered with appropriate local jurisdiction or public authority.
Cardano Foundation
Provide the long form (no acronyms) of the legal entity form/business structure of the applying entity as it appears on the official registration documents. If the original script of the legal entity form/business structure is not English, ONLY provide its official English translation. No additional information should be provided as this will be used for the automatic population of the Registry Agreement.
Foundation
The jurisdiction indicates the location in which the business of the applying entity is registered for legal and financial purposes. This is either 1) a country name, or a 2) state/territory name, depending on where the applying entity is registered. No additional information should be provided as this will be used for the automatic population of the Base Registry Agreement. Examples include "Delaware", "Germany", etc.
Switzerland
Provide the website URL of the applying entity, if available.
https://cardanofoundation.org/
1. Choose Yes or No. 2. Use the definition of Affiliate from the Base Registry Agreement (see https://www.icann.org/en/registry-agreements/base-agreement).
false
Choose Yes or No.
false
41
Provide the primary business phone number without including the country code.
(0) 41 562 01 19
Provide the primary business email address of the applying entity.
registry@cardanofoundation.org
Enter the street address (no PO Box).
Dammstrasse 16
Enter the city, village, municipality, etc.
Zug
Enter the state, province, department, territory, prefecture, oblast, etc., if applicable.
Switzerland
1. Enter the postal code, if applicable. 2. If a postal code does not exist, type “Not Applicable”.
6300
CH
Section: Applying Entity Background and Organization
This question set collects information related to the individuals who will have access to TAMS, manage the application, and receive inquiries.
Jillian Mac Nab Watkins , Mary Beth Buchanan, Fernando Vazquez Cao, Andreas Eschbach
Nicolas Jacquemart, Andreas Pletscher, Stephen Wood, Frederik Gregaard, Giorgio Zinetti
Nicolas Jacquemart, Andreas Pletscher, Stephen Wood, Frederik Gregaard, Giorgio Zinetti
Jillian Mac Nab Watkins , Frederik Gregaard
Section: Self-Certification
Provide a single document for Self-Certification question Q4.2-1. The document must include only the SC4.2-1.1, SC4.2-1.2, or SC4.2-1.3 statements. Do not modify any of the Self-Certification statements.
1. Provide a single document for Self-Certification question Q4.2-1. 2. The document must include only the SC4.2-1.1 through SC4.2-1.3 statements. 3. Do not modify any of the Self-Certification statements. 4. If the applying entity cannot Self-Certify the SC4.2-1.1 through SC4.2-1.3 statements, provide a document that explains why the applying entity cannot Self-Certify the SC4.2-1.1 through SC4.2-1.3 statements.
Section: Security Policy and Planning
Provide a single document for Self-Certification question AGB Q220, Q5.1-1. The document must include only the SC5.1-1.1 through SC5.1-1.3 statements. Do not modify any of the Self-Certification statements. If the applicant cannot Self-Certify SC5.1-1.1 through SC5.1-1.3 statements, provide a document that explains why the entity cannot Self-Certify the SC5.1-1.1 through SC5.1-1.3 statements.
1. Provide a single document for Self-Certification question Q5.1-1. 2. The document must include only the SC5.1-1.1 through SC5.1-1.3 statements. 3. Do not modify any of the Self-Certification statements. 4. If the applying entity cannot Self-Certify the SC5.1-1.1 through SC5.1-1.3 statements, provide a document that explains why the applying entity cannot Self-Certify the SC5.1-1.1 through SC5.1.1-3 statements.
Section: DNS Abuse
Provide a single document for Self-Certification question AGB Q221, Q5.2-1. The document must include only the SC5.2-1.1 through SC5.2-1.7 statements. Do not modify any of the Self-Certification statements. If the applicant cannot Self-Certify the SC5.2-1.1 through SC5.2-1.7 statements, provide a document that explains why the applying entity cannot Self-Certify the SC5.2-1.1 through SC5.2-1.7 statements.
1. Provide a single document for Self-Certification question Q5.2-1. 2. The document must include only the SC5.2-1.1 through SC5.2-1.7 statements. 3. Do not modify any of the Self-Certification statements. 4. If the applying entity cannot Self-Certify the SC5.2-1.1 through SC5.2-1.7 statements, provide a document that explains why the applying entity cannot Self-Certify the SC5.2-1.1 through SC5.2-1.7 statements.
Section: Primary String
This question set collects basic information regarding the string that is being applied for (for example, a-label, meaning, script). If the applying entity opts to designate a replacement string, it must answer the same set of questions for the replacement string from the AGB Question Set 5 on.
ada
Provide the meaning, or restatement of the string in English, that is, a description of the literal meaning of the string in the opinion of the applying entity. If there is no literal meaning in English (for example, a brand name or a proper noun without a translation) simply state "No English Translation"
“ada” refers to the native digital asset of the Cardano blockchain, ada. It is named after mathematician Ada Lovelace, and is used, inter alia, to interact with the Cardano blockchain, operate it and conduct transactions on it.
If an IDN, provide the script of the string (both in English and as referenced by the RZ-LGR/ISO 15924)
Latin
Provide a representation of the string according to the International Phonetic Alphabet.
/ˈeɪdə/ (AY-da)
Confirm the statement using a checkbox.
true
1. Describe the mission and purpose of the applied-for gTLD, including the intended registrants and users, and the related activities that have been or will be carried out to achieve this purpose. 1a. If applying for a variant of an existing gTLD, please also describe the mission and purpose of the existing gTLD, including the intended registrants and users, and the related activities that have been or will be carried out to achieve this purpose. 2. Explain how this purpose is sustainable over time.
The mission of the ada community-based gTLD is to secure a competitive digital presence for the Ada Community and provide added brand value and presence for the Cardano ecosystem, which is commonly identified by “ada”, its native digital asset and the foundation for the ecosystem’s activity. “Ada” and “Cardano” Community are synonymous in this application. This gTLD will operate like any other generic gTLD, but with the purpose of serving the Ada Community. Related activities to achieve this mission include: - Generating revenue to reinvest for the benefit of the gTLD and/or the Ada Community - Coordinated ecosystem marketing endeavours; - Cardano Foundation-driven adoption endeavours; - Community product development and 2030 roadmap. Sustainability of the Mission The purpose of this gTLD is sustained through rigorous maintenance and enforcement policies designed to keep the namespace active and relevant. To ensure community interests are being served, the Registry Operator will continuously seek community input on how registrants can benefit from using the top-level domain.
Section: Community
This question set collects information specific to Community gTLDs. However, question 133 (Mission & Purpose) must be answered by all applying entities.
General
Yes
1. Provide the name of the community that the applying entity is committing to serve. 2. Describe the distinct aspects of the community.
The Ada Community, also known as the “Cardano” Community. This global community is centered around the development, promotion and use of ada, the digital asset of the Cardano blockchain.
Enter a category that best describes your community. Some examples of community categories could include, but are not limited to: activity-based and volunteer groups, online or social media groups, religious or political groups, diasporic communities, linguistic communities, celebrity or sports team supporters.
The Ada/Cardano Community is a global community of identifiable individuals and entities united by their participation in the Cardano blockchain protocol and its native digital asset “ada”. This community is technology and innovation-focused, organized around the governance, development, commercialization, and use of ada and Cardano. The Ada/Cardano Community, through specific voting mechanisms on the Cardano blockchain, has defined itself according to these terms in the Cardano Constitution, published on https://cardano.org/constitution/: “Cardano Community. The collective group of all individuals and organizations that, in embracing the shared principles and objectives set forth in the Cardano Blockchain Ecosystem Constitution, own ada, develop, build on, support, maintain, contribute to, and use the Cardano Blockchain.” The total number of unique addresses in the Cardano ecosystem exceeded 5,700,000 in December 2025. This figure has grown over several years since Cardano's launch in 2017 and shown continual activity over the years via numerous metrics. Community members are represented by and include several organisations, including the Cardano Foundation (see Questions 135 and 136), which is one of the founding entities of Cardano and the trademark holder for “Cardano” and “ada”. Certain member-based organizations, such as Intersect and PRAGMA, provide structured administration and committee-based collaboration for technical, governance, and development activities (see Questions 139 and 146). In addition to on-chain participation, the Ada/Cardano Community operates through structured off-chain governance and coordination mechanisms, including associate members, paid individual members, and enterprise participants collaborating across governance, technical, and community-focused committees.
Organization
Describe and provide evidence of the relationship between the applying entity and the identified community.
The Cardano Foundation is an independent, Swiss-based not-for-profit organization whose purpose is to promote the development of new technologies, specifically the Cardano blockchain and its native digital asset “ada”. The Cardano Foundation is one of the founding entities of Cardano and is a prominent member of the ecosystem - organizing key events, maintaining and developing Cardano technology, and providing a point for community interaction via various forums. The Cardano Foundation is the trademark holder for the “ada” and “Cardano” trademarks and wordmarks. For the World Intellectual Property Organization (WIPO) report showing the Cardano Foundation’s registration of the “ada” trademark, see the attached corresponding documentation. For the “Cardano trademark”, see the attached corresponding documentation. To understand how the Cardano Foundation serves its community, it is helpful to look at its three core operational pillars: Technology, Adoption, and Governance. 1. Technology The Cardano Foundation works to ensure the Cardano blockchain remains secure, stable, and resilient. The Cardano Foundation monitors the blockchain’s health at a system-wide level. The Cardano Foundation supports the development of critical open-source tools. These are shared technical resources that benefit the Ada/Cardano Community, however they are resource-intensive and require stewardship of the Cardano Foundation. The Cardano Foundation also supports the integration of external services to enhance the Cardano blockchain’s reliability and functionality. 2. Adoption The Cardano Foundation drives ada and Cardano adoption through structured programs and partnerships. The Cardano Foundation works with large enterprises and international organizations, such as to pilot applications and key software development. The Cardano Foundation also operates a venture program that provides investment and advisory support to early-stage organizations and community members building on the Cardano network. Through certified programs, the Cardano Foundation provides structured education and certification to learners wanting to improve their knowledge of Cardano. This supports workforce development and professional standards, supporting the Ada/Cardano Community. The Cardano Foundation engages with policymakers and participates in public consultations to support regulatory clarity in matters relevant to the Cardano blockchain and ada digital asset. 3. Governance The Cardano Foundation participates in governance directly on the Cardano blockchain as a member of the Ada/Cardano Community. It seeks to foster robust governance practices and serves in several roles throughout community committees.
Describe and provide evidence related to the community organization, any relevant organizing bodies, and any relevant leaders within the community.
The Ada/Cardano Community is organized through a multi-stakeholder governance framework. Rather than relying on a single entity, the community is administered and represented by multiple organizing bodies. 1. The Cardano Foundation The Cardano Foundation, an independent Swiss non-profit, is one of the founding entities of Cardano, and acts as a distinct body focused on the promotion and development of new technologies, specifically the Cardano blockchain, and accordingly on the external representation and legal protection of the Cardano and Ada brand. The Cardano Foundation administers certain intellectual property (such as the "Ada" and “Cardano” trademarks) and key GitHub repositories, overseeing certain standards, working to ensure that the community's identity is protected. The Cardano Foundation represents the community's interest in promoting the adoption, education, and long-term sustainability of Cardano, functioning as one aspect of the ecosystem's public presence. 2. On-Chain Governance Bodies The Ada/Cardano Community is further organized through on-chain governance roles, which formalize the community's ability to self-administer directly via the Cardano blockchain. This enables the community to vote on certain proposals, such as technical updates to the Cardano blockchain and treasury withdrawals. There is a defined limit of governance actions and they do not include day-to-day operation of the TLD, which will remain with the Cardano Foundation as the applicant and Registry Operator. There were more than 1,000 Delegated Representatives, a governance role, registered on Cardano at the beginning of 2026. 3. Member-Based Organizations: Intersect Intersect serves as a hub for the Ada/Cardano Community. It is a Member-Based Organization (MBO) tasked with coordinating technical development and governance continuity of the Cardano ecosystem. Intersect administers civic infrastructure for participating community members, including the organization of committees and working groups. Intersect has a formal membership structure for participating members, with over 5,000 members as at the end of 2025. The Cardano Foundation is itself a member of Intersect with various positions. PRAGMA PRAGMA is a member-based, not-for-profit Open Source Association for blockchain software projects. It aims to foster an alternative open-source ecosystem for Cardano and beyond. PRAGMA had five members at the end of 2025 with a number of additional Ada/Cardano Community members represented in its maintainer committees.
1. Describe any formal membership process, if there is one. 2. If there is no formal membership process, provide evidence related to how an individual can join the identified community (i.e., “self-identify” as a community member).
Anyone who owns ada or develops the Cardano blockchain is considered part of the Ada/Cardano Community. The Ada/Cardano Community, through specific voting mechanisms on the Cardano blockchain, has defined itself according to these terms in the Cardano Constitution, published on https://cardano.org/constitution/: “Cardano Community. The collective group of all individuals and organizations that, in embracing the shared principles and objectives set forth in the Cardano Blockchain Ecosystem Constitution, own ada, develop, build on, support, maintain, contribute to, and use the Cardano Blockchain.” The identity of the Ada/Cardano Community is intrinsically intertwined with the digital asset ada, as is seen in the Cardano Constitution which is calibrated, throughout, towards the holders of ada as members of the Community.
Provide the primary location of the community.
This community is located worldwide. Its reach is evidenced by on-chain activity, wallet addresses, 5,359 Intersect members over 125+ countries in 2025, plus over 3,000 attendees at recent events in the US, Germany, India, Brazil, Argentina, and Kenya.
1. Provide the estimated size of the community. The size should be in number format (e.g., “1,000,000 members”). 2. If the community is divided by group, region, sector, etc., this should include estimated size for each group.
The community includes over 5.7M unique wallet addresses as of December 2025, 5,359 Intersect members globally, and over 1,000 registered DReps (participating globally), supported by over 3,000 global event attendees at recent events.
Provide the estimated size of the community that is administered or represented by each relevant organizing body in the identified community.
The Cardano Foundation represents the entire community by developing and promoting of ada and protecting the ada/Cardano brand. It represents 3.22% voting power on Cardano (03.2026) Intersect represents 5,359 members and PRAGMA 5 members by end 2025.
Engagement
1. Provide evidence of any documented practices of community efforts to date 2. The applying entity should provide documentation of the following practices, which should have occurred within the two years leading up to application submission: a) Offering support; b) Sharing information; c) Responding to specific community needs; d) Fostering and strengthening relationships within the community.
Yes, please see the below corresponding documentation containing the answer to this question and supporting links.
1. Describe whether the applying entity has a role in any of the activities listed in Question 141. 2. If the applying entity does play a role, provide evidence of the applying entity’s role. If the applying entity does not play a role, describe why this is the case.
Please see the below corresponding documentation containing the answer to this question and supporting links.
Awareness
1. Provide evidence that demonstrates that community members are aware of the identified community and the different member groups or segments within the identified community. 2. The applying entity should provide documentation of the following practices, which should have occurred within the two years leading up to application submission: a) Surveys conducted; b) Records of activities involving a diversity of community groups, segments, or members.
Yes, please see the below corresponding documentation containing the answer to this question and supporting links.
1. Provide evidence of community members’ awareness of the applying entity and its intent to apply for a community gTLD. 2. If there is no such evidence, explain why not.
Yes, the Cardano Foundation launched a public vote (“an Info Action”) prior to preparing this application to gauge community support. The community has long been aware of the Cardano Foundation as a founding entity of the Cardano ecosystem to which ada is the native digital asset. An Info Action is an on-chain governance action that allows submitters to seek community support, and community members can in turn engage with the submitter and one another on the topic before casting a verified vote. The Cardano Foundation’s Info Action received approximately 75% support from Delegated Representatives for its goal of applying to become the registry operator for this top-level domain. The Info Action and results can be found here: https://adastat.net/governances/a36eafaea085b77f97cceacf07fe9450f8c6b47fec3af94da8f7d158a1fc972200 The voting results of the Info Action have been copied to the attached corresponding documentation for ease of reference.
Established Presence
Provide evidence of the established presence of the community prior to the opening of the application submission period.
1. Provide evidence that demonstrates that individuals and groups outside of the community show an awareness of the identified community. 2. The applying entity should provide documentation of the following practices, which should have occurred within the two years leading up to application submission: a) Media or other public information regarding the community and its activities or members; b) Discussion of the community in various fora, whether online or in person; c) Evidence of partnerships or collaborations with groups outside of the identified community; d) Evidence of the chartering or organization of the community prior to the opening of the application submission window; e) Evidence of contributions (for example, cultural or scientific) to a larger society or population;
Yes, please see the below corresponding documentation containing the answer to this question and supporting links.
Longevity
1. Provide evidence of the longevity of the community. 2. The applying entity should provide documentation of the following practices which should have occurred within the two years leading up to application submission: a) Evidence of recurring or scheduled activities that demonstrate continuity over time; b) Documented records of past activities that demonstrate a long-standing tradition or practice; c) Records of discussions emphasizing the community’s enduring presence or its cultural significance.
Yes, please see the below corresponding documentation containing the answer to this question and supporting links.
Nexus
Explain how the applied-for string matches the name of the community or is a well-known alternative name (whether long or short form) of the community.
Yes, the “ada” string matches the ticker symbol (used on all major platforms) and native digital asset for the Cardano blockchain and the community of its users. Ada is a trademark held by the Cardano Foundation, and is recognized globally as signifying both the Ada/Cardano Community, and the ada digital asset around which it is centered. As indicated in previous questions, “Ada” and “Cardano” are synonymous and the Community is well known, of a significant size, and has grown over the years. To join this community, use of Ada is central to community membership (see Question 137). Any new or prospective community member searching “Cardano” or “Ada” online will see both terms used to describe this community, and purchasing ada on any major platform will show “ada” as the symbol and name for the digital asset, while also acting as a short name in referencing the Cardano blockchain.
1. Explain how the applied-for string clearly relates to or represents the community 2. Explain whether the applied-for string has any other significant meaning beyond identifying the community or community members described in the application. The applying entity may wish to provide pertinent information regarding any particular geography, region, or themes that may be alluded to by the string, of which the community may or may not be a part.
Yes, the general public will instinctively think of the Ada/Cardano Community when thinking of the applied-for string (ada). As both the formal name and ticker symbol of Cardano’s native digital asset, as well as a short name when referencing Cardano, the public instinctively recognizes Ada in a similar manner to TSLA, AAPL, META, and GOOG for the organizations they represent, as well as proponents of those brands. Like most 3-letter terms, “ada” could potentially have a different meaning to different people around the world (eg Ada is a popular women’s name in Germany). However, as a highly ranked global blockchain (source: https://coinmarketcap.com/chain-ranking/) with over 5.7 million international users, the Ada/Cardano Community is the only international organization with global recognition by the terms “ada” and/or “Cardano”.
Community Registration Policy
Select from Radio Buttons - Yes/No. Notes: 1. Community Registration Policies are conditions that community gTLD registry operators impose upon registrants within their gTLDs. 2. If you select “Yes” to this question, the applying entity is required to pay the conditional Registry Commitments Evaluation fee, and Community Registration Policies that are approved by ICANN will be scored in the CPE (if the applying entity elects to participate) and included in Specification 12 of the applicable Base RA. 3. If you select “No,” then the application cannot proceed as a community application.
Yes
1. Draft the Community Registration Policy as proposed contract language. Policies that are approved by ICANN will be included in Specification 12 of the applicable Registry Agreement and will be subject to enforcement by ICANN Contractual Compliance. See Appendix 4 Base Registry Agreement, Specification 12 for drafting approach. Consider the usage of defined terms and the definitions of such terms in the 2026 Round Base RA. 2. Enter a single proposed Community Registration Policy with respect to registrant eligibility in each response field. Up to 10 Community Registration Policies can be submitted. 3. Follow this format to propose what the Registry Operator must do and/or must not do: a) “Registry Operator shall___”; and/or b) “Registry Operator shall not___”. 4. Follow this format to propose any specific requirement(s) that the Registry Operator commits to include in its Registry-Registrar Agreement for registrars ,: a) "Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall___”; and/or b) "Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall not___”. 5. Follow this format to propose any specific requirement(s) that the Registry Operator commits to require registrars to include in the applicable Registration Agreements: a) "Registry Operator will include a provision in its Registry- Registrar Agreement that requires Registrars to include in their Registration Agreements a provision requiring ___"; and/or b) "Registry Operator will include a provision in its Registry- Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting ___". 6. Include any objective measures that can be applied to demonstrate the Registry Operator’s compliance with the Community Registration Policy. For example: a) Registry Operator shall develop and implement a registration eligibility policy and publish this policy on its website no later than the date on which the TLD is delegated in the DNS. b) Registry Operator shall review the registration policy described in (a) at least once per year, and publish the results of such review (including any updates to the registration policy) on its website within thirty (30) days following the anniversary of the Effective Date. 7. If the Community Registration Policy is limited in time, duration, scope, or any other factors, specify the applicable limitations. For example, if a registrant eligibility restriction is time-limited, the applying entity must state if the restriction will apply for the lifetime of the gTLD, only during a specified period, or for some other defined period (such as, Registry Operator shall, for a period of x days from the Effective Date, ___). 8. See Section 7.8.3.3 Registry Voluntary Commitments (RVCs) Criteria for evaluation criteria that ICANN will apply for evaluating each proposed Community Registration Policy.
Registry Operator shall adhere to the following eligibility criteria with respect to registration for community members: Eligibility is limited to individuals and entities that are members of the Ada/Cardano Community (the Community) that meet community recognized standards or have a strong Ada- and/or Cardano-brand affiliation: 1. Individuals and entities that are holders of the native digital asset of the Cardano Blockchain (ada) or that otherwise originate transactions on the Cardano Blockchain or promote the Cardano Blockchain that affirm or can provide proof on request of: - Proof of control of a wallet holding ada - Proof of intent to join the Ada/Cardano Community as an ada holder within 90 days of registration; - Other proof of ada ownership (e.g. via a centralized exchange) - Proof of originating transactions on the Cardano Blockchain (ada) - Proof of material promotional efforts for the Cardano Blockchain (ada) 2. Individuals and entities that affirm, or can provide proof on request, of operation of a project that utilises the Cardano Blockchain or ada as a token. Registry Operator shall allow trademark holders, including those who are not necessarily Ada/Cardano Community members, to register their trademarks during Sunrise, General Availability, and/or any other period as published on its website or launch plans, as part of its efforts to promote a safe and reputable namespace. Registry Operator shall develop and implement a registration eligibility policy and publish this policy on its website no later than the date on which the TLD is delegated in the DNS. Registry Operator shall reserve the right to review the registration policy from time to time, and may publish the results of such review on its website.
1. Draft the Community Registration Policy as proposed contract language. Policies that are approved by ICANN will be included in Specification 12 of the applicable Base Registry Agreement and will be subject to enforcement by ICANN Contractual Compliance. See Appendix 4 Base Registry Agreement, Specification 12 for drafting approach. Consider the usage of defined terms and the definitions of such terms in the 2026 Round Base RA. 2. Enter a single proposed Community Registration Policy with respect to name selection criteria or rules for the applied-for string in each response field. Up to 10 Community Registration Policies can be submitted. 3. These criteria or rules should align with the community objectives of the applied-for gTLD string. 4. Follow this format to propose what the Registry Operator must do and/or must not do: a) “Registry Operator shall___”; and/or b) “Registry Operator shall not___”. 5. Follow this format to propose any specific requirement(s) that the Registry Operator commits to include in its Registry-Registrar Agreement for registrars: a) ""Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall___”; and/or b) ""Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall not___”. 6. Follow this format to propose any specific requirement(s) that the Registry Operator commits to require registrars to include in the applicable Registration Agreements: a) ""Registry Operator will include a provision in its Registry- Registrar Agreement that requires Registrars to include in their Registration Agreements a provision requiring___""; and/or b) ""Registry Operator will include a provision in its Registry- Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting ___"". 7. Include any objective measures that can be applied to demonstrate the Registry Operator’s compliance with the Community Registration Policy. For example: a) Registry Operator shall develop and implement a name selection rule and publish it on its website no later than the date on which the TLD is delegated in the DNS. b) Registry Operator shall review the name selection rule described in (a) at least once per year, and publish the results of such review (including any updates to the rule) on its website within thirty (30) days following the anniversary of the Effective Date. 8. If the Community Registration Policy is limited in time, duration, scope, or any other factors, specify the applicable limitations. For example, if a name selection rule is time-limited, the applying entity must state if the rule will apply for the lifetime of the gTLD, only during a specified period, or for some other defined period (such as, Registry Operator shall, for a period of x days from the Effective Date, ___). 9. See Section 7.8.3.3 Registry Voluntary Commitments (RVCs) Criteria for evaluation criteria that ICANN will apply for evaluating each proposed Community Registration Policy.
Registry Operator shall impose that eligible registrants shall be able to register domain names that do not deceive internet users, or cause material detriment to the Ada/Cardano Community. Registry Operator shall not allow Registrants to register any domain names that i) deceive internet users, or cause material detriment to the Ada/Cardano Community or ii) are: 1. Registered according to inaccurate information; 2. Used to facilitate, participate in or further illegal activities; 3. Violate the intellectual property rights of others; 4. Registered in bad faith to create confusion within the Ada/Cardano Community and Internet users; 5. Used against the interests of the Cardano ecosystem; 6. Used to damage, disable, impair, or otherwise attack ada sites or the networks connected to ada sites; Registry Operator shall develop and implement a name selection rule and publish it on its website no later than the date on which the TLD is delegated in the DNS. Registry Operator shall reserve the right to review the name selection rule from time to time, and may publish the results of such review on its website.
1. Draft the Community Registration Policy as proposed contract language. Policies that are approved by ICANN will be included in Specification 12 of the applicable Registry Agreement and will be subject to enforcement by ICANN Contractual Compliance. See Appendix 4 Base Registry Agreement, Specification 12 for drafting approach. Consider the usage of defined terms and the definitions of such terms in the 2026 Round Base RA. 2. Enter a single proposed Community Registration Policy in each response field. Up to 10 Community Registration Policies can be submitted. 3. Follow the format to propose what the Registry Operator must do and/or must not do: a) “Registry Operator shall___”; and/or b) “Registry Operator shall not___”. 4. Follow this format to propose any specific requirement(s) that the Registry Operator commits to include in its Registry-Registrar Agreement for registrars: a) ""Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall___”; and/or b) ""Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall not___”. 5. Follow this format to propose any specific requirement(s) that the Registry Operator commits to require registrars to include in the applicable Registration Agreements: a) ""Registry Operator will include a provision in its Registry- Registrar Agreement that requires Registrars to include in their Registration Agreements a provision requiring___""; and/or b) ""Registry Operator will include a provision in its Registry- Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting___"". 6. Include any objective measures that can be applied to demonstrate the Registry Operator’s compliance with the Community Registration Policy. For example: a) Registry Operator shall develop and implement a Community Registration policy and publish this policy on its website no later than the date on which the TLD is delegated in the DNS. b) Registry Operator shall review the Community Registration Policy described in (a) at least once per year, and publish the results of such review (including any updates to the registration policy) on its website within thirty (30) days following the anniversary of the Effective Date. 7. If the Community Registration Policy is limited in time, duration, scope, or any other factors, specify the applicable limitations. For example, if a commitment is time-limited, the applying entity must state if the rule will apply for the lifetime of the gTLD, only during a specified period, or for some other defined period (such as, Registry Operator shall, for a period of x days from the Effective Date, ___). 8. See Section 7.8.3.3 Registry Voluntary Commitments (RVCs) Criteria for evaluation criteria that ICANN will apply for evaluating each proposed Community Registration Policy.
Registry Operator shall work with the Community prior to launch to reserve a list of community-priority names, and develop a policy for allocating these names to existing Community members. Community-priority reserved names will be allocated to Community members for a defined term, with periodic reviews conducted by the Registry against their use plans. The Registry Operator shall reserve a list of names useful to the Ada/Cardano Community (such as industry sectors, and nouns with economical or technological significance) for allocation at a future time and in a manner determined by the Registry Operator, in consultation with the Community. The Registry Operator shall, for a period of at least 7 days prior to General Availability, hold one or more Limited Registration Periods with eligibility restricted to qualified Community members, and qualifications clearly defined prior to launch and published on its website. Registry Operator shall develop and implement a Community Registration policy and publish this policy on its website no later than the date on which the TLD is delegated in the DNS. Registry Operator shall reserve the right to review the community registry policy from time to time, and may publish the results of such review on its website. The sponsoring registrar of any ada domain registration shall validate customer email addresses or any other contact information it collects.
1. If you are proposing any limitation to a proposed Community Registration Policy in Questions 151-153, please provide a rationale in this response field. Please see Section 7.8.3.3 Registry Voluntary Commitments (RVCs) Criteria. 2. If you are not proposing any limitation to a proposed Community Registration Policy in Questions 151-153, please type ""Not Applicable"" in this response field.
The limitations proposed in the Community Registration Policy (Questions 151–153) are designed to ensure that the top-level domain serves as trusted, authentic namespaces for the Cardano ecosystem and serving the Ada/Cardano Community. These restrictions are necessary to prevent abusive registrations, protect the reputation of the Cardano blockchain and its native asset ada, and ensure that registrants have a connection to the community or otherwise that their participation will further the community’s principles.
1. Provide an explanation of how the proposed Community Registration Policies meet the Registry Commitments Evaluation criteria 4 and 5 using the considerations in the Section 7.8.3.3 Registry Voluntary Commitments (RVCs) Criteria. 2. Consider whether the proposed Community Registration Policy could be argued to be duplicative of a requirement under applicable law, ICANN agreements, or ICANN Consensus Policies or Temporary Policies. There may be circumstances in which a Community Registration Policy that would duplicate requirements under applicable consensus policy or law could be approved at ICANN’s sole discretion. If not duplicative, please explain why you believe the Community Registration Policy is not duplicative. If yes, please specify such a requirement and explain why you believe duplication in the Base RA is necessary. 3. Consider whether the proposed Community Registration Policy could be argued to be contrary to a requirement under applicable law, ICANN agreements, or ICANN Consensus Policies or Temporary Policies. ICANN will not approve any Community Registration Policies that are found to be contrary to applicable laws, ICANN agreements and policies. Please share your views on this issue in the answer to this question. 4. Consider whether the proposed Community Registration Policy could be argued to be incompatible with ICANN’s Bylaws. ICANN will not approve any Community Registration Policies that are found to be incompatible with the ICANN Bylaws. See background at the ICANN Board resolution 2024.06.08.08-2024.06.08.10. Please share your views on this issue in the answer to this question. 5. Consider whether the proposed Community Registration Policy requires the operation of an additional Registry Service. The applying entity shall engage its selected RSP to discuss the implementation of such an additional Registry Service, which must be evaluated through the RSP Program and approved by ICANN.
The proposed policies are designed to ensure the integrity, security, and specific community purpose of the TLDs while adhering to ICANN’s Bylaws and technical requirements. Criterion 4: No Duplication or Contradiction of Existing Requirements Criterion 4 states that any Registry Voluntary Commitment (RVC) "should not duplicate or be contrary to requirements under applicable law, ICANN agreements, or ICANN Consensus Policies or Temporary Policies". The Cardano Foundation’s proposed Community Registration Policies are distinct from existing obligations and do not violate established laws or policies. The proposed eligibility requirement—specifically, that registrants must be bona fide members of the Ada/Cardano Community (e.g., holding Ada or having a history of transaction activity)—is unique to the applied-for gTLD. There is no existing applicable law, ICANN agreement, or Consensus Policy that requires, or prohibits, a domain registrant to participate in a specific blockchain ecosystem. Therefore, these policies introduce new, specific safeguards relevant only to ada and do not repeat or contradict existing laws or policies. While ICANN generally promotes openness, the Applicant Guidebook explicitly permits and requires Community gTLD applicants to establish registration policies that restrict eligibility to the delineated community. Consequently, restricting registration to verified Ada/Cardano Community members is consistent with the New gTLD Program requirements for Community applications and does not contradict ICANN’s standard openness policies in this specific context. Criterion 5: Compatibility with ICANN bylaws The Community Registration Policies are strictly focused on eligibility and technical security, avoiding any regulation of content that would conflict with ICANN's Bylaws. The policies restrict who can register a domain (eligibility), not what they can say on their website. By basing registration on objective criteria like Ada ownership or project validation, the Cardano Foundation ensures the namespace serves the community without becoming a content moderator. This distinction is crucial for meeting Criterion 5, as it respects the Bylaws' limitation on content regulation. Provisions that prevent the use of domains for abuse or attacks on the Cardano network align directly with ICANN's mission to ensure the security and stability of the DNS. These are technical safeguards, not content restrictions, and are therefore fully compatible with the Bylaws. The policies are administered in a neutral, transparent manner, ensuring that the Registry Operator does not exercise arbitrary discretion that could be viewed as unfair or discriminatory under the Bylaws.
Community Endorsement
Please provide evidence of support for the applying entity’s application by attaching written endorsements from the organizing bodies relevant to the identified community (related to Question 136).
The Cardano Foundation has secured support via the Cardano blockchain's native governance system. Through an “Info Action” (a formal on-chain polling mechanism), Delegated Representatives (“DReps”) representing approximately 75% of voting ada ratified the Cardano Foundation’s goal to operate this global top-level domain. The Ada/Cardano Community engages in governance directly using the Cardano blockchain to vote on technological advancements, public community goals and objectives, and a series of other topics. Anyone holding the ada digital asset has the ability to register to vote as a DRep, and voting weight is proportional to the amount of ada they hold. Ada Community members can also delegate to another DRep to vote on their behalf. In this instance, DReps voted overwhelmingly in favour of the Cardano Foundation’s goal to operate this global top-level domain. The complete on-chain record of all votes is available for full verification here: https://adastat.net/governances/a36eafaea085b77f97cceacf07fe9450f8c6b47fec3af94da8f7d158a1fc972200 Additionally, Cardano Foundation has received the following endorsement letters from Ada/Cardano Community Members or supporting institutions, these are attached as supporting documentation to this question. - Intersect - the Member-Based Organization (MBO) that serves as off-chain hub for the community - utxo AG - a leading multi-blockchain and AI infrastructure provider, primarily building on Cardano - Emurgo: a co-founding entity of the Cardano blockchain that drives the commercial adoption of blockchain technology and asset tokenization. - Pragma - a member-based, not-for-profit Open Source Association for blockchain software projects. - Crypto Valley Association - a leading independent association, dedicated to building the world’s largest ecosystem for blockchain and other distributed ledger technologies. These letters are attached as corresponding documentation to this question. An endorsement letter from Grant Thornton Switzerland - a leading Swiss audit, tax, and advisory firm and the registered auditor of the Cardano Foundation - is included in Question Set 20 given the page limit of this question.
Provide an explanation of why opposition may or may not be relevant or how the applying entity intends to address or resolve the opposition, if applicable.
None. The Cardano Foundation is one of the founding entities of Cardano, the registered trademark owner of the Ada trademark, and received overwhelming public voting support by the Cardano/Ada Community, and therefore is the solely qualified entity to operate the ada string. Cardano uses a stake based, active voting model. This means that it counts ada holders who do not vote as a “no” vote by default, however this is not active opposition. Any active “No” votes received were limited and represent less than 3.5% of all votes, which we consider statistically insignificant. Many of the “no” votes cast appeared to object on the basis of using community funds to pay for the application (and not the TLD itself), but we have further clarified that funding would come independently from the Cardano Foundation. Since the vote there has been no opposition to the Cardano Foundation’s application that we are aware of.
Section: Safeguard Identification
This question set collects information related to determining whether certain Safeguard Public Interest Commitments (Safeguard PICs) are required for the applied-for gTLD string. See Section 7.8.2.3 Safeguard PICs. Answers to these questions will inform assessment by ICANN on whether and which Safeguard PICs must be incorporated in the applicable Registry Agreement (RA) if the string proceeds to delegation. The answers themselves will not automatically make such a determination.
1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. 2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.
No
1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. 2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.
No
1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. 2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.
No
1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. 2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.
No
1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. I-2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.
No
1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. I-2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.
No
Select Yes or No. Notes: 1. ICANN will evaluate whether an applied-for gTLD string requires one or more Safeguard Public Interest Commitments (Safeguard PICs) to be included in the Base RA). 2. In addition to the Mandatory Public Interest Commitments (PICs) that must be included in each Base RA, a subset of Base RAs must include Safeguard PICs based on ICANN’s Safeguard Assessment. See Section 7.8.2.3 Safeguard PICs. 3. Applying entities for TLDs that are not found to require Safeguard PICs can elect to add them to the applicable Base RAs voluntarily to, for example, further their business objectives, help address issues or concerns that are raised or could be raised with respect to their applications, or avoid the need for the evaluation and implementation of customized Registry Voluntary Commitment (RVC). See Section 7.8.3 Registry Voluntary Commitments (RVCs).
No
Section: Registry Voluntary Commitments (RVCs)
This question set collects information related to any Registry Voluntary Commitments (RVCs) that the applying entity is submitting. The decision to submit an RVC is typically voluntary, except for those recognized by ICANN to resolve an objection or to address GAC Consensus Advice. See Section 7.8.3 Registry Voluntary Commitments for more information.
1. Select Yes or No. 2. In addition to Safeguard Public Interest Commitments (PICs), an applying entity will be permitted to propose one or more Registry Voluntary Commitments (RVCs) to provide additional safeguards with regard to the registry operator’s operation of an applied-for gTLD string. See Section 7.8.3 Registry Voluntary Commitments (RVCs). 3. RVCs are separate from Community Registration Policies. See Section 7.8.3 Registry Voluntary Commitments (RVCs) and Section 7.8.4 Community Registration Policies for more information. If you are applying for a Community gTLD, please submit the Community Registration Policies by answering Questions 150-155. However, if you propose to include additional Registry Voluntary Commitments in the RA beyond the Community Registration Policies, you may answer "yes" and proceed to answer the following questions. 4. You are encouraged to consider whether there are other means, separate from including commitment(s) in the Base RA, that could be used to further your business objectives or help resolve any anticipated or actual issue(s) raised regarding the applied-for gTLD string or application. See Section 7.8.3 Registry Voluntary Commitments (RVCs). Notes: If you select “yes” to this question, you are required to pay the conditional Registry Commitments Evaluation fee, and commitments that are approved by ICANN will be included in Specification 11 of the applicable Base RA as specific voluntary public interest commitments as contractual obligations.
No
Section: Brand & Code of Conduct Exemptions
This question set collects information related to whether the applied-for gTLD string is a .Brand (see Section 7.3) or if the applying entity is seeking a Code of Conduct exemption (see Section 7.4).
Select Yes or No
No
This serves as an indication of intent to apply for an exemption to Specification 9 and that the applying entity is NOT requesting to be designated a .Brand TLD, pursuant to Specification 13.
No
Section: Additional Information and Supporting Materials
This question set collects any additional information that the applying entity would like to provide, including any supporting materials.
1. An applying entity may use this response field to submit any additional, optional information or documentation that the applying entity believes enhances understanding of its application or may be of interest to the general public. This could include, but is not limited to, the applying entity’s: a) Individual registry policies; b) Separate agreement with a third-party to fulfill certain commitments; c) Terms of use; d) Additional Community Registration Policies not intended for RA inclusion; e) Other materials that clarify the applying entity’s mission, values, or intended use of the gTLD. Notes: 1. This question is optional and for informational purposes only. 2. The information provided here will not be evaluated as part of the application, or be contractually binding on the applying entity. 3. All submissions to this question will be posted for the public to review and comment.
Please see the attached document for a further letter of endorsement.
Section: Bona Fide Intent and Prohibited Communications
This question set contains attestations related to the applying entity’s acknowledgment of bona fide intent and prohibited communications.
Confirm the statement using the checkbox.
true
Confirm the statement using the checkbox.
true