Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update running node doc #802

Merged
merged 1 commit into from
Nov 27, 2024
Merged

update running node doc #802

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions docs/general/run-a-node/advanced-topics/node-configuration.md
View file
Open in desktop
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
View file
Open in desktop
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