Security Considerations

  • MEV / Slippage: Quotes must include deadlineTs & maxSlippageBps. Merchants enforce bounds at receipt verification.

  • Replay: Receipts bind offerId + quoteId; merchants maintain short‑lived offer windows and idempotency keys.

  • Tampering: RouteQuote is signed; merchants verify signature against known facilitator keys or a staked registry.

  • Phishing: Wallets should display payTo, assetOut, amountOut, and deadlineTs prominently.

  • Partial Fill: Either disallowed (default) or opt‑in where receipts encode partials plus PoD for delivered bytes.

  • Privacy: Payer address visible in v0.1; future zk‑receipt mode can hide it while proving constraints.

PreviousError Codes & Failure ModesNextIntegration with x402 Headers

Last updated