TON DNS TXT

TON DNS domains can store multiple on-chain records: wallet, tonsite, tonbag, next resolver, and text records.

DNSText records have no predefined schema. The key space is completely open, so any developer can define their own key convention, write records under it, and build an app that reads them back.

This is what makes it interesting. Your .ton domain stops being just a name pointing to a wallet. It becomes a small public data store attached to a human-readable identity that any application can extend for its own needs.

For example, any app could resolve DNSText records like avatar, bio, and channel to build a rich profile from a domain name alone.

The pattern is the same in each case: agree on a key name, let communities adopt it, and allow any app to resolve it. The .ton domain becomes the coordination point.

I noticed that dns.ton.org has no option to manage DNSText records so I built a Telegram Mini-App (@DNSTextBot) if you want to test it and add key-value pairs to your TON DNS.

I also published the source code on GitHub with example code for using DNSText

Mini-app: @DNStextBot
GitHub: https://github.com/TONresistor/TON-DNS-TXT