.sui

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 Sui community is best categorized as a global, online, activity-based technology community organized around the open-source Sui protocol and ecosystem.

Its members participate in interdependent roles: Move developers create code and applications; validators and node operators operate and secure the network; users controlling active Sui Mainnet wallets and holders of SuiNS identifiers participate through the network’s transaction and on-chain identity infrastructure; and recognized ecosystem-program participants contribute through development, research, education, events, or other ecosystem support. These roles share one protocol, technical standards, network, institutions, and continuing purpose.

The community does not depend on admission by a single centralized membership association. Affiliation instead arises through defined, objectively verifiable participation. Relevant actions/activities may be demonstrated through public Sui Mainnet records or institutional program records, including control of an active Sui Mainnet wallet, operation of an active validator, deployment of a Move package to Mainnet, control of a SuiNS identifier, receipt of a Sui Foundation grant within the applicable period, or verified participation in a program on the published Programs List. These are the same participation paths reflected in the Community Registration Policy in Q151.

The community is decentralized in participation but connected and supported through Sui Foundation, Mysten Labs, independent validators, recognized ecosystem organizations, open-source repositories, technical documentation, grants and builder programs, hackathons, conferences, regional activities, and public communication channels. Accordingly, the Sui community is an established open-technology community with observable boundaries, continuing organization and interaction, and a shared purpose in developing, operating, securing, supporting, and using Sui.

Although the community is global and coordinates largely online, it is not an online or social-media group. Its members are not followers, subscribers, or an audience. Its institutions, technical standards, funding programs, governance, and events exist independently of any social platform, and participation is evidenced by conduct on a public network rather than by association with an account or channel. It is equally distinguishable from a broad interest or market segment such as “blockchain users” or “Web3 developers”: it is organized around one specific open-source protocol and network, with its own technical standards, institutions, funding and builder programs, and recognized organizations, as described in Q136.

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

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

Sui Naming Limited's connection to the Sui community arises from a documented institutional decision. Sui Foundation, the community's principal ecosystem-wide stewardship organization as described in Q136, endorsed the .sui community application and identifies Sui Naming as the entity that will pursue it and, if the application succeeds, operate the TLD for the community under ICANN's Registry Agreement.

That decision was deliberate and documented. The Foundation reviewed the ICANN opportunity, the proposed structure for the application, the ICANN and domain-industry experience of the principals and advisers who would carry it, the intended use of Identity Digital as Registry Services Provider, and the proposed community-based registration framework. It approved its endorsement on or about September 1, 2023, following internal review and discussion among Foundation leadership, and confirmed that endorsement in the written letter submitted with this application.

Sui Naming is a special-purpose registry entity by design. Operating a gTLD requires a dedicated contracting party accountable to ICANN, qualified registry infrastructure, distribution through ICANN-accredited registrars, and continuing compliance, data-escrow, security, and abuse-mitigation obligations. Sui Naming provides that specialized legal and operational vehicle. Its supporting team and advisers bring relevant ICANN, domain-name, and web3 infrastructure experience, while Identity Digital will provide established registry infrastructure and related technical and compliance capabilities.

The relationship is corroborated by organizations serving multiple functional segments of the community. Mysten Labs, the original developer and a principal technical contributor to Sui, supports the Foundation's endorsement. Cetus (DeFi and liquidity), Talus (on-chain AI), DoubleUp (gaming), Miso Labs (music and creators), GiveRep (social and reputation), and Inkray (decentralized publishing) have also provided written support. Their letters describe their respective connections to Sui, recognize .sui as the community's natural DNS identifier, support Sui Naming as the applicant, and look to it to complete the ICANN process and operate the namespace for the community.

Sui Naming is not a corporate affiliate or subsidiary of Sui Foundation, Mysten Labs, or any endorsing organization, and the endorsements confer no ownership, control, or registry decision-making authority. Sui Naming retains sole responsibility for this application and, if successful, ultimate responsibility for registry governance, policies, operations, and compliance with the Registry Agreement. This separation preserves the applicant's independent accountability while allowing established community institutions to provide endorsement, expertise, and continuing community input.

Evidence of the relationship consists of the written endorsement of Sui Foundation and supporting letters from Mysten Labs, Cetus, Talus, DoubleUp, Miso Labs, GiveRep, and Inkray, each submitted as corresponding documentation to this response.

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 Sui community is an open, global, activity-based technology community organized around the Sui network. It is not governed by one membership association or individual leader. Its organization is distributed among an ecosystem-wide stewardship body, a body endorsed for the ICANN function, technical and operational contributors, and independent organizations serving particular activities.

