Skip to content

Conversation

@chong-he
Copy link
Member

@chong-he chong-he commented Jul 1, 2025

Proposed Changes

The main change is adding a guide to partially reconstruct historic states to the FAQ.

Other changes:

@chong-he chong-he added ready-for-review The code is ready for review docs Documentation labels Jul 1, 2025
@chong-he chong-he requested a review from michaelsproul July 1, 2025 01:28
@mergify
Copy link

mergify bot commented Jul 1, 2025

Some required checks have failed. Could you please take a look @chong-he? 🙏

@mergify mergify bot added waiting-on-author The reviewer has suggested changes and awaits thier implementation. and removed ready-for-review The code is ready for review labels Jul 1, 2025
@mergify mergify bot added ready-for-review The code is ready for review and removed waiting-on-author The reviewer has suggested changes and awaits thier implementation. labels Jul 1, 2025
@mergify
Copy link

mergify bot commented Jul 7, 2025

This pull request has merge conflicts. Could you please resolve them @chong-he? 🙏

@mergify mergify bot added waiting-on-author The reviewer has suggested changes and awaits thier implementation. and removed ready-for-review The code is ready for review labels Jul 7, 2025
@mergify mergify bot added ready-for-review The code is ready for review and removed waiting-on-author The reviewer has suggested changes and awaits thier implementation. labels Jul 7, 2025
book/src/faq.md Outdated
"state_upper_limit": "10485760",
```

Lighthouse will now start to reconstruct the historic states from `slot 10485760`. At this point, if you do not want a full state reconstruction, you may remove the flag `--reconstruct-historic-states`. When the process is completed, you will have the state data from `slot 10485760`.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So if I'm understanding correctly, the flag --reconstruct-historic-states is only necessary here to "trick" the database into thinking it is going to perform state reconstruction and so doesn't prune states? Otherwise this is just effectively checkpoint syncing to an older state and then syncing forwards as normal (minus state pruning). Does that mean that over time you'd have to repeat these steps to control state db growth?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, once you sync like this your node keeps all states newer than the checkpoint. In practice it shouldn't be too bad, because state diffs are magic, but I guess users doing this are really interested in saving space. We could add a note along these lines?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If state pruning is already disabled with the flag --reconstruct-historic-states, how to prune states again? Is it done via the manual pruning steps?

So if saving space is a goal, then have to kind of do the manual state pruning from time to time? Because once --reconstruct-historic-state is used, automatic state pruning will not be active for the database from my understanding

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I added some text at the end here which just says to repeat the process

9c6327c

@chong-he
Copy link
Member Author

chong-he commented Jul 14, 2025

Updated the binary installation page 8076ca7 as Lighthouse now supports aarch-apple binary built since v7.1.0: lighthouse-v7.1.0-aarch64-apple-darwin.tar.gz in the release page: https://github.com/sigp/lighthouse/releases/tag/v7.1.0

@michaelsproul michaelsproul added ready-for-merge This PR is ready to merge. and removed ready-for-review The code is ready for review labels Jul 14, 2025
mergify bot added a commit that referenced this pull request Jul 14, 2025
mergify bot added a commit that referenced this pull request Jul 14, 2025
@mergify mergify bot merged commit 6409a32 into sigp:unstable Jul 14, 2025
34 checks passed
@chong-he chong-he deleted the book-faq branch July 14, 2025 03:26
danielrachi1 pushed a commit to danielrachi1/lighthouse that referenced this pull request Jul 18, 2025
…ok (sigp#7679)

The main change is adding a guide to partially reconstruct historic states to the FAQ.

Other changes:
- Update the database scheme info
- Delete the Homebrew issue as it has been solved in Homebrew/homebrew-core#225877
- Update default gas limit in: [7cbf7f1](sigp@7cbf7f1)
- Updated the binary installation page [8076ca7](sigp@8076ca7) as Lighthouse now supports aarch-apple binary built since v7.1.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs Documentation ready-for-merge This PR is ready to merge.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants