Our Way to Unlock the Power of ENS Text Records

ENS Text Records are uncharted waters, but they are data-rich and have tremendous potential for innovation. We believe that they can take Web3 profiling to the next level.

Currently, only about 3% of all ENS holders use Standard Text Records, and even fewer use Custom Text Records. The lack of a user-friendly infrastructure for managing and exploring these records, along with the high gas fees for using them, likely contributes to this low usage.

We’re building Tillies platform. It isn’t working properly right now, but we are planning to launch working beta in couple weeks.

The main goals we are trying to achieve:

  1. To standardize and categorize Text Records

    We are trying to make it easier and more seamless for Web3 users to create, manage, showcase, and most importantly, discover the Text Records.

    Firstly, our goal is to implement three types of Text Records that can be utilized: Text, Link, and List. In the List type, each element can have optional text and a link. We believe that this categorization is sufficient initially for individuals to showcase themselves and connect with like-minded people;

    Secondly, we have a plan to enhance the discoverability of ENS Text Records by fetching and organizing all of them. This approach will enable users to easily discover Text Records, including the most popular ones. Our objective is to establish standards and bring a systematic approach to the discovery of Text Records.

    Thirdly, we are developing a streamlined frontend on our platform to facilitate the creation and management of Text Records. This frontend will enable users to efficiently fill in their Text Records, not only within the ENS ecosystem but also across other Web3 ecosystems such as CyberConnect, Lens, and more.

    The main question here is what recording format should we use to write, and we want to recieve peoples thoughts on simple json format.

  2. Addressing the gas problem by creating Tillies Text Records (beta)

    Our platform offers the capability to create off-chain text records that will be stored on IPFS and linked to ENS Domains. This approach allows users to pay a one-time setup fee to associate their Tillies profile with their ENS domain. By leveraging this solution, users can enjoy the flexibility of making changes to their Text Records dynamically, while ensuring easy accessibility through the Tillies platform.

Our team’s ultimate goal is to unlock the full potential of Text Records by simplifying the process for individuals to showcase themselves, connect with like-minded people, and build meaningful relationships. We aim to facilitate the formation of interest-based DAOs/Clubs, enable users to curate Web3 content, and provide support for brands, communities, and other business-oriented entities to operate more effectively in the Web3 space.

Any feedback would be greatly appreciated! Feel free to contact me here or on telegram @misharik🙃


I think it’s a very interesting space to explore text records. Currently we rely on services like the graph to track non-standard text records, but discoverability of those text records is still limited. From your designs it looks like you’re focussed on the social aspect. I think text records have many more usecases outside of that.

E.g. uniswap using it for deployments https://twitter.com/ensdomains/status/1657095674587131904

Any app/product that decides to index, showcase and allow exploration of text records could explore a wider range of possibilities as the possibilities are quite endless.

Helping to define and set standards would be enormously helpful for ENS


This sounds great!!

I was only just speaking with some friends about how undervalued / overlooked text records are on our domains.

I am keen to take a look at it all and report back!

Congrats :handshake:

1 Like

Will this use CCIP-Read?

1 Like

Apologies for the delay in responding!

We understand that our focus should not be solely on the social aspect. We believe that all wallets, whether they belong to brands, communities, or regular web3 users, should have their profiles. Our aim is to create a user-friendly platform that serves as a playground that simplifies the exploration, creation, and management of text records.

We do not intend to invent new standards for text records. Instead, we aim to provide an intuitive and accessible interface that allows users to interact with these text records effortlessly. The standards will naturally emerge based on user interactions and needs.

Additionally, we believe that these text records should be accessible across different ecosystems and should also be easily transferable.

Thank you! We appreciate your support🙃 We will ensure to keep you updated on our progress

1 Like

Hi! Also apologies for the delay in responding.

Yes, we are considering CCIP-Read as a potential direction. Did you ask because you consider it the right choice?

Also, our CTO is facing personal issues and has decided to leave the project. Perhaps you could know someone who might be interested in joining this pet project?