Sui Foundation is the principal organizing body for the community as a whole and its central coordinating institution. Through grants and RFPs, research awards, builder resources, education, community programming, events, partnerships, developer relations, and project support, it administers programs across the constituencies identified in Q132. It does not own or control the decentralized Sui protocol.

For the limited DNS function, Sui Foundation endorsed the .sui community application and identifies Sui Naming Limited as the applicant and the community's ICANN operating partner, as described in Q135. Sui Naming represents the community for this application and, if delegated, will administer the .sui registry under its Registry Agreement and the commitments in Q151-Q153. It does not govern the Sui protocol or replace the community's other institutions.

Mysten Labs, formed by members of the original team that created Sui, is the original developer and a principal technical contributor. Its work spans protocol development, products, infrastructure, developer tooling, and ecosystem support. Protocol development is conducted in public repositories under a published contribution process and code of conduct, from which maintainers and contributors are identifiable. Co-founder and Chief Product Officer Adeniyi Abiodun documented Mysten Labs' support for the Foundation's endorsement. Mysten Labs contributes technical leadership but does not claim to represent or administer the community as a whole.

A separate operational layer is provided by the Mainnet validator set. 127 active validators, two labelled as Mysten validators, validate transactions, secure the network, and coordinate incident response. Admission to and removal from the active validator set are governed by published protocol rules, and validators exercise stake-weighted voting on network matters, with SUI holders participating through delegation. No single validator or validator association represents the wider community.

Independent ecosystem organizations organize activities and provide services for particular participant groups. Cetus serves DeFi and liquidity users; Talus develops on-chain AI infrastructure and co-hosts accelerator and incubation programs; DoubleUp serves gaming and DeFi users; Miso Labs serves music creators and collectors; GiveRep serves social and reputation participants; and Inkray serves creators and decentralized publishing communities. Their letters show active participation, service to meaningful community segments, and support for .sui and for Sui Naming as the applicant. They do not claim authority to speak for those segments and are therefore supporting contributors, not ecosystem-wide organizing bodies.

Within this structure, SuiNS provides on-chain identity functionality for a distinct participant segment. Its governance is administered through the SuiNS DAO operating through Sui Foundation Ltd. Its role is limited to that on-chain identity function rather than administration of the wider Sui community or the .sui registry. The resulting structure is functional rather than hierarchical: Sui Foundation provides ecosystem-wide stewardship; Sui Naming performs the endorsed DNS role; Mysten Labs and independent contributors advance the technology; validators operate the network; and ecosystem organizations administer their own programs and services. The institutional leaders identified in the evidence act for their respective institutions; none claims personal authority over the Sui community as a whole.

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 Sui 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 that connects them to the shared Sui protocol and ecosystem. Members do self-identify, but affiliation does not rest on self-identification alone: the underlying conduct is independently observable. That participation predates and exists independently of the .sui application.

People and organizations join through several established paths. They may develop with Move or contribute code, applications, or infrastructure; operate a validator or node under Sui’s published technical requirements; actively use Sui Mainnet through a wallet they control; register and control a SuiNS identifier; receive a Sui Foundation grant; use an app that uses Sui; or be admitted to and participate in a recognized builder, research, education, ambassador, validator, or other ecosystem program. Beyond these paths, members engage with one another through public technical repositories, developer forums, communication channels, hackathons, conferences, and regional activities.

The degree of formality depends on the path. Developer, node, wallet, and SuiNS participation is generally open and self-directed. Validator operation is governed by protocol and technical requirements, including published stake or voting-power thresholds for joining and remaining in the active validator set. Foundation grants and recognized programs apply published criteria, application and selection processes, and institutional records. Participation can therefore be evidenced through public Mainnet records of wallet control, deployed Move packages, validator operation, and SuiNS identifier control, and through the records of the institutions that administer grants and recognized programs.

Members do not receive a uniform package of membership rights; the benefits of membership follow the form of participation. They include access to open technical resources, documentation, and public channels; use of network and identity infrastructure; collaboration with other participants; and, where applicable, program-specific funding, mentorship, events, and other support.

The Community Registration Policy in Q151 does not create or define the Sui community. It draws on the subset of these participation paths that produce objective, confirmable records, and translates them into registration and renewal eligibility requirements. Registry eligibility is therefore formally verified even though participation in the community generally remains open to those who with to participate.

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

