feat: add organization residency tagging and residency-aware read DB …#611
Open
Chrisland58 wants to merge 1 commit into
Open
feat: add organization residency tagging and residency-aware read DB …#611Chrisland58 wants to merge 1 commit into
Chrisland58 wants to merge 1 commit into
Conversation
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
1 participant
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.
Implemented canonical Soroban event idempotency by deriving a stable event_key from txHash:ledger:eventIndex.
Added a Knex migration to extend processed_events with event_key text unique not null
Backfilled existing rows when possible from current event metadata
Updated eventParser.ts to derive eventKey from Soroban event payload
Updated eventProcessor.ts to use eventKey for duplicate detection and persistence
Added
src/tests/eventProcessor.idempotency.test.ts to verify canonical key generation, duplicate rejection, and storage
Updated event-processing.md to document the new event key contract and idempotency behavior
This makes retry handling safe and deterministic by enforcing uniqueness on the canonical event key rather than relying on weaker or inconsistent event identity fields.
closes #470