lidofinance/lido-keys-api 5.0.0

on GitHub

Bug Fixes

• 4.0.5 (1b41615)

• 5.0.0 (89d68bd)

• number | null totalWithdrawnKeys in schema (e552b4e)

• operator data refresh (a275350)

• STC-885: serialize concurrent writers with Postgres advisory locks (98bfcd5)

• tests (afcd58b)

• throttler getTracker via cf-connecting-ip (bb4cf72)

• totalWithdrawnKeys to csm module too (72ce391)

• totalWithdrawnKeys to other endpoints (4a9fa5c)

• v2 compounding operators endpoint (bd8abde)

• validators endpoint filter fix & execution provider update (d3201e3)

• feat!: adapt the CL block snapshot to Glamsterdam (EIP-7732) (5596725)

Features

• Cache-Control headers on public GETs, no-store on probes and metrics (ac079a7)
• identify outgoing EL and CL traffic with app User-Agent (d00ced4)
• masked effective-config dump at startup, redact env-validation errors (140c574)
• read build-info.json and label build_info with commit and branch (90679fd)
• readiness endpoint gated on the first meta row, mask every secrets-file value (4dd1ab0)

BREAKING CHANGES

• the meaning of the execution layer fields of
  clBlockSnapshot changes at the Glamsterdam fork. timestamp becomes
  the time of payloadSlot, and blockNumber and blockHash can repeat
  across snapshots. A consumer that reads timestamp as the time of the
  slot, or a new blockNumber as the sign of a new snapshot, has to be
  changed. The new payloadSlot field itself is additive.

Co-Authored-By: Claude Opus 5 noreply@anthropic.com