Where is the community located?

Global and primarily online. Members and activities span North America, Latin America, Europe, the Middle East, Africa, and Asia-Pacific. Sui events reached 17 cities in 2025; Basecamp drew attendees from 90+ countries.

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

238M Mainnet addresses ever transacted; 896K average daily active addresses (Q3 2025); 1,900 developers (June 2025 peak); 127 active validators; 262K SuiNS registrations (24.6K active); 13K+ 2025 event attendees in 17 cities.

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

Sui Foundation’s ecosystem-wide remit spans Q139, but no membership roll. Mysten Labs serves technical contributors; 127 validators self-administer Mainnet; SuiNS DAO administers 24.6K active registrations; endorsers serve their ecosystem segments

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, Sui Foundation—the principal ecosystem-wide organizing body identified in Q136—maintained continuous, publicly documented engagement across the full period. Mysten Labs, validators, and independent ecosystem organizations supplemented those efforts within their technical, operational, and functional roles. The evidence reflects established programs, not outreach created for this application.

OFFERING SUPPORT. Sui Foundation operated grants and RFPs, academic research awards, builder resources, accelerators, developer relations, and security initiatives. Selective-application Hacker Houses offered structured, in-person support during the period, including Sui-presented programs in Bangkok and Bangalore in November 2024. Program benefits included accommodation, technical instruction, collaborative build time, and demo opportunities, depending on the program. Sui Overflow 2025 received 599 project submissions from builders in 85 countries, selected winners across nine primary tracks, and made 10 university awards. The annual program continued with Sui Overflow 2026, offering prizes, seed funding, expert access, and additional resources for builders. Talus also co-hosted an accelerator with Sui and Cicada Capital and incubated a Sui gaming project, while independent applications supported participants through integrations, partnerships, and technical feedback.

SHARING INFORMATION. Sui Foundation and Mysten Labs regularly publish technical releases, developer documentation, ecosystem news, program criteria, event materials, educational resources, and security information through official websites, public repositories, forums, and community channels, including ecosystem recaps published during 2026. Contribution procedures and codes of conduct provide public paths for technical participation. Validators, wallets, SuiNS, and ecosystem applications maintain documentation, integration resources, support channels, and public communications for their respective participant groups.

RESPONDING TO SPECIFIC COMMUNITY NEEDS. Foundation RFPs identify defined technical or ecosystem gaps and invite funded solutions. Sui Overflow 2025 incorporated 195,029 on-chain votes—not unique voters—into project rankings across nine tracks. Following Cetus's request for a community-directed response to its May 2025 security incident, Sui Foundation facilitated a validator vote, conducted with Foundation stake excluded; validators representing 90.9% of stake approved the proposed response. These examples show documented mechanisms through which participants can identify needs, express preferences, and influence institutional action.

FOSTERING AND STRENGTHENING RELATIONSHIPS. Engagement spanned the full period, from regional Builder and Hacker Houses through late 2024 and Sui's introduction of Walrus to developers at ETHDenver in early 2025, to a global events program in 2025. More than 13,000 people attended Sui-hosted events across 17 worldwide stops that year. Sui Basecamp Dubai brought together more than 2,000 attendees from over 90 countries; SuiFest Singapore drew more than 4,000 builders and community members; and seven Sui Connect events reached thousands across Hong Kong, Buenos Aires, Bangkok, Ho Chi Minh City, Hanoi, Paris, and Istanbul. More than one quarter of 2025 event participants were returning attendees, up from just over one in ten in 2024. The Foundation reports that first-time attendees became contributors, new regional leaders emerged, and builders formed continuing collaborations.

Together, these recurring practices engage developer, validator, DeFi, gaming, AI, creator, research, institutional, regional, and user segments and demonstrate active, consistent community engagement independent of the .sui application.

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?

Sui Naming Limited's role in the community's engagement is specific and complementary. It is the entity endorsed by the community’s principal ecosystem-wide organizing body to carry the Internet-naming initiative into the ICANN system and, if approved, to operate .sui as a durable DNS resource for the ecosystem those efforts have built.

