test: verify x402 payments on Solana and EVM - #202
Merged
BitHighlander merged 2 commits intoJul 31, 2026
Conversation
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.
Purpose
Stage the protocol binding, client plumbing, and release evidence for hardware-verifiable x402 payments without publishing a package or merging a release branch.
Changes
5a8e2702a4cc5f6e6c401f9cbb9bb07b43828c8bmessages_solana_pb2.pywith repository-standard protoc 3.5.1TransferWithAuthorizationfixtureTransferChecked+ Memo fixtureFirmware treats recipient owners as untrusted candidates and displays one only after independently deriving its ATA and matching the signed destination.
Validation against the candidate firmware
0.002 USDCSOP
This PR targets the canonical
reconcile/upstream-syncstaging branch. It does not publish Python/device-protocol packages, merge firmware upstream, cut an RC, or release anything. The merged staging SHA will become the exact firmware submodule pin before the fork firmware PR is opened.