This proposal seeks to establish a unified top-level domain (TLD) for SPACE ID community, built using the SPACE ID 3.0 toolkit.
The purpose is twofold: in the short term, it aims to provide new and diverse utilities for the SPACE ID community. In the long term, it envisions a multi-chain domain from the outset.
The proposal encompasses the launch of the .sid or .id TLD for SPACE ID community using the SPACE ID 3.0 toolkit. This will allow users to have a shared domain utility while benefiting from various functionalities of dApps on integrated SDKs and APIs provided by SPACE ID. Furthermore, this TLD can evolve into a multi-chain domain in the future.
- Develop and shape the structure of the .sid or .id TLD using the SPACE ID 3.0 toolkit.
- Integrate it into the SPACE ID Web3 Name SDK for collaboration with SPACE ID partners.
- Develop a registration process, confirming ownership rights of .sid or .id domains for users through a unique code.
The projected project timeline is approximately 2 months:
- Build and development: 1 month
- Testing: 2 weeks
- Preparation for official deployment: 2 weeks
The estimated budget for this proposal, covering development, testing, official deployment, and related support costs, is $30,000. This budget accounts for development resources, software licenses, and any ancillary costs associated with the endeavor.
- Successful launch of the .sid or .id TLD
- Increased revenue and popularity for SPACE ID within the Web3 community
- Enhanced user benefits through the use of SPACE ID domains
- Future expansion of this TLD into a multi-chain domain
Risks and Challenges:
While the benefits of launching this TLD are substantial, it’s essential to acknowledge the inherent complexities and subjectivity involved in introducing separate domain name for SPACE ID community. There’s a potential risk of reduced revenue from selling separate TLDs for each chain or Web3 community. However, this reduction is expected to be negligible, as users or fans of specific chains or communities would still be eager to register “their chains or communities” domain names.
In conclusion, I strongly believe that launching this dedicated TLD for SPACE ID community is crucial. This is especially timely given the impending official release of SPACE ID 3.0, the increasing number of chain-specific TLD launches on SPACE ID, and the growing integration of SDKs and APIs by chains partners. Furthermore, this also holds the promise of a multi-chain domain in the future, alongside avoiding the complexities of domain duplication across different chains.