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: documentation/cli/05_debug.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,4 +12,4 @@ sidebar_label: Debug
12
12
`leo debug` has been removed in Leo 4.0. The interactive interpreter is no longer available.
13
13
:::
14
14
15
-
For testing and debugging your Leo programs, use [`leo test`](13_test.md), which runs your test suite against the real VM. For integration testing against a live network or a local devnet, use the [SDK](https://github.com/ProvableHQ/sdk) directly.
15
+
For testing and debugging your Leo programs, use [`leo test`](14_test.md), which runs your test suite against the real VM. For integration testing against a live network or a local devnet, use the [SDK](https://github.com/ProvableHQ/sdk) directly.
Leo devnode is a lightweight-node network that bypasses the consensus algorithm and the requirement to generate proofs for deployment and execution transactions. It is a development tool intended for rapidly iterating on Aleo program design and running end-to-end tests prior to deploying Aleo programs to testnet and mainnet.
14
14
15
+
:::note
16
+
`leo devnode` is the recommended local development tool for lightweight testing. The older [`leo devnet`](./07_devnet.md) command (which requires a full snarkOS installation and spins up a multi-validator network) remains available for more complex testing scenarios.
17
+
:::
18
+
15
19
To initialize devnode, run the following command:
16
20
17
21
```bash
@@ -26,7 +30,7 @@ The default endpoint for a local devnode is `http://localhost:3030`.
26
30
27
31
<!-- markdown-link-check-enable -->
28
32
29
-
Press `Ctrl+C` to stop the devnode. If started with persistent storage (`-l`), the ledger state is saved and can be resumed by running `leo devnode start -l`again. If started without persistent storage, the ledger is discarded when the devnode exits.
33
+
Press `Ctrl+C` to stop the devnode. If started with `--ledger-path`, the ledger state is saved and can be resumed by running the same command again. If started without `--ledger-path`, the ledger is discarded when the devnode exits.
30
34
31
35
## `leo devnode start`
32
36
@@ -36,32 +40,32 @@ leo devnode start [OPTIONS]
36
40
37
41
| Flag | Short | Default | Description |
38
42
|------|-------|---------|-------------|
39
-
|`--private-key`|`-p`|| Private key (required, or set via environment variable) |
43
+
|`--private-key`||| Private key (required, or set via`PRIVATE_KEY` environment variable) |
Copy file name to clipboardExpand all lines: documentation/cli/13_run.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ toc_max_heading_level: 2
10
10
11
11
# `leo run`
12
12
13
-
You can run an entry function by using the `leo run` command. This will simply run the specified entry function with the provided inputs and show what the produced output will be. It will NOT generate the zero-knowledge proof of execution or the transaction, and nothing will be run onchain. For that, please see the [`leo execute`](08_execute.md) command.
13
+
You can run an entry function by using the `leo run` command. This will simply run the specified entry function with the provided inputs and show what the produced output will be. It will NOT generate the zero-knowledge proof of execution or the transaction, and nothing will be run onchain. For that, please see the [`leo execute`](09_execute.md) command.
14
14
15
15
To run a Leo entry function with inputs from the command line, run the following command:
0 commit comments