>> .com's cannot be MITM-proofed in a practical manner, unless they imported into a blockchain. > Trying to "import" domains from traditional TLDs into a block

>> .com's cannot be MITM-proofed in a practical manner, unless they imported into a blockchain. > Trying to "import" domains from traditional TLDs into a blockchain really isn't a good idea. This would require miners to somehow validate ownership at time of registration and on every update. I've seen no plausible proposal on how to do that without introducing significant risks of forking the blockchain. You could import a domain into a blockchain using DPoS, with some number of delegates agreeing on a published DNS record over a given period of time. An attacker's ability to disrupt the process is limited by their ability to disrupt the publication of DNS information more generally. > Making blockchain validation depend on external data is trouble. This gets closer to the real problem. You are basically using the blockchain to perform triangulation of cryptographic information which is ultimately controlled by a third party. Throwing that information on the blockchain doesn't make it magically impervious to MITM attacks.