.sol

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.

Answered with a document. Attachments are not published by ICANN.

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: SC5.1-1.1 - The applying entity will appropriately protect confidentiality of data and prevent unauthorized access to data and services. SC5.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. SC5.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.

Answered with a document. Attachments are not published by ICANN.

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: SC5.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. SC5.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. SC5.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). SC5.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. SC5.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. SC5.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. SC5.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.

Answered with a document. Attachments are not published by ICANN.

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.

true

How would you categorize your community?

The Solana community is best categorized as a global, online, activity-based technology community centered on the open-source Solana protocol and network.

The community comprises developers who build and deploy software, independent validators and infrastructure operators, wallet users, SNS name holders, organizations that build applications, protocols, wallets, and infrastructure, grant recipients, educators, regional contributors, and participants in recognized ecosystem programs. Its functional segments include on-chain naming, DeFi, payments, consumer applications, digital assets, gaming, infrastructure, research, education, and community development.

Like other open-source technology communities, affiliation follows from participation rather than admission by a single centralized membership body. Its boundaries are nevertheless objective and observable. Participation may be demonstrated through control or use of a Solana wallet, operation of a validator, deployment of programs to Solana, ownership or control of an SNS name, receipt of a Solana Foundation grant, contributions to software or infrastructure, promotion of the ecosystem, or documented participation in an ecosystem or regional program. These activities may be verified through public blockchain records, software repositories, program records, or institutional documentation.

The community is supported by Solana Foundation, a nonprofit foundation based in Zug, Switzerland, together with independent validators, developers, infrastructure providers, wallet providers, protocols, businesses, users, and community organizations worldwide. These participants are connected by shared technology, common technical standards, established institutions and communication channels, recurring activities, and the common purpose of developing, operating, securing, supporting, promoting, and using Solana.

The supporting letters illustrate this functional organization. SNS serves the on-chain naming segment; Phantom and Solflare serve wallet users; Kamino Foundation and Jupiter serve DeFi participants; and Solana Foundation provides ecosystem-wide stewardship. Each participates in and serves a distinct segment while recognizing the same broader Solana community.

Accordingly, the Solana community is not merely an audience, social-media following, or group defined by general interest in a technology. It is an established open-technology community whose members have identifiable connections to the ecosystem through technical, operational, economic, institutional, educational, naming, or other active participation.

Answered with a document. Attachments are not published by ICANN.

What is the applying entity's connection to the community?

Sol Naming Limited’s connection to the Solana community arises from the community’s institutional choice. Solana Foundation, the community’s principal ecosystem-wide stewardship organization, selected and endorsed Sol Naming as the community’s applicant and ICANN operating partner for .sol.

That selection was deliberate and documented. The Foundation evaluated the ICANN new gTLD opportunity and the role a Solana-aligned DNS namespace could play in the ecosystem’s development. It reviewed the proposed applicant structure, the ICANN and domain-industry experience of the principals and advisers carrying the initiative, the intended use of Identity Digital as Registry Services Provider, and the proposed community-based registration framework. The Foundation approved its endorsement on October 25, 2024, following internal review and Director and President approval. Sol Naming is the dedicated entity through which that initiative is pursued.

The applicant is a special-purpose registry entity by design. Operating a gTLD requires an identified contracting party accountable to ICANN, qualified registry infrastructure, accredited-registrar distribution, and continuing compliance, security, escrow, and continuity capabilities. Sol Naming’s supporting team and advisers bring relevant ICANN, domain-name, and web3 experience, while Identity Digital will provide established registry infrastructure and compliance capabilities.

Sol Naming is not a corporate affiliate or subsidiary of Solana Foundation. The Foundation does not own or control the applicant or acquire authority over registry decisions through its endorsement. Sol Naming retains sole responsibility for the application and, if successful, ultimate responsibility for registry governance, policies, operations, and compliance with the Registry Agreement. This structure connects the community’s initiative to specialized ICANN execution while preserving the applicant’s independent accountability.

The connection is also technical. Principals and technical contributors supporting the application led or contributed to development of the Solana Record Service in coordination with members of the Foundation’s technical team. SRS permits records associated with names and identifiers to be created, updated, and deleted on Solana and is publicly available at records.solana.com as ecosystem infrastructure. It is technically separate from the DNS and neither creates nor resolves DNS domain names. This work demonstrates experience with Solana-native identity and record infrastructure and an established working relationship with ecosystem participants.

The connection is further corroborated across major community segments. SNS, which operates the Web3 name service for .sol on Solana, supports recognition of .sol in the global DNS and the Foundation’s endorsement of Sol Naming. Phantom and Solflare support the application from the wallet and consumer-user segments, while Jupiter and Kamino Foundation support it from the DeFi and application ecosystem. Their letters identify Sol Naming, recognize .sol as the community’s natural DNS identifier, support the Foundation’s selection, and look to Sol Naming to complete the ICANN process and operate the namespace for the community. These endorsements confer no ownership, governance rights, or decision-making authority over the applicant or registry.

Evidence includes Solana Foundation’s written endorsement; the supporting letters from SNS, Phantom, Solflare, Jupiter, and Kamino Foundation; documentation concerning SRS and the relevant contributors’ work; and materials describing the proposed applicant structure and community-based registry framework. Together, this evidence demonstrates an institutional, technical, and cross-segment relationship with the Solana community while preserving Sol Naming’s independent responsibility as the applicant and proposed registry operator.

Answered with a document. Attachments are not published by ICANN.

How is the community organized? Are there one or multiple organizations ("organizing body") that represent or administer the community?

The Solana network is the underlying technology. The Solana community is the organized body of people and organizations that develop, operate, support, and participate in it through identifiable institutions, programs, events, and ecosystem services. Solana Foundation is its principal ecosystem-wide nonprofit institution.

The Foundation is based in Switzerland and advances the decentralization, adoption, and security of Solana. It does not control the network, which independent validators operate. It supports and coordinates the community through funding and validator programs, technical resources, communications, partnerships, and recurring events.

