Merge pull request MinaProtocol#30 from o1-labs/zkapps-proof-checking

Paragraph on proof checking ; fixes MinaProtocol#6

Author: bkase

MIPS/mip-zkapps.md

@@ -20,12 +20,12 @@ The zkApps protocol aims to add a smart contract layer to Mina which extends the
 
 
   **General programmability** - able to execute and settle arbitrary programs, not constrained to a particular VM model, but instead flexibly designed to support any number of execution models, VM-like or otherwise
-  
+
   **Programmable privacy** - the privacy of both inputs to smart contracts and their state can be programmed by their developers
-  
+
   **Constant in verification time** - individual transactions are executed, or more accurately “proven” asynchronously off-chain and verified on chain in constant time, independent of computational complexity
-  
-  
+
+
 This MIP represents the first iteration of such a protocol.
 
 ## Specification
@@ -430,6 +430,14 @@ the second pass does not change the result from the first pass.
 The first-pass processing is identical to what it was in the protocol
 before the changes proposed in this document.
 
+Proofs inside of account updates are checked when zkApp transactions are
+added to the transaction pool against some known potential future verification
+key (see the "Mitigation of Attack 2: Verification Key Superposition" section
+for more details). When a block is created, the proofs are not re-checked
+because they were already checked when added to the pool. When a block is
+received, all checks required to verify that the sender hasn't manipulated the
+payload are re-verified, but the proof is not explicitly checked in all cases.
+
 #### Transaction Application
 
 If the zkApp succeeds, the balance changes from all the account