Within the activities described in Q141, Sui Naming's contribution has been consultative and preparatory. It engaged with Sui Foundation, Mysten Labs, and organizations serving major ecosystem segments to define the initiative, understand the community's naming and identity needs, and develop the community-based registration framework proposed in Q151-Q153. Sui Foundation’s written endorsement identifies Sui Naming as the applicant and ICANN operating partner following the review described in Q135. That engagement is evidenced by the written endorsement of Sui Foundation and the supporting letters of Mysten Labs, Cetus, Talus, DoubleUp, Miso Labs, GiveRep, and Inkray, submitted as corresponding documentation to this response; each records the organization's connection to Sui, recognizes the community benefit of .sui, supports Sui Naming as the applicant, and looks to it to complete the ICANN process.

The broader programs described in Q141 — grants and RFPs, hackathons and Hacker Houses, documentation and publications, governance facilitation, and global events — are conducted by Sui Foundation, Mysten Labs, validators, and independent ecosystem organizations, which continue that work in their established roles. Sui Naming was formed as a special-purpose entity for the ICANN application and registry function described in Q135, and its role complements rather than duplicates theirs.

Sui Naming's continuing contribution is prospective and distinct: translating the community-supported initiative into enforceable Community Registration Policies, qualified registry infrastructure, registrar distribution, DNS security and abuse controls, and continuing ICANN compliance. It remains independently accountable for the application and registry; no endorsing organization owns or controls it or acquires authority over registry decisions by providing support.

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

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

Yes. Members recognize both the Sui community as a whole and the distinct segments within it. Awareness is demonstrated through shared channels, recurring cross-segment activities, on-chain voting, regional and global events, and public records identifying developers, validators, applications, and ecosystem organizations. These records show participants interacting under a common Sui identity rather than operating as isolated audiences of unrelated projects.

Records of diverse participation provide direct evidence. Sui Overflow 2025 drew builders from 85 countries and received 599 submissions across nine primary tracks, including DeFi, AI, entertainment and culture, and infrastructure. Eligible Sui users could review shortlisted projects and vote across all nine tracks through a common portal, producing 195,029 on-chain votes—not unique voters—for the project rankings. The program brought builders, judges, sponsors, mentors, university teams, and users from different functional and geographic segments together around a shared ecosystem-wide activity.

Segments also interact directly in matters affecting the network. Following the May 2025 Cetus incident, a DeFi protocol’s request was put to the validator set through a transparent on-chain process. SUI holders and stakers could participate through stake delegation, validators voted on the proposed response, and validators representing 90.9% of stake approved it, with Sui Foundation’s stake excluded. Application users, token holders, stakers, and validators therefore engaged with the same issue through a publicly observable network process.

In-person events provide additional evidence. In 2025, more than 13,000 people attended Sui-hosted events across 17 global stops. Sui Basecamp Dubai brought together more than 2,000 attendees from over 90 countries; SuiFest Singapore drew more than 4,000 builders, partners, and community members; and Sui Connect events reached local communities in Hong Kong, Buenos Aires, Bangkok, Ho Chi Minh City, Hanoi, Paris, and Istanbul. More than one quarter of 2025 event participants were returning attendees, up from just over one in ten in 2024.

Sui Builder House: Singapore provides a detailed cross-segment example from September 2024. More than 600 people from different communities and industries gathered across three floors for presentations, partner demonstrations, activities, conversations, and networking. Participants encountered organizations including Aftermath, NHN, Shinami, Studio Mirai, SuiLend, Lucky Kat, and Tradeport alongside ecosystem-wide presentations and announcements.

Public network and institutional records reinforce this mutual visibility. Mainnet records identify validators and their delegated stake; public repositories identify contributors and maintainers; and deployed Move packages, ecosystem directories, and grant and program records identify applications, builders, and recipients. Shared documentation, forums, event channels, and application communities provide continuing means for participants to discover, communicate with, and collaborate across segments.

The eight endorsements accompanying this application provide further evidence of cross-segment recognition. Sui Foundation, Mysten Labs, Cetus, Talus, DoubleUp, Miso Labs, GiveRep, and Inkray - representing stewardship, protocol development, DeFi, on-chain AI, gaming, music and creators, social and reputation, and decentralized publishing-identify the same broader Sui community and their respective places within it.

No general community-awareness survey was conducted during the two-year period. This response therefore relies on documented activities involving diverse community groups, segments, and members. The Overflow and validator voting records are not presented as surveys; they provide independently verifiable records of cross-segment participation and awareness.

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 community’s principal institutions and organizations serving major functional segments are aware of the .sui initiative and of Sui Naming Limited as the applicant. Sui Foundation’s awareness dates to a decision taken in 2023 and is confirmed by its current written endorsement; awareness across additional community segments is demonstrated by seven contemporaneous supporting letters.