Its programs support the community’s principal participant groups:

Developers and builders. Foundation funding programs have supported more than 500 projects with more than $100 million across six continents. Applicants undergo documented review, and approved projects receive milestone-based funding. The Foundation also works with Colosseum to conduct global online hackathons through which developers build applications, receive mentorship, and enter the broader ecosystem.

Validators. Validators independently operate the computers that process and confirm network activity. The Solana Foundation Delegation Program applies published eligibility, performance, and participation requirements. As of Epoch 1000 on July 10, 2026, it supported 362 validators across 24 countries.

Regional participants. Superteam’s network of more than 20 regional chapters organizes developers, founders, creators, and other contributors locally. Its chapters maintain leadership, participation processes, grants, work opportunities, and recurring events.

The broader ecosystem. The Foundation convenes Solana Breakpoint, held annually since 2021, together with community calls, developer events, regional gatherings, and the Solana Accelerate series. It also maintains developer resources, communications channels, and ecosystem programs.

Independent ecosystem organizations serve major functional segments. Phantom and Solflare provide principal wallet interfaces through which users participate. Jupiter serves trading and liquidity participants; Kamino serves lending and decentralized-finance participants; and SNS operates the established Web3 name service for .sol on Solana. Each maintains products, integrations, communications channels, and identifiable participant communities. Their endorsements document their respective roles and shared recognition of the broader Solana community. They administer their own services but do not claim authority to represent the community as a whole.

These bodies perform complementary functions. Solana Foundation provides ecosystem-wide stewardship; Colosseum and Superteam administer developer and regional programs; validators operate the network; and independent organizations serve functional participant groups. Developers, businesses, and users participate through these structures and the network’s public technical processes.

Relevant institutional leaders include Solana Foundation President Lily Liu and the executives who signed the supporting letters for SNS, Phantom, Solflare, Jupiter, and Kamino Foundation. Each acts for the identified organization; none claims personal authority over the community as a whole.

The community resembles global open-source communities that combine an umbrella institution with regional, operational, and functional organizations. Its institutions, programs, requirements, recurring activities, participant groups, and public records are identifiable and independently verifiable.

Through the relationship described in Q135, Solana Foundation endorsed Sol Naming Limited to represent the community solely for the ICANN application and DNS registry function. Sol Naming does not govern the Solana protocol or replace or control the community’s other institutions.

Answered with a document. Attachments are not published by ICANN.

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?

The Solana community has no single universal admission, licensing, or membership-registration process. It is an open, participation-based community in which individuals and organizations become members through conduct connecting them to the shared Solana protocol, mainnet, infrastructure, applications, naming system, and ecosystem. Members self-identify, but affiliation does not rest on assertion alone: the underlying participation is ordinarily observable and exists independently of the .sol application.

People and organizations join through several established paths. They may create or control a Solana wallet and use the network; develop or deploy programs; contribute code, applications, or infrastructure; operate a validator or other network infrastructure; register and control an SNS on-chain name; receive a Solana Foundation grant; participate in a recognized developer, regional, validator, education, or ecosystem program; or promote, educate about, organize for, or otherwise contribute to Solana. Members also engage through public repositories, developer forums, communications channels, hackathons, conferences, and regional activities.

The degree of formality depends on the path. Wallet, developer, infrastructure, and SNS participation is generally open and self-directed. Validator operation is governed by published protocol and technical requirements. Foundation grant recipients undergo an application and review process. The Solana Foundation Delegation Program applies published identity-verification, performance, and community-contribution requirements, while Superteam maintains documented participation and contribution levels through its regional chapters.

Participation can therefore be evidenced in different ways. Wallet control, validator operation, deployed programs, and SNS names can be verified through public Solana mainnet records. Technical contributions may be identified through public software repositories. Grants, delegation-program participation, Superteam activity, and other recognized programs can be confirmed through institutional records. Promotion, education, events, and other contributions may be demonstrated through attributable public activities or documentation.

Members do not receive a uniform package of membership rights. The benefits of participation depend on the activity and may include access to open technical resources and public channels, use of network and identity infrastructure, collaboration with other participants, and, where applicable, grants, delegation support, mentorship, events, work opportunities, or regional programming.

The Community Registration Policy in Q151 does not create or exhaustively define the Solana community. It translates objective participation and affiliation paths into registrant eligibility criteria. It also permits a good-faith new participant intending to establish a qualifying connection within 90 days to register and allows other evidence of community participation to be considered. The separate trademark-holder exception is a namespace-safety measure and does not make a trademark holder a community member absent an independent community connection. Eligibility is assessed at initial registration under the Registry Operator’s verification methodology.

Where is the community located?

Global and primarily online, with members and organized programs across North America, Europe, Asia, Latin America, Africa, the Middle East, and Oceania. Significant concentrations include the United States, India, and Southeast Asia.

What is the estimated size of the community? This should take into account any regions listed in Question 138.

Estimated size: 105,000,000 monthly active users/wallets worldwide as of June 2026. Overlapping segments include approximately 2,600 active developers and 700 validators.

What portion of the community do any organizing bodies represent or administer to?

Solana Foundation represents the ecosystem, supporting 500+ projects and 362 validators in 24 countries. Superteam connects 15,000+ developers through 25+ regional teams. With endorsing organizations, these bodies represent a majority of the community.

Do the organizing bodies demonstrate active and consistent efforts to engage and connect with the identified community and its members?

Yes. During the two years preceding submission, Solana Foundation—the principal ecosystem-wide organizing body identified in Q136—maintained continuous, publicly documented engagement with the community. Colosseum, Superteam, validators, and independent ecosystem organizations supplemented those efforts within their established roles. The evidence reflects continuing programs, not outreach created for the .sol application.

