# Configuration for the Script Blockchain Node

The script blockchain node can be launched with parameter --config=path/to/config/folder as shown in the command below.

script start --config=../scriptnet/node

If the --config parameter is not specified, the script node uses \~/.script as the default config folder. The script node also uses the config directory to store other important data. For example, it stores its encrypted key under the key folder, and the blockchain data under the db folder.

The configuration for the script node is defined by file config.yaml under path/to/config/folder. Below are the options

storage:

 statePruningEnabled: true # true by default, when set to true the node will perform state pruning which can effectively reduce the disk space consumption

 statePruningInterval: 16 # the purning interval (in terms of blocks) which control the frequency the pruning procedure is activated

 statePruningRetainedBlocks: 2048 # the number of blocks prior to the latest finalized block whose corresponding state tree need to be retained

p2p:

 address: 127.0.0.1 # the binding address of the RPC service, 0.0.0.0 by default

 port: 50001 # the p2p port that the Script node listens on, 50001 by default

 seeds: 3.20.109.241:21000,18.223.165.134:21000,35.184.232.41:21000 # the IP addresses of the seed nodes

rpc:

 enabled: true # false by default, when set to true the RPC API is enabled

 port: 16888 # the PRC API port, 16888 by default

 maxConnections: 100 # max number of simultaneous RPC connections, 200 by default

log:

 levels: "\*:info" # level of logs to be printed, "\*:debug" by default


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://documentation.script.tv/api-references/scriptcli-apis/tx-apis/configuration-for-the-script-blockchain-node.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.