Repository navigation
Release v4.15.1 follow-up x402 issue - #1041
Merged
Merged
Conversation
`x402 pay --max-raw-amount` without `--token`/`--asset` turned off the SDK spend controls (its $1 cap and its default-asset allowlist) and put a unitless raw cap in their place. A seller could then name any token, or the same stablecoin at another precision, under a cap sized for a different one, and the CLI would sign a Permit2 authorization for it. - Reject `--max-raw-amount` without `--token` or `--asset` in the pay schema (invalid_option), and again in selectMatching before anything is signed. - `x402 roundtrip --raw-amount` pins its payment to the asset its own paywall serves. - Spend-control hints no longer suggest an unpinned raw limit. - The pay result reports what the created payment pays in `data.payment` (asset, token, decimals, amount, rawAmount), taken from the requirement the SDK built the payment for; text output shows Amount and Asset.
Keep Codex/MCP config, the CodeGraph index and local security audit output out of the repository.
fix(ts): pin x402 raw payment limits to a token
zerodevblock-cyber
approved these changes
Oct 21, 2026
matrix-agent116
approved these changes
Oct 22, 2026
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.
x402 pay --max-raw-amountwithout--token/--assetturned off the SDK spend controls (its $1 cap and its default-asset allowlist) and put a unitless raw cap in their place. A seller could then name any token, or the same stablecoin at another precision, under a cap sized for a different one, and the CLI would sign a Permit2 authorization for it.--max-raw-amountwithout--tokenor--assetin the pay schema (invalid_option), and again in selectMatching before anything is signed.x402 roundtrip --raw-amountpins its payment to the asset its own paywall serves.data.payment(asset, token, decimals, amount, rawAmount), taken from the requirement the SDK built the payment for; text output shows Amount and Asset.