(a) OFFERING SUPPORT. The Foundation’s funding program remained active throughout this period and has cumulatively supported more than 500 projects with more than $100 million across six continents. The Foundation also works with Colosseum to conduct global online hackathons and an accelerator. The Radar Hackathon in 2024 attracted more than 10,000 participants from over 120 countries, who submitted 1,359 projects. The Frontier Hackathon in 2026 attracted more than 10,000 participants from over 150 countries, who submitted 2,857 projects. The Foundation Delegation Program provided continuing support to qualifying validators; as of Epoch 1000 on July 10, 2026, it supported 362 validators across 24 countries. Superteam chapters separately offer grants, bounties, work opportunities, mentorship, and local programming.

(b) SHARING INFORMATION. The Foundation regularly publishes ecosystem news, technical updates, developer materials, event information, and program requirements through official websites and communications channels. Its Delegation Program maintains public eligibility criteria and a current validator dashboard. Breakpoint, Accelerate, and hackathon sessions and results are published online. Superteam chapters and independent organizations serving functional segments—including Phantom, Solflare, Jupiter, Kamino, and SNS—maintain documentation, support resources, integration materials, and communications channels for their participants.

(c) RESPONDING TO SPECIFIC COMMUNITY NEEDS. The Foundation uses open grant applications and targeted requests for proposals to support identified ecosystem public goods. Recent requests address needs such as multi-validator staking tools and automated stake delegation and rebalancing. In May 2026, the Delegation Program revised its published criteria to address infrastructure concentration, adding limits for data-center and network-provider concentration. Colosseum’s accelerator provides selected hackathon teams with funding, mentorship, and technical resources to help promising projects progress beyond initial development.

(d) FOSTERING AND STRENGTHENING RELATIONSHIPS. The Foundation convened Breakpoint 2024 in Singapore and Breakpoint 2025 in Abu Dhabi; the 2025 event brought together more than 7,200 attendees from over 100 countries. In 2026, Solana Accelerate held events in Hong Kong and Miami, with the Miami program drawing approximately 3,000 participants. Superteam’s 20+ regional chapters conduct recurring local events and member programming, while Foundation-supported hackathons connect developers and founders globally. Together, these programs sustain relationships among developers, validators, founders, businesses, and users across the community.

Corresponding documentation includes Foundation program pages, published criteria and dashboards, event archives, hackathon results, and Superteam materials documenting each category of engagement during the relevant two-year period.

Answered with a document. Attachments are not published by ICANN.

What is the role of the applying entity in the engagement efforts listed in Question 141?

Sol Naming Limited’s role in the engagement described in Q141 is specific and complementary. It is the entity designated to carry the Solana community’s Internet-naming initiative through the ICANN process and, if approved, establish and operate .sol as an enduring DNS namespace.

Within the activities described in Q141, Sol Naming’s contribution has been consultative, technical, and preparatory. Solana Foundation evaluated the need for a Solana-aligned DNS namespace and reviewed the proposed applicant structure, the ICANN and domain-industry experience of the principals and advisers carrying the initiative, the intended use of Identity Digital as Registry Services Provider, and the proposed community-based registration framework. Following that review, the Foundation selected and endorsed Sol Naming as the community’s applicant and ICANN operating partner. Its written endorsement documents that decision.

Sol Naming’s supporting principals and technical contributors also led or contributed to development of the Solana Record Service in coordination with members of the Foundation’s technical team. SRS is public-good infrastructure that permits records associated with names and identifiers to be created, updated, and deleted on Solana. It is available at records.solana.com and documented through the public solana-foundation/solana-record-service repository. SRS is technically separate from the DNS and neither creates nor resolves DNS domain names. This work provided relevant experience concerning Solana-native identity, record infrastructure, and the community’s naming requirements.

The .sol initiative was also presented and discussed at Solana community events. Supporting principals and service providers staffed a product kiosk and participated in a tokenized-domain presentation with InterNetX/IONOS at Breakpoint Abu Dhabi. At Solana Accelerate Miami, the initiative was discussed publicly with Foundation Chief Product Officer Vibhu Norby in connection with Internet-native assets and naming infrastructure. Supporting participants also co-hosted Playa Du Sol for approximately 100 attendees. These activities created awareness, relationships, and practical input concerning the proposed namespace.

Consultation extended across major functional segments. SNS, Phantom, Solflare, Jupiter, and Kamino Foundation each submitted a signed letter identifying its community role, supporting the Foundation’s selection of Sol Naming, and recognizing the expected benefit of .sol to its participants. Engagement with these naming, wallet, DeFi, application, and user organizations informed the proposed Community Registration Policies and the intended relationship between the DNS namespace and technically distinct Solana-native identity infrastructure. Their support confers no ownership or authority over the applicant or registry.

The Foundation, Colosseum, Superteam, validators, and independent ecosystem organizations continue to conduct the broader grants, delegation programs, hackathons, conferences, regional activities, and participant services described in Q141. Sol Naming complements those established roles by translating the community-supported initiative into an ICANN application, Community Registration Policies, qualified registry infrastructure, registrar distribution, DNS-security and abuse controls, and continuing ICANN compliance.

Sol Naming will independently administer the application and registry and remain responsible for its policies, operations, and Registry Agreement compliance. Its continuing engagement will focus on responsible launch and adoption of .sol, consultation concerning community naming needs, and operation of the namespace as a stable DNS resource for the Solana community.

Answered with a document. Attachments are not published by ICANN.

Are community members aware of the identified community and each other?

Yes. Community members demonstrate awareness of the Solana community and its principal member groups through shared communications channels, recurring cross-segment activities, regional organizations, and public records identifying active developers, validators, applications, and ecosystem organizations.

(a) Surveys conducted. Sol Naming has not identified a community-wide survey conducted during the relevant two-year period that asked members specifically whether they recognize the Solana community and its different segments. Accordingly, this response does not rely on survey evidence. Awareness is instead demonstrated through documented participation in shared community channels and activities involving diverse groups.

