fix(security): attest settled payments when destination appears - #351
Draft
cursor[bot] wants to merge 1 commit into
Draft
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 could enter the local settlement ledger as
Settledbefore BTCPay exposed a usable BOLT11 destination. The first sync skipped payee attestation because there was no invoice to decode, and later syncs did not retry because the payment status stayedSettled. That let a payment to an unexpected Lightning node avoid the wallet payee mismatch incident path.Root cause
SettlementLedgerService::shouldAttestPayment()retried attestation only for newly-created rows orpayment_statuschanges. It did not treat the first appearance of a destination on an already-settled row as an attestation-worthy transition.Fix
Settledpayment whose destination appears on a later sync.Validation
APP_KEY=$(php -r 'echo "base64:".base64_encode(random_bytes(32));') BTCPAY_BASE_URL=https://btcpay.test BTCPAY_API_KEY=test php artisan test --filter=PayeeAttestationTestgit diff --checkNote: Docker and graphify were not available in this runner (
docker: command not found,graphify: command not found), so validation used local PHP dependencies with dummy test env values.