update reference

Author: Jiloc

docs/generated/configuration-reference.md

@@ -166,7 +166,7 @@ The configuration is automatically generated from the Rust source code documenta
 | [<span id="node-rpc_bind">rpc_bind</span>](#node-rpc_bind) | The IPv4 address and port (e.g., "0.0.0.0:20443") on which the node's HTTP RPC server<br>should bind and listen for incoming API requests. | `"0.0.0.0:20443"` |
 | [<span id="node-seed">seed</span>](#node-seed) | The node's Bitcoin wallet private key, provided as a hex string in the config file.<br>Used to initialize the node's keychain for signing operations.<br>If [[miner].mining_key](#miner-mining_key)  is not set, this seed may also be used for mining-related signing.<br><br>**Notes:**<br>- Required if [miner](#node-miner)  is `true` and [[miner].mining_key](#miner-mining_key)  is absent. | Randomly generated 32 bytes |
 | [<span id="node-stacker">stacker</span>](#node-stacker) | Setting this to `true` enables the node to replicate the miner and signer Stacker DBs<br>required for signing, and is required if the node is connected to a signer. | `false` |
-| [<span id="node-stacker_dbs">stacker_dbs</span>](#node-stacker_dbs) | A list of specific StackerDB contracts (identified by their qualified contract identifiers,<br>e.g., "SP000000000000000000002Q6VF78.pox-3") that this node should actively replicate.<br><br>**Notes:**<br>- Values are strings representing qualified contract identifiers.<br><br>**Example:**<br><pre><code>stacker_dbs = ["SP000000000000000000002Q6VF78.pox-3", "SP2C2YFP12AJZB4M4KUPSTMZQR0SNHNPH204SCQJM.stx-oracle-v1"]</code></pre> | - If [miner](#node-miner)  is `true` or [stacker](#node-stacker)  is `true`, relevant system contracts<br>  (like `.miners`, `.signers-*`) are automatically added in addition to any contracts<br>  specified in the configuration file.<br>- Otherwise, defaults to an empty list `[]` if not specified in the TOML. |
+| [<span id="node-stacker_dbs">stacker_dbs</span>](#node-stacker_dbs) | A list of specific StackerDB contracts (identified by their qualified contract identifiers,<br>e.g., "SP000000000000000000002Q6VF78.pox-3") that this node should actively replicate.<br><br>**Notes:**<br>- Values are strings representing qualified contract identifiers.<br><br>**Example:**<br><pre><code>stacker_dbs = [&#10;  "SP000000000000000000002Q6VF78.pox-3",&#10;  "SP2C2YFP12AJZB4M4KUPSTMZQR0SNHNPH204SCQJM.stx-oracle-v1"&#10;]</code></pre> | - If [miner](#node-miner)  is `true` or [stacker](#node-stacker)  is `true`, relevant system contracts<br>  (like `.miners`, `.signers-*`) are automatically added in addition to any contracts<br>  specified in the configuration file.<br>- Otherwise, defaults to an empty list `[]` if not specified in the TOML. |
 | [<span id="node-txindex">txindex</span>](#node-txindex) | Enables the transaction index, which maps transaction IDs to the blocks containing them.<br>Setting this to `true` allows the use of RPC endpoints that look up transactions by ID<br>(e.g., `/extended/v1/tx/{txid}`), but requires substantial additional disk space for the index database. | `false` |
 | [<span id="node-use_test_genesis_chainstate">use_test_genesis_chainstate</span>](#node-use_test_genesis_chainstate) | If set to `true`, the node initializes its state using an alternative test genesis block definition,<br>loading different initial balances, names, and lockups than the standard network genesis.<br>This is intended strictly for testing purposes and is disallowed on mainnet.<br><br>**Notes:**<br>- This is intended strictly for testing purposes and is disallowed on mainnet. | `None` (uses standard network genesis) |
 | [<span id="node-wait_time_for_blocks">wait_time_for_blocks</span>](#node-wait_time_for_blocks) | When operating as a miner, this specifies the maximum time (in milliseconds)<br>the node waits after detecting a new burnchain block to synchronize corresponding<br>Stacks block data from the network before resuming mining attempts.<br>If synchronization doesn't complete within this duration, mining resumes anyway<br>to prevent stalling. This setting is loaded by all nodes but primarily affects<br>miner behavior within the relayer thread.<br><br>**Units:** milliseconds | `30_000` (30 seconds) |