v5.3.2

Nuthatch 5.3.2 makes an address-history nest's first backfill finish in minutes over a hosted RPC,
and stops it reading every block body for accounts nobody asked about. Nothing outside an
[address_history] nest changes. There is no storage migration.

Fixes

• A backfill over a remote RPC no longer crawls. Each window's checks cost about 2.3 s over
  Alchemy whatever the window's size, more than a quarter of the default 8 s request deadline, so the
  pacer halved the window to its 64-block floor and kept it there. One year of one wallet was heading
  for 12 hours. The pacer now tells a window's fixed cost from its per-block cost and lets the window
  grow past it, never past the request deadline. The same wallet, 1.19 million blocks, now backfills
  in about 20 minutes with 7,324 RPC calls.
• Block bodies are read only for an account that was asked about. After discovery the nest read
  one body a block for every watched account, to find withdrawals and produced blocks. rotki asks for
  those only by a tracked validator's withdrawal address, so an ordinary wallet paid for a scan of
  hours and about a million calls it would never use. An account now joins the background body scan
  once a request has asked for its withdrawals or produced blocks. One that already holds body
  coverage keeps it, and with validators and a beacon node configured the scan stays whole.

Security

• rustls 0.23.46. Clears RUSTSEC-2026-0346 to 0349, published 2026-10-14 against 0.23.45: TLS
  secrets in Debug output, data sent to the outer server after an ECH rejection, an unbounded
  certificate decompression, and a key-exchange downgrade.

Gated on Lodestar's data

Every change is in the address-history path, which no production nest declares, so this release
changes no query path the release gate measures.

Compatibility and upgrade

Replace the binary and restart. A 5.3.1 store is used as it is. The table of asked accounts is
created on open.