Optimize espresso-dev-node startup #281
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR tries to speed up espresso-dev-node startup time by using a new option called
ESPRESSO_DEV_NODE_L1_DEPLOYMENT=skip
only currently available at themain
unreleased version ofespresso-dev-node
. It expects the smart contract to already be deployed to the L1 provider (anvil).For that to work we first created a cannon package for the espresso network smart contracts.
That is available at https://github.com/cartesi/espresso-network/tree/cartesi
So the first step to test this PR is to clone that repo, switch to branch
cartesi
and runcannon build
(assuming cannon is installed).Then we integrated the cannon package into our devnet, which can be built using
That assumes the cannon package
espresso-network:0.0.1@main
was built locally.ps: when a stable version exists, we can publish to cannon registry.
Then we changed the binary used by the SDK to a
main
unreleased version.Copy the unreleased devnet into SDK and build it.
Then run the CLI with a
devel
image: