It is easy to misunderstand the point of data availability in this protocol.
First, this protocol does not rely on off-chain decentralized storages. This is just an option.
I edited the document and added this.
Second, this is important that operators don’t need to write the commonly shared storage to calldata.
Let’s talk about the Uniswap V2 on this protocol spec, and let’s start with all LPs are online for the simplest case.
It’s essentially a transaction between a transactor and several LPs.
The secret smart contract execution of this Uniswap goes as below.
- The transactor send a transaction to the operator
- The operator send the diff of the commonly shared storage (like pooled amounts of ERC20 tokens and k-value) to the transactor and the LPs
- All of them make a zkp proof of the transitions of the Merkle roots of their user states caused by balance changes from that transaction. These can be receipts as well.
- The operator includes the proofs as the transactions in the next batch.
Then do you think it is dangerous that all nodes lose the commonly shared storage?
If it’s lost, the operators can not make a new transaction, then liveness will die. But anyone can exit her fund to L1 with the latest receipt. The service will end, but no fund will be compromised.
The commonly shared storage is needed for liveness, not safety.