{"applicationHumanReadableId":"CS2678T-T83663","applicationDetails":{"applicationHumanReadableId":"CS2678T-T83663","applicationType":"New gTLD","primaryString":{"aLabel":"ada","uLabel":""},"tldVariants":[],"originalTldVariants":[],"tldTypes":["Community"],"priorityNumber":-1,"applicationStatus":"Active","processingStage":"Pre-Evaluation Processing","hasClarifyingQuestions":false,"hasChangeRequests":false,"hasObjections":false,"lastPublishedAt":"2026-10-07T15:37:50.121Z"},"questionAndResponses":{"applicationHumanReadableId":"CS2678T-T83663","sections":[{"displayOrder":1,"sectionId":"1","sectionTitle":"Applying Entity Information","sectionInstructions":"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.","questions":[{"displayOrder":1,"questionText":"AGB Q1. Full Legal Name","instructions":"Provide the full legal name of the applying entity as it appears on the official registration documents. Do not use abbreviations.","responseText":"Cardano Stiftung","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":2,"questionText":"AGB Q2. Doing Business As ","instructions":"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.","responseText":"Cardano Foundation","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":3,"questionText":"AGB Q3. Legal Entity Form/Business Structure","instructions":"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.","responseText":"Foundation","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":4,"questionText":"AGB Q4. Jurisdiction","instructions":"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.","responseText":"Switzerland","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":10,"questionText":"AGB Q10. Website URL","instructions":"Provide the website URL of the applying entity, if available.","responseText":"https://cardanofoundation.org/","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":11,"questionText":"AGB Q11. Is the applying entity an existing registry operator, ICANN accredited registrar, or an Affiliate of either?","instructions":"1. Choose Yes or No. \n2. Use the definition of Affiliate from the Base Registry Agreement (see  https://www.icann.org/en/registry-agreements/base-agreement).","responseText":"false","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":13,"questionText":"AGB Q13. Is the applying entity a back-end registry service provider (RSP), an ICANN-approved data escrow agent, an emergency back-end registry operator, a Uniform Rapid Suspension (URS) service provider, an ICANN dispute resolution service provider, a Privacy or Proxy Service Provider, or a Reseller?","instructions":"Choose Yes or No.","responseText":"false","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":17,"questionText":"AGB Q17. Phone Country Code","instructions":"","responseText":"41","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":18,"questionText":"AGB Q18. Primary Business Phone","instructions":"Provide the primary business phone number without including the country code.","responseText":"(0) 41 562 01 19","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":19,"questionText":"AGB Q19. Primary Business Email Address","instructions":"Provide the primary business email address of the applying entity.","responseText":"registry@cardanofoundation.org","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":20,"questionText":"AGB Q20. Address Line 1","instructions":"Enter the street address (no PO Box).","responseText":"Dammstrasse 16","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":22,"questionText":"AGB Q22. Locality","instructions":"Enter the city, village, municipality, etc.","responseText":"Zug","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":23,"questionText":"AGB Q23. State/Province/Region","instructions":"Enter the state, province, department, territory, prefecture, oblast, etc., if applicable.","responseText":"Switzerland","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":24,"questionText":"AGB Q24. Postal Code","instructions":"1. Enter the postal code, if applicable.\n2. If a postal code does not exist, type “Not Applicable”. ","responseText":"6300","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":25,"questionText":"AGB Q25. Country Code of Location","instructions":"","responseText":"CH","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]},{"displayOrder":2,"sectionId":"1","sectionTitle":"Applying Entity Background and Organization","sectionInstructions":"This question set collects information related to the individuals who will have access to TAMS, manage the application, and receive inquiries.","questions":[{"displayOrder":1,"questionText":"AGB 104. List all directors of the applying entity.","instructions":"","responseText":"Jillian  Mac Nab Watkins , Mary Beth Buchanan, Fernando Vazquez Cao, Andreas Eschbach","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":2,"questionText":"AGB 105. List all officers & partners of the applying entity.","instructions":"","responseText":"Nicolas Jacquemart, Andreas Pletscher, Stephen Wood, Frederik Gregaard, Giorgio Zinetti","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":4,"questionText":"AGB 107. List Individuals with Executive Responsibility","instructions":"","responseText":"Nicolas Jacquemart, Andreas Pletscher, Stephen Wood, Frederik Gregaard, Giorgio Zinetti","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":5,"questionText":"AGB 108. Disclose Ultimate Control of applying entity","instructions":"","responseText":"Jillian  Mac Nab Watkins , Frederik Gregaard","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]},{"displayOrder":4,"sectionId":"16","sectionTitle":"Self-Certification","sectionInstructions":"Provide a single document for Self-Certification question Q4.2-1.\r\nThe document must include only the SC4.2-1.1, SC4.2-1.2, or SC4.2-1.3 statements.\r\nDo not modify any of the Self-Certification statements.","questions":[{"displayOrder":1,"questionText":"AGB Q212. Q4.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. If financial statements are provided by a Qualified Parent Entity (QPE), the CEO, President, CFO, and/or equivalent officer of the QPE must co-sign the certification document. The self-certification document must represent and warrant: SC4.2-1.1 - The applying entity and/or a QPE will fund the startup and long-term operation of all applied-for gTLD strings and (if applicable) currently operated gTLDs of a QPE. SC4.2-1.2 - The applying entity or QPE has at a minimum of US$50,000 plus 25% of the application base fee for each applied-for gTLD string in Cash and Cash Equivalents on the balance sheet of the provided financial statements, up to a maximum of US$300,000, designated to support the startup and operation of all of the applying entity’s applied-for gTLD strings. SC4.2-1.3 - The applying entity and/or its officers are bound by law in its jurisdiction to represent financial statements accurately and the applying entity is in good standing in that jurisdiction.","instructions":"1. Provide a single document for Self-Certification question Q4.2-1.\n2. The document must include only the SC4.2-1.1 through SC4.2-1.3 statements.\n3. Do not modify any of the Self-Certification statements.\n4. 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.","responseText":"","hasResponseDocuments":true,"hasCr":false,"hasCq":false}]},{"displayOrder":6,"sectionId":"18","sectionTitle":"Security Policy and Planning","sectionInstructions":"Provide a single document for Self-Certification question AGB Q220, Q5.1-1.\r\nThe document must include only the SC5.1-1.1 through SC5.1-1.3 statements.\r\nDo not modify any of the Self-Certification statements.\r\nIf 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.","questions":[{"displayOrder":1,"questionText":"AGB Q220. Q5.1-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant:\nSC5.1-1.1 - The applying entity will appropriately protect confidentiality of data and prevent unauthorized access to data and services.\nSC5.1-1.2 - The applying entity will maintain a mature, appropriately funded and staffed security program, following a recognized, modern security framework based on risk management (such as the ISO27000 series, COBIT, HITRUST CSF, legally required security frameworks, or equivalent).  The security program must be in place prior to delegation, and exist through at least the period of the registry agreement.\nSC5.1-1.3 - The applying entity is aware of and has designed its systems and business to comply with the relevant privacy and security regulations for all countries in which it operates.","instructions":"1. Provide a single document for Self-Certification question Q5.1-1.\n2. The document must include only the SC5.1-1.1 through SC5.1-1.3 statements.\n3. Do not modify any of the Self-Certification statements.\n4. 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.","responseText":"","hasResponseDocuments":true,"hasCr":false,"hasCq":false}]},{"displayOrder":7,"sectionId":"19","sectionTitle":"DNS Abuse","sectionInstructions":"Provide a single document for Self-Certification question AGB Q221, Q5.2-1.\r\nThe document must include only the SC5.2-1.1 through SC5.2-1.7 statements.\r\nDo not modify any of the Self-Certification statements.\r\nIf 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.","questions":[{"displayOrder":1,"questionText":"AGB Q221. Q5.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant:\nSC5.2-1.1 - The applying entity will, no later than delegation of the Top Level Domain (TLD), establish a dedicated abuse point of contact responsible for addressing matters requiring expedited attention and providing a timely response to abuse complaints concerning any name registered in the TLD.\nSC5.2-1.2 - The applying entity will, no later than delegation of the TLD, establish, publish, and provide to ICANN the location of a mechanism for members of the public to submit reports of abuse in accordance with the current obligations of the Base RA and any Consensus Policies.\nSC5.2-1.3 - The applying entity has developed proposed measures for removal of orphan glue records for names removed from the zone when provided with evidence in written form that the glue is present in connection with malicious conduct (see Specification 6).\nSC5.2-1.4 - The applying entity has or will have at time of delegation, established policies for handling complaints regarding abuse. Such policies are to be maintained and posted publicly so that anyone can review the policies via the Internet and any other means deemed appropriate by the applying entity. The applying entity’s policies at a minimum should contain appropriate confirmation of the receipt of the abuse report, the process of review of the report, and actions that will be taken if the applying entity confirms the report is legitimate.\nSC5.2-1.5 - The applying entity understands that DNS Abuse is Phishing, Malware, Botnets, Pharming and Spam (when used to deliver other forms of DNS Abuse). The applying entity understands and is prepared to contribute to the mitigation or disruption of DNS Abuse in domains in the TLD zone.\nSC5.2-1.6 - The applying entity’s abuse response capabilities are resourced appropriately to ensure a timely and adequate investigation and response to reports of DNS Abuse. This includes capabilities to receive and evaluate evidence of DNS Abuse in reports, and to take action to stop or disrupt the DNS Abuse.\nSC5.2-1.7 - The applying entity is prepared to conduct periodic scans of its zone to identify if domains are being used to perpetrate DNS Abuse, and to maintain statistical reports of the scans, the findings, and actions taken.","instructions":"1. Provide a single document for Self-Certification question Q5.2-1.\n2. The document must include only the SC5.2-1.1 through SC5.2-1.7 statements.\n3. Do not modify any of the Self-Certification statements.\n4. 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.","responseText":"","hasResponseDocuments":true,"hasCr":false,"hasCq":false}]},{"displayOrder":8,"sectionId":"16","sectionTitle":"Primary String","sectionInstructions":"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.","questions":[{"displayOrder":4,"questionText":"AGB Q118. What is the meaning/definition of the applied-for gTLD string?","instructions":"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\"","responseText":"“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.","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":5,"questionText":"AGB Q119. Script of String","instructions":"If an IDN, provide the script of the string (both in English and as referenced by the RZ-LGR/ISO 15924)","responseText":"Latin","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":6,"questionText":"AGB Q120.  Phonetic Representation","instructions":"Provide a representation of the string according to the International Phonetic Alphabet.","responseText":"/ˈeɪdə/ (AY-da)","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":7,"questionText":"AGB Q121. As per Section 3(d) of Specification 11 of the Base Registry Agreement, a registry operator of a “generic string” may not impose eligibility criteria for registering names in the TLD that limit registrations exclusively to a single person or entity and/or that person’s or entity’s “Affiliates” (as defined in Section 2.9(c) of the Registry Agreement). “Generic String” means a string consisting of a word or term that denominates or describes a general class of goods, services, groups, organizations or things, as opposed to distinguishing a specific brand of goods, services, groups, organizations or things from those of others. Confirm that the applied-for string is not a “generic string” in which the applying entity intends to limit registrations exclusively to a single person or entity.","instructions":"Confirm the statement using a checkbox.","responseText":"true","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":8,"questionText":"AGB Q133. What is the mission and purpose of the applied-for gTLD?","instructions":"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.\n\n1a. 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.\n\n2. Explain how this purpose is sustainable over time.","responseText":"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. \n\nRelated activities to achieve this mission include:\n\n- Generating revenue to reinvest for the benefit of the gTLD and/or the Ada Community\n- Coordinated ecosystem marketing endeavours; \n- Cardano Foundation-driven adoption endeavours;\n- Community product development and 2030 roadmap.\n\nSustainability of the Mission\n\nThe 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.\n","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":1,"questionText":"AGB Q116. Applied-for Primary String (ASCII Label)","instructions":"","responseText":"ada","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]},{"displayOrder":10,"sectionId":"5","sectionTitle":"Community","sectionInstructions":"This question set collects information specific to Community gTLDs. However, question 133 (Mission & Purpose) must be answered by all applying entities.","subsections":[{"displayOrder":1,"subsectionTitle":"General","questions":[{"displayOrder":2,"questionText":"AGB Q132. What community will the applied-for string serve?","instructions":"1. Provide the name of the community that the applying entity is committing to serve. \r\n2. Describe the distinct aspects of the community.","responseText":"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.","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":3,"questionText":"AGB Q134. How would you categorize your community?","instructions":"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.","responseText":"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.\n\nThe 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/:\n\n“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.”\n\nThe 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. \n\nCommunity 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).\n\nIn 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.\n\n","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":1,"questionText":"AGB Q131. Is this application for a community TLD?","instructions":"","responseText":"Yes","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]},{"displayOrder":2,"subsectionTitle":"Organization","questions":[{"displayOrder":3,"questionText":"AGB Q135. What is the applying entity's connection to the community?","instructions":"Describe and provide evidence of the relationship between the applying entity and the identified community.","responseText":"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.\n\nThe 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. \n\nFor the “Cardano trademark”, see the attached corresponding documentation.\n\nTo understand how the Cardano Foundation serves its community, it is helpful to look at its three core operational pillars: Technology, Adoption, and Governance.\n\n1. Technology\n\nThe 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.\n\nThe 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.\n\n2. Adoption\n\nThe 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.\n\nThe 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.\n\nThrough 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.\n\nThe 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.\n\n3. Governance\n\nThe 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.\n","hasResponseDocuments":true,"hasCr":false,"hasCq":false},{"displayOrder":4,"questionText":"AGB Q136. How is the community organized? Are there one or multiple organizations (\"organizing body\") that represent or administer the community?","instructions":"Describe and provide evidence related to the community organization, any relevant organizing bodies, and any relevant leaders within the community.","responseText":"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. \n\n1. The Cardano Foundation\n\nThe 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.\n\nThe 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.\n\nThe 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.\n\n2. On-Chain Governance Bodies \n\nThe 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.\n\nThere were more than 1,000 Delegated Representatives, a governance role, registered on Cardano at the beginning of 2026.\n\n3. Member-Based Organizations: \n\nIntersect\n\nIntersect 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. \n\nIntersect 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.\n\nPRAGMA\n\nPRAGMA 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.\n","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":5,"questionText":"AGB Q137. Does the community have defined membership requirements, such as registration, licensing, or use of specific communication? Or, do community members self-identify as part of the community? ","instructions":"1. Describe any formal membership process, if there is one.\r\n2. 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).","responseText":"Anyone who owns ada or develops the Cardano blockchain is considered part of the Ada/Cardano Community.\n\nThe 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/:\n\n“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.”\n\nThe 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. \n","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":6,"questionText":"AGB Q138. Where is the community located?","instructions":"Provide the primary location of the community.","responseText":"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.","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":7,"questionText":"AGB Q139. What is the estimated size of the community? This should take into account any regions listed in Question 138.","instructions":"1. Provide the estimated size of the community. The size should be in number format (e.g., “1,000,000 members”).\r\n2. If the community is divided by group, region, sector, etc., this should include estimated size for each group.","responseText":"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.","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":8,"questionText":"AGB Q140. What portion of the community do any organizing bodies represent or administer to?","instructions":"Provide the estimated size of the community that is administered or represented by each relevant organizing body in the identified community.","responseText":"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.","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]},{"displayOrder":3,"subsectionTitle":"Engagement","questions":[{"displayOrder":9,"questionText":"AGB Q141. Do the organizing bodies demonstrate active and consistent efforts to engage and connect with the identified community and its members?","instructions":"1. Provide evidence of any documented practices of community efforts to date\r\n2. The applying entity should provide documentation of the following practices, which should have occurred within the two years leading up to application submission: \r\na) Offering support; \r\nb) Sharing information; \r\nc) Responding to specific community needs;\r\nd) Fostering and strengthening relationships within the community.","responseText":"Yes, please see the below corresponding documentation containing the answer to this question and supporting links.","hasResponseDocuments":true,"hasCr":false,"hasCq":false},{"displayOrder":10,"questionText":"AGB Q142. What is the role of the applying entity in the engagement efforts listed in Question 141?","instructions":"1. Describe whether the applying entity has a role in any of the activities listed in Question 141.\r\n2. 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.","responseText":"Please see the below corresponding documentation containing the answer to this question and supporting links.","hasResponseDocuments":true,"hasCr":false,"hasCq":false}]},{"displayOrder":4,"subsectionTitle":"Awareness","questions":[{"displayOrder":11,"questionText":"AGB Q143. Are community members aware of the identified community and each other?","instructions":"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. \r\n2. The applying entity should provide documentation of the following practices, which should have occurred within the two years leading up to application submission:\r\na) Surveys conducted;\r\nb) Records of activities involving a diversity of community groups, segments, or members.","responseText":"Yes, please see the below corresponding documentation containing the answer to this question and supporting links.","hasResponseDocuments":true,"hasCr":false,"hasCq":false},{"displayOrder":12,"questionText":"AGB Q144. Are community members aware of the applying entity and its intention to apply for a community gTLD?","instructions":"1. Provide evidence of community members’ awareness of the applying entity and its intent to apply for a community gTLD. \r\n2. If there is no such evidence, explain why not.","responseText":"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.\n\nAn 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.\n\nThe 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. \nThe Info Action and results can be found here: https://adastat.net/governances/a36eafaea085b77f97cceacf07fe9450f8c6b47fec3af94da8f7d158a1fc972200 \n\nThe voting results of the Info Action have been copied to the attached corresponding documentation for ease of reference.","hasResponseDocuments":true,"hasCr":false,"hasCq":false}]},{"displayOrder":5,"subsectionTitle":"Established Presence","questions":[{"displayOrder":13,"questionText":"AGB Q145. Was there an established presence of the identified community prior to the opening of the application submission period?","instructions":"Provide evidence of the established presence of the community prior to the opening of the application submission period.","responseText":"Yes","hasResponseDocuments":true,"hasCr":false,"hasCq":false},{"displayOrder":14,"questionText":"AGB Q146. Are individuals and groups outside of the identified community aware of the existence of the identified community?","instructions":"1. Provide evidence that demonstrates that individuals and groups outside of the community show an awareness of the identified community. \r\n2. The applying entity should provide documentation of the following practices, which should have occurred within the two years leading up to application submission:\r\na) Media or other public information regarding the community and its activities or members; \r\nb) Discussion of the community in various fora, whether online or in person; \r\nc) Evidence of partnerships or collaborations with groups outside of the identified community;\r\nd) Evidence of the chartering or organization of the community prior to the opening of the application submission window;\r\ne) Evidence of contributions (for example, cultural or scientific) to a larger society or population;","responseText":"Yes, please see the below corresponding documentation containing the answer to this question and supporting links.","hasResponseDocuments":true,"hasCr":false,"hasCq":false}]},{"displayOrder":6,"subsectionTitle":"Longevity","questions":[{"displayOrder":15,"questionText":"AGB Q147. Are the pursuits of the identified community enduring and sustainable?","instructions":"1. Provide evidence of the longevity of the community. \r\n2. The applying entity should provide documentation of the following practices which should have occurred within the two years leading up to application submission:\r\na) Evidence of recurring or scheduled activities that demonstrate continuity over time;\r\nb) Documented records of past activities that demonstrate a long-standing tradition or practice;\r\nc) Records of discussions emphasizing the community’s enduring presence or its cultural significance.","responseText":"Yes, please see the below corresponding documentation containing the answer to this question and supporting links.","hasResponseDocuments":true,"hasCr":false,"hasCq":false}]},{"displayOrder":7,"subsectionTitle":"Nexus","questions":[{"displayOrder":16,"questionText":"AGB Q148. Does the string match the name of the identified community?","instructions":"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.","responseText":"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. \n\nAs 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.","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":17,"questionText":"AGB Q149. Will the general public instinctively think of the community when thinking of the applied-for string?","instructions":"1. Explain how the applied-for string clearly relates to or represents the community \r\n2. 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.","responseText":"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. \n\nLike 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”. \n","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]},{"displayOrder":8,"subsectionTitle":"Community Registration Policy","questions":[{"displayOrder":18,"questionText":"AGB Q150. Are you proposing to include one or more Community Registration Policies in the Registry Agreement (RA) that are unique to the applying entity's applied-for community gTLD?","instructions":"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.","responseText":"Yes","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":19,"questionText":"AGB Q151.1. Please state a specific Community Registration Policy with respect to registration eligibility for community members.","instructions":"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.\n\n2. 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.\n\n3. Follow this format to propose what the Registry Operator must do and/or must not do:\na) “Registry Operator shall___”; and/or\nb) “Registry Operator shall not___”.\n\n4. Follow this format to propose any specific requirement(s) that the Registry Operator commits to include in its Registry-Registrar Agreement for registrars ,:\na) \"Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall___”; and/or\nb) \"Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall not___”.\n\n5. Follow this format to propose  any specific requirement(s) that the Registry Operator commits to require registrars to include in the applicable Registration Agreements:\na) \"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\nb) \"Registry Operator will include a provision in its Registry- Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting ___\".\n\n6. Include any objective measures that can be applied to demonstrate the Registry Operator’s compliance with the Community Registration Policy. For example:\na) 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.\nb) 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.\n\n7. 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, ___).\n\n8. 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.","responseText":"Registry Operator shall adhere to the following eligibility criteria with respect to registration for community members:\n\nEligibility 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:\n\n1. 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:\n- Proof of control of a wallet holding ada \n- Proof of intent to join the Ada/Cardano Community as an ada holder within 90 days of registration;\n- Other proof of ada ownership (e.g. via a centralized exchange)\n- Proof of originating transactions on the Cardano Blockchain (ada)\n- Proof of material promotional efforts for the Cardano Blockchain (ada)\n\n2. 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. \n\n\nRegistry 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.\n\nRegistry 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.\n\nRegistry 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. \n","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":20,"questionText":"AGB Q152.1. State a specific Community Registration Policy with respect to name selection criteria or rules for the applied-for string.","instructions":"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.\n\n2. 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. \n\n3. These criteria or rules should align with the community objectives of the applied-for gTLD string.\n\n4. Follow this format to propose what the Registry Operator must do and/or must not do:\na) “Registry Operator shall___”; and/or\nb) “Registry Operator shall not___”.\n\n5. Follow this format to propose any specific requirement(s) that the Registry Operator commits to include in its Registry-Registrar Agreement for registrars:\na) \"\"Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall___”; and/or\nb) \"\"Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall not___”.\n\n6. Follow this format to propose any specific requirement(s) that the Registry Operator commits to require registrars to include in the applicable Registration Agreements:\na) \"\"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\nb) \"\"Registry Operator will include a provision in its Registry- Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting ___\"\".\n\n7. Include any objective measures that can be applied to demonstrate the Registry Operator’s compliance with the Community Registration Policy. For example:\na) 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.\nb) 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.\n\n8. 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, ___).\n\n9. 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.","responseText":"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.\n\nRegistry 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:\n\n1. Registered according to inaccurate information;\n2. Used to facilitate, participate in or further illegal activities;\n3. Violate the intellectual property rights of others;\n4. Registered in bad faith to create confusion within the Ada/Cardano Community and Internet users;\n5. Used against the interests of the Cardano ecosystem;\n6. Used to damage, disable, impair, or otherwise attack ada sites or the networks connected to ada sites;\n\nRegistry 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.\n\nRegistry 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. \n","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":21,"questionText":"AGB Q153.1. State a specific Community Registration Policy with respect to an additional commitment besides registration eligibility for community members and naming selection criteria or rules for the applied-for string.","instructions":"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.\n\n2. Enter a single proposed Community Registration Policy in each response field. Up to 10 Community Registration Policies can be submitted.  \n\n3. Follow the format to propose what the Registry Operator must do and/or must not do:\na) “Registry Operator shall___”; and/or\nb) “Registry Operator shall not___”.\n\n4. Follow this format to propose any specific requirement(s) that the Registry Operator commits to include in its Registry-Registrar Agreement for registrars:\na) \"\"Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall___”; and/or\nb) \"\"Registry Operator will include the following provisions in its Registry-Registrar Agreement: Registrar shall not___”.\n\n5. Follow this format to propose any specific requirement(s) that the Registry Operator commits to require registrars to include in the applicable Registration Agreements:\na) \"\"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\nb) \"\"Registry Operator will include a provision in its Registry- Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting___\"\".\n\n6. Include any objective measures that can be applied to demonstrate the Registry Operator’s compliance with the Community Registration Policy. For example:\na) 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.\nb) 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.\n\n7. 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, ___).\n\n8. 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.","responseText":"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.\n\nThe 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. \n\nThe 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. \n\nRegistry 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.\n\nRegistry 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. \n\nThe sponsoring registrar of any ada domain registration shall validate customer email addresses or any other contact information it collects.\n","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":22,"questionText":"AGB Q154. Explain the rationale for any limitations to the Community Registration Policy proposed by the applying entity in Questions 151-153.","instructions":"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.\n2. 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.","responseText":"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.\n","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":23,"questionText":"AGB Q155. Explain how the proposed Community Registration Policies of the applying entity meets the Registry Commitments Evaluation criteria 4 and 5?","instructions":"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.\n2. 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.\n3. 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.\n4. 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.\n5. 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.","responseText":"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.\n\nCriterion 4: No Duplication or Contradiction of Existing Requirements\n\nCriterion 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\".\n\nThe Cardano Foundation’s proposed Community Registration Policies are distinct from existing obligations and do not violate established laws or policies.\n\nThe 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.\n\nThere 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.\n\nWhile 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.\n\nCriterion 5: Compatibility with ICANN bylaws\n\nThe Community Registration Policies are strictly focused on eligibility and technical security, avoiding any regulation of content that would conflict with ICANN's Bylaws.\n\nThe 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.\n\nProvisions 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.\n\nThe 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.\n","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]},{"displayOrder":9,"subsectionTitle":"Community Endorsement","questions":[{"displayOrder":24,"questionText":"AGB Q156. From where does the applying entity have the support to run the applied-for string on behalf of the identified community?","instructions":"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).","responseText":"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. \n \nThe 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.\n\n\nThe complete on-chain record of all votes is available for full verification here: https://adastat.net/governances/a36eafaea085b77f97cceacf07fe9450f8c6b47fec3af94da8f7d158a1fc972200 \n\nAdditionally, 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.\n\n- Intersect - the Member-Based Organization (MBO) that serves as off-chain hub for the community\n- utxo AG - a leading multi-blockchain and AI infrastructure provider, primarily building on Cardano\n- Emurgo: a co-founding entity of the Cardano blockchain that drives the commercial adoption of blockchain technology and asset tokenization.\n- Pragma - a member-based, not-for-profit Open Source Association for blockchain software projects.\n- Crypto Valley Association - a leading independent association, dedicated to building the world’s largest ecosystem for blockchain and other distributed ledger technologies.\n\nThese 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.\n","hasResponseDocuments":true,"hasCr":false,"hasCq":false},{"displayOrder":25,"questionText":"AGB Q157. Is there any opposition to the applying entity, application, or applied-for string that the applying entity is aware of? If yes, please explain.","instructions":"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.","responseText":"None. \n\nThe 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. \n\nCardano 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. \n","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]}]},{"displayOrder":13,"sectionId":"2","sectionTitle":"Safeguard Identification","sectionInstructions":"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.","questions":[{"displayOrder":1,"questionText":"AGB Q164. Will people see a domain name as more trustworthy because it is registered in your TLD?\r\nThink about how people around the world will understand the TLD string(s) in the application, including literal and informal meanings in different languages and regions.","instructions":"1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts:\r\na. Literally as described in the application\r\nb. Literally in any other language in which the string is a recognized word or phrase.\r\nc. Informally in any language or regional variant, where alternative meanings exist.\r\n2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.","responseText":"No","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":2,"questionText":"AGB Q165. Is it likely that consumers will face significant risks if domain names in the TLD(s) in the application are abused?\r\nThink about how people around the world will understand the TLD string(s) in the application, including literal and informal meanings in different languages and regions.","instructions":"1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts:\r\na. Literally as described in the application\r\nb. Literally in any other language in which the string is a recognized word or phrase.\r\nc. Informally in any language or regional variant, where alternative meanings exist.\r\n2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.","responseText":"No","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":3,"questionText":"AGB Q166. Would people generally think that this TLD will be used by entities that require strict licensing or accreditation to do business?\r\nThink about how the TLD string(s) in the application will be understood around the world, including both literal and informal meanings in different languages and regions.","instructions":"1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts:\r\na. Literally as described in the application\r\nb. Literally in any other language in which the string is a recognized word or phrase.\r\nc. Informally in any language or regional variant, where alternative meanings exist.\r\n2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.","responseText":"No","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":4,"questionText":"AGB Q167. Would most people think that (domains in) the TLD(s) in the application are used for activities that require regular government reporting, inspections, and oversight in various countries?\r\nThink about how the TLD string(s) in the application will be understood around the world, including both literal and informal meanings in different languages and regions.","instructions":"1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts:\r\na. Literally as described in the application\r\nb. Literally in any other language in which the string is a recognized word or phrase.\r\nc. Informally in any language or regional variant, where alternative meanings exist.\r\n2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.","responseText":"No","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":5,"questionText":"AGB Q168. Could people reasonably believe that (domains in) your TLD will cause or lead to harassment, harm, aggression, complaints, criticism, distress, or embarrassment?\r\nThink about how the TLD string(s) in the application will be understood globally, including different languages and cultures.","instructions":"1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts:\r\na. Literally as described in the application\r\nb. Literally in any other language in which the string is a recognized word or phrase.\r\nc. Informally in any language or regional variant, where alternative meanings exist.\r\nI-2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.","responseText":"No","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":6,"questionText":"AGB Q169. Would most people think that the TLD is used for something usually done by governments?\r\nThink about how the TLD string(s) in the application will be understood globally, including different languages and cultures.","instructions":"1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts:\na. Literally as described in the application\nb. Literally in any other language in which the string is a recognized word or phrase.\nc. Informally in any language or regional variant, where alternative meanings exist.\nI-2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.","responseText":"No","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":7,"questionText":"AGB Q170. Are you proposing to include one or more of the Safeguard Public Interest Commitments (Safeguard PICs) in the Registry Agreement (RA) voluntarily regardless of ICANN’s Safeguard Assessment outcomes?","instructions":"Select Yes or No.\n\nNotes:\n1. 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).\n2. 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.\n3. 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).","responseText":"No","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]},{"displayOrder":14,"sectionId":"12","sectionTitle":"Registry Voluntary Commitments (RVCs)","sectionInstructions":"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.","questions":[{"displayOrder":1,"questionText":"AGB Q172. Are you proposing to include one or more Registry Voluntary Commitments (RVCs) in the Registry Agreement (RA) that are unique to your applied-for string?","instructions":"1. Select Yes or No.\n2. 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).\n3. 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.\n4. 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).\n\nNotes:\nIf 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.","responseText":"No","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]},{"displayOrder":16,"sectionId":"11","sectionTitle":"Brand & Code of Conduct Exemptions","sectionInstructions":"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).","questions":[{"displayOrder":1,"questionText":"AGB Q179. Are you applying for a Brand TLD?","instructions":"Select Yes or No","responseText":"No","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":7,"questionText":"AGB Q185. Does the applying entity request a Code of Conduct Exemption?","instructions":"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.","responseText":"No","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]},{"displayOrder":17,"sectionId":"13","sectionTitle":"Additional Information and Supporting Materials","sectionInstructions":"This question set collects any additional information that the applying entity would like to provide, including any supporting materials.","questions":[{"displayOrder":1,"questionText":"AGB Q222. If the applying entity wishes to provide any additional information or supporting materials that the applying entity believes may be of interest to the public or relevant to the application, please include them here.","instructions":"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: \r\na) Individual registry policies;\r\nb) Separate agreement with a third-party to fulfill certain commitments; \r\nc) Terms of use; \r\nd) Additional Community Registration Policies not intended for RA inclusion; \r\ne) Other materials that clarify the applying entity’s mission, values, or intended use of the gTLD. \r\n\r\nNotes:\r\n1. This question is optional and for informational purposes only. \r\n2. The information provided here will not be evaluated as part of the application, or be contractually binding on the applying entity. \r\n3. All submissions to this question will be posted for the public to review and comment. ","responseText":"Please see the attached document for a further letter of endorsement.","hasResponseDocuments":true,"hasCr":false,"hasCq":false}]},{"displayOrder":18,"sectionId":"14","sectionTitle":"Bona Fide Intent and Prohibited Communications","sectionInstructions":"This question set contains attestations related to the applying entity’s acknowledgment of bona fide intent and prohibited communications.","questions":[{"displayOrder":1,"questionText":"AGB Q223. By submitting this Application, the applying entity confirms that it is submitting this Application with a good faith (“bona fide”) intent to operate the gTLD for which it has applied, and that the applying entity has read and understands the provisions of Section 5.2.3.1 Prohibited Communications and Activities of the Applicant Guidebook regarding the New gTLD Program rules prohibiting certain communications and activities to prevent parties from privately resolving string contention among themselves.","instructions":"Confirm the statement using the checkbox.","responseText":"true","hasResponseDocuments":false,"hasCr":false,"hasCq":false},{"displayOrder":2,"questionText":"AGB Q224. By submitting this Application, the applying entity confirms that it has read and understands the provisions of Section 5.2.3.1  Prohibited Communications and Activities of the Applicant Guidebook regarding the New gTLD Program rules prohibiting certain communications and activities to prevent parties from privately resolving string contention among themselves.","instructions":"Confirm the statement using the checkbox.","responseText":"true","hasResponseDocuments":false,"hasCr":false,"hasCq":false}]}]}}