The problem link3 solves

1. Centralized CDNs: Most websites and DNS registries today are hosted by centralized organizations that face the risk of a single point of failure.

2. Privacy: Since the website code is self-hosted and executed in a decentralized manner, we do not track your visitor’s behavior on the website.

3. Censorship: You are in complete control of the content you showcase. You can choose to hide certain wallet information or include additional details.

P.S. We never log your IP address or HTTP headers, which means all the request data is completely anonymized.

Web3 is all about status signaling and owning one’s social graph. (1) Creators are constantly looking for ways to showcase their collections across various platforms and own their distribution. And (2) Collectors are on the lookout for avenues to display their credentials, digital collectibles, proof of work, proof of attendance, etc. In a world where the most valuable social real estate is one’s ‘Link in Bio’ ($7.2Bn market globally), there’s yet to be a web3 equivalent.

Challenges we ran into

We decided to use IPFS to store user web pages. To upload the webpage to users’ ENS content, we need to set the content hash every time there is a change in the webpage. If we change the ENS content hash every time the user updates their page, the user would have to pay gas with every change.

To work around this we thought to use IPNS which uses a key pair for naming similar to an Ethereum address and maps it to an underlying IPFS hash. We quickly realized that there’s a reason no service (Infura, Moralis, etc) that gives IPFS support, supports IPNS. Cluster APIs as well as libraries are old and are really hard to use with IPNS.