Eitan Seri-Levi 5d0f8a083a Ensure custody backfill sync couples all responses before importing (#8339) ...

Custody backfill sync has a bug when we request columns from more than one peer per batch. The fix here ensures we wait for all requests to be completed before performing verification and importing the responses.

I've also added an endpoint `lighthouse/custody/backfill` that resets a nodes earliest available data column to the current epoch so that custody backfill can be triggered. This endpoint is needed to rescue any nodes that may have missing columns due to the custody backfill sync bug without requiring a full re-sync.


  


Co-Authored-By: Eitan Seri- Levi <eserilev@gmail.com>

Co-Authored-By: Eitan Seri-Levi <eserilev@ucsc.edu>

Co-Authored-By: Jimmy Chen <jchen.tc@gmail.com>

Co-Authored-By: Michael Sproul <michaelsproul@users.noreply.github.com>

2025-11-03 08:06:06 +00:00

..

src

Ensure custody backfill sync couples all responses before importing (#8339)

2025-11-03 08:06:06 +00:00

tests

Ensure custody backfill sync couples all responses before importing (#8339)

2025-11-03 08:06:06 +00:00

Cargo.toml

Create network_utils crate (#7761)

2025-09-10 12:59:24 +00:00