> If your name is like `microsoft.com`, then you call the registrar.

As I said, large companies like Microsoft don't risk their domains being stolen in the first place, since they use enterprise protection services like MarkMonitor.

> there's a formal process

Ultimately every time I discuss ENS, the conversation turns into a discussion about how feasible it is for a layperson to afford, file, and actually win a UDRP dispute to recover a stolen domain name, which doesn't have any provision for theft by the way. UDRP only considers whether the current owner of the domain is using the domain to infringe upon your business trademark (if you have one).

The answer is that UDRP is completely unworkable for the vast majority of people who are at risk of domain theft; it isn't even an anti-theft tool. In terms of theft resolution, it's a justice theater where you can watch it work for very specific types of companies who have very specific trademark issues that the UDRP covers, and imagine that it must work great for every mom and pop who has a domain name nicked because surely we live in a just world.

The individual filing the dispute is on the hook for the UDRP fees which are significant and I believe well into the four figures (completely unaffordable in developing countries, and likely not worth it for small businesses). Typically companies need to hire a specialized lawyer to navigate the UDRP system, at additional expense.

So you're misinformed that there is a formal process for domain theft - the UDRP is only for trademark infringement. UDRP is unnecessary for large companies (who have the resources to safeguard their name from theft) and it's useless to individuals and small companies who can't afford it and/or have theft problems but no trademark infringement problems. UDRP is only useful if you are a medium-sized company with a well-established trademark in a developed country and you didn't do your due diligence in properly securing your domain name.

So I'll give you that - if you're a medium-sized company with a well-established trademark in a developed country and you didn't do your due diligence in properly securing your domain name, then UDRP might be better than nothing. But depending on what kind of company you are, it still might be cheaper and easier to just switch domain names.

> Never mind that most registrars have protections against the transfer and will generally spam the hell out of you with notifications.

A blockchain can be designed to be more reliable because it doesn't "generally" do anything. It always, specifically, does exactly what it's programmed to do. A smart contract's predictability is a function of how well it's understood, and the tooling for creating and auditing bug-free smart contracts is maturing rapidly.

If you want to be spammed with notifications, there's nothing more reliable than multiple audited pieces of open source software that run directly on all your devices and monitor a public blockchain for an action. Add several third-party blockchain monitoring services for good measure.

And, of course, it's easy to write custody code in such a way that transfers are time-locked, so you have time to see the notification before the name changes owners. Write-once, audit-once, use-many.

> Have you actually ever done anything like that in real life?

Yes.

But aside from that, I use cryptographic keys in my life for countless reasons other than cryptocurrency. Git, SSH, E2E messaging apps, web passkeys, object storage, HTTPS server certificates, tapping my credit card at the supermarket, accessing the cell network, unlocking my car, etc. Everyone is already managing cryptographic keys whether they know it or not, and everyone's cell phone has keys already available and quite safe in its secure element, ready to sign messages with.

No need to break out the pocket protectors and meet up in someone's living room. A key signing ceremony for ENS could be easily piggybacked off a standard E2E group chat, like for example a Signal or iMessage chat:

* Someone creates a group chat on their smartphone and invites people (specifying the "M" value, aka the threshold for a valid group signature)

* The invited people join, their devices silently and automatically exchange keys, and the chat displays the group key

* Whoever has the asset transfers it to the group key

* Whenever someone proposes a message to sign, the system messages the group chat showing how many more signatures are needed, with a "sign" button that people can click.

This is pretty similar to what Safe Wallet already does, and it currently secures over $100 billion worth of cryptocurrency for some of the largest companies in the industry. But it's also quite simple to just download the app and use it as an end-user. It's directly compatible with ENS, since they both implement the ERC-721 token standard.

I've thought through all of this extensively, I know quite a lot of details about how both blockchains and the current DNS systems work, I've had numerous conversations with countless people about it, and it all adds up to me.