Fix payee attestation on settled payment transitions - #348
Closed
cursor[bot] wants to merge 2 commits into
Closed
cursor[bot] wants to merge 2 commits into
cursor[bot] wants to merge 2 commits 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 |
Co-authored-by: SiriusBig <webiumsk@users.noreply.github.com>
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
Lightning payment rows can first be written while BTCPay still reports them as
Processing, then later update toSettledunder the same payment identity. The previous attestation gate only ran on newly created ledger rows, so the settled transition could skip payee attestation entirely. If the early row had no usable BOLT11 destination, a later settled payment to an unknown node would not raise the wallet-security incident; with no canary allow-list, an unsettled payment could also seed trust too early.Root cause
SettlementLedgerService::syncPaymentMethod()invokedPayeeAttestationServicebased only on$row->wasRecentlyCreated, without requiring the payment to be settled or considering an existing row whosepayment_statuschanged toSettled.Fix
payment_statustransitions toSettled.Validation
APP_KEY=base64:AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA= BTCPAY_BASE_URL=https://btcpay.example.com BTCPAY_API_KEY=dummy php artisan test --filter=PayeeAttestationTestphp -l app/Services/Boltz/SettlementLedgerService.phpphp -l tests/Feature/PayeeAttestationTest.phpgit diff --checkNote: Docker and graphify metadata were unavailable in this runner, so validation used the local PHP fallback and
graphify update .was skipped.