Is your feature request related to a problem? Please describe.
I would like to load the ENS App via IPFS.
Describe the solution you'd like
When a new release of the ENS App is created, CI (or a human) should publish it to IPFS and include the IPFS CIDv1 to the release notes for the page.
Describe alternatives you've considered
I could rebuild and publish for every release myself, but I want someone else who cares more about ENS to do it.
Additional context
Currently, ens.eth points to an IPNS name which points to an IPFS hash, but this is only for ens.domains. The "Go To App" button on that page just sends the user to https://app.ens.domains and there doesn't appear to be any ENS name that points at the app itself.
It doesn't associate a particular IPFS hash with each version of the UI, so someone who wants to access an older archived version of the site (such as if a change introduces a breaking bug), they have no way to find the previous IPFS hashes.
Is your feature request related to a problem? Please describe. I would like to load the ENS App via IPFS.
Describe the solution you'd like When a new release of the ENS App is created, CI (or a human) should publish it to IPFS and include the IPFS CIDv1 to the release notes for the page.
Describe alternatives you've considered I could rebuild and publish for every release myself, but I want someone else who cares more about ENS to do it.
Additional context Currently,
ens.eth
points to an IPNS name which points to an IPFS hash, but this is only for ens.domains. The "Go To App" button on that page just sends the user tohttps://app.ens.domains
and there doesn't appear to be any ENS name that points at the app itself.