v5.3.3

Nuthatch 5.3.3 lets an address-history backfill grow its windows over an RPC whose calls are slow
whatever their range, and replaces a Polygon default endpoint that stopped serving logs. Nothing
outside an [address_history] nest changes, apart from that one default. There is no storage
migration.

Fixes

• A backfill over a slow RPC no longer stays at its smallest window. 5.3.2 let the pacer's target
  rise to three times a window's fixed cost, but still grew a window only when the whole window took
  under half that target. Over GraphOps, three eth_getLogs at about 1.5 s each put 4.5 s on every
  window, more than half the 8 s deadline, so windows stayed at 64 blocks: one wallet's year of
  history was heading for 14 hours. Growth is now judged on the per-block part of a window's time.
  The same wallet, with GraphOps for the plain calls and Alchemy for traces, backfilled 1.19 million
  blocks in 48 minutes (#2046).
• Polygon's second default RPC is Tenderly's gateway. polygon-bor-rpc.publicnode.com failed even
  a 10-block eth_getLogs a few thousand blocks behind the tip; polygon.gateway.tenderly.co serves
  archive state and a 163,840-block window (#2041).

Gated on Lodestar's data

The pacer change is in the address-history path, which no production nest declares, and the Polygon
default changes no query path the release gate measures.

Compatibility and upgrade

Replace the binary and restart. A 5.3.2 store is used as it is. A nest that names its own Polygon
rpc_urls is unaffected by the default change.