feat: add indexer lag guard to prevent broken UX during testnet insta…#537
Merged
Merged
Conversation
|
@fadee26 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Cedarich
approved these changes
Jun 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Indexer Lag Guard
Prevent broken UX during testnet instability by detecting Soroban indexer lag and automatically disabling risky write flows when the system is too far behind.
Features:
INDEXER_LAG_THRESHOLD_LEDGERSenv var, default: 100)@RequiresIndexerLagCheck()to mark endpoints that should be blocked when lag is too highINDEXER_LAGGINGtelling clients to retry laterINDEXER_LAG_GUARD_OVERRIDE=trueenv var)Acceptance Criteria:
✅ When lag exceeds threshold, risky flows are blocked consistently
✅ Read‑only endpoints remain available
✅ Operators can observe lag and overrides via metrics/logs
closes #534