Thanks for writing @UnknownENS
I love the possible business use cases the ENS protocol brings to the table. One really exciting feature being deployed is the new NameWrapper contract. I suspect we’ll see many builders creating platforms and projects based off of the new fuse permissions within the new NameWrapper contract.
One of the devs working on the NameWrapper gave a scenario that I thought was pretty interesting:
Allowing subname owners access to an airbnb, which expires automatically at the end of their stay, and only allows them access to 2/3 of the rooms that they paid for.
I know a lot of the community is super excited about the NameWrapper. I think once that’s rolled out, the use-cases created are going to be amazing!
If you haven’t done so already, joining the weekly ENS Ecosystem Working Group meeting is really helpful. Projects building on top of ENS often come to present and share what they are creating. The meeting time, agenda, and link gets posted here: 🌱 ENS Ecosystem - ENS DAO Governance Forum
I’m also bullish on Subdomains and possible use cases.
Also I appreciate the invitation.
Sadly, if I go to a Company or any Business with this information, they will tell me to come back when Subdomains are released to show them a demonstration.
You see, they receive big amount of salesman everyday and most of them tell wonders of the product or service they are selling. But these “Sharks” don’t fall for promises even if the Product comes from Ethereum.
You can use any Web programming language to build websites addressed in any top-level domain.
Personally, I recommend using HTML + CSS + TypeScript in some framework that can help accelerate development (we use React) but that is not the only option, and what’s best depends in part on what you/your team knows and what other technologies/components you might want to integrate.
You’ll need to figure out hosting separately from ENS, though help for decentralized hosting on IPFS is available through e.g. Valist and Spheron.