Long espresso-dev-node startup time

[fabiooshiro]

          While testing this the espresso service takes a lot of time to be healthy.

The start wait is over after 1 minute, as expected, and espresso service is still trying to be up.
The espresso service is healthy after 2:40 minutes.
And still there are a LOT of errors in the console.
If all this is expected we can merge as is, especially because this is an optional service and experimental.
I don't think it's ready for non-alpha release though.

Originally posted by @tuler in #263 (review)

[fabiooshiro]

Following the documentation provided by @miltonjonat (https://docs.google.com/document/d/1sN4sytNhnstKQTWbzdNJAstAeno0bDvfQXlqcPBvBy8/edit?tab=t.0),
it’s possible to skip contract creation, making the startup about 2 minutes faster.

https://github.com/cartesi/rollups-espresso-reader/actions/runs/15063286157

https://github.com/Calindra/rollups-espresso-reader/actions/runs/15085467438

Also, the Espresso's logs only show warnings:
logs_38721431671.zip

[tuler]

Do you have an example of the mentioned file in hand?
To predeploy contracts to anvil beforehand we will need to create cannon packages with all the necessary contracts. And then load those to our CLI devnet.
To create a cannon package we will need the source code of the smart contracts and some instructions for deployment.

[miltonjonat]

Source code is available at https://github.com/EspressoSystems/espresso-network. To deploy on Cannon, we just need a cannonfile.toml, or do we need something else? I'm wondering if we could ask Espresso to do this or help with this

[fabiooshiro]

@tuler The files to build Espresso from the main branch are here:
https://github.com/Calindra/cartesi-docker-images
There’s also a ./dump folder (not ideal) to get the Anvil state.

[tuler]

First step to create a cannon package is to compile the smart contracts.

I forked the espresso repo to https://github.com/cartesi/espresso-network and created a cartesi branch starting from tag 20250428-dev-node-decaf-pos, which I believe is what we are using in our environment.

Then I tried to compile the contracts using forge build, but get this error:

Error: Encountered invalid solc version in contracts/src/LightClientV2.sol: No solc version exists that matches the version requirement: ^0.8.28

Their README says this about compiling the contracts:

In order to avoid constant warnings about checksum mismatches with [svm-rs](https://github.com/roynalnaruto/svm-rs) managed solc we set FOUNDRY_SRC to solc installed via flake.nix.

I don't have nix installed in my macOS. And I'd hate to install it, because it's very intrusive.
Either way, I tried to install it and got an error in the process. And stopped there.

[fabiooshiro]

I'll give this new version a try:
https://github.com/espressosystems/espresso-network/pkgs/container/espresso-sequencer%2Fespresso-dev-node/411530716?tag=20250508

[tuler]

EspressoSystems/espresso-network@main...cartesi:espresso-network:cartesi

I just changed the compiler version to 0.8.28, as described in the comment at foundry.toml

# Version should match the solc installed via flake, otherwise the contract
# artifacts may differ slightly.

Created a cannon package with the following contracts:

PlonkVerifier
PlonkVerifierV2
FeeContract
EspToken
StakeTable
LightClient
LightClientV2

I don't know if I need to deploy the upgradable proxies they use.
https://github.com/Calindra/cartesi-docker-images/blob/main/espresso-dev-node/espresso-skip.env

Does anyone have any idea?

[tuler]

This is the deployment log by the espresso-dev-node.
This is what we need to reproduce using cannon instead. Deployments and invokes.

INFO espresso_contract_deployer: deploying ESPRESSO_SEQUENCER_PLONK_VERIFIER_ADDRESS
INFO espresso_contract_deployer: deployed ESPRESSO_SEQUENCER_PLONK_VERIFIER_ADDRESS at 0x959922be3caee4b8cd9a407cc3ac1c251c2007b1
INFO espresso_contract_deployer: deployed LightClientMock at 0x9a9f2ccfde556a7e9ff0848998aa4a0cfd8863ae
INFO espresso_contract_deployer: deploying ESPRESSO_SEQUENCER_LIGHT_CLIENT_PROXY_ADDRESS
INFO espresso_contract_deployer: deployed ESPRESSO_SEQUENCER_LIGHT_CLIENT_PROXY_ADDRESS at 0x68b1d87f95878fe05b998f19b66f4baba5de1aed
INFO espresso_contract_deployer: deploying ESPRESSO_SEQUENCER_PLONK_VERIFIER_V2_ADDRESS
INFO espresso_contract_deployer: deployed ESPRESSO_SEQUENCER_PLONK_VERIFIER_V2_ADDRESS at 0x3aa5ebb10dc797cac828524e59a333d0a371443c
INFO espresso_contract_deployer: deployed LightClientV2Mock at 0xc6e7df5e7b4f2a278906862b61205850344d4e7d
INFO espresso_contract_deployer: LightClientProxy successfully upgrade to:  lcv2_addr=0xc6e7DF5E7b4f2A278906862b61205850344D4e7d
INFO espresso_contract_deployer: deploying ESPRESSO_SEQUENCER_FEE_CONTRACT_ADDRESS
INFO espresso_contract_deployer: deployed ESPRESSO_SEQUENCER_FEE_CONTRACT_ADDRESS at 0x4ed7c70f96b99c776995fb64377f0d4ab3b0e1c1
INFO espresso_contract_deployer: deploying ESPRESSO_SEQUENCER_FEE_CONTRACT_PROXY_ADDRESS
INFO espresso_contract_deployer: deployed ESPRESSO_SEQUENCER_FEE_CONTRACT_PROXY_ADDRESS at 0x322813fd9a801c5507c9de605d63cea4f2ce6c44
INFO espresso_contract_deployer: deploying ESPRESSO_SEQUENCER_ESP_TOKEN_ADDRESS
INFO espresso_contract_deployer: deployed ESPRESSO_SEQUENCER_ESP_TOKEN_ADDRESS at 0xa85233c63b9ee964add6f2cffe00fd84eb32338f
INFO espresso_contract_deployer: deploying ESPRESSO_SEQUENCER_ESP_TOKEN_PROXY_ADDRESS
INFO espresso_contract_deployer: deployed ESPRESSO_SEQUENCER_ESP_TOKEN_PROXY_ADDRESS at 0x4a679253410272dd5232b3ff7cf5dbb88f295319
INFO espresso_contract_deployer: deploying ESPRESSO_SEQUENCER_STAKE_TABLE_ADDRESS
INFO espresso_contract_deployer: deployed ESPRESSO_SEQUENCER_STAKE_TABLE_ADDRESS at 0x7a2088a1bfc9d81c55368ae168c2c02570cb814f
INFO espresso_contract_deployer: deploying ESPRESSO_SEQUENCER_STAKE_TABLE_PROXY_ADDRESS
INFO espresso_contract_deployer: deployed ESPRESSO_SEQUENCER_STAKE_TABLE_PROXY_ADDRESS at 0x09635f643e140090a9a8dcd712ed6285858cebef
INFO staking_cli::demo: staking to stake table contract for demo stake_table_address=0x09635F643e140090A9A8Dcd712eD6285858ceBef
INFO staking_cli::demo: ESP token address: 0x4A679253410272dd5232B3Ff7cF5dbB88f295319
INFO staking_cli::demo: token distributor account 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266 balance: 10000000000.000000000000000000 ESP
INFO staking_cli::demo: fund val 0 address: 0x6f6c6d0e7A6Bb0898333aadaeB4C87368041c9D6, 10000000000000000000 ETH
INFO staking_cli::demo: validator 0 address: 0x6f6c6d0e7A6Bb0898333aadaeB4C87368041c9D6, balance: 19999999999999547453
INFO staking_cli::demo: transfer 1000000000000000000000 ESP to 0x6f6c6d0e7A6Bb0898333aadaeB4C87368041c9D6
INFO staking_cli::demo: approve 1000000000000000000000 ESP for 0x09635F643e140090A9A8Dcd712eD6285858ceBef
INFO staking_cli::demo: deploy validator 0 with commission 1.00 %
INFO staking_cli::demo: delegate 100.000000000000000000 ESP for validator 0 from 0x6f6c6d0e7A6Bb0898333aadaeB4C87368041c9D6
INFO staking_cli::demo: fund val 1 address: 0xD208510A88Ed64FE278dC04d331901fD8aD99434, 10000000000000000000 ETH
INFO staking_cli::demo: validator 1 address: 0xD208510A88Ed64FE278dC04d331901fD8aD99434, balance: 19999999999999560481
INFO staking_cli::demo: transfer 1000000000000000000000 ESP to 0xD208510A88Ed64FE278dC04d331901fD8aD99434
INFO staking_cli::demo: approve 1000000000000000000000 ESP for 0x09635F643e140090A9A8Dcd712eD6285858ceBef
INFO staking_cli::demo: deploy validator 1 with commission 1.10 %
INFO staking_cli::demo: delegate 200.000000000000000000 ESP for validator 1 from 0xD208510A88Ed64FE278dC04d331901fD8aD99434
INFO staking_cli::demo: completed staking for demo
INFO espresso_contract_deployer::network_config: Initializing stake table from node for epoch None

[tuler]

This is the minimal and fastest way to build espresso-dev-node and run the deployment procedure, from the espresso-network repo.

RUST_LOG=info cargo run --bin espresso-dev-node --features="testing embedded-db" -- --l1-deployment dump --sequencer-api-port 24000