Skip to content

Commit

Permalink
update running node doc (#802)
Browse files Browse the repository at this point in the history
  • Loading branch information
Pana authored Nov 27, 2024
1 parent 09ec130 commit b2c5f2f
Show file tree
Hide file tree
Showing 2 changed files with 16 additions and 1 deletion.
15 changes: 15 additions & 0 deletions docs/general/run-a-node/advanced-topics/node-configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -100,6 +100,19 @@ Enabling the fullstate mode for dual spaces.
enable_single_mpt_storage=true
```

> The Conflux Foundation currently does not provide snapshot data containing the full historical state; users need to synchronize the data themselves.
### PivotHint

If you want to `fully synchronize the data`, you need to enable the pivot_hint related configuration option.

* `pivot_hint_path`: Path to the pivot hint file
* `pivot_hint_checksum`: Expected checksum of Page Digests section (hex string without "0x" prefix)

Note: These two configurations must either both be specified or both be omitted. Specifying only one will result in an error.

PivotHint file can be downloaded [here](https://github.com/Conflux-Chain/conflux-rust/pull/2935)

### cfx_getLogs/eth_getLogs related options

The `getLogs` RPC method imposes a significant performance overhead on the node. Excessive querying of data with this method can lead to high node loads. To mitigate this, adjust the following configuration option to limit the amount of data requested per `getLogs` request.
Expand Down Expand Up @@ -206,6 +219,7 @@ jsonrpc_ws_port=12535
public_rpc_apis='safe'
persist_block_number_index=true
persist_tx_index=true
max_estimation_gas_limit=30000000
```

### I want to run an eSpace RPC node, what parameters do I need to configure?
Expand All @@ -217,6 +231,7 @@ jsonrpc_ws_eth_port=8546
public_evm_rpc_apis = "evm"
persist_block_number_index=true
persist_tx_index=true
max_estimation_gas_limit=30000000
```

### After my node has been running for a while, I want to enable the `executive_trace` configuration. Do I need to resynchronize the data?
Expand Down
2 changes: 1 addition & 1 deletion docs/general/run-a-node/nodes-faqs.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ tags: [node]

### How long does it take to synchronize the data from beginning?

It takes about 3 weeks to synchronize the data from beginning. As blockchain data grows, the time required for syncing from scratch will increase.
It takes about two month to synchronize the data from beginning. As blockchain data grows, the time required for syncing from scratch will increase.

### How to synchronize data quickly to run an archive node?

Expand Down

0 comments on commit b2c5f2f

Please sign in to comment.