Sui Foundation, the community’s principal ecosystem-wide organizing body, evaluated the ICANN new gTLD opportunity and the role a Sui-aligned DNS namespace could play in the ecosystem’s long-term development. It reviewed the proposed application structure, the ICANN and domain-industry experience of the principals and advisers who would carry it forward, the intended use of Identity Digital as Registry Services Provider, and the proposed community-based registration framework. On that basis, the Foundation approved its endorsement on or about September 1, 2023, following internal review and discussion among Foundation leadership.

Sui Naming Limited is the dedicated entity through which that endorsed initiative is now being pursued. The Foundation’s June 2026 letter identifies Sui Naming as the applicant and ICANN operating partner, describes the registration framework and registry arrangements, formally endorses the application, and urges approval. It therefore documents both the initiative’s approximately three-year history preceding submission and the Foundation’s awareness of the entity now carrying it through the ICANN process.

Mysten Labs, the original developer and a principal technical contributor, separately identifies Sui Naming, supports the Foundation’s endorsement, describes .sui as the natural DNS representation of the Sui ecosystem, and urges approval. Signed letters from Cetus, Talus, DoubleUp, Miso Labs, GiveRep, and Inkray likewise identify Sui Naming by name, support its application, and describe the expected benefit to the participant groups they serve across DeFi and liquidity, on-chain AI, gaming, music and creators, social and reputation, and decentralized publishing. The seven supporting letters were signed between June 25 and July 23, 2026.

The awareness recorded in these letters is informed rather than nominal. Each addresses an application to establish .sui as an ICANN-administered community gTLD within the global DNS. Mysten Labs additionally addresses the proposed division between community support, technical ecosystem input, and ICANN registry operations. The Foundation letter further addresses the community-based registration policies and Identity Digital registry infrastructure.

Institutional and organizational evidence is appropriate for this community. As described in Q136 and Q137, the Sui community has no membership roll, admitting body, or general assembly whose notice or decision would reach or bind every participant. Sui Foundation provides ecosystem-wide stewardship, while Mysten Labs and the six participating ecosystem organizations demonstrate awareness from technical and functional segments. Each supporting organization speaks from its own participation in and service to the identified segment; none is presented as its exclusive representative.

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. External awareness is demonstrated by independent analyst coverage, financial research, public filings, infrastructure integrations, international industry events, and collaborations with universities and organizations outside Sui.

MEDIA AND PUBLIC INFORMATION. Independent analysts publish recurring coverage dedicated to Sui: Messari issues quarterly State of Sui reports, and Electric Capital tracks Sui as a distinct developer ecosystem within its industry-wide data. Grayscale launched the Grayscale Sui Trust in August 2024 and published materials identifying SUI and the Sui network. In May 2025, 21Shares published an "Investment Case for Sui" describing the network's architecture, applications, users, and ecosystem. Circle's September 2024 announcement of native USDC and Cross-Chain Transfer Protocol support described Sui as a general-purpose blockchain with a growing DeFi and gaming ecosystem and more than 85 applications. Public securities filings concerning SUI-linked products likewise describe the network, Foundation, validators, developers, and applications for investors and regulators. These materials are directed to audiences outside Sui's own channels.

DISCUSSION IN EXTERNAL FORA. Sui and its participants have been presented and discussed at broader industry gatherings, including ETHDenver in February 2025, Consensus Hong Kong in February 2025, and Korea Blockchain Week in September 2025. These settings brought Sui builders and institutions into contact with developers, investors, enterprises, media, and other technology communities. Sui's consensus protocols are also analyzed, benchmarked, and extended by researchers with no affiliation to the ecosystem in the independent distributed-systems literature.

PARTNERSHIPS AND COLLABORATIONS. Circle's deployment of native USDC and CCTP on Sui required technical integration by an external regulated financial-technology company. In May 2025, 21Shares announced a strategic partnership involving product collaboration, research reports, and other initiatives. In 2025, Sui Foundation partnered with Press Start Capital on a four-week BTCfi and payments fellowship combining investment, mentorship, and technical support for early-stage companies. These are operational collaborations, not merely references to Sui.

ESTABLISHED ORGANIZATION. As documented in Q145, Sui Mainnet launched publicly on May 3, 2023 with more than 100 validators. Before the window opened on April 30, 2026, the community already had an ecosystem-wide stewardship institution, a public validator set, open-source repositories, developer and grant programs, recurring global events, regional communities, and numerous independent applications.

