github.com/number571/tendermint@v0.34.11-gost/docs/nodes/state-sync.md (about) 1 --- 2 order: 5 3 --- 4 5 # Configure State-Sync 6 7 State sync will continuously work in the background to supply nodes with chunked data when bootstrapping. 8 9 > NOTE: Before trying to use state sync, see if the application you are operating a node for supports it. 10 11 Under the state sync section in `config.toml` you will find multiple settings that need to be configured in order for your node to use state sync. 12 13 Lets breakdown the settings: 14 15 - `enable`: Enable is to inform the node that you will be using state sync to bootstrap your node. 16 - `rpc_servers`: RPC servers are needed because state sync utilizes the light client for verification. 17 - 2 servers are required, more is always helpful. 18 - `temp_dir`: Temporary directory is store the chunks in the machines local storage, If nothing is set it will create a directory in `/tmp` 19 20 The next information you will need to acquire it through publicly exposed RPC's or a block explorer which you trust. 21 22 - `trust_height`: Trusted height defines at which height your node should trust the chain. 23 - `trust_hash`: Trusted hash is the hash in the `BlockID` corresponding to the trusted height. 24 - `trust_period`: Trust period is the period in which headers can be verified. 25 > :warning: This value should be significantly smaller than the unbonding period. 26 27 If you are relying on publicly exposed RPC's to get the need information, you can use `curl`. 28 29 Example: 30 31 ```bash 32 curl -s https://233.123.0.140:26657/commit | jq "{height: .result.signed_header.header.height, hash: .result.signed_header.commit.block_id.hash}" 33 ``` 34 35 The response will be: 36 37 ```json 38 { 39 "height": "273", 40 "hash": "188F4F36CBCD2C91B57509BBF231C777E79B52EE3E0D90D06B1A25EB16E6E23D" 41 } 42 ```