Except the examples you give demonstrate two widely divergent use cases - public and private. If you are managing an internal database, you don't need proof of

Except the examples you give demonstrate two widely divergent use cases - public and private. If you are managing an internal database, you don't need proof of work. You need concurrent conflict resolution. Every major database right now has such faculties built in and you don't need to spend megawatts of power to maintain it. In the public dns replacement use case there is promise and potential, but it has the laundry list of problems you would need to solve to make it happen. I look forward to the attempts, of course, because traditional dns is a brittle top down nightmare of exploitable corruption and manipulation. But still, blockchains as they are are only useful when you don't trust participants. And for along large-scale application, making that claim puts you in a political position - either you trust or distrust the governments oversight of whatever you are trying to reach consensus on. While a lot of people will, at inquiry, say they don't trust the government, very few people are willing to put the effort into forging an alternative public trust framework for things like property rights or certification that you mentioned.