The Foundation’s official community page identifies common channels through which members receive information and interact. As of July 21, 2026, those channels included approximately 3.03 million followers on X, 344,000 Reddit subscribers, 141,556 Engineering Discord members, 70,463 Telegram members, and 95,100 YouTube subscribers. These figures demonstrate widespread recognition of and participation in common Solana community spaces.

(b) Records of activities involving diverse community groups and segments. The Foundation’s June 2025 Network Health Report separately identifies and discusses developers, validators, applications, wallets, and other ecosystem participants. It reported more than 7,600 new developers during 2024, using Electric Capital’s independent developer data. Foundation-provided data for June 2026 identifies approximately 2,600 active developers, 80% monthly development retention, and approximately 700 validators, demonstrating continuing participation across distinct community segments.

Recurring activities bring these groups together under a shared Solana identity. The 2024 Radar Hackathon attracted more than 10,000 participants from over 120 countries and produced 1,359 project submissions. The 2026 Frontier Hackathon attracted more than 10,000 participants from over 150 countries and produced 2,857 submissions. These events required developers and founders to identify their projects as part of the Solana ecosystem and interact with sponsors, judges, mentors, and other teams across application segments.

The Foundation also convened Breakpoint 2024 in Singapore and Breakpoint 2025 in Abu Dhabi. The 2025 event brought together more than 7,200 attendees from over 100 countries across developer, validator, wallet, payments, DeFi, infrastructure, institutional, and consumer segments. Solana Accelerate USA in Miami brought together approximately 3,000 participants in May 2026. Superteam’s 25+ regional teams connect more than 15,000 developers and provide recurring forums in which developers, founders, creators, and other contributors identify and interact as members of local and global Solana communities.

Awareness is also reflected in the community’s public infrastructure and institutional relationships. Public validator dashboards, software repositories, program records, and ecosystem directories allow members to identify active participant groups. The written endorsements described in Q156 from Phantom, Solflare, Jupiter, Kamino, and the Solana Name Service further demonstrate that major wallet, trading, lending, and naming organizations recognize the broader Solana community and their respective roles within it.

These records show more than parallel use of the same technology. Community members gather in shared channels, participate in common programs and events, organize through regional teams, collaborate across functional segments, and publicly identify their work with the Solana ecosystem.

Answered with a document. Attachments are not published by ICANN.

Are community members aware of the applying entity and its intention to apply for a community gTLD?

Yes. The Solana community’s principal institution and organizations serving its major functional segments are aware of the .sol initiative and of Sol Naming Limited as the applying entity. That awareness originates in a decision taken in 2024 and continued through the development and public presentation of the initiative and the subsequent written endorsements.

Solana Foundation evaluated the ICANN new gTLD opportunity and the role a Solana-aligned DNS namespace could play in the ecosystem’s long-term development. It reviewed the proposed applicant structure, the ICANN and domain-industry experience of the principals and advisers who would carry the initiative, the intended use of Identity Digital as Registry Services Provider, and the proposed community-based registration framework. The Foundation approved its endorsement on October 25, 2024, following internal review and Director and President approval. Sol Naming Limited is the dedicated entity through which that endorsed initiative is pursued. The Foundation’s written endorsement identifies Sol Naming as the applicant and ICANN operating partner, describes the proposed registry arrangements, and urges ICANN to approve the application.

The initiative was also presented publicly through activities documented in Q142. Supporting principals and service providers presented .sol at Solana Breakpoint Abu Dhabi, participated in a public discussion concerning tokenized domains, co-hosted Playa Du Sol, contributed to the Solana Record Service, and discussed Internet-native assets and naming infrastructure at Solana Accelerate Miami. These activities created awareness of the .sol DNS initiative and the team responsible for carrying it into the ICANN process.

Specific awareness of Sol Naming and its application is demonstrated across major community segments. Signed letters from SNS, Phantom, Solflare, Jupiter, and Kamino Foundation each identify Sol Naming Limited by name, support its application for the .sol community gTLD, and support Solana Foundation’s selection of Sol Naming as the applicant or ICANN operating partner. These organizations serve on-chain naming, wallets, consumer users, trading and liquidity, lending, DeFi, applications, and other economically active participants.

The awareness reflected in these letters is informed rather than nominal. The endorsing organizations recognize that the proposal concerns an ICANN-administered namespace in the global DNS and describe the expected benefits of .sol for identity, discoverability, trust, interoperability, wallets, applications, developers, and users. SNS expressly distinguishes its Web3 naming role on Solana while supporting recognition of .sol within the global DNS.

Institutional evidence is appropriate for this open, participation-based community. As described in Q136 and Q137, the Solana community has no membership roll or general assembly through which a community-wide notice or vote could be administered. Solana Foundation and organizations serving identifiable functional segments are the established channels through which awareness and support for an initiative of this kind can be demonstrated. Their letters establish both awareness of the applying entity and knowledge of its intention to apply for .sol as a community gTLD.

Answered with a document. Attachments are not published by ICANN.

Was there an established presence of the identified community prior to the opening of the application submission period?

Yes

Answered with a document. Attachments are not published by ICANN.

Are individuals and groups outside of the identified community aware of the existence of the identified community?

Yes. Individuals and organizations outside the Solana community demonstrate substantial and continuing awareness of the community, its institutions, activities, and members.

(a) Media and public information. During the two years preceding this application, major financial and technology publications, including Reuters, Bloomberg, CNBC, the Financial Times, Forbes, Fortune, and TechCrunch, regularly covered Solana as a distinct, named ecosystem. This reporting addressed its developers, validators, applications, institutional adoption, network activity, and community events, demonstrating recognition extending beyond blockchain-focused media.

(b) Discussion in external fora. Solana has been discussed in regulated financial markets, government records, academic research, industry conferences, and institutional research. In March 2025, CME Group listed SOL and Micro SOL futures in response to stated customer demand. Federal Register notices concerning proposed exchange-traded products discuss the Solana network, its participants, and its ecosystem. Independent academic publications similarly study Solana’s technical operation, applications, and user activity.

