Fix critical bugs: viem checksum (#17) and spend-cap race condition (…#25
Merged
Conversation
) #17 — isAddress called with { strict: false } so non-checksummed addresses (including the mockPaymentFlow hardcoded demo address) pass validation. Strict checksum enforcement belongs at user-input boundaries, not inside the payment pathway where addresses arrive from trusted env/config. #22 — withSpendLock() serialises concurrent handle402Payment calls using a promise chain so the checkSpendLimit read and recordSpend write are never interleaved between two concurrent payments. Extracted _makePayment() so the locked critical section is explicit. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
AaronUppal-AI
requested review from
Cooldeepcode,
wd7zfpysvs-ui and
yogeshramchandani7
as code owners
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.
…#22)
#17 — isAddress called with { strict: false } so non-checksummed addresses (including the mockPaymentFlow hardcoded demo address) pass validation. Strict checksum enforcement belongs at user-input boundaries, not inside the payment pathway where addresses arrive from trusted env/config.
#22 — withSpendLock() serialises concurrent handle402Payment calls using a promise chain so the checkSpendLimit read and recordSpend write are never interleaved between two concurrent payments. Extracted _makePayment() so the locked critical section is explicit.
Summary
Describe the changes introduced by this PR.
Related issues
Checklist