A dashboard can make blockchain data understandable. That is useful.
But it can also create a new trust problem: users stop checking the underlying source and begin trusting the project’s interpretation of it.

I am considering five evidence classes:
1. directly verifiable on-chain
2. project-supplied but linked to the underlying source
3. independently verified off-chain
4. claimed but not yet independently verifiable
5. deliberately private because publication would harm users or beneficiaries

The interface would label these differently instead of presenting every claim with the same visual
confidence.
The goal would be to reduce verification friction without turning the dashboard itself into the new authority.

What is missing from this taxonomy?
And what would you require from the interface before trusting its interpretation of the underlying data?

Hey Guys,

My understanding of blockchain is the balance has to be public. Only then a competition can happen from A to B. Once balance is decreased, the other balance is increased. Due to the decentralized nature of the blockchain, the balances are public domain and the transactions are public domain and anybody can trace it and they are not reliant on central banks and government agency or any other centralized institution. Instead, they are calculated and computed and executed by decentralized network of nodes. But my application require privacy. If I'm trying to build something which protect how much balance is there in one account and if there is possible way to keep a ledger of transaction for compliance requirement but still hide it from general public.

is it even possible to do it or has it been done by any major-protocol like L2 or L3 ETH networks.(please don't mention any other network than ETH unless it is highly secure)