[Feature] Leo Devnode CLI command #29012

Roee-87 · 2025-11-26T10:43:27Z

Motivation

Devnode is a new tool that creates a local development network to enable developers to rapidly test and iterate through Aleo program design.

leo devnode has two commands: leo devnode start --private-key APrivateKey1zkp8CZNn3yeCseEtxuVPbDCwSyhGW6yZKUYKfgXmcpoGPWH which creates a local network at localhost:3030 and leo devnode advance which creates a block and adds it to the ledger. leo devnode advance takes an optional value n which advances the ledger by n blocks. Default value is 1.

Furthermore, this PR adds a --skip-execute-proof flag for leo execute commands along with a --skip-deploy-certificate for program deployment transactions.

JS SDK tests

Reviewers are welcome to use the JS SDK Devnode support methods in this script: https://github.com/ProvableHQ/sdk/tree/mainnet/create-leo-app/template-devnode-js

vicsn · 2025-11-27T10:51:49Z

Cargo.toml

-tag = "v4.4.0"
-features = [ "test_consensus_heights" ]
+rev = "7787e6e"
+features = ["dev_skip_checks", "test_consensus_heights", "test_targets"]


It seems to me that this will always disable checks in the devnode.

Can we enable dev_skip_checks only if the Leo build feature flag devnode_skip_checks is enabled, so developers can also use the devnode with checks enabled?

And maybe you can also write some comments giving context to future developers:
// We set test_consensus_heights to give developers freedom to set custom consensus version upgrade heights.
// We set test_targets because the devnode's genesis block was created with the same feature flag

vicsn · 2025-11-27T10:57:34Z

leo/cli/commands/devnode/rest/routes.rs

+                // Prepare the new block.
+                let new_block = rest
+                    .ledger
+                    .prepare_advance_to_next_beacon_block(&private_key, vec![], vec![], txs, &mut rand::thread_rng())


It's a bit funky that all transactions will be pushed into the first block. But I don't think we should necessarily change it. Maybe add a comment for clarity.

vicsn

LGTM besides a few nits!

…/leo-devnode-final

JoshuaBatty · 2026-01-13T01:21:41Z

leo/cli/commands/devnode/mod.rs

