Questions tagged [cli]
The cli tag has no usage guidance.
Why can't we pass the path to a database other than RocksDB (e.g. ParityDB) to the Substrate Service?
The Substrate Client has a: Substrate CLI here, where we're given the option to choose to use either RocksDB or ParityDB Substrate Service (sc-service) where here it states: "The RocksDB ...
Why can we limit the memory the RocksDB database cache can use but not for ParityDB?
In the Substrate CLI why can we limit the memory that the RocksDB database cache can use if we choose to use it here, but we're not given the option to limit the memory that ParityDB uses if we choose ...
create a dev chainspec with specific test users
I'd like to use the Polkadot CLI to create a chainspec with specific user balances pre-seeded. I'd like to be able to do this for any of the dev runtimes. In the case of the polkadot dev runtime, I ...
Custom Metadata Command Returnning Incorrect Data
I have written a command that exports the metadata at the CLI which /should/ duplicate the results of state_getMetadata. Full Source Code: https://github.com/LibertyDSNP/frequency/blob/main/node/cli/...
How is the logging CLI implemented in substrate?
Often I've used the flags like -lruntime=debug or -lparachain=debug without really understanding how they work. I know that the env_logger crate allows you to specify which crates to emit log messages ...
`check-blocks` command not re-executing the block
I am confused about the behavior of the check-block command. I was expecting it to re-execute the block, but it seems like this is not the case. For example, the following command: ➜ ~ RUST_LOG=...
Cannot run benchmarking: "Did not find the benchmarking metadata."
I have problems with trying to benchmark my custom pallet. I tried different scenarios and received different errors: Using the same binary: I built my node with cargo build --release --features ...
Do we have CLI support for ink! smart contract deployment on configured test-net?
I want to deploy my contract on Rococo contract test net. Apart from polkadot.js/apps, do we have any other way to upload and then instantiate the contract? My goal is to create a script for the ...
How to generate node information?
How can i generate this information while starting my chain???
RPC enabled? CLI configuration?
I need to determine whether RPCs are enabled in a OCW. I am thinking that I could check rpc_external and/or ws_external in sc_cli::commands::run_cmd but (1) is this the best way and (2) if it is, how ...
Calling an extrinsic using the polkadot-js-api CLI tool
How can I call an extrinsic on a palette using the polkadot-js-api CLI tool? I don't see much documentation on the tool nor does the --help provide much detail. Could I use this tool for this ...
What is the best way to find the genesis hash for a chain?
My understanding is the following terms which are used in different contexts and applications all refer to the same thing: "genesis hash", "network key", "chain id". I ...
How to see the hardware benchmark results?
Substrate has introduced a flag called --no-hardware-benchmarks to disable automatic hardware benchmarks. This implies if the flag is not set, the benchmark should run automatically at startup and ...
Calling CLI subcommand through different terminal after running the node
I'm trying to set some off-chain storage through a different terminal using a custom subcommand after starting up the node. Question here is: Is there any way to call the custom CLI subcommand in the ...
What does the `--dev` flag do?
I get a different set of behaviors when running my node with --dev than when I run my node with my own custom setup. What is happening in the background?
What is the internal logic of `--force-authoring` flag?
From where do I get the internal logic of --force-authoring flag? Here is my scenario: I've added a custom chain-spec that is similar to the default one where we are setting the environment for --dev ...
What does the `--tmp` flag do when running the Substrate Node Template?
The Substrate Node Template says in the "Run" section of the README, that the single-node development chain will start with "non-persistent state" if run with the following command:...