Looking at all the comments here I have a single response to most of them: I'll call it a solution when it is implemented. You can talk all you want about solutions to some of the (minor) problems addressed here (ignoring the rest of the problems) but unless it is in use then the article's commentary still stands. Unless it has a ton of users, the article's commentary still stands. If you really do believe in block c…
Number mobility between Indian telecoms runs on private blockchain. AFAIK it is live and actively used. BC solves a problem there because operating a database for that scale would be very complicated. So every telco has their own copy that get synced via a consensus mechanism and signed transactions
Would it, though? Google tells me that India has a population of around 1.4 billion people. Let's assume each person has one phone number, and each phone number requires one kilobyte of number-mobility-related data. Then the database would need to store 1.4 terabytes of information.
1.4 terabytes doesn't seem like an impossible amount of data to store. That fits on a consumer hard drive! Dell will sell you a single server with that much memory! Request volume doesn't seem like a huge issue either, since porting a phone number is something people do extremely rarely.