Skip to content

Commit 196f72e

Browse files
committed
fixed more links
1 parent b8964dc commit 196f72e

File tree

5 files changed

+6
-6
lines changed

5 files changed

+6
-6
lines changed

archive/advanced/dive-into-avm/00_overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ It was formalised and implemented in the Aleo Network as [ARC-0002](https://gith
1818

1919
## **AVM’s Architecture and Design**
2020

21-
The AVM is virtual machine that operates on a last-in, first-out (LIFO) principle where data is stacked and the most recently added data is the first to be accessed or removed. This design is conducive to the execution of complex arithmetic circuits that are essential for the privacy-preserving features of Aleo. The AVM's architecture is designed to support the execution of private applications by leveraging zero-knowledge proofs. It uses Leo (high-level programming language), which compiles down into an intermediate representation known as AVM opcodes. These opcodes are then used to construct the R1CS, which are essential for generating zero-knowledge proofs. Check the full list [here](https://docs.leo-lang.org/aleo/opcodes/)
21+
The AVM is virtual machine that operates on a last-in, first-out (LIFO) principle where data is stacked and the most recently added data is the first to be accessed or removed. This design is conducive to the execution of complex arithmetic circuits that are essential for the privacy-preserving features of Aleo. The AVM's architecture is designed to support the execution of private applications by leveraging zero-knowledge proofs. It uses Leo (high-level programming language), which compiles down into an intermediate representation known as AVM opcodes. These opcodes are then used to construct the R1CS, which are essential for generating zero-knowledge proofs. Check the full list [here](https://developer.aleo.org/guides/aleo/opcodes)
2222

2323
The AVM architecture can be broken down into several key components and characteristics:
2424

archive/create-aleo-app/02_create_aleo_app_full.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -277,7 +277,7 @@ Congratulations on becoming a Leo contributor! 🎉
277277
278278
2. You also installed [Leo](https://docs.leo-lang.org/leo/), our statically-typed programming language built for writing private applications.
279279
280-
3. You executed `helloworld` using WASM, which called on in-browser resources to use [snarkVM](https://docs.leo-lang.org/aleo/), the data execution layer. It is used to compile Leo programs and execute them locally off-chain. All Leo programs eventually become Aleo instructions via Aleo’s compiler during the execution phase of snarkVM.
280+
3. You executed `helloworld` using WASM, which called on in-browser resources to use [snarkVM](https://github.com/ProvableHQ/snarkVM), the data execution layer. It is used to compile Leo programs and execute them locally off-chain. All Leo programs eventually become Aleo instructions via Aleo’s compiler during the execution phase of snarkVM.
281281
282282
4. You also executed `helloworld` locally in your terminal using `leo execute`, which similarly uses local computational resources to compile your Leo program using snarkVM.
283283

archive/src/learn/zkcloud/snarkos_build_guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -184,4 +184,4 @@ OPTIONS:
184184
2. Sign a message with your private key using `snarkos account sign --raw -m "Message" --private-key-file=<PRIVATE_KEY_FILE>`
185185
3. Verify your signature with `snarkos account verify --raw -m "Message" -s sign1SignatureHere -a aleo1YourAccountAddress`
186186

187-
Note, using the `--raw` flag with the command will sign plaintext messages as bytes rather than [Aleo](https://docs.leo-lang.org/aleo/language#data-types-and-values) values such as `1u8` or `100field`.
187+
Note, using the `--raw` flag with the command will sign plaintext messages as bytes rather than [Aleo](https://docs.leo-lang.org/language/data_types) values such as `1u8` or `100field`.

documentation/sdk/create-leo-app/01_create_leo_app.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -207,7 +207,7 @@ git push -u origin main
207207

208208
2. You also installed [Leo](https://docs.leo-lang.org/leo/), our statically-typed programming language built for writing private applications. Using Leo, you can write, build, compile, and execute Leo programs locally.
209209

210-
3. We provided the `helloworld` Leo program already pre-compiled into Aleo instructions and then executed it locally using WASM + web workers, which was an abstraction on snarkVM’s capabilities. [snarkVM](https://docs.leo-lang.org/aleo/) is the data execution layer. It is used to compile Leo programs and execute them locally off-chain. All Leo programs eventually become Aleo instructions via Aleo’s compiler during the execution phase of snarkVM.
210+
3. We provided the `helloworld` Leo program already pre-compiled into Aleo instructions and then executed it locally using WASM + web workers, which was an abstraction on snarkVM’s capabilities. [snarkVM](https://github.com/ProvableHQ/snarkVM) is the data execution layer. It is used to compile Leo programs and execute them locally off-chain. All Leo programs eventually become Aleo instructions via Aleo’s compiler during the execution phase of snarkVM.
211211

212212
4. Similarly, we deployed the `helloworld` program, again using the WASM + web workers abstraction layer but you can also deploy programs on-chain using [snarkOS](https://docs.leo-lang.org/testnet/getting_started/deploy_execute/#deploy), the data availability layer or blockchain / distributed ledger.
213213

documentation/sdk/typescript/00_sdk_overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -132,7 +132,7 @@ was run correctly. Keeping program inputs and outputs private allows developers
132132
Zero-Knowledge programs are written in one of two languages:
133133
1. [Leo](https://docs.leo-lang.org/language/overview): A high level, developer friendly language for developing
134134
zero knowledge programs.
135-
2. [Aleo Instructions](https://docs.leo-lang.org/aleo/): A low level language that provides developers fine
135+
2. [Aleo Instructions](https://developer.aleo.org/guides/aleo/aleo): A low level language that provides developers fine
136136
grained control over the execution flow of zero knowledge programs. Leo programs are compiled into Aleo Instructions
137137
under the hood.
138138

@@ -166,7 +166,7 @@ function hello:
166166
The SDK provides the ability to execute Aleo Instructions programs %100 client-side within the browser.
167167

168168
The `ProgramManager` object encapsulates the functionality for executing programs and making zero knowledge proofs about
169-
them. Under the hood it uses cryptographic code compiled from [snarkVM](https://docs.leo-lang.org/aleo) into WebAssembly.
169+
them. Under the hood it uses cryptographic code compiled from [snarkVM](https://github.com/ProvableHQ/snarkVM) into WebAssembly.
170170
JavaScript bindings to this WebAssembly code allows execution of programs in zero knowledge fully within the browser
171171
without requiring any external communication with the internet. Users interested in lower level details on how this is
172172
achieved can visit the [aleo-wasm](https://github.com/ProvableHQ/sdk/tree/testnet3/wasm) crate.

0 commit comments

Comments
 (0)