Which is what I'm saying, it's a centralized db. Whoever is using Hivemind is trusting the Hivemind node operator that the data is correct and identical to the layer 1 chain. Where's the fraud proof or validity proof to give me, an app user, that verification? What's stopping whoever is running the Hivemind node from manipulating data as they see fit before presenting to the user?
This is not layer 2. This is just a centralized db. My point is, layer 2 has a specific meaning in the blockchain space, and it is to do with a 2nd computational layer that has the same underlying security of layer 1. As with optimistic or zk Rollups on ethereum. Which is absolutely not the case here.
This has nothing to do with Hivemind in particular, but effects all Web3 DApps and even Wallet Apps on your desktop or smartphone. If you use etherscan.io for example, it accesses a centralized db and could theoretically return false or manipulated data. This risk is mitigated by decentralization. You can switch to other block explorers or Hivemind nodes and compare the results, or even run your own full node + Hivemind if you wish so.
My point here, which is literally in the title of the post, then mentioned in the post itself, then again mentioned in my last reply to you is.... Wait, I'll just quote from my last reply:
So, stop calling Hivemind layer 2. I notice you never called it layer 2, and props to you for that, but I'd like to see other people here understand that too. That's it, that's all I'm saying. Hive is a vastly ignored chain that's #140 and perpetually falling down the ranks, it's best to follow the semantic conventions of other chains like Ethereum which have thousands of times greater economic activity and usage, if you want to attract any of their developers and users at all.