Pratik Mankawde 7d875c0e76 refactor(telemetry): name the unit and epoch in the close-time span attrs ...

The three close-time span attributes hold NetClock readings, which are whole
seconds since the XRP Ledger epoch of 2000-01-01 rather than the Unix epoch.
Neither the unit nor the epoch was recoverable from the key, so a consumer
rendering one as a wall-clock time without first adding the epoch offset lands
roughly thirty years early. The sibling close_resolution_ms already named its
unit, so the header disagreed with itself.

  close_time        -> close_time_ripple_epoch_s
  parent_close_time -> parent_close_time_ripple_epoch_s
  close_time_self   -> close_time_self_ripple_epoch_s

Emitted values do not change; only the keys do. The public RPC response fields
of the same name are deliberately untouched, as renaming those would break the
ledger API.

2026-09-02 15:30:13 +01:00

..

xrpl

refactor(telemetry): name the unit and epoch in the close-time span attrs

2026-09-02 15:30:13 +01:00