4 ms·
There's a simple solution for that: to buy a domain on-chain that has an equivalent off-chain, the existing owner first needs to prove ownership of that equival
by detrites 4y ago
There's a simple solution for that: to buy a domain on-chain that has an equivalent off-chain, the existing owner first needs to prove ownership of that equivalent domain. After, it can be sold freely (as uniques could already).
The on-chain contract could be written such that a buyer generates a token, supplied to an on-chain verification oracle that checks token.owned-domain.TLD exists, and if it does grants issuance of the new on-chain version.
This essentially allows for a fair transition from the old system to the new system, while eliminating squatting.
- jeroenhd 4y agoWhat happens to these domains when the "legacy" domain expires and gets re-bought? Do you lose access when you stop paying? What if someone managed to hack your DNS, does it and its integration with TLS then break the supposed security guarantees? This system just seems to be traditional DNS with extra steps and a lack of manual recourse against bad actors, to be honest.
- deleted 4y ago[deleted]
- detrites 4y agoThe first question is irrelevant and affects nothing - the same owner proves ownership of both at the outset, if they choose to let the legacy version expire, well they chose that - so who cares what happens to it? I suppose it could be configurable at purchase to allow it to be a recurring verification, if that was desired, but it would seem to overcomplicate for no reason. "Subscribing" to domains each year is legacy inefficiency. I'm not sure what you mean about DNS, any chain-based system would be... chain-based, and therefore cryptographically-assured that a domain points where the owner chooses. "Not your keys, not your domain" applies.