CONTRIBUTIONS BEYOND THE COMMUNITY. Sui Foundation's academic research program funded researchers at universities including Yale, UC Berkeley, NYU, EPFL, Georgia Tech, and the National University of Singapore. Its June 2024 cohort included 19 teams working on zero-knowledge proofs, privacy, consensus, smart-contract security, AI-assisted auditing, formal verification, and blockchain benchmarking, supported by an additional $1 million funding commitment. The community also contributes to the field directly: the Mysticeti consensus protocol was co-authored by researchers at Mysten Labs, Cornell Tech, IC3, University College London, and IST Austria and published on arXiv, and the Bullshark protocol developed for Sui has been adopted by other networks including Aleo and Fleek. Sui maintains a public index of the peer-reviewed research underlying the network, and Sui Overflow 2025 recognized university projects from IIT Roorkee, City College of San Francisco, and the University of Lodz.

Together, these records show awareness well beyond token markets or Sui-controlled communications. Financial institutions, technology providers, universities, researchers, event participants and analysts identify Sui as an established network and recognize the community that constitutes it

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

Are the pursuits of the identified community enduring and sustainable?

Yes. The community’s pursuits are enduring because they concern the continuing development, operation, security, support, and use of a public network and the applications and infrastructure built upon it. They are recurring functions of an operating technology ecosystem, not a single event, product cycle, or social-media audience.

CONTINUING CORE ACTIVITY. Sui progressed from public Testnet activity to Mainnet operation on May 3, 2023 and has operated publicly since. Independent validators validate transactions and secure the network; SUI holders support operation through stake delegation; developers publish and maintain Move packages and applications; and users participate through wallets, DeFi, gaming, identity, creator, enterprise, and consumer services. Mysten Labs and independent open-source contributors continue to develop the protocol, tooling, and broader Sui Stack.

RECURRING AND SCHEDULED PROGRAMS. Sui Foundation maintains recurring grants, RFPs, research awards, builder resources, developer programs, security initiatives, and events. Sui Overflow has operated as an annual global hackathon across 2024, 2025, and 2026. The 2024 and 2025 editions together drew more than 5,000 registrants and 950 project submissions, and the 2026 edition continues the program with scheduled workshops, building periods, judging, and awards. Builder Houses, Hacker Houses, Sui Connect gatherings, Basecamp, and other events provide further recurring opportunities for education, collaboration, and project development.

DOCUMENTED CONTINUITY. The record shows activity across every year of Mainnet operation. The 2024 and 2025 Overflow editions produced successive cohorts of projects and university participants. The 2025 global events program reached more than 13,000 attendees across 17 stops, including more than 2,000 attendees from over 90 countries at Basecamp Dubai and more than 4,000 at SuiFest Singapore. More than one quarter of 2025 event participants were returning attendees, compared with just over one in ten in 2024, demonstrating repeat participation rather than isolated attendance.

RECORDS EMPHASIZING ENDURING PRESENCE. Sui Foundation’s 2025 events review describes local communities as central to Sui’s continued development and records first-time attendees becoming contributors, regional leaders emerging, and builders forming continuing collaborations. Its 2025 technical review documents continuing protocol improvements and the launch of additional infrastructure for storage, access control, and data. The Foundation’s endorsement submitted with this application likewise describes its mission in terms of the growth, development, and long-term stewardship of the Sui ecosystem.

SUSTAINABLE STRUCTURE. Responsibility is distributed among complementary participants. Sui Foundation provides ecosystem-wide stewardship and recurring programs; Mysten Labs and independent contributors develop technology; validators operate the network; holders delegate stake; and independent applications and infrastructure providers serve their users. Activity spans protocol development, validation, wallets, DeFi, gaming, AI, social systems, music, publishing, storage, research, education, and institutional uses. This diversity creates recurring reasons to build, operate, use, fund, and support Sui and reduces dependence on any one participant or market segment.

The proposed .sui registry is intended to serve this existing continuity, not create it. The community’s multi-year record of network operation, recurring programs, repeat participation, technical development, and institutional stewardship demonstrates that its pursuits are enduring and sustainable.

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

Does the string match the name of the identified community?

