x402 v2 #9
Description
https://www.x402.org/writing/x402-v2-launch
（以下这些我看了一遍，等咱们一起开会的时候再梳理成具体需求）
High-Impact V2 Upgrades for Copus
- Wallet-Based Sessions & Reusable Access (Biggest Win)
Current pain point: Users must sign and pay for every single article. This creates friction for heavy readers.
V2 enables:
- Sign-In-With-X (SIWx): User proves wallet ownership once, gets a session
- Subscription-like patterns: Pay once, access multiple articles for a period
- Skip repeat payment flows: If user already unlocked content, no re-signing needed
- Lower latency: No on-chain interaction for repeat access
Brainstorm ideas:
- "Unlock 10 articles for $X" bundle pricing
- Creator subscription tiers (pay creator monthly, access all their content)
- Session tokens that persist across browser sessions
- "Already unlocked" detection without hitting your API each time
- Header Migration (Breaking Change to Plan For)
Current: X-PAYMENT, X-PAYMENT-ASSET headers
V2 standard:
- PAYMENT-SIGNATURE (replaces X-PAYMENT)
- PAYMENT-REQUIRED (server response)
- PAYMENT-RESPONSE (payment confirmation)
- SIGN-IN-WITH-X (new identity header)
Action: Plan a migration path - your backend should accept both old and new headers during transition.
- Migrate to @x402/paywall Package
Current: 750+ lines of custom logic in x402Utils.ts, 1980 lines in Content.tsx
V2 offers:
- @x402/paywall - modular, maintained package with EVM and Solana support built-in
- Plugin architecture - add new chains without editing SDK internals
- Lifecycle hooks - inject custom logic (analytics, error handling, retry logic)
Benefits:
- Less code to maintain
- Automatic updates when x402 evolves
- Community-tested edge cases
- Dynamic payTo Routing (Revenue Split Opportunities)
Current: Single recipient per payment (your platform?)
V2 enables:
- Per-request routing to different addresses
- Callback-based payout logic
- Multi-recipient splits in a single payment
Brainstorm ideas:
- Creator royalties: 85% to creator, 15% to platform - handled at protocol level
- Referral rewards: If user came from a referral link, split payment 3 ways
- Tiered creator payouts: Top creators get better splits
- Dynamic pricing: Price based on content length, author tier, or demand
- CAIP Standards for Chain/Asset Identification
Current: Hardcoded chain IDs and contract addresses in contracts.ts
V2 uses CAIP (Chain Agnostic Improvement Proposals):
- Standardized format: eip155:8453/erc20:0x833589fcd6edb6e08f4c7c32d4f71b54bda02913
- Easier to add new chains without code changes
- Interoperable with other x402 services
- Automatic Discovery Extension
Current: Your payment endpoints are manually configured
V2 enables:
- Publish structured metadata about your x402 endpoints
- Facilitators auto-index your available content
- Pricing stays synchronized without manual updates
Use case: AI agents could automatically discover and pay for Copus content without hardcoded integration.
- Multi-Facilitator Support
Current: You handle payment verification yourself (or single facilitator)
V2 enables:
- Use multiple facilitators simultaneously
- SDK picks best match based on preferences
- Express preferences: "prefer Base", "only USDC", "avoid high-gas networks"
Benefit: Redundancy and better rates by letting SDK optimize.