Files
lighthouse/beacon_node/http_api
Michael Sproul 1587f1e1d2 Optimisations relating to get_expected_withdrawals (#9314)
Tweaking/optimising `get_expected_withdrawals` on the pre-Gloas path, after the removal of some optimisations in:

- https://github.com/sigp/lighthouse/pull/9102


  - Remove `prepare_beacon_proposer` calls from `register_validator`. These calls were: heavily duplicated, happening _too early_ (at the start of the slot before the block arrived), expensive on epoch boundaries (forcing an early epoch transition), _and_ unnecessary. They are completely safe to remove because the scheduled proposer preparation routine exists.
- Instrument `get_expected_withdrawals`/`prepare_beacon_proposer` to find more unexpected callers.


Co-Authored-By: Michael Sproul <michael@sigmaprime.io>

Co-Authored-By: Tan Chee Keong <tanck@sigmaprime.io>

Co-Authored-By: Michael Sproul <michaelsproul@users.noreply.github.com>
2026-07-02 07:10:40 +00:00
..