3 ms·
I have a question about blockchain DNS's. This might be the time to ask! There is a centralization aspect in any DNS, blockchain or otherwise in that, literall
by quickthrower2 5y ago
I have a question about blockchain DNS's. This might be the time to ask!
There is a centralization aspect in any DNS, blockchain or otherwise in that, literally to be useful, there needs to be consensus about which chain operators own which .{name} extensions for a given name. Which makes financial incentive for say an investor to 'bribe' browsers into using their DNS, which then charges money to end users, which er... feels a lot like the DNS we have.
I think that "true" decentralization might come from nameless "domain". If a domain is a SHA256 hash with no name, then with QR Codes and search engines and hyperlinks it doesn't matter as much that they are not memorable (we managed with nameless phone numbers, right!). Hash providers can be any chain, and then your job as a browser is to add as many mainstream chains as possible (there is no need to decide who is the 'official' one, or rank them, so Ethereum is no better than Dogecoin) as hash collisions are practically impossible.
- azophy_2 5y agowe already have "nameless" IP addresses, in which DNS is built on top of it as abstraction. using SHA256 is no better that using IPv6 IMO
- webmaven 5y agoThere is probably a decent case to be made for having an indirection layer above IP addresses, even if they are as meaningless and unmemorizable as a hash: for portability (IP addresses are tied to the host infra provider), load balancing, etc.
- quickthrower2 5y agoExcept you have your ownership in the blockchain allowing you to mutate the IP address. I don’t know if you can get a guaranteed for life IPv6. And who dishes them out. It is centralised.
- djrogers 5y agoA nameless phone number can be relayed verbally, and is easily memorized. Neither of those things is really true for a SHA256 hash.
- _Algernon_ 5y agoIf you are going to use an immemorable hash instead of a memorable name, why not use IP directly?
- tasuki 5y agoThere could be several immemorable hashes pointed at the same IP, the server needs to know which immemorable hash it should serve. (don't think this makes much sense, just answering your question...)
- quickthrower2 5y agoIPv6 may work for that. But the idea is to have a decentralised allocation so the hashes from your own generate PKs is better.
- ahtihn 5y agoBecause you don't necessarily own your IP, usually it's owned by your hosting provider.