I understand the potential nightmare scenarios that the author describes, because the author is worried about the sheer amount of "editing capabilities" of a co

I understand the potential nightmare scenarios that the author describes, because the author is worried about the sheer amount of "editing capabilities" of a company compared to a small community of OSM editors. But doesn't that automatically imply that the current way of verifying OSM data is flawed and needs a better architecture? Setting aside my personal opinions about feasibility... I think that this is actually a valid use case for a proof-of-map based system that removes the statistical power of a company with too many (maybe unintended) potentially malicious editors.