Module sc_service::config
source · Expand description
Service configuration.
Structs
- The base path that is used for everything that needs to be written on disk to run a node.
- Service configuration.
- Execution strategies settings.
- A single request received by a peer on a request-response protocol.
- Representation of a Multiaddr.
- Address of a node, including its identity.
- Network service configuration.
- Extension to
SetConfigfor sets that aren’t the default set. - Configuration of the database of the client.
- Response for an incoming request to be send by a request protocol handler.
- Configuration of the Prometheus endpoint.
- Protocol name prefix, transmitted on the wire for legacy protocol names. I.e.,
dotin/dot/sync/2. Should be unique for each chain. Always UTF-8. Deprecated in favour of genesis hash & fork ID based protocol names. - Configuration for a single request-response protocol.
- Configuration for a set of nodes.
- List of telemetry servers we want to talk to. Contains the URL of the server, and the maximum verbosity level.
- Pool configuration options.
Enums
- Block pruning settings.
- Where to find the database..
- Strategy for executing a call into the runtime.
- Configuration of the client keystore.
- The configuration of a node’s secret key, describing the type of key and how it is obtained. A node’s identity keypair is the result of the evaluation of the node key configuration.
- Pruning mode.
- Role of the local node.
- Available RPC methods.
- Type for tasks spawned by the executor.
- Configuration for the transport layer.
- Specification of different methods of executing the runtime Wasm code.
- The instantiation strategy to use for the WASM executor.