MinwooJ

@wojake Then what can I do for my rippled node..?

I am using `--reconstruct-historic-states` options now..but the state is not found.

``` { "schema_version": 28, "config": { "block_cache_size": 0, "state_cache_size": 128, "state_cache_headroom": 1, "compression_level": 1, "historic_state_cache_size": 1, "cold_hdiff_buffer_cache_size": 16, "hot_hdiff_buffer_cache_size": 1, "compact_on_init": false, "compact_on_prune": true, "prune_payloads": true, "backend": "LevelDb", "hierarchy_config": {...

Based on the document you shared, I understand that archiving occurs for slots after the state-upper-limit (a multiple of 2**21). Currently, it is set to 14,680,064 (2**21 * 7), but...

Thank you for your response. I have one more question. After re-syncing Lighthouse, does archiving start from the point when it is synced to the latest slot, or does it...

@michaelsproul Thank you for your answers. > Did you resync from the 2^21-aligned snapshot? No, I just used `"--checkpoint-sync-url=https://beaconstate.ethstaker.cc"` and `"--reconstruct-historic-states"` options. How can I set 2^21-aligned snapshot? Which option...

@michaelsproul After "Downloading historical blocks" is completed, I still receive a NOT_FOUND response. Do I need to wait until "State reconstruction in progress slot: 6685184, remaining: 6480223" is also completed?

@michaelsproul Thank you for the answer! What should the state_lower_limit be set to? Also, is there a way to estimate how long the state reconstruction in progress will take?