Merge pull request #554 from o1-labs/barriebyron-fix-offchain

fix 2: off-chain storage clarity

Author: barriebyron

docs/zkapps/how-zkapps-work.mdx

@@ -151,13 +151,7 @@ If you anticipate your state to be larger, or if the state accumulates per user
 
 ### Off-chain state
 
-:::info
-
-Off-chain state is not yet supported.
-
-:::
-
-For larger data, you might want to consider storing the root of a [Merkle tree](/zkapps/snarkyjs/merkle-tree) or a similar data structure within your zkApp's on-chain storage that references self-hosted off-chain state stored elsewhere.
+For larger data, you might want to consider storing the root of a [Merkle tree](/zkapps/snarkyjs/merkle-tree) or a similar data structure within your zkApp's on-chain storage that references self-hosted off-chain state stored elsewhere. Mina doesn't offer an out-of-the-box solution for off-chain storage.
 
 When the zkApp runs in a user's web browser, it can insert state to an external storage, such as IPFS. When the transaction is sent to the Mina network, if it accepts this zkApp transaction then proof and state are known to be valid valid so the updates are allowed, then the zkApp transaction can update the root of the Merkle tree that is stored on chain.