Run a Tracing Node

You need to start your node with the following flag(s) depending on the features you would like to enable:

• --ethapi=debug - optional flag that enables debug_traceTransaction, debug_traceBlockByNumber, and debug_traceBlockByHash

• --ethapi=trace - optional flag that enables trace_filter

• --ethapi=txpool - optional flag that enables txpool_content, txpool_inspect, and txpool_status

• --wasm-runtime-overrides=/jaz/test-net-substitutes-tracing - required flag for tracing that specifies the path where the local WASM runtimes are stored. Accepts the network as a parameter: moonbeam, moonriver, or moonbase (for development nodes and Moonbase Alpha) --runtime-cache-size 64 - required flag that configures the number of different runtime versions preserved in the in-memory cache to 64

The complete command for running a tracing node is as follows:

Make sure you replace <50% RAM in MB> for 50% of the actual RAM your server has. For example, for 32 GB RAM, the value must be set to 16000. The minimum value is 2000, but it is below the recommended specs

curl https://s3.amazonaws.com/jaz.s3/bin/latest/jaz_runtime.wasm -o jaz_runtime.wasm
mkdir overriedes
mv jaz_runtime.wasm overrides

jaz \
--base-path=data \
--chain mainnet \
--name="Jaz-Tutorial" \
--pruning archive \
--state-cache-size 0 \
--db-cache <50% RAM in MB> \
--ethapi=debug,trace,txpool \
--wasm-runtime-overrides=runtime \
--runtime-cache-size 64 \
--execution wasm \
--pruning 1000 \
--name="Jaz-Tutorial"

If you want to run an RPC endpoint, to connect polkadot.js.org, or to run your own application, use the flags --unsafe-rpc-external and/or --unsafe-ws-external to run the full node with external access to the RPC ports. More details are available by running jaz --help.