Default ENS IPFS Template

Hey ENS community, :raised_hand_with_fingers_splayed:

The Idea:

I’d like to propose adding an optional default dweb IPFS template to the ENS registration flow. This would give new users the choice to activate a simple, decentralized landing page immediately after registering their ENS name. They could keep it private or make it public.

The Situation:

When I registered my ENS name (jasonblais.eth), I was taken to my profile dashboard, which is great for editing records. But when I visited the domain itself, it displayed a blank page with plain text across the top that read, “Requested ENS name does not have a content hash set.” There was no visual identity, no onboarding guidance, and nothing that explained the potential of ENS as a decentralized web presence. Standard website add a landing page to park your domain before uploading a website. It would be honorable to users to see their ENS domain live right away. Personally, I was a little disappointed the first time checking my own ENS domain.

The Knowledge:

As someone with a little over 25 years in web design and code development, I believe new users would benefit from seeing a working example of a dweb landing page right away. It would demonstrate what ENS can represent beyond wallet routing and help bridge the gap for people crossing over from web2. This could also open up a completely new industry for Dweb development. This opens up new possibilities for ENS and Dweb development.

The Software

A lightweight static HTML template hosted on IPFS, using standard ENS resolvers and ethers-ens js. Once the template CID is published, users could toggle it on during registration. If they enable it, their ENS name would immediately resolve to a functional landing page displaying their ENS records in a clean, safe, readable format.One template to use for all ENS users. Once pinned through IPFS, there is no need to make individual templates.

The Backup

From a development perspective, this appears to be a small, self-contained feature, though ENS Labs would ultimately determine feasibility. I’m fully willing to contribute the files I’ve built, share my research, and help test or refine the integration if the community sees value in it. I will agree to transfer ownership of defaultens.eth for the cause so ENS can use and keep the original founding ENS domain that could represent the ENS default template system.

The Research

I’ve spent the past two years experimenting with ENS-powered dweb systems, and I believe this small improvement could help more developers discover what’s possible. Right now, very few ENS names use dweb templates, and many people don’t realize they can upload a simple static site to IPFS and point their ENS name to it. A default template could serve as both an onboarding tool and a showcase of ENS’s potential.

For anyone who wants to see an example, here are two working beta testing template I am using to test on:

defaultens.eth.limo

jasonblais.eth.limo


Thanks for taking the time to consider this idea. I’d love feedback from the community and the ENS team on how this might fit into the broader roadmap. I am interested in creating a group to teach and learn more about dweb possibilities as I do believe the future could be grown into the Dweb system for website building. I am a dweb developer in today’s standards and I would like to explore it with other interested individuals.

Although I do use AI for grammar checks and spelling on occasion, I do swear this is not AI generated and has been fully typed out by my hands personally (just in case the question comes up).

Thank you, Jason Blais

6 Likes

Default ENS Template update: From a landing page to a new way to build on ENS

Hey ENS community,

Last year, Our team proposed an optional IPFS landing page that people could activate when registering an ENS name. My reason was simple: when I first opened jasonblais.eth, I saw a message saying it had no content hash. I had registered a name, but I couldn’t immediately see or show someone what I could do with it. As a webmaster in prior years, I know plenty about websites and how they can be used. ENS domains offers one of the most unique ways to launch a website or landing page. Any developer or business owner would be very interested to see how a ENS domains can be used to power their business with more then just a website. ENS offers a full business solution under the hood, but it hasn’t been fully discovered until now.

A lot has changed since my original post. The DefaultENS Template is now being prepared for open source release in the next few weeks. It has grown from a basic landing page into an ENS profile and website with social features built in.

We don’t expect ENS labs or the DAO to completely understand or see the opportunity we see just yet. Website designing is far from crypto currency building and controlling. Why would ENS labs even build into something they never learned about

The template reads ENS records to display a user’s avatar, banner, links, and other profile details. It also includes the UBNet SDK, which lets people post, follow, and interact through a network built around ENS identities. UBNet builds on Spasm, developed by Degen Rocket. Messaging is also part of the experience we’re building. You can see an example of the ENS page at jasonblais.eth.limo.