+}
+
+// A helper function to handle the Devnode command based on the subcommand provided.
+fn hanlde_devnode(devnode_command: LeoDevnode, context: Context) -> Result<<LeoDevnode as Command>::Output> {


Suggested change

fn hanlde_devnode(devnode_command: LeoDevnode, context: Context) -> Result<<LeoDevnode as Command>::Output> {

fn handle_devnode(devnode_command: LeoDevnode, context: Context) -> Result<<LeoDevnode as Command>::Output> {

fixed: 77c4102

JoshuaBatty · 2026-01-13T01:21:59Z

leo/cli/commands/devnode/mod.rs

+    }
+
+    fn apply(self, context: Context, _: Self::Input) -> Result<Self::Output> {
+        hanlde_devnode(self, context)


Suggested change

hanlde_devnode(self, context)

handle_devnode(self, context)

fixed: 77c4102

JoshuaBatty · 2026-01-13T01:25:34Z

Cargo.toml

 ]
 license = "GPL-3.0"
 edition = "2024"
-rust-version = "1.92.0"


are we able to keep using 1.92.0? Any reason we downgraded?

JoshuaBatty · 2026-01-13T01:26:15Z

Cargo.toml

 default-features = false

 [workspace.dependencies.rayon]
-version = "1.11.0"


Same here, are we able to keep using the newer version of rayon rather than downgrading?

JoshuaBatty · 2026-01-13T01:33:21Z

leo/cli/commands/devnode/rest/helpers/error.rs

+/// An enum of error handlers for the REST API server.
+#[derive(Debug)]
+pub enum RestError {
+    /// 400 Bad Request - Invalid input, malformed parameters, validation errors
+    BadRequest(AnyhowError),
+    /// 404 Not Found - Resource not found
+    NotFound(AnyhowError),


We could also consider using thiserror instead of raw anyhow for the RestError. Since this is a structured error type with distinct variants (rather than ad-hoc error propagation), thiserror might be a better fit:

#[derive(Debug, thiserror::Error)] pub enum RestError { #[error("Bad request: {0}")] BadRequest(#[source] AnyhowError), #[error("Not found: {0}")] NotFound(#[source] AnyhowError), #[error("Unprocessable entity: {0}")] UnprocessableEntity(#[source] AnyhowError), #[error("Too many requests: {0}")] TooManyRequests(#[source] AnyhowError), #[error("Internal server error: {0}")] InternalServerError(#[source] AnyhowError), }

This would give you Display and std::error::Error for free, while still keeping AnyhowError inside for error chain functionality. The constructor methods (lines 54-77) could then be removed as optional boilerplate.

Not a blocker, just a thought!

JoshuaBatty · 2026-01-13T01:39:53Z

leo/cli/commands/devnode/rest/routes.rs

+            {
+                return Err(RestError::too_many_requests(anyhow!("{err_msg}")));
+            }
+            println!("We've arrived at the transaction check section.");


Just checking if this was left from local debugging or if it's meant to be in the CLI output? I think it should be removed or converted to tracing::debug!.

JoshuaBatty · 2026-01-13T01:41:20Z

leo/cli/commands/devnode/rest/helpers/error.rs

+impl From<&str> for RestError {
+    fn from(msg: &str) -> Self {
+        // Default to 500 Internal Server Error
+        Self::InternalServerError(anyhow::anyhow!(msg.to_string()))


anyhow! accepts &str directly, so this can just be:

Suggested change

Self::InternalServerError(anyhow::anyhow!(msg.to_string()))

Self::InternalServerError(anyhow::anyhow!("{msg}"))

JoshuaBatty

Really excited for this feature. Spun it up locally and ran through the multisig example end-to-end. Iteration speed feels really good. Just left a few minor nits. Nice work!

updated branch from feat/leo-devnode

07c01e5

Roee-87 requested a review from d0cd November 26, 2025 10:43

Roee-87 self-assigned this Nov 26, 2025

Roee-87 added the feature A new feature. label Nov 26, 2025

ran cargo fmt

a247939

Roee-87 marked this pull request as ready for review November 26, 2025 10:51

Roee-87 added 3 commits November 26, 2025 03:12

made path to genesis block a const var with docblock

cbb870c

ran cargo fmt

2e10d2f

reverted path for genesis block to use include_bytes

d762314

vicsn mentioned this pull request Nov 26, 2025

[Feature] Leo Devnode #28982

Closed

changed snarkVM rev

47f7f9c

vicsn self-requested a review November 26, 2025 21:11

modified comment

31bb3d8

vicsn reviewed Nov 27, 2025

View reviewed changes

vicsn approved these changes Nov 27, 2025

View reviewed changes

Roee-87 added 3 commits November 27, 2025 21:05

listener_addr var passed to POST requests

6f6b170

changed var name listener_addr -> socket_addr

ad1e02c

Merge branch 'mainnet' of https://github.com/ProvableHQ/leo into feat…

ba9f5b5

…/leo-devnode-final

Roee-87 requested a review from mohammadfawaz December 1, 2025 05:16

Roee-87 added 6 commits December 4, 2025 08:26

pulled in main

f555d43

pulled latest main

b6a7547

fixed merge conflicts

92ec02c

pulled in latest main

03495fe

fixed build error

e0f14ba

ran cargo fmt

9a66033

Roee-87 requested review from JoshuaBatty and mitchmindtree January 12, 2026 06:29

JoshuaBatty reviewed Jan 13, 2026

View reviewed changes

fixed typo

77c4102

	fn hanlde_devnode(devnode_command: LeoDevnode, context: Context) -> Result<<LeoDevnode as Command>::Output> {
	fn handle_devnode(devnode_command: LeoDevnode, context: Context) -> Result<<LeoDevnode as Command>::Output> {

	Self::InternalServerError(anyhow::anyhow!(msg.to_string()))
	Self::InternalServerError(anyhow::anyhow!("{msg}"))

[Feature] Leo Devnode CLI command #29012

Are you sure you want to change the base?

[Feature] Leo Devnode CLI command #29012

Uh oh!

Conversation

Roee-87 commented Nov 26, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Motivation

JS SDK tests

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

vicsn left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

JoshuaBatty left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Roee-87 commented Nov 26, 2025 •

edited

Loading