fix(x402): migrate CDP bazaar path to x402 protocol v2#270
Merged
Conversation
CDP indexer stopped picking up v1 (outputSchema) entries — verified by 3
successful v1 settlements on Base mainnet + Base Sepolia that never
appeared in /discovery/merchant after 15+ minutes. All entries CDP
indexed today are x402Version: 2 with extensions.bazaar at the top
level of PaymentRequired. The v1 ranking in CDP appears deprecated in
practice.
Types and wire format taken directly from
@x402/core/src/types/payments.ts so the shape matches what CDP's
facilitator expects:
- paymentRequirements.amount (was maxAmountRequired in v1)
- paymentRequirements.network CAIP-2 "eip155:8453"
- paymentPayload.accepted (chosen requirement, v2-only)
- PaymentRequired.resource ResourceInfo object {url, ...}
- PaymentRequired.extensions.bazaar top-level, not on accepts[]
PayAI path is untouched and stays on v1, which is what
facilitator.payai.network currently indexes (PolyPay listing is live
there). The same EIP-3009 signature works across versions, so the
bootstrap script and the UI keep sending v1 X-PAYMENT; only the CDP
forwarding step translates to v2.
Refs #259
Huygon764
added a commit
that referenced
this pull request
May 18, 2026
CDP indexer stopped picking up v1 (outputSchema) entries — verified by 3
successful v1 settlements on Base mainnet + Base Sepolia that never
appeared in /discovery/merchant after 15+ minutes. All entries CDP
indexed today are x402Version: 2 with extensions.bazaar at the top
level of PaymentRequired. The v1 ranking in CDP appears deprecated in
practice.
Types and wire format taken directly from
@x402/core/src/types/payments.ts so the shape matches what CDP's
facilitator expects:
- paymentRequirements.amount (was maxAmountRequired in v1)
- paymentRequirements.network CAIP-2 "eip155:8453"
- paymentPayload.accepted (chosen requirement, v2-only)
- PaymentRequired.resource ResourceInfo object {url, ...}
- PaymentRequired.extensions.bazaar top-level, not on accepts[]
PayAI path is untouched and stays on v1, which is what
facilitator.payai.network currently indexes (PolyPay listing is live
there). The same EIP-3009 signature works across versions, so the
bootstrap script and the UI keep sending v1 X-PAYMENT; only the CDP
forwarding step translates to v2.
Refs #259
Huygon764
added a commit
that referenced
this pull request
May 18, 2026
* fix(x402): migrate CDP bazaar path to x402 protocol v2 (#270) CDP indexer stopped picking up v1 (outputSchema) entries — verified by 3 successful v1 settlements on Base mainnet + Base Sepolia that never appeared in /discovery/merchant after 15+ minutes. All entries CDP indexed today are x402Version: 2 with extensions.bazaar at the top level of PaymentRequired. The v1 ranking in CDP appears deprecated in practice. Types and wire format taken directly from @x402/core/src/types/payments.ts so the shape matches what CDP's facilitator expects: - paymentRequirements.amount (was maxAmountRequired in v1) - paymentRequirements.network CAIP-2 "eip155:8453" - paymentPayload.accepted (chosen requirement, v2-only) - PaymentRequired.resource ResourceInfo object {url, ...} - PaymentRequired.extensions.bazaar top-level, not on accepts[] PayAI path is untouched and stays on v1, which is what facilitator.payai.network currently indexes (PolyPay listing is live there). The same EIP-3009 signature works across versions, so the bootstrap script and the UI keep sending v1 X-PAYMENT; only the CDP forwarding step translates to v2.
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.
Migrate to v2