N esplora backends behind one backend-shaped surface, rotating per request.
The genealogy walk spends thousands of requests on one build, so a failure
partway through used to discard everything walked so far: fetchSatIdentity
looped over backends and restarted the walk from the reveal. Here a failing
request rotates to the next member and retries THAT REQUEST, so the walk
keeps its progress and only the request is repeated. A request fails when
every member has failed it.
The starting member rotates per request so load spreads instead of always
landing on member 0, and usedBaseUrls records every member that actually
served bytes, which is what header anchoring must exclude from its vote.
N esplora backends behind one backend-shaped surface, rotating per request.
The genealogy walk spends thousands of requests on one build, so a failure partway through used to discard everything walked so far: fetchSatIdentity looped over backends and restarted the walk from the reveal. Here a failing request rotates to the next member and retries THAT REQUEST, so the walk keeps its progress and only the request is repeated. A request fails when every member has failed it.
The starting member rotates per request so load spreads instead of always landing on member 0, and
usedBaseUrlsrecords every member that actually served bytes, which is what header anchoring must exclude from its vote.