v2.5.0
v2.5.0
- x402 v2 payment requirements are read correctly: amount from the v2 amount field and resource from the top-level resource object, in addition to the v1 fields. The version is taken from x402Version, or inferred when absent; payloads whose version conflicts with their fields are rejected.
- The signed payment returned for a v2 request now uses the v2 PAYMENT-SIGNATURE shape — an accepted block (including extra) and a top-level resource — so resource servers can verify it. v1 requests keep the flat v1 shape.
- Payment skill examples updated to x402 v2 (v1 still supported).