v4.15.1

Nuthatch 4.15.1 fixes one wrong answer in the GraphQL surface of the graph build: a filter on a
Bytes field with a checksummed address matched nothing. It is 4.15.0 plus that fix. A default build
behaves exactly as 4.15.0 does.

A checksummed address now matches

graph-node decodes a Bytes input as hex, so its case means nothing there, and a nest stores hex in
lower case. Compared as text, cards(where: { owner: "0xFeBD…" }) with the mixed-case address a
wallet hands an app returned an empty list instead of the owner's rows: a wrong answer with no error.

Filter values on a Bytes field, or on a reference to an entity whose id is Bytes, are now lowercased
before they reach SQL, for equality, _in lists and _contains. A singular lookup by a Bytes id is
treated the same way. String and ID values keep their case (#1992).

Found on the subgraph stopgap for openloom-bsc (nightswatchhq/graph-support#53), which has run this
fix since 2026-10-08.

Gated on Lodestar's data

The change is confined to how a GraphQL filter value is written into SQL in a graph build. No query
path of a default build, and nothing the release gate measures, is touched.

Compatibility and upgrade

Replace the binary and restart. No re-index and no configuration change.