account updates "how the state on a zkApp account gets updated on chain.
When the prover function runs in a web browser, the smart contract outputs a proof and some associated data called ""account updates"" that are sent as part of the transaction when sending a transaction to a zkApp address. The account updates are a JSON plaintext description that describe how to update the state on a zkApp account.
The integrity of these account updates is ensured by passing a hash of the account updates as a public input to the smart contract. The account updates must be present and unmodified for the verification function to pass successfully when it runs on Mina. In this way, the Mina network can confirm the integrity of both the proof and the associated account updates that describe how to update the zkApp account’s state."
actions Actions & events are features of Mina Protocol. These docs related to how to use these features within SnarkyJS, but they are Mina zkApp features.
Some requested terms did not get addressed in the first PR #381 and are captured in this next iterative glossary improvement.
This issue adds terms to the backlog for next glossary iteration:
cold wallet
token ID https://docs.minaprotocol.com/zkapps/advanced-snarkyjs/custom-tokens#understanding-important-terms
actions Actions & events are features of Mina Protocol. These docs related to how to use these features within SnarkyJS, but they are Mina zkApp features.
events
reducer https://docs.minaprotocol.com/zkapps/advanced-snarkyjs/actions-and-reducer reducer's job is to process previous actions in a smart contract "
Provable code
zkCPU
From Steve Pack, a request to add:
From Maki a request to add anything that helps message our products so things like:
From Samuel