> Rather than artificial set costs, the market will dictate this.
But you're coming into this conversation claiming that Handshake is going to democratize TLDs, that anyone will be able to buy one. We don't really know that the average cost of a TLD won't spike up to a thousand dollars, right? We don't know that every fortune 500 company in the world and every government in the world won't step in and snatch up every auction that gets posted. By design, there's no way for us to stop them from doing that.
There are very plausible scenarios here where ordinary people will not be able to buy TLDs under Handshake. Meanwhile, the worst case pricing scenario for the .com domain market, even with all of the centralization problems, is that it ends up costing $10-20 more per year over the 5-10 years.
I'm not saying that there aren't advantages to letting the market decide, and I'm not saying that the worst-case scenario will necessarily happen. It might be great. But I am saying that people learning about Handshake for the first time are looking at it as a drop-in replacement for .com, and it's decidedly not. I'm skeptical anyone has any idea what price or availability is going to be.
> or choose one owned by someone who doesn’t want to gouge people.
Without protocol-level migration tools between TLDs this is still centralization. I'm still stuck relying on a rented product owned by a private individual that I can move away from.
Remember, when .com and .org came out, they were also owned by an organization that didn't want to gouge people.
The decentralization benefits of Handshake are entirely encapsulated in ordinary people owning their own TLDs. We really shouldn't be talking about rented subdomains at all, rented subdomains are the problem that Handshake was advertised as solving.
> Unfortunately, all the details (like Bitcoin was at the beginning) are buried in technical papers and developer docs.
For what it's worth, Handshake isn't the only project of its type that struggles with this. It was similarly difficult to find out how projects like IPFS really worked.