Skip to content

Comments

Back merge release-v7.0.0.beta.4 to unstable#7194

Merged
michaelsproul merged 17 commits intosigp:unstablefrom
eserilev:backmerge
Mar 23, 2025
Merged

Back merge release-v7.0.0.beta.4 to unstable#7194
michaelsproul merged 17 commits intosigp:unstablefrom
eserilev:backmerge

Conversation

@eserilev
Copy link
Member

Issue Addressed

#7179

Proposed Changes

Back merge release-v7.0.0.beta.4 to unstable

michaelsproul and others added 16 commits March 10, 2025 04:51
This is a backport from `holesky-rescue`.

Part of:

- sigp#7039

Original PR to `holesky-rescue`:

- sigp#7054


  Avoid doing database lookups for slots that lie in the hot database when processing status messages. This avoids a DoS vector during non-finality, as loading hot states to iterate block roots is very expensive.
Cherry-picking sigp#7055 from `holesky-rescue` branch to the clean `release-v7.0.0` branch.
Partially sigp#7100


  Set blob pruning to default to once per day
Resolves sigp#7091


  The `prometheus` crate pulls in `protobuf 2.x` which fails cargo audit. We actually dont use any `protobuf` related features in LH. By disabling default features for `prometheus`, we no longer pull in the `protobuf` crate
…g_partial_withdrawals) (sigp#7006)

Resolves sigp#7003


  Added two endpoints as ethereum/beacon-APIs#500 proposed:
- `/eth/v1/beacon/states/{state_id}/pending_deposits`
- `/eth/v1/beacon/states/{state_id}/pending_partial_withdrawals`
Backport of:

- sigp#7067

For:

- sigp#7039


  - Prevent writing to state cache when migrating the database
- Add `state-cache-headroom` flag to control pruning
- Prune old epoch boundary states ahead of mid-epoch states
- Never prune head block's state
- Avoid caching ancestor states unless they are on an epoch boundary
- Log when states enter/exit the cache

Co-authored-by: Eitan Seri-Levi <eserilev@ucsc.edu>
Hardcode config for the upcoming `hoodi` testnet so we can run with `--network hoodi`.
This is a backport of:
-  sigp#7059
- sigp#7071

For:
- sigp#7039


  Introduce a new lighthouse endpoint that allows a user to force a pseudo finalization. This migrates data to the freezer db and prunes sidechains which may help reduce disk space issues on non finalized networks like Holesky

We also ban peers that send us blocks that conflict with the manually finalized checkpoint.

There were some CI fixes in sigp#7071 that I tried including here

Co-authored with: @jimmygchen  @pawanjay176 @michaelsproul
Backports:
- sigp#7072

To:
- sigp#7039

sigp#7103 should be merged first


  This PR introduces an endpoint that allows users to manually trigger background compaction.
Cross builds were failing since:

- sigp#7086

This seems to have been due to a regression upstream in `ring` which is noted in the v0.17.14 release notes. I'm hoping that updating remedies it.

> Compatibility with GNU binutils 2.29 (used on Amazon Linux 2), and probably even earlier versions, was restored. It is expected that ring 0.17.14 will build on all the systems that 0.17.12 would build on.

https://github.com/briansmith/ring/blob/main/RELEASES.md#version-01714-2025-03-11
New release for Hoodi testnet including clean versions of fixes from `holesky-rescue`.
@eserilev eserilev requested a review from jxs as a code owner March 23, 2025 17:11
@eserilev
Copy link
Member Author

@michaelsproul I've tested git checkout unstable; git merge --ff-only backmerge; git push origin unstable on my lighthouse fork, seems to work just fine. I'm just a bit nervous to do it for real without a second set of eyes 😅

@eserilev eserilev linked an issue Mar 23, 2025 that may be closed by this pull request
@michaelsproul
Copy link
Member

I'll have a review of this and then merge it, thanks!

Copy link
Member

@michaelsproul michaelsproul left a comment

Choose a reason for hiding this comment

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

Looks good. I'll just squash the last few commits

@michaelsproul michaelsproul merged commit 2f37bf4 into sigp:unstable Mar 23, 2025
28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Back merge v7.0.0-beta.4 to unstable

4 participants