Fix Lighthouse v8.1.0 SSE race condition and reward calculation bugs

[Zyra-V21]

Summary

This PR merges all recent dev changes into master, addressing two main areas:

Lighthouse v8.1.0 SSE timing fix

Lighthouse v8.1.0 (commit cd8049a69) emits the Head SSE event before the block and state are fully committed. This causes GotEth to fetch stale data when following the chain head, resulting in f_proposed=false, f_timestamp=0, and f_attestations=0 for affected epochs.

Changes:

• Cache state root from Head SSE events and use root-based state lookup with retry at epoch boundaries (8e21b77, f5db50c, 0e35d96, ecaa493, 8a7ba8e, 5e995b9)
• Retry block downloads on 404 instead of immediately marking blocks as missing (66d1730)

Validated on a test machine running Lighthouse v8.1.0 + GotEth against mainnet: all blocks correctly show f_proposed=true with proper f_timestamp and f_attestations values after applying the fix.

Reward calculation and overflow fixes

These commits were merged to dev prior to the Lighthouse fix and address several issues found in reward/fee calculations:

• eba4883 — fix: use NextState for consolidated amounts in EpochReward calculation
  Consolidated validator balances were being read from the current state instead of the next state. Since consolidations take effect at the start of the next epoch, the amounts must be sourced from NextState to reflect the actual post-consolidation balances.

• d74d19b — fix: change aggregated_rewards from UInt64 to Int64 in t_pool_summary
  Aggregated rewards can be negative (e.g. penalties exceeding rewards in a given epoch). The column type was UInt64 which caused underflow wrapping negative sums to huge values near 2^64.

• 63bb131 — chore: add math import for overflow protection in BlockGasFees
  Adds the math package import required by the overflow protection logic.

• 51f6713 — fix: add overflow protection in BlockGasFees calculation
  Large gas prices or unusual fee values could cause uint64 overflow when computing (gasPrice - baseFee) * gasUsed, corrupting EL fee data. Added validation that gasPrice >= baseFee, a cap on maximum reasonable transaction fee, and overflow checks before accumulating totals.

• 563ad4c — fix: adjust maxReasonableTxFee to fit uint64 range
  The initial maxReasonableTxFee constant exceeded uint64 range. Adjusted to ~184 ETH which still catches anomalous fees while fitting within bounds.

• ab95a42 — fix: correct consolidation timing in EpochReward calculation
  Consolidations are processed at the start of the epoch, not at the end. The reward calculation was applying consolidation adjustments at the wrong point, causing incorrect balance diffs for validators involved in consolidations.

• 1aa0a77 — fix: prevent double-counting consolidations in reward calculation
  When a source validator consolidates into a target, both the source's balance decrease and the target's balance increase were being counted separately. This fix ensures consolidation transfers are only accounted for once.

• 5461500 — fix: add deposit tracking for reward calculation and fix bounds check
  External deposits were not being subtracted from the balance diff, causing deposited ETH to appear as earned rewards. Added processDepositsForRewardCalculation() to filter external deposits. Also fixed an array bounds check.

Closes

• Closes Lighthouse v8.1.0 Head SSE timing can cause GotEth to fetch inconsistent epoch-boundary states (incorrect f_proposed, f_timestamp, f_attestations) #220 — Lighthouse v8.1.0 Head SSE timing can cause GotEth to fetch inconsistent epoch-boundary states
  Fixed by caching the state root from Head SSE events and using root-based state lookup with retry (8e21b77, f5db50c, 0e35d96, ecaa493, 8a7ba8e, 5e995b9), plus retrying block downloads on 404 (66d1730).

• Closes f_reward Inflated by Consolidated Amounts (Post-Electra Validators) #215 — f_reward Inflated by Consolidated Amounts (Post-Electra Validators)
  Fixed by correcting consolidation timing (ab95a42), preventing double-counting (1aa0a77), and using NextState for consolidated amounts (eba4883).

• Closes UInt64 Underflow in t_pool_summary.aggregated_rewards #214 — UInt64 Underflow in t_pool_summary.aggregated_rewards
  Fixed by changing aggregated_rewards from UInt64 to Int64 (d74d19b), allowing negative reward sums without underflow.

• Closes Dashboards missing Execution Layer rewards and APR #212 — Dashboards missing Execution Layer rewards and APR
  Fixed by adding overflow protection in BlockGasFees (51f6713, 563ad4c) which was producing corrupted EL fee data, and adding deposit tracking (5461500) so reward calculations correctly separate deposits from earned rewards.

Files changed

File	Change
pkg/analyzer/chain_analyzer.go	Add epochBoundaryStateRoots sync.Map
pkg/analyzer/epoch_boundary_state_root.go	New: cache helpers for epoch boundary state roots
pkg/analyzer/download.go	Root-based state download with retry
pkg/analyzer/routines.go	Cache state root from Head SSE events
pkg/clientapi/block.go	Retry block download on 404
pkg/clientapi/state.go	Add RequestBeaconStateByRoot
pkg/spec/block.go	Overflow protection in BlockGasFees
pkg/spec/metrics/standard.go	Bounds check for deposits
pkg/spec/metrics/state_electra.go	Consolidation/deposit processing
pkg/db/migrations/000001_init_schema.up.sql	Int64 for aggregated_rewards

Testing

• Reproduced the bug: GotEth + Lighthouse v8.1.0 → all head-mode blocks incorrectly marked as f_proposed=false
• Verified fix: same setup → all blocks correctly marked as f_proposed=true with valid metrics
• Backwards compatible with Lighthouse v8.0.1 (slot-based fallback remains for non-cached states)
• Goteth changes has been tested during months in testing site without any anomaly. --OK

Breaking Changes

None. Internal behavior change only.

[leobago]

LGTM