(c) Partnerships and collaborations with outside groups. Established companies and financial institutions have integrated with or deployed products using Solana. PayPal made its regulated PYUSD stablecoin available on Solana in May 2024. Visa uses Solana in its live USDC settlement infrastructure. Shopify supports an approved Solana Pay integration, and Franklin Templeton permits shares of its registered Franklin OnChain U.S. Government Money Fund to be maintained on Solana. These organizations are external to the identified community and necessarily evaluated and engaged with the Solana ecosystem before undertaking these activities.

(d) Organization before the application window. The Solana mainnet began operating in March 2020, and the Solana Foundation was established in Switzerland in 2020 to support the network’s development, decentralization, education, research, grants, and validator community. By the end of 2020, published records documented hundreds of validators, more than 100 project integrations, millions of wallets, and an established developer community. The community and its organizing institutions therefore predate this application by more than six years.

(e) Contributions to broader society. Solana-based infrastructure supports activities extending beyond the blockchain industry. Visa and PayPal use the network for payment and settlement infrastructure. Helium uses it to support decentralized wireless connectivity, Hivemapper uses it to coordinate mapping contributions, and Render Network uses it in connection with distributed computing resources. Regulated financial products, including Franklin Templeton’s government money market fund, also use Solana-based recordkeeping. These applications provide payment, communications, mapping, computing, and financial services to users and institutions outside the Solana community.

Collectively, this media coverage, institutional discussion, commercial integration, longstanding organization, and broader technical use demonstrate extensive awareness of the Solana community among individuals and groups outside it.

Answered with a document. Attachments are not published by ICANN.

Are the pursuits of the identified community enduring and sustainable?

Yes. The Solana community’s pursuits are enduring and sustainable. It has existed for more than six years and demonstrates continuity through recurring programs, longstanding technical and organizational activity, functional diversification, and scheduled future engagement.

(a) RECURRING OR SCHEDULED ACTIVITIES. Solana Breakpoint has been held annually since 2021: Lisbon in 2021 and 2022, Amsterdam in 2023, Singapore in 2024, and Abu Dhabi in 2025. Breakpoint 2026 is scheduled for November 15-17 in London. These events convene developers, validators, application teams, businesses, institutions, and users.

Solana Foundation maintains recurring grant and funding programs and an ongoing Validator Delegation Program with published requirements. Colosseum conducts recurring global hackathons and accelerator programs, while Superteam’s 20+ regional chapters maintain grants, work opportunities, member programs, and events. These activities provide continuing channels for new participants, projects, and infrastructure support.

(b) DOCUMENTED RECORDS OF LONGSTANDING ACTIVITY. Solana Mainnet Beta began operating in March 2020, and Solana Foundation was established in Switzerland that year. Contemporaneous records documented more than 350 active validators, more than 100 project integrations, 4.9 million unique SOL wallets, and an inaugural hackathon involving more than 1,000 registered developers.

Subsequent records document recurring conferences, hackathons, grants, validator activity, software development, integrations, and application launches through multiple technology and market cycles. The community is not dependent on a single event, company, product, or application.

Its functional diversity includes protocol development, validation, infrastructure, wallets, on-chain naming, payments, DeFi, trading, lending, gaming, digital ownership, consumer applications, education, and regional programming. The supporting letters document established organizations serving these segments, including Solflare’s continuous wallet service since 2020, Kamino’s operation since 2022, SNS naming infrastructure, and the continuing activities of Phantom and Jupiter.

(c) RECORDS EMPHASIZING ENDURING PRESENCE AND SIGNIFICANCE. Foundation reports, Breakpoint materials, developer reports, and program records consistently describe Solana as an established global ecosystem. They document its development from an early validator and developer base into a multi-institutional community supporting financial services, payments, communications infrastructure, digital ownership, and consumer applications. Breakpoint 2026, continuing grants, recurring hackathons, and ongoing validator and regional programs demonstrate forward-looking commitments.

The .sol initiative provides additional evidence of long-term stewardship. Solana Foundation approved its endorsement of the proposed applicant structure and initiative in October 2024. Technical work, public presentations, consultation, and written support from SNS, Phantom, Solflare, Jupiter, and Kamino continued through 2025 and 2026. This multi-year record shows an institutional effort to secure and responsibly administer the community’s DNS identifier.

If delegated, .sol will add a sustainable Internet-identity function. Sol Naming’s dedicated registry structure, Identity Digital’s infrastructure, accredited-registrar distribution, registration and renewal revenue, and ICANN’s continuity, security, and compliance requirements provide an enduring operational model. Sol Naming’s independent accountability under the Registry Agreement will preserve that function over time.

The community therefore has a substantial historical record, continuing institutional mechanisms, and a documented stewardship initiative supporting its future DNS namespace.

Answered with a document. Attachments are not published by ICANN.

Does the string match the name of the identified community?

Yes. “SOL” is the universally recognized short-form identifier for Solana and the Solana community.

Official Solana documentation identifies SOL as Solana’s native currency and uses the designation throughout its technical, validator, developer, and community materials. Regulated markets, financial institutions, exchanges, data providers, regulatory filings, and media consistently identify Solana using the paired designation “Solana (SOL).” CME Group, for example, lists its Solana futures under the symbol SOL. This consistent global usage makes “SOL” immediately recognizable as referring to Solana and its ecosystem.

SOL is also integral to participation in the community. It is used to pay network fees, support validator operations, interact with applications, and satisfy certain community membership criteria described in Q137. Independent organizations and publications consequently use expressions such as the “SOL community” when referring to Solana participants. SOL therefore functions as more than an asset symbol: it is the established short-form identifier associated with the network and the community organized around it.

