As decentralized web is evolving I do suggest Kagi becoming Web3-native by supporting a variety of decentralized TLDs.
Based on the current trends I recommend Kagi to implement the following:
Benefits:
- Attraction to Web3 Users
- Crypto support for wallets and dApps (Smart contracts)
- Support for wallet lookups and associating social profiles
- Becoming anonymous and censorship-resistant against DNS centralization
- Support for decentralized content (IPFS, Airweave, Shadow Drive, Swarm, Skynet)
- Onion routing possible → Popup Dialog for opening links in Tor
Usage Data
Workflow
An ideal workflow would be a user searching with a decentralized keyword and a specified Web3 lense on Kagi.
Kagi would index the metadata, records and owners, and optionally crawl the content for inclusion into the search results.
Integration:
- Autocompletion of domain names
- Metadata, addresses, content IPFS hashes
- Displaying avatars and ENS / SNS profile cards
- Resolve and preview IPFS content
- Cross linking to .onion (Tor Browser)
- For NFTs optionally link domains to NFT metadata or appropriate trading platforms
Indexing Requirements:
- Domain names
- Owner address
- Resolved address (Root Zone info (NS, SOA, TXT, A/AAAA)
- contenthash (IPFS, Shadow Drive or Arweave and show a popup for crosslinking to open the site with the Tor Browser)
- avatar, social links (onion, avatar, location, contact info)
- subdomains
- Expiry Date. (avoiding stale records)
- Registration (helpful for sorting by recency or provenance)
Text Records
- url = Website or app url
- twitter = twitter handle
- discord = discord tag or invite link
- telegram = telegram handle
- bio = bio text
- avatar = profile image
- email
- shdw = Shadow Drive content id or link
- ipfs = content hash for IPFS
- arweave = content hash for Arweave
Gateways:
Resolvers:
- HNS Resolver
- ENS Resolver , Unstoppable Domains
- Bonfida SNS Resolver, Solana RPC API
- ENS and UD: Resolution Service API
Decentralized:
