Skip to content

Commit e55d8dd

Browse files
committed
added summary table
1 parent 594def7 commit e55d8dd

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

documentation/guides/01_async.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -71,3 +71,9 @@ program second_mapping.aleo {
7171
## Managing public and private state in async transitions
7272

7373
Updating private state on Aleo utilizes off-chain proof generation to preserve the confidentiality of the user’s data and associated address. Therefore, Records cannot be created or consumed within the scope of `async functions`. However, Records can be used inside of the scope of `async transitions`. This is because transition and async transition functions are initially executed off-chain and are accompanied by proofs of correct execution which are subsequently verified by validators. Once the proof is verified, validators execute the code contained within a Future, which is solely defined by code within an `async function`.
74+
75+
| | **Public State** | **Private State** |
76+
|--------------------------|----------------------|------------------------------------|
77+
| **Function Type** | `async function` | `async transition` or `transition` |
78+
| **Data Storage** | `mapping` | `record` |
79+
| **Visibility** | everyone | Visible if you have the `viewkey` |

0 commit comments

Comments
 (0)