Transparency protocol

I don't understand the purpose of using EVM off-chain or limiting solutions by underground programming languages when it finally ends up with publishing data in cheap storage and a possibility to validate proofs:
- Polygon's solution is limited by 100TPS
- zkSync and StarkWare can achieve 3k TPS but are limited by L1 block size
- even my favorite Avalanche Subnet reports about 4.5k TPS, but also is limited by the vertical scaling potential of validators' hardware

I propose using "Transparency protocol" to achieve the same but in a more flexible, efficient, and scalable way.
You just save for your web2.0 application a changelog with public data, share this data and periodically save Merkle tree to a blockchain. In this case, we are not flooding L1 with application data, we save just small hashes once a day.

In "Transparency protocol" applications share only significant, anonymized pieces of data. Anyone can make sure his data is valid and in place via "read" endpoints. Anyone can make sure that history is valid and unchanged via "prove" endpoints. The data should be chanked by meaningful periods and types, so validators can start from any checkpoint.

There are of course a few limitations.

The first one is hidden implementation, but let's be honest. Who checks smart contract's code before using it? Who follows updating implementation behind proxy contracts? We all care about data and reputation.

The second one is - missed operation. E.g. all parties agreed to do an exchange and want this transaction to be hidden. It's possible and since it doesn't affect other wallets it's not a problem.

One more problem is that tradable assets are not unified and isolated in a platform. However, there could be a platform that can manage your assets from many other applications supporting "Transparency protocol" and enabling inter-application trading.

transparency protocol.png