The community’s longstanding use of .sol-formatted on-chain identifiers provides additional evidence of this recognition. The Solana Name Service enables users to associate a human-readable .sol identifier with a Solana wallet address and other on-chain information. These identifiers are used across major wallets and applications as community identity and addressing tools.

For clarity, those existing on-chain identifiers are not DNS domain names, are not registered through ICANN-accredited registrars, and do not exist within or resolve through the ICANN DNS root. Their relevance to this question is limited to demonstrating that the community independently selected and recognizes “sol” as an identity-related short form. The proposed .sol TLD will be a technically distinct DNS namespace, subject to ICANN requirements and capable of standard DNS resolution.

The Solana Name Service, which supports the existing on-chain identifier system, has endorsed this application. That endorsement further confirms that the applied-for string is recognized by the relevant community and that the proposed DNS TLD is intended to complement, rather than be confused with, the community’s separate on-chain identifiers.

Accordingly, the applied-for string matches the identified community because “SOL” is its globally recognized short-form identifier. The separate historical use of .sol-formatted on-chain identifiers corroborates that community recognition without suggesting technical equivalence between those identifiers and DNS domain names.

Answered with a document. Attachments are not published by ICANN.

Will the general public instinctively think of the community when thinking of the applied-for string?

Yes. When encountered as the applied-for Internet identifier .sol, the general public would associate the string with the Solana community.

As explained in Q148, SOL is the globally recognized short-form identifier for Solana. That association is not limited to community insiders. Official Solana materials, regulated markets, financial institutions, regulatory filings, data providers, and mainstream publications consistently use the paired designation “Solana (SOL).” CME Group lists regulated Solana futures as “SOL Futures,” while Fidelity presents its public explanation under the title “What Is Solana (SOL)?” These repeated uses by organizations outside the community demonstrate that SOL publicly identifies Solana and its ecosystem.

The .sol format further reinforces that association for persons encountering the string as an Internet identifier. For several years, Solana participants have used .sol-formatted on-chain identifiers for wallet addressing and identity across widely used ecosystem applications. Those identifiers are technically separate from the DNS, are not DNS domain names, and do not resolve through the ICANN root. Their relevance here is that a large existing audience already recognizes “sol” as an identity-related reference to the Solana community. The proposed .sol TLD will establish a distinct, ICANN-regulated DNS namespace capable of standard DNS resolution.

The string also has other meanings. “Sol” means “sun” in Spanish and other languages, is used as a syllable in solfège, describes a solar day on Mars, and is the name of Peru’s national currency. The application does not contend that these meanings do not exist.

Those meanings, however, do not identify a delineated global community commonly known as the .sol community in an Internet-identifier context. The Peruvian currency’s ISO 4217 code is PEN rather than SOL. The astronomical and musical meanings describe concepts rather than organized communities. Likewise, “sun” is a dictionary meaning, not the established name or recognized short form of a particular community represented by the applied-for string.

By contrast, Solana is consistently and publicly identified as SOL by both community members and independent institutions, and it has a large, organized community whose members already recognize “sol” as an identity-related identifier. Accordingly, when .sol is encountered as a top-level domain, the clearest community association is with the Solana community.

See Q.148 for Corresponding Documentation, which we believe also supports response to this question.

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?

Yes

Please state a specific Community Registration Policy with respect to registration eligibility for community members.

Registry Operator shall restrict registrant eligibility for second-level domain names in the .sol TLD to persons or entities that demonstrate participation or affiliation with the Solana blockchain ecosystem at the time of initial registration or an intent to participate within 90 days of registration. Eligible registrants shall satisfy at least one of the following criteria pursuant to the verification methodology described below:

(a) Operates a Solana wallet address, as verifiable on the Solana mainnet; (b) Operates a Solana validator node, as registered on the Solana mainnet; (c) Has deployed one or more programs to the Solana mainnet, as verifiable on the Solana mainnet; (d) Holds one or more on-chain names registered through the Solana Name Service, as verifiable on the Solana mainnet; (e) Has received a Solana Foundation grant within the 36 months preceding registration, as evidenced by documentation from the Solana Foundation or its authorized representative; or (f) Is a verified member of a Solana Foundation-recognized ecosystem program, as confirmed by reference to the Programs List described below. (g) Promotes the Solana ecosystem (h) Can provide any other evidence of community participation, upon request (i) Intends to satisfy one or more of the above criteria within 90 days of registration.

Registry Operator shall maintain and publish on its website a sample list of Solana Foundation-recognized ecosystem programs eligible under criterion (f) (the "Programs List"). Registry Operator shall review and, as appropriate, update the Programs List or make exceptions.

Registry Operator will allow trademark holders to register their trademarks at any time, even if they do not otherwise satisfy one of the criteria above, as part of the Registry Operator’s efforts to create a safe and reputable namespace.

State a specific Community Registration Policy with respect to name selection criteria or rules for the applied-for string.

Registry Operator Registry Operator shall not permit registration of a second-level domain name in the .sol TLD that is identical, without regard to letter case, to a label included on the Reserved Names List unless Registry Operator provides written authorization.

Registry Operator shall maintain and publish on its registrar portal a Reserved Names List containing second-level labels, which for example may correspond to documented names, trademarks, or commonly used identifiers of persons or entities with a documented connection to the Solana ecosystem.

Registry Operator shall independently establish and administer the Reserved Names List under this policy.

Registry Operator shall create the initial Reserved Names List no later than commencement of the first registration period for the TLD. An addition to the Reserved Names List shall apply prospectively and shall not affect a Registered Name created before the addition unless required by applicable ICANN policy, an applicable dispute-resolution proceeding, court order, or agreement with the Registered Name Holder.

Registry Operator will not allow any domain name registrations that violate any of the policies below: - Used for illegal activities - Used for DNS abuse - Used against the interests of the Solana ecosystem or Registry Operator - Violate intellectual property rights - Used to attack .sol websites or the Solana network

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.

