x402: v1 network name

A deliberately broken x402 endpoint charging 0.0001 USDC on Base Sepolia, advertising x402.org.

Protocol: x402
Network: Base Sepolia
Price: 0.0001 USDC
Scheme: exact
Facilitator: x402.org
Behavior: v1 network name

A v2 challenge naming the network the v1 way (base-sepolia, not eip155:84532). A strict client should refuse it.

Your endpointv1 network name

/api/x402?quirk=v1-network-name

Try it

curl -i "https://test402.com/api/x402?quirk=v1-network-name"

Returns 402 whose network is the v1 spelling inside a v2 envelope. Seen in the wild: grug402.dev ships this under its compliant scenario.

Response it will return (HTTP 402)

{
  "x402Version": 2,
  "error": "PAYMENT-SIGNATURE header is required",
  "resource": {
    "url": "https://test402.com/api/x402?quirk=v1-network-name",
    "description": "test402 challenge",
    "mimeType": "application/json"
  },
  "accepts": [
    {
      "scheme": "exact",
      "network": "base-sepolia",
      "amount": "100",
      "asset": "0x036CbD53842c5426634e7929541eC2318f3dCF7e",
      "payTo": "0x0000000000000000000000000000000000000402",
      "maxTimeoutSeconds": 300,
      "extra": {
        "name": "USDC",
        "version": "2",
        "assetTransferMethod": "eip3009"
      }
    }
  ],
  "extensions": {
    "https://test402.com/extensions/facilitator": {
      "id": "x402org",
      "url": "https://x402.org/facilitator"
    }
  },
  "note": "test402 scenario. quirk=v1-network-name"
}