3 ms·
So something like ENS [0] is not a use-case? Here's a product that is using it: [1][2] [0] https://ens.domains/ https://ens.domains/ [1] https://www.skiff.org
by rvz 5y ago
So something like ENS [0] is not a use-case? Here's a product that is using it: [1][2]
[0] https://ens.domains/ https://ens.domains/
[1] https://www.skiff.org/ https://www.skiff.org/
[2] https://www.skiff.org/updates/skiff-ens https://www.skiff.org/updates/skiff-ens
- gumby 5y agoI have never seen a defi example that didn’t ignore Coase.
- biztos 5y agoOff-topic a bit, but I actually registered a name on ENS recently and now I can’t stop thinking how weird it is that the registrations are time limited, considering “blockchain” and all that.
- DennisP 5y agoENS was purposely designed that way. A smart contract can implement whatever rules you like. It doesn't seem like a great idea to me for name registrations to be perpetual, but a name service on Ethereum could certainly work that way.
- biztos 5y agoYes, I assumed it was not done by mistake. The funny thing (to me anyway) is that a big part of the culture seems to be how absolute "ownership" is -- at least around NFTs -- and how this is decentralized, but with ENS it's a rental just like a .COM (but with something like 1000% processing fees) and it's more centralized than DNS. I wanted to try out the .ETH name and I'm fine with them doing whatever they want with the contract, I just find it amusing. Unstoppable seems a lot closer to the overall ethos: https://unstoppabledomains.com https://unstoppabledomains.com