Yes. The identified community is commonly and consistently named “the Sui community.” “Sui” is the distinctive proper-name element of that name; “community” merely describes the body of participants organized around it. Because DNS labels are case-insensitive, the applied-for string “sui” is an exact match for “Sui” notwithstanding capitalization.

Sui Foundation, Mysten Labs, official technical documentation, validators, developers, applications, exchanges, financial institutions, and public sources consistently use “Sui” to identify the network, ecosystem, and community. Sui Foundation’s official materials expressly refer to “the Sui community,” and the Foundation owns trademarks that include the name “Sui” as used for the blockchain technology.

The documentary evidence accompanying this application is consistent. Sui Foundation describes .sui as the natural DNS representation of the Sui community and identifies the community by the Sui name. Mysten Labs likewise states that “SUI” is widely recognized as referring to the Sui blockchain, ecosystem, and community and recognizes .sui as the community’s natural DNS identifier. The supporting letters from Cetus, Talus, DoubleUp, Miso Labs, GiveRep, and Inkray use the same community name and string.

“SUI” is also the established symbol of the network’s native token, reinforcing public recognition of the term. The match, however, does not depend on the token symbol: it rests on “Sui” being the exact proper name of the network and the community organized around it.

Accordingly, the applied-for string does not merely abbreviate, translate, or allude to the identified community. It matches the community’s exact recognized name.

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 a contemporary Internet identifier, .sui would be associated with the Sui network and the global community organized around it.

“Sui” is the exact proper-name element of “the Sui community.” Sui Foundation, which owns trademarks in the Sui name as used for the blockchain technology, uses it throughout its official community, ecosystem, and technical materials. Mysten Labs, validators, developers, applications, exchanges, wallets, and market-data services use the same name. Independent institutions—including Circle, Grayscale, 21Shares, and regulated securities-market participants—likewise use “Sui Network” for the technology and “SUI” for its native asset in integrations, investment products, regulatory filings, research, and public reporting. This repeated third-party usage makes the association visible beyond the community’s own channels, particularly in Internet, technology, and financial contexts.

The community identified in Q132 is coextensive with that usage: it encompasses the network-wide community of developers, validators and node operators, qualifying users, and recognized ecosystem participants, rather than a narrow applicant-selected subgroup. The string therefore does not identify a wider Sui technology community than the community the applicant commits to serve.

The applicant acknowledges that “Sui” is not semantically exclusive in every language or context. It is the conventional English-language name of the historical Chinese Sui dynasty; “Sui” or “Shui” is used for an ethnic group and language in China; and Sui occurs as a surname and personal or commercial name, including Anna Sui. The Sui network’s name and water-themed identity were inspired by the Japanese water element. More precisely, the Japanese character 水 is ordinarily read mizu when used as the standalone word for water, while sui is an on-reading used in compounds and elemental contexts; the applied-for string should not be described simply as the Japanese word for water.

These are unrelated historical, ethnolinguistic, proper-name, and linguistic associations. None describes a broader geographic or thematic community of which the identified Sui technology community is merely a subset. Conversely, the identified community has a direct, current, and extensively documented Internet-technology association with the exact string.

