Repository navigation
feat(indexer): reorg-aware event ingestion with ledger rollback (#724) - #1184
Merged
Chucks1093 merged 3 commits intoOct 22, 2026
Merged
Conversation
…sslayerorg#724) Detect Stellar ledger rollbacks by anchoring every ingested ledger and event to its hash (LedgerCheckpoint + new IngestedEvent table), walk back to the fork point on a previousLedgerHash mismatch, reverse all affected database side effects in one atomic transaction, emit a warn log with the fork point and affected counts, re-ingest the canonical chain from the fork point, and gate buy/sell confirmations on confirmed ledger depth >= 2. 🤖 Generated with Codebuff Co-Authored-By: Codebuff <noreply@codebuff.com>
|
@DanbabaJr 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! 🚀 |
…rorg#724) Bring the branch up to date with main so the new ledger-depth gate and checkpoint model are validated against main's invoice-protocol suite. 🤖 Generated with Codebuff Co-Authored-By: Codebuff <noreply@codebuff.com>
The accesslayerorg#724 ledger-depth gate reads latestLedger from getTransaction, which a real Soroban node always returns. The invoice-protocol integration stub omitted it, so every buy/sell waited out the full 120s poll budget and CI timed out; report a head two ledgers past inclusion instead. 🤖 Generated with Codebuff Co-Authored-By: Codebuff <noreply@codebuff.com>
6 tasks
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.
PR: Implement Reorg-Aware Stellar Event Ingestion Pipeline
Closes #724
Summary
Implements a reorg-aware Stellar event ingestion pipeline that detects ledger rollbacks, identifies fork points, and restores database consistency before re-ingesting affected events.
Changes
Testing
Expected Outcome
The ingestion pipeline now handles Stellar ledger reorganizations safely, prevents stale event data from affecting application state, and reduces exposure to unconfirmed ledger changes.