To use the eth.limo gateway, you need to have an ENS domain with a valid resolver and a supported contenthash record. Wildcard resolvers conforming to the ENSIP-10 standard are supported. Just append .limo to the end of any .eth or .gno domain to serve your dWebsite content.
The *.eth.limo, *.eth.link, and *.gno.limo gateways support off-chain resolution via CCIP. For more information, please consult the following resources:
By default all content is cached for 5 minutes. This means that if you update the contenthash of your ENS domain, it may take up to 5 minutes for those changes to become visible. We are actively working on a refactor of the caching layer which will eventually deprecate this limitation.
All subdomain certificates, i.e. non *.eth.limo are generated on demand, provided that there is a valid resolver and contenthash record set for the subdomain. Users no longer need to request certificates manually in our Discord server.
If you require custom HTTP response headers to support features such as SharedArrayBuffer please contact us in Discord. We are actively collaborating on an ENSIP specification that will allow ENS domain holders to specify server side headers in a TXT record, however this feature is still in heavy development for the time being.
Currently, we support IPFS, IPNS, Arweave, ARNS (Arweave Name System), and Swarm.
Last updated