Repository navigation
fix(monitor): watch multi-seller wallets with per-account cursors and postgres leader lease (#582) - #591
Open
mumusama75 wants to merge 1 commit into
Conversation
… postgres leader lease (Quittance-Labs#582)
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.
Resolves #582
Context & Summary
Previously, PaymentMonitorService only polled a single seller account (SELLER_PUBLIC_KEY). In wallet-scoped deployments without SELLER_PUBLIC_KEY, the payment monitor remained disabled, requiring explicit verify calls to move invoices to PAID. Furthermore, server-dual.ts wired a FilePaymentMonitorCheckpointStore even in Postgres mode, �alidateStellarConfig demanded SELLER_SECRET_KEY for watch-only monitoring, and POST /api/payment/sync was unauthenticated.
This PR implements multi-seller wallet monitoring with durable per-account cursors, fair round-robin budgeting, creation-aligned cursor bootstrapping, PostgreSQL advisory lock leader leasing across replicas, operator token protection, and 100% test coverage.
Key Changes