You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
epoch/finder: use GetEpochInfo instead of GetSlot for authoritative epoch
Replace the slot-based epoch approximation with GetEpochInfo which
returns the authoritative epoch directly from the RPC. This fixes an
issue where a stale GetSlot(finalized) response caused the epoch finder
to return the wrong epoch for ~51 minutes after an epoch boundary,
leading to Account Not Found alerts on all circuits.
For recent targets (within the current epoch), the authoritative epoch
from GetEpochInfo is returned directly. For targets in prior epochs,
slot math is used as before but with the authoritative slot from
GetEpochInfo.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,8 @@ All notable changes to this project will be documented in this file.
11
11
- E2E Tests
12
12
- Add geoprobe E2E test (`TestE2E_GeoprobeDiscovery`) that exercises the full geolocation flow: deploy geolocation program, create probe onchain, start geoprobe-agent container, and verify the telemetry-agent discovers and measures the probe via TWAMP
13
13
- Add geoprobe Docker image, geolocation program build/deploy support, and manager geolocation CLI configuration to the E2E devnet infrastructure
14
+
- Tools
15
+
- Fix epoch finder returning wrong epoch for ~51 minutes after epoch boundaries by using `GetEpochInfo` (authoritative epoch) instead of approximating from `GetSlot` which was vulnerable to stale finalized slot responses ([#3227](https://github.com/malbeclabs/doublezero/pull/3227))
0 commit comments