Create & manage OpenNIC TLD for IPFS website hosting

ipfs / in-web-browsers

Tracking the endeavor towards getting web browsers to natively support IPFS and content-addressing

https://docs.ipfs.tech/how-to/address-ipfs-on-web/

MIT License

349 stars 29 forks source link

Create & manage OpenNIC TLD for IPFS website hosting #199

Open matyapiro31 opened 2 years ago

matyapiro31 commented 2 years ago

Checklist

[X] My issue is specific & actionable.
[X] I am not suggesting a protocol enhancement.
[X] I have searched on the issue tracker for my issue.

Description

OpenNIC project requirements are here. I think the largest obstacle of hosting IPFS website is buying domain. OpenNIC domains are totally free and very easy to add new domain.

lidel commented 2 years ago

Kubo already supports using OpenNIC TLDs (opt-in via DNS.Resolvers configuration).

I understand you are suggesting setting up custom TLD at OpenNIC, and ensuring it a resolver for that TLD is enabled by default (like ENS).

@matyapiro31 any thoughts on how such integration could look like?

Namely:

How new domains are registered?
- How things like domain squatting are solved?
What are use cases?
- What is the value added when compared to ENS or ICANN?

matyapiro31 commented 2 years ago

I understand you are suggesting setting up custom TLD at OpenNIC, and ensuring it a resolver for that TLD is enabled by default (like ENS).

It's correct.

How OpenNIC project accepts new TLD is written here.

What we need the most is authoritative DNS server working for 24hs. Next is domain registering system.

Why creating new OpenNIC domain?

Because it's free and perfectly under our control, so adding new domain from ipfs commands automatically, no cost, no personal information is enabled by new TLD.