What excites me most is that this gives an ENS name another practical use without taking away any of its existing uses. Your name can still resolve a wallet, hold records, and work with the apps you use today. Setting a content hash adds a website at that name. From there, the name can become a personal profile, a business homepage, a portfolio, a publishing space, or an entry point into a decentralized network.

Why I think the website opportunity is bigger than a template

The market for this is not limited to people already interested in ENS. Almost everyone who wants to be online needs a page or website at some point: individuals, artists, developers, clubs, local businesses, and larger companies. Website developers already help those people get online. If we make ENS and IPFS practical for that work, those developers can bring their clients with them. Businesses can build more around their domain name.

Imagine a web developer showing a business owner how to register a name, activate a live starter page, fill in their profile, and publish a custom site to IPFS. The business owner gets a usable online presence. The developer gets a new way to design, build, maintain, and improve that presence. The ENS name becomes more useful to both of them.

That could grow into a real industry around ENS: templates, site builders, static HTML publishing, IPFS hosting and pinning, design services, business integrations, and tools that make updates easier. It could also give developers a path to build social applications and operate network nodes around ENS identities. UBNet is one example of what becomes possible when an ENS website connects to a network instead of existing as an isolated page.

I’m not claiming this market will appear automatically or replace established website platforms overnight. We need to make the experience easy enough for ordinary users and useful enough for professional builders. But the potential audience is much larger than the current ENS community. Website developers know how to reach it because they already build for it every day. Imagine what the world would do with it if adaption was simple.

What we’ve learned from UBNet registration

At UBNet, we offer users a free ubnet.eth subname and cover the registration gas. Its content hash points to the Default ENS Template, so a new user can open their name and see a working page right away. They have a starting point they can explore and make their own. We also ask for funding to continue to pay the gas fees for new users to register a sub.domain. $1000 to fill the freegas.ubnet.eth wallet.

I believe ENS should offer that kind of first experience as an option when someone registers a name. A user could choose to activate a default content hash and leave registration with a live page. They could then edit their ENS records, customize the page, or replace the content hash with their own website whenever they want.

Dwebb.eth.limo offers users a fast content hash activation feature so users can immidetly add a website to their ENS domain name. Users can enter a ENS domain name, then add a HTML website using AI to IPFS generating a CID key that is saved to the users content hash. Immediately, the user can access their ENS eth url to view the website they activated. This is the future of website building at a fast speed and at a affordable cost. Making this easier to users will only benifit ENS and add more value to ENS in general.

Speed matters here. I believe we can make the path from ENS registration to a live, shareable website remarkably short. That is a claim we should test openly: measure the steps, time, and cost, then compare the result with other ways people get a website online.

My proposal began with a better welcome for new ENS users. It now points toward something larger: making ENS names useful as website addresses from the moment people register them, while opening the door for developers and businesses to build on that foundation. The template is nearly ready for open source release, and I want the community to help examine both the immediate registration idea and the wider opportunity it creates.

We are beginning to see many other IPFS builders entering the market like ensgiant.eth, web3audio.eth. These are only a few of the builders we have learned about.

hoodfi.eth.limo

roots.ubnet.eth.limo

advancedinstallations.ubnet.eth.limo

Video that shows how a user can land on the DefaulENS template automatically after registration

https://unblocked-profile.mypinata.cloud/ipfs/bafybeigjlt7psayobzq7dquj4fzuwjcptmov7wzmfbhmwu4xdubvfom2wi

We would appreciate any support ENS can give us.

Its unfortunate that Users won’t be given this opportunity as V2 was launched without a default template option but hopefully ENS can see the advantage of adding this moving forward. This is a full ENS profile system that can be used right now.

Thank you,
Unblocked Team

1 Like

This is something tens of millions of users need.

Users want ENS domains to be usable in real life.

1 Like