Repository navigation
fix(x402): share global network aliases for provider filters - #1014
Closed
boboliu-1010 wants to merge 1 commit into
Closed
boboliu-1010 wants to merge 1 commit into
boboliu-1010 wants to merge 1 commit into
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.
Summary
x402 provider-list --network sepoliaand--network tron:mainnetwere rejected because provider filtering maintained a separate, incomplete alias table. Resolve aliases through the shared NetworkRegistry in X402Service, including configured aliases, and pass canonical IDs to the catalog adapter.Explicit canonical IDs remain usable without local RPC configuration. A valid network absent from the catalog returns an empty list; omitting the filter continues to list providers across networks. Update the option help and remove the duplicate alias table.
This PR targets release_v4.14.0 independently of #1013 and contains no documentation changes. Both PRs touch nearby code, so the remaining PR may need rebasing after either merges.
Validation