You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/3_guides/2_integrating_aligned_into_your_application.md
+37-6Lines changed: 37 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -116,9 +116,8 @@ The proof submission and verification can be done either with the SDK or by usin
116
116
117
117
#### Using the SDK
118
118
119
-
To submit a proof using the SDK, you can use the `submit_and_wait_verification` function.
120
-
This function submits the proof to aligned and waits for it to be verified in Aligned.
121
-
Alternatively you can call `submit` if you dont want to wait for proof verification.
119
+
To submit a proof using the SDK, you can use the `submit` function, and then you can use the `verify_proof_onchain` function to check if the proof was correctly verified in Aligned.
120
+
122
121
The following code is an example of how to submit a proof using the SDK:
You can find an example of the proof submission and verification in the [ZKQuiz Program](../../examples/zkquiz/quiz/script/src/main.rs).
178
209
179
210
This example generates a proof, instantiates a wallet to submit the proof, and then submits the proof to Aligned for verification. It then waits for the proof to be verified in Aligned.
Copy file name to clipboardExpand all lines: docs/3_guides/3_validating_public_input.md
+6-12Lines changed: 6 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ This guide assumes you are in the `examples/validating-public-input` directory.
10
10
11
11
## Generate your ZK Proof
12
12
13
-
> [!IMPORTANT]
13
+
> [!IMPORTANT]
14
14
> To generate the proof ensure you have [docker](https://www.docker.com/get-started/) installed and the docker daemon running.
15
15
> This is necessary to ensure deterministic builds of the binary we want to generate a proof of. If not used, builds may differ depending on the system you are running on. To know more about this, check [this link](https://dev.risczero.com/terminology#deterministic-builds) from RiscZero docs.
0 commit comments