Accordingly, although “Sui” is not unique in every possible context, a person encountering .sui as a TLD would most naturally understand it as the DNS namespace for the Sui network and community.

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

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 .sui TLD to persons or entities that demonstrate participation or affiliation with the Sui 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) Controls a Sui wallet address; (b) Operates an active Sui Mainnet validator, as registered on Sui Mainnet; (c) Has deployed one or more Move packages to Sui Mainnet, as verifiable on Sui Mainnet; (d) Holds one or more on-chain names registered through SuiNS, as verifiable on Sui Mainnet; (e) Has received a Sui Foundation grant within the 36 months preceding registration, as evidenced by documentation from Sui Foundation or its authorized representative; (f) Is a verified member of a Sui Foundation-recognized ecosystem program, as confirmed by reference to the Programs List described below; (g) Promotes the Sui ecosystem; (h) Can provide any other evidence of community participation (including for example use an app that uses Sui), upon request; or (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 Sui 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 Registry Operator’s efforts to create a safe and reputable namespace.

Registry Operator shall publish on its website, no later than delegation of the TLD, an eligibility policy identifying the records or other proof accepted for each criterion and the applicable verification procedures (the “Eligibility Policy”). Registry Operator shall review the Eligibility Policy at least annually and publish the review date, results, and any updates within thirty (30) days after each anniversary of the Effective Date. Updates shall be limited to verification procedures and accepted forms of evidence and shall not add, remove, or materially alter the eligibility categories stated above.

Registry Operator shall independently administer and enforce this policy and make all eligibility determinations under the published criteria. Evidence supplied by Sui Foundation or any other person or organization shall be evidentiary only and shall not confer authority to direct, approve, veto, or otherwise control an eligibility determination, the Eligibility Policy, or operation of the .sui TLD.

Registry Operator shall not create or renew a Registered Name unless eligibility has been verified under at least one criterion. Eligibility shall be a continuing requirement and shall be re-verified at each renewal.

These restrictions are not time-limited and shall apply throughout the term of the Registry Agreement.

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

Registry Operator shall not permit registration of a second-level domain name in the .sui 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 Sui 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:

1. Used for illegal activities; 2. Used for DNS abuse; 3. Used against the interests of the Sui ecosystem or Registry Operator; 4. Violate intellectual property rights; or 5. Used to attack .sui websites or the Sui network.

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.

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 .sui 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 period, as published on 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 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 Sui 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 .sui-specific eligibility framework based on participation or affiliation with the Sui 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 .sui-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 Sui ecosystem. The policy supplements those requirements without replacing or limiting them.

Q153 establishes an internal review procedure for determinations made under the .sui 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 .sui 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 .sui 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 .sui 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 Sui Mainnet and SuiNS are used solely to identify evidence of community participation; the policies do not require DNS resolution through Sui, create interoperability with on-chain identifiers, or establish an alternative naming root.

ADDITIONAL REGISTRY SERVICE CONSIDERATIONS. Sui Naming Limited is coordinating implementation with its selected Registry Service Provider, Identity Digital. The policies can be implemented through ordinary registration, reservation, verification, and launch workflows. Eligibility may be evaluated using public Sui 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 Identity Digital determines that a particular implementation would constitute an additional Registry Service, Sui Naming Limited 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?

Sui Naming Limited has written support from Sui Foundation, the principal organizing and stewardship body for the identified community; Mysten Labs, the original developer and a principal technical contributor; and organizations serving major DeFi, AI, gaming, music, social, creator, publishing, and user segments.

SUI FOUNDATION. The Foundation formally selected and endorses Sui Naming as the community’s applicant and ICANN operating partner. Its letter describes the Foundation’s ecosystem-wide role, its review and selection process, the reasons for choosing Sui Naming, the proposed community policies, and the community benefit of .sui. This is the primary institutional endorsement. Sui Naming remains independently responsible for the registry.

MYSTEN LABS. Mysten Labs supports the Foundation’s selection and recognizes .sui as the natural DNS representation of the ecosystem. Its letter explains that the proposed structure appropriately separates community support, technical input, and ICANN registry operations while serving developers, validators, enterprises, applications, and users.

CETUS. Cetus, a Sui decentralized exchange and concentrated-liquidity protocol, reports more than $101 billion in cumulative trading volume and 18.3 million cumulative trading addresses. It supports .sui for trusted identity and discoverability in Sui-based financial applications.

TALUS AND DOUBLEUP. Talus supports the application from its role serving of on-chain AI builders and participants, citing its live protocol, accelerator and incubation work, ecosystem integrations, and 5,555-item Talus community. DoubleUp supports it from the gaming and DeFi segment, citing more than 1,000 unique V2 players, $15 million in V2 volume, technical contributions, partnerships, and event sponsorship.

MISO LABS, GIVEREP, AND INKRAY. Miso Labs supports .sui for music creators, collectors, and digital-asset users after two years building on Sui. GiveRep supports it from the social-engagement and reputation segment; GiveRep was a first-place Sui Overflow 2025 winner. Inkray supports it for creators, publications, communities, and users of decentralized publishing powered by Walrus.

BREADTH OF SUPPORT. The Sui community has no single roster of human members. Support is therefore demonstrated through its principal stewardship institution, original technical contributor, and organizations serving complementary functional segments. Together, these endorsements demonstrate support across ecosystem-wide stewardship, protocol development, DeFi, AI, gaming, music and creators, social reputation, and decentralized publishing. The letters show that the organizations look to Sui Naming to obtain, launch, and maintain .sui for the community. They do not confer ownership, control, or registry decision-making authority.

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, Sui Naming Limited is not aware of any opposition to the applying entity, this application, or the applied-for .sui string. No person, organization, or Sui community entity has communicated opposition to Sui Naming Limited. Accordingly, there is no known opposition to assess or address.

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