Linktree for web3

Use ENS records to store 'links and their descriptions' data and construct linktree-like profile

What is Linktree?

Linktree is a platform to aggregate all your important links in one place. It's been widely used in the web3 space by companies as well as individuals.

Why do we need its web3 version?

ENS has grown in popularity so much that users love to mention them on their social media profiles. It has become their on-chain identity yet it does not contain information that is vital to those users. They use Linktree to aggregate links which define their work and their personality. I propose a web3 native solution where anybody can access a Linktree-like profile by visiting <ens name>.eth.<some domain>. The data which would map domains-description-icon can be stored on-chain in the form of txt records. This will push the boundaries for creating an on-chain profile identified by ENS names.

What other products do users use with ENS?

.xyz has come up with a similar idea where you can open <name>.eth.xyz to see a basic profile for the ens names. But it only contains their assets holding and NFTs. The above solution would extend ens usability beyond just displaying assets and NFTs.

Can it replace Linktree?

Yes and indeed it can become bigger than that. Linktree names are not easy to remember but since ENS is more like an on-chain identity and less like a domain, as long as you know an ENS, you can access its profile by visiting <name>.ens.<domain>. Moreover, it is not restricted to one frontend but multiple frontends can be built around it since data is stored through ENS records. It will also require writing a data management contract to manage data more efficiently since ENS does not allow spaces and ASCII in txt records.

Revenue model?

Not required, since it will be launched as a public good. The major work will be writing smart contracts (as required) and SDKs so that it's easy to integrate them into other websites. A basic version (similar to linktree) will be delivered as a first version to demonstrate the use case.

Who is working on it?

At the present, it's just me, feel free to reach out if you want to support me in any way.