Fix payee attestation on settlement transition - #347
Closed
cursor[bot] wants to merge 1 commit into
Closed
cursor[bot] wants to merge 1 commit into
cursor[bot] wants to merge 1 commit into
Conversation
Co-authored-by: SiriusBig <webiumsk@users.noreply.github.com>
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Bug and impact
A Lightning payment can arrive in BTCPay as
ProcessingonInvoiceReceivedPayment, which creates a localstore_settlementsrow before the payment is final. When the laterInvoicePaymentSettled/InvoiceSettledwebhook updates that same payment row toSettled, payee attestation did not run because it was tied towasRecentlyCreatedonly. That left a concrete security blind spot where a payment signed by an unknown Lightning node could settle without raising a wallet security incident.Root cause
SettlementLedgerService::syncPaymentMethod()upserts BTCPay payment rows for all positive-value payments, including non-settled states, but only calledPayeeAttestationServicewhen the ledger row was first inserted.Fix
The ledger now records the previous settlement status before the upsert and runs payee attestation when a Lightning payment is first observed as
Settled, whether that is on insert or on a later status transition.Validation
php artisan test --filter=PayeeAttestationTestphp artisan test --filter=StoreSettlementTest./vendor/bin/pint --test app/Services/Boltz/SettlementLedgerService.php tests/Feature/PayeeAttestationTest.phpNote: local PHPUnit emitted existing environment warnings for a missing Vite manifest and one deprecated doc-comment metadata annotation, but all assertions passed.