Custom chain config for post-beta-5 fuel-core run

General
1

Description

In the latest builds of fuel-core the --chain option has been removed. How can I start a chain with a custom config in the new versions?

I’ve scoured through the cli help, but cannot find an option.

Reproduction

Minimal version of the fuel-core run command
fuel-core run --db-type in-memory --debug --chain ./chainConfig.json

Fuelup show run

nightly-aarch64-apple-darwin (default)
  forc : 0.55.0+nightly.20240423.d092929664
    - forc-client
      - forc-deploy : 0.55.0+nightly.20240423.d092929664
      - forc-run : 0.55.0+nightly.20240423.d092929664
    - forc-crypto : not found
    - forc-doc : 0.55.0+nightly.20240423.d092929664
    - forc-explore : 0.28.1+nightly.20240423.4bb7392eed
    - forc-fmt : 0.55.0+nightly.20240423.d092929664
    - forc-lsp : 0.55.0+nightly.20240423.d092929664
    - forc-tx : not found
    - forc-wallet : 0.6.0+nightly.20240423.412dbda76b
  fuel-core : 0.23.0+nightly.20240311.4110889668
  fuel-core-keygen : not found
2

Hey @svimes

After a breaking change to fuel-core now the parameter should be --snapshot.

You can take a look at our test suite at sway repo for reference, the command we execute in our CI:

fuel-core run --db-type in-memory --debug --snapshot ./.github/workflows/local-testnode

And this is the contents of local-testnode folder:

We are working on a CLI wrapper on forc side for easily configuring a node instance so that this won’t be this verbose in the near future.

2 Likes
3

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.