Points number 7, 8, and 9 in Vitalik's article are about your 1, if you cared to read it. The rest of your points are as you say "currency" and usability probl

Points number 7, 8, and 9 in Vitalik's article are about your 1, if you cared to read it. The rest of your points are as you say "currency" and usability problems, problems that a layer above will decide to solve or not. There is a lot of work being done on these points too, but Vitalik and the Ethereum 2.0 research teams are tackling a more low level set of issues. Think of it like Visa, SWIFT, or the internet: those are also technical platforms that need to be engineered and thought about, often in abstraction of other issues like monetary policy and local regulations. Many systems are built that way, where the underlying platform is kept "dumb", and requirements that need highly flexible enforcement (like the selective censorship/cancelation in your examples) are applied a level above, where humans are kept in the loop. There aren't any protocol-level rules in TCP/IP that says network packets containing information about the Tiananmen square protests can't go from US to China, those rules are implemented in Chinese routers. Maybe if you had your say in the design of TCP/IP things would've been different, but this approach has so far proven wildly successful.