Name Resolution
Domain Name Service for Resolving Chopin Apps
Overview
Web browsers rely on traditional DNS. This is inescapable in the modern web environment. However, there is room to build a name system that addresses the shortcomings of this centralized system.
Chopin Framework's name service should do the following:
- Resolves unique human readable names to Chopin App IDs.
- Enables Chopin clients to connect to the correct app without relying on traditional DNS.
- Works with a DNS gateway to allow users to access Chopin apps natively in their browser via traditional DNS.
- Be used across Chopin apps for usernames.
- Be tokenized as NFTs, so that DAOs can manage names of the apps they develop and deploy on decentralized infrastructure.
Furthermore, the name resolution should support non-Chopin native naming schemes including traditional DNS and, possibly, ENS, Handshake, etc.
Existing Name Systems
Prism seems like a great technical solution to build on top of. Right now they are focused on solving issues with E2EE key resolution, but this is fundamentally the same problems as DNS.
Celestials is the only production-ready name service built for the Celestia ecosystem. Whether or not Celestials ends up powering Chopin's native name service, it should certainly be integrated as a resolution option.