Registry Operator shall maintain a process through which a registrant or prospective registrant may request review of an adverse determination made under the .sol registrant eligibility or name selection policies.

Registry Operator shall permit a request for review to be submitted within 7 days after notice of the adverse determination and shall provide the requesting party with a written decision within 30 days after receiving the request.

Registry Operator shall publish the review process on its website no later than the commencement of General Availability.

Registry Operator will work with community members to create a reserve list and policy for community-priority names that may be allocated to community members. Community-priority names will be allocated during a defined as published on the Registry Operator’s website.

Registry Operator will hold one or more Limited Registration Periods prior to General Availability, with eligibility restricted to qualified Community members, and qualifications and launch dates published on the Registry Operator’s website.

Registry Operator reserves the right to review these policies from time to time and may publish the results of any review on its website.

Explain the rationale for any limitations to the Community Registration Policy proposed by the applying entity in Questions 151-153.

The proposed Community Registration Policies contain limited temporal and scope qualifications, each tailored to the purpose of the applicable policy.

Q151 evaluates community eligibility at initial registration rather than at each renewal. This permits a Registered Name to remain a stable Internet identifier after a registrant establishes a qualifying connection to the community, even if the particular form of participation later changes. The 90-day intent pathway allows good-faith new participants to obtain an identity for an activity they are preparing to undertake within the Solana ecosystem. The 36-month period for grant-based eligibility ensures that a grant used as evidence reflects a reasonably current community connection. The trademark-holder exception is limited to registration of the holder’s trademark and supports the creation of a safe and reputable namespace without creating a broader exception to community eligibility.

Under Q152, an addition to the Reserved Names List applies prospectively. This protects the reasonable expectations of an existing Registered Name Holder and avoids retroactively impairing a registration that was permitted when created. The written-authorization exception allows an associated person or entity to approve an otherwise reserved registration.

Under Q153, the seven-day period for requesting review promotes prompt resolution of adverse determinations, while the 30-day decision period provides the Registry Operator sufficient time to evaluate the request and issue a reasoned written decision. Community-priority allocation periods and Limited Registration Periods are time-limited because they serve launch and priority-allocation purposes before the ordinary registration process applies.

Except for these expressly identified temporal and scope qualifications, the proposed Community Registration Policies are not time-limited and are intended to apply throughout the term of the Registry Agreement.

Explain how the proposed Community Registration Policies of the applying entity meets the Registry Commitments Evaluation criteria 4 and 5?

CRITERION 4: DUPLICATION AND CONTRARY REQUIREMENTS. The proposed Community Registration Policies do not duplicate, and are not contrary to, requirements under applicable law, the Base Registry Agreement, ICANN Consensus Policies, or ICANN Temporary Policies.

Q151 establishes a .sol-specific eligibility framework based on participation or affiliation with the Solana ecosystem, evidence of community participation, promotion of the ecosystem, or an intent to participate within 90 days. No applicable law or ICANN requirement establishes or administers these community-specific eligibility conditions. The limited trademark-holder exception is an eligibility provision and does not replace or duplicate the Trademark Clearinghouse, Sunrise, Trademark Claims, UDRP, URS, or any other applicable rights-protection mechanism.

Q152 establishes a .sol-specific Reserved Names List and rules governing the availability and prospective reservation of community-related second-level labels. Applicable ICANN requirements and rights-protection mechanisms do not require the Registry Operator proactively to identify and reserve documented names, trademarks, or identifiers associated with the Solana ecosystem. The policy supplements those requirements without replacing or limiting them.

Q153 establishes an internal review procedure for determinations made under the .sol eligibility and name-selection policies, together with community-priority allocation and Limited Registration Period processes. Applicable law and ICANN requirements do not provide an equivalent review or priority-allocation process for the .sol community. These processes operate subject to, and do not limit, any rights or remedies available under applicable law, the Registry Agreement, or ICANN policies.

Nothing in Q151-Q153 authorizes conduct prohibited by, excuses compliance with, or alters any obligation imposed by applicable law, the Registry Agreement, an ICANN Consensus Policy, or an ICANN Temporary Policy.

CRITERION 5: ICANN BYLAWS COMPATIBILITY. The proposed policies concern who may register a .sol domain name, when registration may occur, which second-level labels may be available, and how Registry Operator determinations may be reviewed. These are operational and procedural conditions directly concerning the allocation and administration of unique identifiers within the .sol TLD.

The policies do not restrict or require evaluation of website content, communications, applications, products, or services. They therefore do not place ICANN in the position of evaluating or enforcing restrictions on content carried or provided through a Registered Name. References to the Solana mainnet and the Solana Name Service are used solely to identify evidence of community participation; the policies do not require DNS resolution through Solana, create interoperability with on-chain identifiers, or establish an alternative naming root.

ADDITIONAL REGISTRY SERVICE CONSIDERATIONS. The Registry Operator is coordinating implementation with its selected Registry Service Provider. The policies can be implemented through ordinary registration, reservation, verification, and launch workflows. Eligibility may be evaluated using public Solana mainnet records or documentary evidence without altering DNS, DNSSEC, EPP, RDDS, or data-escrow services and without providing an on-chain resolution service. On the proposed implementation, the policies do not require an additional Registry Service. If ICANN or the selected Registry Service Provider determines that a particular implementation would constitute an additional Registry Service, the Registry Operator will complete the required RSP Program evaluation and obtain ICANN approval before offering that service.

From where does the applying entity have the support to run the applied-for string on behalf of the identified community?

Sol Naming Limited has written support from the Solana Foundation, the principal organizing body for the identified community, and from recognized organizations serving the community’s naming, wallet, user-access, application, and decentralized-finance segments. The attached endorsements are described below.

SOLANA FOUNDATION. The Solana Foundation has endorsed Sol Naming as the applicant and intended independent registry operator for the .sol community gTLD. Its attached endorsement explains the Foundation’s role in organizing and supporting the Solana community, its reasons for supporting Sol Naming’s application, and why the proposed .sol TLD will benefit the community. This is the application’s primary institutional endorsement.

