WDK Docs

Migration Guide

Migrate from USDC-only EIP-3009 integration to WDK + USDT0 routing with zero downtime.

⌘KCommand-palette first navJump:QuickstartAPIErrorsMigrationSecurity

Phase 0: Baseline audit

  • Inventory all callers using USDC-only assumptions (asset defaults, decimal math, domain constants).
  • Record existing success/failure metrics for current settle flow (latency, failed signatures, retries).

Phase 1: Backward-compatible API expansion

  • Add additive settle fields: quoteId, routeId, client, authType.
  • Ship /api/v1/liquidity/quote without breaking existing /api/v1/router/settle clients.

Phase 2: SDK adapter migration

  • Implement signer abstraction (wagmi + wdk) while keeping old SDK methods operational.
  • Gate WDK mode behind feature flag and collect telemetry from early integrators.

Phase 3: Route-aware UI rollout

  • Replace token-only selector with token+route cards in payment surfaces.
  • Expose route and receipt metadata for supportability and trust.

Upstream lock checklist (release blocker)

  • Finalize WDK API mapping doc with links to exact upstream sections used.
  • Confirm fallback behavior for AI-agent signer flows matches official guidance.
  • Document any divergence between P402 adapter behavior and upstream examples.
  • Publish verification date and owner for ongoing maintenance cadence.

Compatibility contract

  • Legacy settle payloads remain valid until an announced deprecation window.
  • New fields are optional and additive.
  • Clients can progressively adopt quote routing and WDK signing without full rewrite.