Add ENS Domain Support for IPFS Published Sites

[akhileshthite]

Enable Distributed Press to link IPFS-published websites with their Ethereum-based ENS domains. By integrating ENS support, users can seamlessly associate .eth domains with their IPFS-hosted content, enhancing accessibility and discoverability. This involves leveraging ENS records and enabling workflows for publishing updates that automatically sync IPFS content with ENS domains. Note that linking a domain with IPFS involves user-triggered crypto transactions (e.g., setting content hashes on ENS).

Learn more: https://docs.ipfs.tech/how-to/websites-on-ipfs/link-a-domain/#ethereum-naming-service-ens

[akhileshthite]

ENS DAO funding: https://docs.ens.domains/dao/proposals/4.7

Recent DAO thread here discussing the next iteration https://discuss.ens.domains/t/a-brain-dump-on-service-provider-program-season-2/19929

ENS weekly meetings:
Public goods: https://discuss.ens.domains/t/ens-public-goods-weekly-meeting-1pm-et-5pm-utc-thursday-term-5/18581/94

Ecosystem: https://discuss.ens.domains/t/ens-ecosystem-weekly-meeting-12pm-et-thursday-term-5/18533/95

[RangerMauve]

Would this mean us publishing to ENS on behalf of users? Not clear to me where ENS would fit in the stack since IIRC ENS owners can already set their DNS records to point to DP if they wish to do so.

[akhileshthite]

Would this mean us publishing to ENS on behalf of users? Not clear to me where ENS would fit in the stack since IIRC ENS owners can already set their DNS records to point to DP if they wish to do so.

We’re not planning to publish to ENS for users. Instead, we want to make it easier for users who already have an ENS domain to connect it to their IPFS website through Distributed Press.

Right now, if you have an ENS domain, you can manually set it up to point to your website on IPFS. Our idea is to help make that process easier by adding an option in DP where users can quickly link their website’s IPFS address to their ENS domain.

[akhileshthite]

Would this mean us publishing to ENS on behalf of users? Not clear to me where ENS would fit in the stack since IIRC ENS owners can already set their DNS records to point to DP if they wish to do so.

We’re not planning to publish to ENS for users. Instead, we want to make it easier for users who already have an ENS domain to connect it to their IPFS website through Distributed Press.

Right now, if you have an ENS domain, you can manually set it up to point to your website on IPFS. Our idea is to help make that process easier by adding an option in DP where users can quickly link their website’s IPFS address to their ENS domain.

This would still require the user to confirm the transaction through their wallet, like MetaMask.
cc @tripledoublev

[tripledoublev]

Some context.

ENS allows to set a contenthash record, linking an ethereum name to an IPFS hash.
From there we can access the website through a ENS gateway such as eth.limo

This means you can access decentralized frontends through this format:
yourENS.eth.limo

Fleek's product offering deals with IPNS so that the contenthash is updated and the user does not need to manually set the IPFS hash on every change.

There is only one blockchain transaction necessary through fleek's dev portal.

Some related docs.
eth.limo -> ENS gateway
fleek's IPFS + ENS dev guide