As described in Q136, the Foundation supports the Solana ecosystem through grants, validator programs, developer resources, community events, regional initiatives, and other documented programs. Its endorsement therefore reflects its ecosystem-wide organizing role rather than the interests of a single product or constituency. Sol Naming remains independently responsible for the application and, if successful, the operation and policies of the registry.

SOLANA NAME SERVICE. IIFSNS Limited, the operator of the Solana Name Service, has provided a signed endorsement of Sol Naming’s application. SNS operates the technically separate on-chain naming service through which Solana participants use .sol-formatted identifiers. Those identifiers are not DNS domain names and do not exist within or resolve through the ICANN DNS root.

The SNS endorsement states that, as of July 1, 2026, its on-chain system included 449,663 identifiers associated with 288,506 distinct wallets. It describes “sol” as a natural and established identifier for the Solana community and supports establishing a distinct, community-aligned .sol TLD within the global DNS. This endorsement is particularly relevant because SNS represents the community segment most directly associated with the existing on-chain use of .sol-formatted identifiers. Its support demonstrates alignment between that segment and the proposed, technically distinct DNS registry.

WALLET AND USER-ACCESS ORGANIZATIONS. Phantom and Solflare have provided written endorsements. These organizations provide principal wallet interfaces through which community members access the Solana network and its applications. Their endorsements demonstrate support from organizations serving a broad cross-section of users, developers, and application participants. Their letters describe their respective roles and explain why a community-aligned .sol TLD would benefit the community members they serve.

ECOSYSTEM APPLICATIONS AND FINANCIAL INFRASTRUCTURE. Jupiter and Kamino have provided written endorsements. Both operate widely used applications and infrastructure within the Solana ecosystem and interact directly with active community participants. Their letters describe their respective community roles and support establishing .sol as a community-aligned TLD in the global DNS under Sol Naming’s independent operation.

BREADTH OF COMMUNITY SUPPORT. The Solana community is open and global and does not maintain a single authoritative roster of individual human members. Support is therefore demonstrated through its principal organizing body and recognized organizations serving distinct functional segments. The attached endorsements cover ecosystem-wide stewardship, on-chain identity, principal user-access tools, trading and liquidity infrastructure, and lending and decentralized finance.

Although the organizations’ user populations overlap and should not be aggregated into an unsupported cumulative percentage, the endorsements demonstrate support across the principal institutional and functional channels through which members identify themselves, access the network, and participate in the ecosystem.

Answered with a document. Attachments are not published by ICANN.

Is there any opposition to the applying entity, application, or applied-for string that the applying entity is aware of? If yes, please explain.

No. As of the date of submission, Sol Naming Limited is not aware of any opposition to the applying entity, this application, or the applied-for .sol string. No person, organization, or Solana community entity has communicated opposition to Sol Naming Limited. Accordingly, there is no known opposition to assess for relevance or for the applying entity to address or resolve.

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.

Sol Naming Limited’s application for the .sol TLD is supported by Solana Foundation and by independent organizations serving major functional segments of the Solana ecosystem: SNS, Phantom, Solflare, Jupiter, and Kamino Foundation. Their activities span ecosystem stewardship, on-chain naming, wallets, consumer users, trading and liquidity, lending, DeFi, applications, and infrastructure. The letters demonstrate cross-segment support; they are not presented as a statistical survey or as evidence that any organization represents the community as a whole.

Sol Naming is the independent applying entity and, if the application succeeds, will be responsible for establishing and operating .sol under its Registry Agreement with ICANN. Solana Foundation and the other supporting organizations do not own, manage, or control Sol Naming, the application, or the proposed registry. Their endorsements confer no registry governance or decision-making authority.

The endorsements express more than approval of the string. Solana Foundation describes its review of the proposed applicant structure, the ICANN and domain-industry experience supporting the initiative, the intended use of Identity Digital as Registry Services Provider, and the proposed community-based registration framework. It identifies Sol Naming as the community’s applicant and ICANN operating partner and urges approval of the application.

The other letters identify Sol Naming by name, support Solana Foundation’s selection, and describe the expected benefit of establishing .sol as an ICANN-administered namespace in the global DNS:

• SNS operates the Web3 name service for .sol on Solana. As of July 1, 2026, its legacy registry comprised 449,663 on-chain names associated with 288,506 distinct wallets. SNS recognizes the DNS TLD as a natural extension of the broader Solana identity layer while remaining technically separate from DNS resolution.

• Phantom and Solflare provide principal self-custodial wallet interfaces for Solana users. Phantom reports serving millions of users globally and billions of dollars in annual transaction volume. Solflare has served the ecosystem continuously since 2020 and reports more than four million active users and billions of dollars in user assets.

• Jupiter is a leading decentralized-exchange aggregator on Solana and serves DeFi participants, users, and ecosystem contributors. It describes .sol as a means of strengthening trust, discoverability, and identity for Solana-based financial applications.

• Kamino Foundation supports the Kamino ecosystem, described in its letter as Solana’s largest lending and liquidity protocol by total value locked, with multi-billion-dollar deposits. It likewise supports .sol as a community-aligned identity and discoverability resource.

Solana Foundation’s continuing programs provide additional evidence of community breadth and institutional capacity. Its funding programs have supported more than 500 projects with more than $100 million across six continents, and its Delegation Program supported 362 validators in 24 countries as of July 2026.

These indicators are not aggregated because the organizations’ participant populations may overlap. Their significance lies in the diversity and scale of the segments independently supporting the same initiative. Collectively, the letters demonstrate informed, cross-segment support for .sol and confidence in Sol Naming’s ability to establish and sustain a useful DNS namespace while remaining independently accountable for registry governance, policies, operations, and ICANN compliance.

Answered with a document. Attachments are not published by ICANN.

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.

true

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.

true